Email¶
Atfinity sends email through any SMTP server, such as your own mail server or a mail delivery service. Every email Atfinity sends goes through it: the Send Email action, notifications, documents and booklets sent from a case, wizard links, new user invitations and password resets.
The Send Email rule action makes email a notification framework of your own. The rule computes the recipients, the subject and the body from the case, or takes the subject and the body from an email template in the language you pick. It can also attach the booklet, a document of the case, or both. The conditions of the rule decide when it is sent, and a scheduled rule sends reminders and follow-ups on a date rather than on a change.
Without a configuration of its own, a tenant sends through the SMTP server of the installation. Turn on "Use custom email configuration" under Integrations in Services, on the Email tab, to send through your own server instead.
- SMTP host and SMTP port: Atfinity gives up on a server that does not answer within 30 seconds
- Use TLS: upgrades the connection with STARTTLS, usually on port 587. A server that only accepts implicit TLS, usually on port 465, is not supported
- Sender to show: the sender address alone, such as
onboarding@yourbank.com, replacing the name and address the field starts with. Atfinity puts the title of your tenant in front of it as the sender name, keeping only its letters, digits and spaces - Authenticate with username and password: turn it off for a relay that accepts mail from your network without signing in
"Bcc" applies whichever server you use: every address in it, separated by commas, receives a copy of every email, which is a way to archive them.
Send a test email before you rely on the server. The test shows the settings Atfinity used and, when sending fails, the error the server returned, so a refused login or a blocked port shows up there rather than in a case.