I think 1 important spfv1 cleanup idea is to warn strongly about sender-id's
mis-appropriation of spfv1 records and syntax
and thus a good spfv1 implementating domain should avoid this via say a minimum
of
example.com v=spf1 redirect=_spf1.%{o}
spf2.0/mfrom redirect=_spfm2.%{o}
spf2.0/pra redirect=_spfp2.%{o}
and having the actual spf1 record under
_spf1 v=spf1 {details}
_spfm2 spf2.0/mfrom (same details)
and i a pra {sender-id} believer use it or if just a SPF believer have
_spfp2 spf2.0/pra ?all
{i personally do a combo like this but use a redirect=%{l}._spf1.%{o} for all
so each user can personalize their use/non-use -all/~all/?all themselves}
all non-existent envelopes get a v=spf1 -all or spf2.0/mfrom,pra -all
and some special cases like mailer-deamon@ have a spf2.0/pra ?all but a v=spf1
-all or spf2.0/mfrom -all
as they never are used in envelope
-------------------------------------------
Sender Policy Framework: http://www.openspf.org
Modify Your Subscription: http://www.listbox.com/member/
Archives: https://www.listbox.com/member/archive/735/=now
RSS Feed: https://www.listbox.com/member/archive/rss/735/
Powered by Listbox: http://www.listbox.com