Join our Newsletter — 33% off our NHI Course
Home› Glossary› Cyber Security› SMTP Relay
Cyber Security

SMTP Relay

← Back to Glossary
By NHI Mgmt Group Updated November 1, 2026 Domain: Cyber Security

An email transfer path that forwards messages from one server or service to another. Organisations use relays for application mail and infrastructure messaging, but poorly secured relay points can become a path for spoofed or unauthenticated email to reach users under a trusted domain.

What SMTP relay means in practice

An SMTP relay is the forwarding path that hands email from one server or service to another, usually so applications, devices, or internal systems can send mail without talking directly to every recipient domain. In secure environments, the relay is a trust boundary, because it decides which senders and messages are allowed to pass onward.

That makes relay design more than a delivery convenience. A well-run relay enforces sender identity, message policy, and destination restrictions, while a weak one can quietly become an open forwarding point for spoofed or unauthenticated mail.

Why SMTP relays exist

Organisations use relays to centralise outbound mail, standardise authentication, simplify logging, and keep application systems from needing direct internet mail delivery rights. The same pattern also supports infrastructure messaging such as alerts, password resets, system notices, and transactional email.

Relays are especially useful when many producers need to send mail but should not all be able to reach the internet independently. That separation lets teams apply one consistent policy layer instead of distributing mail-delivery logic across every host and application.

The term also covers ordinary mail-transfer infrastructure, not just marketing or application email. The secure protocol path and the server policy around it matter as much as the software brand or mail platform.

How relay security is supposed to work

A secure relay accepts mail only from authorised senders, verifies transport security where appropriate, and constrains who can relay to which destinations. Strong implementations usually bind SMTP AUTH to TLS, limit relay rights by account or host, and reject unauthenticated forwarding to external domains unless there is an explicit business reason.

This is where message routing becomes an access-control problem. If the relay accepts mail too broadly, it can be abused to impersonate a trusted domain, bypass domain-level filtering, or send messages that look legitimate to users and downstream mail systems. NHIMG’s Exim and Postfix Mail Server Hardening Guide covers the relay controls, sender binding, logging, and rate-limiting choices that keep that boundary tight.

Exposure signals and configuration mistakes

The most common exposure pattern is an unintended open relay, where the server forwards mail for unauthenticated or untrusted sources. A second problem is overly broad authenticated relay access, where any valid login can send as any sender or to any destination, which weakens trust in the domain and makes abuse harder to trace.

Relay security also depends on the surrounding mail stack. DNS records, sender policy, transport security, application credentials, and mail server configuration all influence whether the relay is merely a transit point or a convenient abuse channel. NHIMG’s Network Ports and Protocols Security Guide places SMTP in the broader protocol context and helps readers distinguish normal mail ports and secure transport choices from risky exposure patterns.

When a relay is exposed to the internet, its security posture depends on more than firewall placement. Administrators should treat it as a high-value service because it can reveal whether a sender is trusted, whether a domain is being impersonated, and whether mail policy is being enforced at the edge.

Why compromised relays matter

When an SMTP relay is misused, the immediate consequence is often abuse of trust rather than classic server takeover. Attackers or spammers can use it to push fraudulent messages through a trusted domain, increasing delivery success and making phishing or business-email-compromise lures more convincing. If relay secrets or API keys are exposed, the attacker may not need a full server compromise to reach that outcome.

For that reason, relay compromise review should include message logs, relay rules, authentication records, and any credentials or keys that allowed mail submission. NHIMG’s Gravity SMTP CVE-2026-4020 API Keys Exposure shows how exposed SMTP-related keys can become a direct abuse path even when the relay software itself is not fully seized.

Because the relay sits between origin systems and recipients, a compromise can also create reputational damage. Once external mail providers or users lose trust in the domain, legitimate mail delivery can suffer long after the technical issue is fixed.

Risk and Threat Considerations

SMTP relays are attractive abuse points because they sit inside a trusted delivery chain. If relay policy is weak, an attacker can use the service to send spoofed mail, relay spam, or bypass reputation controls under a legitimate domain.

Failure mechanism: The relay accepts unauthorised senders, permits overly broad sender or destination use, or exposes submission credentials and API keys that can be reused for mail abuse.

Impact: Trusted-domain spoofing, phishing delivery success, message abuse, reputational harm, and potentially credential exposure if the relay is also used for application or infrastructure mail.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5, CIS Controls v8 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5AC-3 — Access EnforcementSMTP relays enforce who may forward mail and under what conditions.
IA-5 — Authenticator ManagementRelay accounts, SMTP AUTH secrets, and API keys must be managed across their lifecycle.
AU-2 — Event LoggingRelay logs are needed to trace sender, destination, and abuse activity.
Recommendation — Enforce relay allowlists and sender restrictions with access checks on every submission. Rotate and protect relay credentials and revoke any exposed submission secrets promptly. Log relay submissions and forwarding decisions so abuse can be investigated quickly.
CIS Controls v8CIS-5 — Account ManagementRelay accounts and submission identities need controlled provisioning and review.
Recommendation — Restrict and review relay accounts so only approved systems can submit mail.
NIST CSF 2.0PR.AA-05 — Identity Management, Authentication, and Access ControlA relay is a trust boundary where authenticated senders need tightly scoped access.
Recommendation — Apply least-privilege access rules to relay submission paths and trusted senders.

Practitioner Guidance

Why practitioners should care: An SMTP relay should be governed as an access-controlled service, not just as plumbing. If many applications depend on one relay, a weak policy or exposed credential can become a single abuse path across multiple systems.

Common misunderstanding: “Authenticated” does not automatically mean “safe.” The important question is whether the relay ties each sender to a narrow, well-audited set of allowed messages and destinations.

Practitioner takeaway: Treat relay permission, sender binding, and logging as part of the mail trust boundary, and review them with the same care you would apply to any privileged forwarding path.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 1, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org