Skip to content
AdminKit

VERP (Variable Envelope Return Path)

What is VERP (Variable Envelope Return Path)?

VERP (Variable Envelope Return Path) encodes each mailing-list subscriber's own address into the envelope sender of the copy they're sent, so a later bounce is self-identifying instead of generic. AdminKit's guide to email bounces and backscatter explains how the envelope sender normally routes a failed delivery back to its source.

By AdminKit team, Netbase JSC · Updated

VERP (Variable Envelope Return Path) is a mailing-list convention that rewrites the envelope sender of each individual copy of a message to encode the recipient it was sent to, for example rewriting list-request@example.com into list-request=subscriber=other.example@example.com for one subscriber’s copy. If that copy later bounces, the DSN lands on an address that already names the failing subscriber, so list software can identify and unsubscribe a dead address without parsing the bounce body at all. Exim’s own specification documents VERP support via its return_path transport option, crediting the original mechanism description; Postfix and Mailman implement equivalent support. The Postfix VERP Howto says Postfix 1.1 and later support it on request, giving each recipient a customized copy of the message with that recipient’s own address encoded in the envelope sender address. VERP is a widely deployed MTA convention rather than an IETF standard — unlike the RFC 3464 DSN format it relies on (current document status at its IETF Datatracker entry), no RFC defines its address-encoding syntax.

VERP (Variable Envelope Return Path) is part of AdminKit’s email authentication cluster; the full AdminKit glossary lists other related terms.

Frequently asked questions

Is VERP an IETF standard?

No -- VERP is a widely deployed MTA convention rather than an IETF standard; no RFC defines its address-encoding syntax, unlike the RFC 3464 DSN format it relies on.

How does VERP let list software identify a dead subscriber address?

Each subscriber's copy has the envelope sender rewritten to encode that recipient, so a later bounce's DSN lands on an address that already names the failing subscriber, with no bounce-body parsing needed.

Which mail transfer agents support VERP?

Exim documents VERP support via its return_path transport option; Postfix and Mailman implement equivalent support.

What does a VERP-rewritten envelope sender look like?

For example, list-request@example.com becomes list-request=subscriber=other.example@example.com for one subscriber's individual copy of the message.