For Admins
Outgoing mail (SMTP)
Emails to customers go out through the SMTP server of the project's email channel — from your address and your domain.
Where to set it up
“Settings → Channels → Email”, the Outgoing Mail (SMTP) block. There is no separate SMTP page in settings — the server belongs to the email channel.
- SMTP server and Port (465 by default). The Provider picker in the incoming mail block fills in the servers and ports for Gmail, Yandex, Mail.ru, Outlook / Office 365 and Rambler.
- Login and Password. Once saved, the password isn't shown again; an empty field keeps the saved one.
- From — email is the address recipients see, plus From — sender name.
- Encryption follows the port: on 465 the connection uses TLS from the start; on other ports STARTTLS is used when a login is set.
“Send test email” in the Test email field sends a real email to the address you enter; “Check everything” tests the IMAP and SMTP connections. If the channel has a proxy, SMTP goes through it too.
What goes through this SMTP
- operator replies on email tickets and on widget tickets with Email Bridge on;
- emails from the email templates — acknowledgement, Ticket resolved and the rest;
- auto-close reminders on email tickets;
- email broadcasts — only through this server, with no fallback.
Sign-in and sign-up emails, invitations, billing emails, notification-rule emails and analytics email reports go through the platform's mail and need no setup on the project side.
Until the email channel has SMTP, incoming mail is received but nobody can reply: the operator gets an error on sending, and template emails and email broadcasts don't go out.
For deliverability, use your own domain's mail server with SPF, DKIM and DMARC set up — the DNS records are configured with your mail provider.
Was this page helpful?