Topic · Email Infrastructure
SMTP relay
An SMTP relay accepts mail from one system and forwards it toward its destination.
How it works
Relay hosts route mail based on policies, authentication and recipient domains.
What can go wrong
An open relay can be abused for spam and damage sending reputation. Check relay restrictions on every externally accessible listener.
What to check or do
Require authorization and restrict relay permissions. Monitor authenticated submissions and outbound destinations.
Practical scenario
A mail gateway is configured to relay outbound traffic from internal applications. A firewall change unexpectedly exposes the relay to the public internet, allowing unauthenticated third parties to submit messages.
Verification checklist
- Test external relay authorization safely with controlled domains.
- Restrict clients and recipients using explicit policy.
- Monitor queue growth, sender identities and anomalous volumes.
- Require protected authenticated submission where applicable.
How to investigate SMTP relay
- Signal to investigate
- A relay accepts mail from networks that should have no sending privileges.
- Evidence to collect
- Test relay acceptance only in authorized scope, and review SMTP AUTH and permitted sender restrictions.
- Common wrong conclusion
- Confusing relay authentication with SPF/DKIM often masks an open-relay exposure.
Put this into practice
Run a focused check, then explore protection if your domain needs it.