On Friday 17 October 2003 01:56, Meng Weng Wong wrote:
Yeah, I hate sender rewriting too. Is there a better way?
I will try to put some thought into this over the next few days. But, at the
moment, the following argument seems reasonable (some will hate this too
though!)
When do we hit the forwarding problem?
1) mailing lists
2) .forward files / relayed mailboxes
3) ?
Mailing-lists SHOULD be configured so that the sender is the list itself, so
if it is properly configured, this shouldn't be a problem - no rewriting
required. SPF is simply enforcing best practice.
Could we not treat .forward generated email the same way?
Rational:
jane(_at_)test(_dot_)com sends an email to fred(_at_)bigfoot(_dot_)com
bigfoot.com accepts the mail, because fred(_at_)bigfoot(_dot_)com is a valid
account.
from this point on, bigfoot.com has accepted the responsibility of delivering
email. (so far, exactly the same as a list-manager)
But when bigfoot.com forwards the email, who is sending it?
At the moment, bigfoot.com says :
HELO mail.bigfoot.com
MAIL FROM: jane(_at_)test(_dot_)com
RCPT TO: fred(_at_)forward(_dot_)domain
But logic says Jane ISN'T sending the email. it might be FROM: jane, but the
sender is, in fact, maildaemon(_at_)bigfoot(_dot_)com(_dot_)
which, of course, would then pass the SPF check.
It would take me 2 minutes to implement this change on my system, if required.
Questions: Are there any other situations where mail is forwarded that don't
fit into the above 2 cases? Would this change break anything that currently
exists?
-------
Sender Permitted From: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname(_at_)©#«Mo\¯HÝÜîU;±¤Ö¤Íµø?¡