--On Sonntag, November 12, 2006 16:40:20 -0500 "Stuart D. Gathman"
<stuart(_at_)bmsi(_dot_)com> wrote:
On Sun, 12 Nov 2006, Ralf Doeblitz wrote:
I don't think this would be the best solution. The exist mechanism
combined with macro expansion can almost do the job. All that would be
But he is the *receiving* (RCPT TO) domain, not the sending domain.
He has no control over the senders SPF record. The sender has no idea
what his personal forwarding setup is.
The receiving system must include a local whitelist. With the mentioned
extensions, you can then expand to names in the receivers namespace so that
he can configure by himself which forwarders to trust for *his* address.
The admin of the receiving MX onyl has to enter the whitelist entry with
the macro once instead of once per customer/localpart/forwarder.
Ralf Döblitz
-------
Sender Policy Framework: http://www.openspf.org/
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/?list_id=735