"Tom Neff" <firstname.lastname@example.org> wrote:
>Instead of (or in addition to) serializing the Subject header in each
>probe message, you also serialize the From: and Errors-To: headers as
> From: email@example.com
> Errors-To: firstname.lastname@example.org
> Subject: List Test #001347
> This is a list test message - please ignore it.
>Now even the most uncooperative Prodigy-class mail agent can't help revealing
>which message it's bouncing, because each one will be delivered to a unique
>"userid." Even if they omit a To: header in the bounce, you can examine the
>Received: headers for the delivery address your local MTA saw.
This is very similar to VERP, which encodes the recipient's address in
the SMTP envelope return path. The advantage of VERP is that it can be
used for each delivery--obviating the need for special probes, and
allowing the list manager to keep track of which messages have bounced
to which subscribers.
The advantages of your method over VERP are that it will work with
idiotic daemons that send bounces to the From: address, and it'll work
with MTA's that can't do VERP.
>This is particularly easy to do with today's "virtual servers" that forward
>email@example.com to the same address.
qmail's wildcardable user-defined extension addressing makes VERP'ed
bounces easy to deal with. And qmail supports sending VERP'ed
messages. Of course, ezmlm uses VERP to implement automatic bounce
handling. There's also a VERP bounce handler for Majordomo under
qmail that works nicely.