-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Philip Gladstone wrote:
Can I get a test case added to the SPF test suite that deals with the
problematic situation in my SPF record.
In particular I have the following piece:
-exists:%{i}.%{l1r-}.user.%{d}
In practice the %{l1r-} causes problems for some implementations -- I
can see from my DNS logs that they map a local part of 'philip' into
'hilip'. This is wrong. [This piece of SPF is actually quite effective
at eliminating spammers who guess incorrect userids in my domain]
This bug exists at at least two distinct sites (both of which are mail
forwarding sites handling personal domains) so I suspect that there is
a common implementation with this as a defect.
We can add a test case to the test suite easily, however trying to
identify the MTA software running on those broken sites may of more
immediate use. Maybe we can guess the SPF implementations used by them
and try to get them fixed directly?
What MTAs are they running? Does their SMTP signature (e.g. the welcome
message) give any hints?
Julian.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHV+CFwL7PKlBZWjsRAmOBAKDTxgnDYWiE9R+l52G4P4nZUa7XqgCdHvT/
tEm5g7nbmnWFWAof0fKVW30=
=+LnG
-----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=73120781-c6a20f
Powered by Listbox: http://www.listbox.com