On Fri, Feb 17, 2006 at 03:50:01PM -0500, Internet-Drafts(_at_)ietf(_dot_)org
wrote:
Title : Sieve Email Filtering -- Subaddress Extension
Author(s) : K. Murchison
Filename : draft-ietf-sieve-rfc3598bis-02.txt
Pages : 14
Date : 2006-2-17
This draft allows both prefix and suffix encoding, but still requires
both user and detail part to be substrings of the local part.
Why? VERP (http://cr.yp.to/proto/verp.txt) is a popular encoding
and if you relaxed the encoding specification, Sieve could be
used to decode it. A filter in front of a MLM may be very useful.
I fail to see the mismatch. In a VERP scheme the user part tells you the name
of the list whie the detail part tells you the address that failed.
I suppose you could also use subdomains to encode some of this information
(VERP is an approach, not a particular encoding), but that's not how it is
normally done.
Ned