I assume the reason people developed new headers like Received-SPF was
to
avoid these problems.
No, Received-SPF has very different information than the Received header.
The only duplicated element is connection IP.
Yes quite different.. this is the type of Received-SPF header I get using
the SPF Socketmap: (testing today)
(Accept from message header)
Received-SPF: pass (dbmail-mx4.orcon.co.nz: domain of
XXXX(_at_)bounces(_dot_)spamcop(_dot_)net designates 64.74.133.248 as
permitted
sender)
receiver=dbmail-mx4.orcon.co.nz;
client-ip=64.74.133.248;
envelope-from=<XXXX(_at_)bounces(_dot_)spamcop(_dot_)net>;
helo=vmx1.spamcop.net;
A rejection from the sendmail logs:
Feb 23 18:45:58 dbmail-mx4 sm-mta[3731]: j1N5joV5003731: ruleset=check_mail,
arg1=<dcknip(_at_)subscribe(_dot_)ru>,
relay=na-148-243-225-194.na.avantel.net.mx
[148.243.225.194] (may be forged), reject=550 5.7.1
<dcknip(_at_)subscribe(_dot_)ru>...
Please see
http://spf.pobox.com/why(_dot_)html?sender=dcknip(_at_)subscribe(_dot_)ru&ip=148.243.225.194&
receiver=dbmail-mx4.orcon.co.nz
The socketmap has lasted (not crashed) a lot longer than the milter type
stuff.
Thanks
Craig