Hello!
On Wed, Dec 08, 2004 at 11:56:43AM -0500, Stuart D. Gathman wrote:
[...]
The downside of DBBF is that the recipient often needs to extract
the original MAILFROM when evaluating the overall authenticity of
the message - which is easy to do with normal SRS or SES.
For instance, you need the original MAILFROM to query an
SES validation server.
Any kind of SRS may break SES, unless you force SES implementors to know
all kinds of SRS and SRS-like sender address rewriting schemes. But then
you could also ask sender address rewriters to skip rewriting on SES
envelopes.
I suppose the forwarder can record the original sender in an
RFC2822 header.
Which reduces the use of SES, too. With SES *envelope* senders you can
check them before the SMTP DATA phase. With the original SES in an
RFC2822 header, you have to defer checking to the end of DATA, and you
have a bit more resource usage to fiddle the SES sender out of the
header.
Kind regards,
Hannah.