Skip to content
AdminKit

SRS (Sender Rewriting Scheme)

What is SRS (Sender Rewriting Scheme)?

SRS (Sender Rewriting Scheme) fixes SPF failures caused by email forwarding by rewriting the envelope sender address at the forwarding server to one on the forwarder's own domain, so the forwarder's own SPF record is checked instead. AdminKit's guide explains how SRS keeps forwarded mail passing SPF.

By AdminKit team, Netbase JSC · Updated

SRS (Sender Rewriting Scheme) fixes SPF failures caused by email forwarding by rewriting the envelope sender address at the forwarding server, replacing it with an address on the forwarder’s own domain that still encodes the original sender for bounce routing. Microsoft’s own documentation for Exchange Online describes exactly this for its implementation: “SRS was added to Microsoft 365 to resolve a problem where autoforwarding is incompatible with the Sender Policy Framework (SPF).” Because SPF checks the connecting server’s IP against the domain in the, now rewritten, envelope sender, and that address belongs to the forwarder, it’s the forwarder’s own SPF record — which correctly lists its own IP — that gets checked, so the forwarded message passes instead of failing on the original domain’s SPF record, which never authorized the forwarder. On self-hosted Postfix servers the open-source PostSRSd daemon provides SRS, and its README notes that the temporary rewritten address is bound to the original sender and only valid for a certain amount of time, which prevents abuse by spammers. SRS is a widely implemented convention rather than a formal IETF standard — unlike SPF itself, which the IETF Datatracker lists as a full Proposed Standard; SRS only works if the forwarding server itself supports it, and it does nothing for DKIM, which a message-modifying forwarder can still break separately. The SPF failure SRS works around is defined in RFC 7208; DKIM, which SRS does not help with, is defined separately in RFC 6376.

SRS (Sender Rewriting Scheme) is part of AdminKit’s email authentication cluster; the full AdminKit glossary lists other related terms.

Frequently asked questions

Is SRS an official IETF standard?

No -- SRS is a widely implemented convention rather than a formal IETF standard, and it only works if the forwarding server itself supports it.

Does SRS fix DKIM failures caused by forwarding too?

No -- SRS only addresses the SPF failure caused by forwarding; it does nothing for DKIM, which a forwarder that modifies the message can still break separately.

Why does forwarding break SPF in the first place?

SPF checks the connecting server's IP against the domain in the envelope sender; after forwarding, the connecting server is the forwarder, not the original sender's server, so the original domain's SPF record -- which never authorized the forwarder -- fails.

How does SRS fix that?

It rewrites the envelope sender at the forwarding server to an address on the forwarder's own domain that still encodes the original sender for bounce routing, so the forwarder's own SPF record, which correctly lists its IP, is checked instead.