-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Alessandro Vesely wrote:
I've read some posts on this list about SOFTFAIL. I agree with
most of them saying it is a debugging feature. As such, it
leaves something to be desired, doesn't it? I'd propose the
following addition:
If example.com says "~ip4:1.2.3.4", then a receiving server
should send a DSN to postmaster(_at_)example(_dot_)com saying something
like
Hey,
someone did actually manage to send a message from 1.2.3.4
Here are the relevant headers...
Nearly a breakpoint, isn't it?
Possibly a mandatory string (e.g. "SPF: SOFTFAIL") either in the
subject or in some other header may help postmasters to properly
collect their debug messages.
Besides my dislike for mandating receiver policy, I think mandating
receivers to send DSNs (delivery status notifications AKA bounces, for
those who don't know the acronym) is a particularly touchy issue.
However I do like the idea of making it more clear that the ~ qualifier is
supposed to be a testing tool, not a permanent band-aid for SPF's alleged
"forwarding problem" as many domain owners seem to think.
I just can't see how to introduce new semantics into SPFv1 (e.g. by adding
a "testing=yes" modifier and _deprecating_ the ~ qualifier), given that
there are about half a dozen stable open implementations of the "classic"
SPFv1 and probably dozens of proprietary ones hidden in commercial
software. Most of the existing implementations will probably NEVER be
changed to adopt those new semantics.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHf2x3wL7PKlBZWjsRAnkxAJ95ToE2QDGIxzHZ6dKXv40yqWRT9gCgtBBH
nY3NdGnPVneUb4Htibk+2mg=
=wRuO
-----END PGP SIGNATURE-----
-------------------------------------------
Sender Policy Framework: http://www.openspf.org
Archives: http://v2.listbox.com/member/archive/735/=now
RSS Feed: http://v2.listbox.com/member/archive/rss/735/
Modify Your Subscription:
http://v2.listbox.com/member/?member_id=2183229&id_secret=82137501-24a418
Powered by Listbox: http://www.listbox.com