spf-discuss
[Top] [All Lists]

Re: Re: change of version string

2004-08-07 14:02:24
On Sat, 2004-08-07 at 06:35, Frank Ellermann wrote:
John Glube wrote:

I am not going to raise this over at MARID as I view this
as an internal SPF issue.

Tnx anyway, it's all very confusing.  I don't understand why
MARID doesn't simply publish a RfC for classic SPF MAIL FROM
tests based on draft-ietf-marid-protocol-00.txt (or rather
its next version with some minor technical fixes).

*cough* Microsoft *cough*

Based on SPF classic it could be easy to define a visible PRA
for MUAs:  If (one of) the From: address(es) matches the
MAIL FROM, then that's it.  Otherwise if the Sender: address
matches that's it.  Otherwise try Resent-From: etc. (we could
even add To: / Cc: for wayne 's private forwarding scenario).

If nothing matches and there's no Sender: then treat MAIL FROM
as "PRA".  Otherwise MUAs should warn users, they could still
display the Return-Path as PRA.

If the MAIL FROM passed a classic SPF test by the MDA (or MX)
MUAs can display the PRA as verified.  Otherwise they display
the PRA as unverified.  That's already possible today, if the
MDA (or MX) inserted a Received-SPF header as defined in the
classic draft-mengwong-spf-01.txt

Caller-Id / Unified / Sender-Id / SUBMITTER are not necessary
to determine and display a verified PRA in a MUA without DNS.

IMHO Not only are they NOT necessary, they are convoluted with terrible
and useless ideas as an attempt to integrate patented technology within
the core of the internet, or something like that.  I mean honestly much
of it is so stupid, what other possible reason could there be?

Cheers,

James

-- 
James Couzens,
Programmer
                                                     ( ( (      
      ((__))         __lib__        __SPF__        '. ___ .'    
       (00)           (o o)          (0~0)        '  (> <) '    
---nn-(o__o)-nn---ooO--(_)--Ooo--ooO--(_)--Ooo---ooO--(_)--Ooo---

http://libspf.org -- ANSI C Sender Policy Framework library
http://libsrs.org -- ANSI C Sender Rewriting Scheme library
-----------------------------------------------------------------
PGP: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7A7C7DCF

-------
Sender Policy Framework: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
http://www.InboxEvent.com/?s=d --- Inbox Event Nov 17-19 in Atlanta features 
SPF and Sender ID.
To unsubscribe, change your address, or temporarily deactivate your 
subscription, 
please go to 
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com

Attachment: signature.asc
Description: This is a digitally signed message part