3. Gmx bounces it:
<>@gmx.net => bob(_at_)pobox(_dot_)com
right
4. pobox forwards it again, replacing original sender:
bob(_at_)pobox(_dot_)com -> bob(_at_)gmx(_dot_)net
...=> ad infinitum.
I think the problem (in this example) is at pobox.com and/or gmx.net
not with alice(_at_)yahoo(_dot_)com; the problem should be found, recognized and
solved by pobox.com and/or gmx.net
On a qmail system, emails have to hit the .qmail file before being
forwarded. Using procmail or whatever, one can catch loops caused by
bounces and send appropriate notices to alice if desired and stop the
looping.
The SRS stuff looks heavy to put on mxs that may need all the processing
power they've got to deal with bounces floods and what not. Forwarding
and other stuff for existing accounts can all be dealt with on the
second layer where things can be dealt with at a one's leisure
comparatively.
Also, SRS is additional code to add to working mta software and you have
to bite the bullet to see if it works when you could have a solution
with proven tools.
Does one have to implement SRS to deal with SPF? Back to same question I
asked: is SRS the sole solution to forward with SPF implemented?
If the message author is made aware, he/she can take action (send
message again hoping that problem is solved; use a different
communication channel such as the phone; ...)
Please publish your phone number, pager, or whatever other technology
I can use to reach you 24/7. But don't expect me to do the same.
IOW, you cannot rely on this to work and thus have to fix forwarding.
cheers,
Alex
-------
Sender Permitted From: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
Latest draft at http://spf.pobox.com/draft-mengwong-spf-02.9.4.txt
Wiki:
http://spfwiki.infinitepenguins.net/pmwiki.php/SenderPermittedFrom/HomePage
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname(_at_)©#«Mo\¯HÝÜîU;±¤Ö¤Íµø?¡