Skip to main content
Without an SMTP sender configured, email goes out from a platform default address. Adding your own means it comes from your domain — which customers trust and which is far less likely to land in spam.

​
Add a sender

Email settings → Create, then fill in what your email provider gave you:
Gmail and Microsoft 365 reject your normal login password. You need an app password with two-factor authentication enabled on the account:
  • Gmail — Google Account → Security → 2-Step Verification → App passwords
  • Microsoft 365 — Security info → Add sign-in method → App password
If SMTP authentication fails and you are certain the password is right, this is almost always why.

​
Landing in inboxes rather than spam

Configured at your DNS provider, not here, but they matter more than anything on this page:
  • SPF — lists who may send on your domain’s behalf.
  • DKIM — signs your mail so it cannot be forged.
  • DMARC — tells receivers what to do when the first two fail.
Sending from a domain with none of these set up means a meaningful share of your email will be filtered. Your email provider’s documentation will give you the exact records.

​
Common failures

An app password is needed (see above), or the username is not the full email address.
Wrong port, or your provider blocks the one you chose. Try 587 if you used 465.
SPF/DKIM/DMARC are missing or wrong for the sending domain.
Most providers refuse to send as an address the authenticated account does not own. The username and the from address should be the same mailbox, or an alias it is permitted to send as.