Custom Email & SMTP
Send ProductBridge emails from your own domain by connecting your SMTP server — so notifications, assignments, and changelog announcements reach your customers from your brand.
Send Email From Your Own Domain
By default, ProductBridge sends emails through our shared system mailer. To send from your own domain, connect your own SMTP server (Google Workspace, Amazon SES, Postmark, SendGrid, Mailgun, etc.) under Custom SMTP.
Custom SMTP is never required for delivery. Every ProductBridge email falls back to the system mailer when custom SMTP isn't configured or fails — nothing is skipped.
Custom SMTP
Use this option to route ProductBridge emails through your own SMTP server. Choose this if you already have a mail infrastructure and want everything to flow through it.
Custom SMTP is available on plans that include the email_notifications feature.
Set Up Custom SMTP
Open SMTP settings
Go to Settings → Brand Settings, open the SMTP tab, and turn on the Custom SMTP switch.
Enter your SMTP credentials
Provide:
- Sender Name — the display name shown in the inbox (e.g., "Acme Product Team")
- Email Address — the address messages are sent from (e.g.,
feedback@yourproduct.com) - SMTP Host — your SMTP server hostname (e.g.,
smtp.gmail.com,email-smtp.us-east-1.amazonaws.com,smtp.postmarkapp.com) - Port — typically
587(TLS) or465(SSL) - Username — your SMTP login
- Password — your SMTP password or app-specific token
Your password is encrypted at rest and only decrypted at send time. We never log or display it after you save.
Test the connection
Click Test Connection. ProductBridge attempts a real SMTP handshake using the credentials you provided.
On success, the status changes to Active. On failure, you'll get an error so you can fix the credentials.
Done
Once active, outgoing email from ProductBridge routes through your SMTP server.
Status
| Status | Meaning |
|---|---|
| Not Tested | Credentials saved but the connection test hasn't run yet |
| Active | Test connection succeeded — your SMTP is used for outbound email |
| Error | Last test failed — emails fall back to the system mailer until fixed |
You can re-test or update credentials at any time.
How Delivery Works
ProductBridge sends every email using a two-tier strategy:
- Your custom SMTP — tried first when configured and active
- System SMTP fallback — used if custom SMTP isn't configured or fails
A misconfigured SMTP setup won't block delivery — every email type falls back to the system mailer until you fix it.
Which Emails Are Affected?
When your custom SMTP is active, all outbound emails from ProductBridge route through it:
- Changelog subscriber announcements
- Post assignment notifications
- Status change and comment emails
- Team member invitations
- Subscription confirmation emails
- Any other transactional message
Common Provider Setups
- SMTP Host:
smtp.gmail.com - Port:
587 - Username: the full email address (e.g.,
feedback@yourproduct.com) - Password: an App Password generated for your Google Account — your normal Google password will not work
You must enable 2-Step Verification on the Google Account to create App Passwords.
- SMTP Host:
email-smtp.<region>.amazonaws.com(e.g.,email-smtp.us-east-1.amazonaws.com) - Port:
587 - Username & Password: SMTP credentials generated in the SES console (not your AWS access keys)
- Verify your sender in SES before testing — SES rejects sends from unverified addresses
- SMTP Host:
smtp.postmarkapp.com - Port:
587 - Username: your Postmark Server Token
- Password: the same Server Token (Postmark uses it for both)
- SMTP Host:
smtp.sendgrid.net - Port:
587 - Username:
apikey(literally the stringapikey) - Password: your SendGrid API Key with at least "Mail Send" permission