Connect via SMTP/IMAP
For any provider that doesn't offer OAuth — Amazon SES, Zoho, a custom domain mailbox, or a provider-agnostic sending service — SubsiMail connects directly with SMTP (to send) and IMAP (to poll for replies).
When to use this
Use SMTP/IMAP when your sending inbox isn't a Gmail or Microsoft 365 mailbox. If it is, prefer Gmail or Outlook OAuth instead — those integrate more deeply (real-time API instead of polling) and don't require storing a raw password.
What you'll need
Both an SMTP and an IMAP endpoint for the same mailbox — your provider's documentation will list these, usually under "SMTP/IMAP settings" or "third-party client setup":
From email address | The address contacts will see mail arrive from |
SMTP host / SMTP port | Typically port 587 (STARTTLS) or 465 (implicit TLS) |
SMTP username / SMTP password | Credentials for sending |
IMAP host / IMAP port | Typically port 993 |
IMAP username / IMAP password | Credentials for reading the inbox (stop-on-reply detection) |
Connect in SubsiMail
- Go to Accounts → SMTP / IMAP and click Connect SMTP/IMAP account to expand the form
- Fill in all fields above and submit
- SubsiMail tests the connection immediately — if either SMTP or IMAP login fails, you'll see the error before the account is saved
Example: Amazon SES
SES is a common SMTP/IMAP choice since it doesn't have its own inbox (you'd pair it with a separate IMAP-capable mailbox, or use it purely for sending with reply detection via another connected account). SES SMTP settings look like:
SMTP host: email-smtp.us-east-1.amazonaws.com
SMTP port: 587
SMTP username: (SES SMTP credentials, not your AWS access key)
SMTP password: (SES SMTP credentials, not your AWS secret key)Generate SES-specific SMTP credentials from the SES console — they're different from your regular AWS IAM keys.