> > http://spf.pobox.com/
> - Assuming your mail server supported it, who wouldn't want SPF
> protected turned on?
I consider some things about SPF objectionable. It makes mobile e-mail more
difficult, especially with some loose ends surrounding it. It makes
assumptions like "all up-to-date ISPs support [SASL] on the server end." It
effectively requires @apache.org addresses to be sent via the ASF mail
server. Forwarding your @apache.org address would require the server to
perform Sender Rewriting (which is a bit of a mess), and parsing in the
event of a bounce. I'm not thrilled about the runtime overhead of having to
parse TXT records for SPF content (see Appendix B.3 for some examples).
That said, SPF does have potential, particularly given the extension
mechanism. I will find it more interesting when domain keys were supported,
since those would be sufficient for most cases, support mobile workers, and
could eliminate the need to rewrite the sender. And I would like to see the
parsing requirements reduced.
> - Does it have to reject during the SMTP connection, or can you
> accept and then reject?
You can accept and then reject.
> - If an SPF test failed (connection from server a.b.c.d that does not
> meet my lokitech.com SPF rule), would I still accept email with a
> from of lokitech.com, i.e., a domain this mail server handles locally?
SPF is applied to MAIL FROM. Would you want to accept
MAIL FROM: <[EMAIL PROTECTED]>
RCPT TO: <[EMAIL PROTECTED]>
if the sending machine were not valid for lokitech.com?
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
