Julian Mehnle wrote:
In which way?  Could you please describe an abstract requirements
scenario which cannot be satisfied by SPF?

Sure.


I connect my work machine to my home Earthlink network.

Since the only machine whose port 25 I am alowed to talk to is smtp.earthlink.net, I connect to it.

My client sends to it:
MAIL FROM:<[EMAIL PROTECTED]>
RCPT TO:<[EMAIL PROTECTED]>

smtp.earlink.net connects to smtp.fardomain.com and says:
EHLO smtp.earthlink.net
MAIL FROM:<[EMAIL PROTECTED]>

...but it's not SPF'd for workdomain.com, of course.

BTW, as far as I understand it, Yahoo's scheme is not about
certificates which need to be trusted.  It's about checking mail
"signatures" which could only possibly have been generated by the
sending domain's owner.

Right -- mechanisms for the attachment of which can be passed to the user, such that the user can sign mail not as "I am Joe Blow" but "I am a legitimate user of domain X".



------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to