EonMailer The agency pain
IT mandates SMTP; marketing still needs a multi-client process and compliance footers.
Integrations · Live
Custom SMTP for agencies — when the client mandates a relay
Some clients will only send through their approved relay. EonMailer still gives you workspaces, approvals, and campaigns — with clear expectations on reporting.
What EonMailer adds
Connect host, port, encryption, and credentials; set From identities; send campaigns. Tracking is limited without ESP webhooks.
Outcome
You can say yes to constrained clients without abandoning the agency desk.
Capabilities
Custom SMTP with EonMailer
- Generic SMTP (TLS/SSL/none) per workspace
- Useful for M365 / Google / on-prem relays
- Same approvals and campaign pipeline as other providers
- Unsubscribe links still work via EonMailer
- Honest UI: limited bounce/open/click feedback vs SES/SendGrid/Mailgun
Setup path
From zero to first safe send
- Get SMTP host, port, encryption, and mailbox credentials from the client’s IT
- Connect Custom SMTP in guided setup and verify the connection
- Set the allowed From address and compliance defaults
- Send a test through the relay
- Prefer SES/SendGrid/Mailgun later if full engagement reporting is required
Help Center
Step-by-step SMTP guides
Deep setup docs live on Help — linked from the product wizard too.
FAQ
SMTP questions agencies ask
Will I get open and click reports on SMTP?
Usually not at ESP quality. Generic SMTP has no standard webhook channel. Unsubscribes still work; prefer SES/SendGrid/Mailgun for full engagement reporting.
Is SMTP a good default for agencies?
Use it when policy forces a relay. For most retainers, SES/SendGrid/Mailgun give better deliverability feedback and cheaper scale (especially SES).
Connect Custom SMTP for your next client
Free plan includes 1 workspace — enough to validate BYO SMTP end to end.