Of course, now i see the light :)
Sorry for being stubborn :)
Koen
On Tue, Aug 17, 2004 at 10:30:00PM +0200, Roger Moser wrote:
Koen wrote:
Yes, but with SES you don't have the info on who was the previous
forwarder, unless you keep a database which sounds a bit cumbersome to
me. I know how this works with SRS, but I thought you suggested SES.
Only the original MTA does SES. If there is a signed envelop sender
(starting with "SES"), then the forwarders don't have to modify it. But is
does not harm if the forwarder applies SRS.
Example:
name(_at_)example(_dot_)com sends mail to <john(_at_)forwarder1(_dot_)com>.
The envelop sender is
<SES=xxx=name(_at_)example(_dot_)com>.
The first forwarder (not aware of SES) applies SRS and sends it to
<jimmy(_at_)forwarder2(_dot_)com>. The envelop sender is
<SRS0=yyy=example(_dot_)com=SES=xxx=name(_at_)forwarder1(_dot_)com>.
The second forwarder (not aware of SES) applies SRS and sends it to
<ben(_at_)final(_dot_)com>. The envelop sender is
<SRS1=zzz=forwarder1(_dot_)com=yyy=example(_dot_)com=SES=xxxx=name(_at_)forwarder2(_dot_)com>.
The bounce is sent to
<SRS1=zzz=forwarder1(_dot_)com=yyy=example(_dot_)com=SES=xxxx=name(_at_)forwarder2(_dot_)com>
then to <SRS0=yyy=example(_dot_)com=SES=xxx=name(_at_)forwarder1(_dot_)com>
and then to
<SES=xxx=name(_at_)example(_dot_)com>.
Roger
-------
Sender Policy Framework: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
http://www.InboxEvent.com/?s=d --- Inbox Event Nov 17-19 in Atlanta features
SPF and Sender ID.
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
--
K.F.J. Martens, Sonologic, http://www.sonologic.nl/
Networking, embedded systems, unix expertise, artificial intelligence.
Public PGP key: http://www.metro.cx/pubkey-gmc.asc
Wondering about the funny attachment your mail program
can't read? Visit http://www.openpgp.org/