SMTP
Connect any SMTP-compatible email server to GoodPostal. This is the most flexible option, supporting Amazon SES, custom mail servers, and any provider that offers SMTP access.
Generic SMTP is available by request after one-time admin approval. Most users connect one of the supported API-based services instead, like SendGrid, Mailgun, or Postmark.
Prerequisites
- SMTP server hostname and port
- Authentication credentials (username and password)
- Knowledge of the encryption method (TLS or SSL)
- A verified custom tracking domain. SMTP is the one connection type that always needs one before you can send. See Tracking Domain
Setup Steps
- 1
Gather SMTP credentials
Get the hostname, port, username, and password from your email provider. Most providers list these in their settings or documentation. - 2
Add the provider in GoodPostal
Go to Configure > Email Providers, click "Add Provider", select SMTP, and enter your credentials. - 3
Test the connection
GoodPostal will attempt to connect to the SMTP server and authenticate. If the test fails, verify your credentials and firewall settings.
Configuration Fields
| Name | Type | Required | Description |
|---|---|---|---|
Host | string | Yes | SMTP server hostname (e.g., smtp.example.com) |
Port | number | Yes | SMTP port (typically 587 for TLS, 465 for SSL, 25 for unencrypted) |
Encryption | TLS|SSL|None | No | Encryption method. TLS (port 587) is recommended. None sends your credentials and mail unprotected over the network, so only choose it if you understand and accept that risk. |
Username | string | Yes | SMTP authentication username |
Password | string | Yes | SMTP authentication password or app-specific password |
Common Provider Settings
SMTP settings by provider
Host: email-smtp.us-east-1.amazonaws.com
Port: 587
Encryption: TLS
Username: (SMTP username from SES console)
Password: (SMTP password from SES console)Warning
Gmail and Outlook have low sending limits (500/day for Gmail, 300/day for Outlook) and are not suitable for bulk email campaigns. Use a dedicated email sending service for production sending.
Webhook Tracking for SMTP
SMTP does not natively support delivery event webhooks like API-based providers. GoodPostal provides basic tracking for SMTP connections, but all of it runs on your own tracking domain:
Warning
A plain SMTP server cannot host an unsubscribe link, so GoodPostal has to host it for you. That means a verified custom tracking domain is required before you can send any campaign through an SMTP connection, and the open and click tracking below only works once it is verified. Set one up at Configure > Tracking Domain, or see Tracking Domain.
- Open tracking - Works via tracking pixel (handled by GoodPostal)
- Click tracking - Works via link wrapping (handled by GoodPostal)
- Bounce/complaint tracking - Limited, depends on your SMTP provider. Some providers (like Amazon SES) support separate bounce notification configuration.
Tip
Troubleshooting
- Connection timeout - Check that the port is open in your firewall. Some hosting providers block port 25.
- Authentication failed - Some providers require app-specific passwords (Gmail, Outlook with 2FA). Generate one in your provider's security settings.
- TLS handshake failure - Try switching between TLS and SSL, or check if your server supports the encryption method you selected.