Newsletter: sign-ups and sending.

The Newsletter feature adds the Newsletter sign-up element.

1. A visitor enters an e-mail address.
2. Kaleta sends a confirmation link (double opt-in).
3. After the click, the address appears in Content → Newsletters → Subscribers.

Send newsletters from Kaleta

Content → Newsletters sends your latest news to confirmed subscribers. There is no e-mail builder to learn: one template follows your site appearance – colours, fonts, corner radius and logo – and holds:

• a subject and a preview text shown in the inbox,
• an introduction (plain text; web addresses become links),
• the latest news items at the time of sending, chosen ones, or none,
• an optional button and your company details with an unsubscribe link.

Save the draft, check the preview and send a test to yourself. Then send it now or at a set time – sending to subscribers needs the publishing permission.

Two things must be set up first; the screen tells you when one is missing:

• an SMTP server in Settings → Mail – Brevo, Amazon SES, Mailgun or your own mailbox. Bulk mail through the hosting’s mail() function would end up in spam. Set Newsletters: e-mails per hour to your service’s limit.
• cron calling the tasks address from Site care → System status every few minutes. The e-mails go out in batches on each call, so a newsletter never stalls on a quiet site.

Every e-mail carries the subscriber’s own unsubscribe link and one-click unsubscribe for mail clients. Nothing tracks opens; links to your site carry utm parameters, so Statistics show the visits a newsletter brought. The recipient list is kept only while sending – afterwards only the counts and dates remain. Claude can draft newsletters and send tests too, and sends to subscribers only when you ask.

Or send subscribers to your mailing service

In Administration → Features → Newsletter (or the Mailing service card in Integrations) choose Brevo, MailerLite, Mailchimp, Ecomail or SmartEmailing, enter the API key and the list, group or audience ID. Every confirmed subscriber is then added to that list, and removed when they unsubscribe or you delete them. Sending, deliverability and unsubscribing from e-mails stay with the service.

• Any other service works through a webhook (Make, Zapier, n8n): the site sends JSON with the event and the e-mail.
• The transfer runs in the background, so visitors never wait; failed attempts are retried.
• Subscribers shows the state of each address, sends all existing subscribers at once and retries the failed ones.
• The API key is stored only on your site and is never shown over MCP.

Or export to CSV

Export confirmed addresses to CSV, including each subscriber’s unsubscribe link, and import them into another mailing tool.

Unsubscribe and confirmation links keep working even if you later switch the feature off. A sign-up in a pop-up counts as its conversion.