Outgoing mail

Admin → Settings → Outgoing mail configures how Justflows sends every email — account notices, password resets, comment moderation, form notifications, and test sends. The look of each message is set separately in Email templates.

Sender identities#

• From — the address recipients see.
• Reply-To — where replies are directed, if different.
• Envelope sender — the return-path used for bounce handling, if different again.

Transports#

Register a provider transport (SMTP or a supported provider) with its credentials. A test send returns the full transport response, so a misconfiguration is visible immediately. Transport secrets and queued retry payloads are encrypted at rest.

On a multisite installation a sub-site never uses the host's sendmail. Its default is Platform mail: email goes through the main site's transport and sender address, under the sub-site's own sender name, and replies go to its own reply-to or administration address. The Own email settings switch (feature.ownMail, on by default) under Platform → Defaults → Features decides whether a sub-site may use its own SMTP or plugin transport.

Delivery log and retries#

• Delivery log — every send with its status, privacy-masked so addresses are not stored in the clear.
• Dead-letter log — messages that exhausted their retries.
• Manual retry — re-send a failed message from the log.
• Per-type suppression — turn off one category of mail (for example form notifications) without disabling the rest.
• Delivery limits — cap the send rate to stay inside a provider's quota.

Attachments from plugins#

A plugin can attach up to 5 files to an email with ctx.mail.send({ attachments: [{ filename, content, contentType }] }): PDF, PNG, JPEG, CSV, plain text, or calendar, 10 MB each and 15 MB together. They go out through SMTP, sendmail, or a plugin transport. The delivery log keeps only their names, types, and sizes, so a delivery retried from the admin is sent without them. Shop uses this for PDF invoices and credit notes.

Incoming mail#

Settings → General also has Incoming mail. Turn on Read this mailbox and set the IMAP host, port, encryption, mailbox, username, and password. The password is stored encrypted and is not returned by the settings API.

• The main site, and a website whose plan allows its own mail settings, each read their own mailbox.
• A website without that permission is read from the main site's mailbox. While that mailbox is on, its replies go to the main site's reply-to (or From) address, so they arrive in the mailbox that is read.
• Each unseen message is filed once. Helpdesk claims it when the reply token or ticket number belongs to that site; otherwise it is filed on the one website whose administration, reply-to, or From address is on the message.
• A website's IMAP server must be a public host on port 143 or 993, with STARTTLS or SSL.
• POST /api/mail/inbound still accepts a pushed message when JUSTFLOWS_INBOUND_MAIL_SECRET is set. Plugins with mail:hook see accepted mail through email.received and can route it with email.route.

Deliverability#

The screen includes SPF, DKIM, and DMARC guidance for the sender domain so mail is less likely to be filtered. Operational access is gated by the mail:read and mail:manage capabilities.