Outgoing mail for invoices, notifications and campaigns, and incoming mail for the support desk.
Outgoing mail
Open System → Settings → Email. Enter the sender address and name, pick SMTP as the mailer and fill in host, port, encryption, user name and password. Send a test email delivers a message to the address you enter and reports the server's answer, so a wrong password or a blocked port shows up right away.
Until SMTP is configured the mailer is set to log: messages are written to storage/logs/laravel.log instead of being sent. That is useful on a test installation and must be changed before clients are added.
Use a mailbox on your own domain as the sender and publish SPF and DKIM records for it; most mail providers reject or spam-folder messages sent from an address whose domain does not authorise your SMTP server.
Email templates
Every message the application sends (invoices, payment confirmations, service details, domain notices, ticket replies, staff alerts and so on) has a template under Customers → Email templates. Templates use placeholders such as the client name, invoice number or service details; the editor shows the placeholders each template understands and previews the result with sample values. Templates can be switched off individually.
Emails to clients
- Customers → Send email writes to one client, or to a selection, from the staff area and records the message on the client's account.
- Customers → Email campaigns sends a message to a filtered group of clients in batches through the scheduler. Marketing campaigns go only to clients who opted in; every campaign message carries an unsubscribe link.
Incoming mail for support
Each support department can read a POP3 mailbox. Under System → Support desk → Departments open a department, enable the mailbox and enter host, port (995 for POP3 over TLS), user name and password. The scheduler fetches the mailbox; messages from known clients open tickets or are added as replies, and messages that cannot be matched wait under Operations → Inbound email where staff can attach them to a ticket, open a new one or discard them.
Replies sent by email are matched by the token in the ticket message, so clients can answer from their mail program. Attachments follow the size and type limits set for the support desk.
Checking delivery
- A failed send is recorded against the message in the activity log of the client and in
storage/logs/laravel.log. - Operations → Recovery shows queued mail that has been waiting too long.