Sending e-mail.

The site sends password reset links, system notifications and enquiries from forms. Settings → Mail decides how these messages leave the server. With your own SMTP server they go out from a verified mailbox and do not end up in spam.

Sending method

• Hosting server – uses the server's mail() function. Nothing to set up, but with some hosts messages end up in spam.
• Custom SMTP server – a mailbox at your host, Google Workspace, Seznam, or a service such as Brevo, Mailgun or Amazon SES. Recommended, and required for newsletters.

SMTP server

When you choose Custom SMTP server, fill in:

• Server address – for example smtp.gmail.com, smtp.seznam.cz or smtp-relay.brevo.com.
• Security – STARTTLS – port 587 (most common), SSL/TLS – port 465, or none only for a server on your own network.
• Port – usually 587 or 465, to match the security setting.
• User name – usually the full e-mail address of the mailbox.
• Password – for Gmail and Seznam use an “app password”, not your account password. The password is stored only on your site and is never shown again. Leave the field empty to keep it, or tick Remove saved password.
• Newsletters: e-mails per hour – newsletters go out in batches while cron runs. Keep to your SMTP service's limit; free plans often allow only a few hundred e-mails a day. The default is 300.

Sender and replies

• Sender address – empty means the Site email from the General tab. With SMTP it must be an address your mailbox is allowed to send from.
• Send replies to – optional, when replies should go somewhere other than the sender.

The sender name is the site name.

Test message

Save the settings first – the test uses the saved values. Then click Send a test e-mail to the site address. The message goes to the Site email. If sending fails, you see the reason straight away, for example a wrong password or a server that cannot be reached. Some hosts block outgoing SMTP; then ask your host or use their mail server. The same button is on the System status tab.

Recent messages

The table shows the last 30 messages the site sent, with Time, To, Subject and Status:

• sent – delivered to the mail server, with the attempt number if it needed more than one.
• waiting for the next attempt – sending failed; the error is shown below.
• not sent – sending failed and will not be tried again, for example after the last attempt or for a test message.

A message that fails is tried again after 5 minutes, 30 minutes, 2 hours and 12 hours, so a new password or an enquiry is not lost during a short outage. Retries run in the background on site visits, or from cron. Records are deleted after 30 days, and the message content is not kept. Newsletters have their own queue and do not appear here.

Why SMTP matters

Mail from mail() often has no link to your domain's mail records (SPF, DKIM). Receiving servers then treat it as suspicious. Sending through a mailbox on your own domain lets your mail provider match those records, so enquiries reach you and replies reach your customers. For newsletters, Kaleta requires SMTP and a running cron.