At any rate, I added a few lines to SPF socketmap to prevent any SPF stuff
being done when the domain does not exist/does not resolve; and you can
find the updated version at:
http://srs-socketmap.info/spf/SPF-socketmapd.0.28.tar.gz
Updated now..
and correctly..
Feb 23 22:50:50 dbmail-mx4 sm-mta[25208]: j1N9omeF025208:
ruleset=check_mail, arg1=<curtm(_at_)wrldnet(_dot_)net>, relay=[210.221.37.156],
reject=553 5.1.8 <curtm(_at_)wrldnet(_dot_)net>... Domain of sender address
curtm(_at_)wrldnet(_dot_)net does not exist
and
Feb 23 22:51:20 dbmail-mx4 sm-mta[25651]: j1N9pI6R025651:
ruleset=check_mail, arg1=<myfcwc(_at_)check1check(_dot_)com>,
relay=c-24-99-119-123.atl.client2.attbi.com [24.99.119.123], reject=550
5.7.1 <myfcwc(_at_)check1check(_dot_)com>... Please see
http://spf.pobox.com/why(_dot_)html?sender=myfcwc(_at_)check1check(_dot_)com&ip=24.99.119.123&receiver=dbmail-mx4.orcon.co.nz
but (dunno if this is broken or what)..
an email came thru
Had:
Return-path: SRS0=PtJo=RF=XXX(_dot_)XXX=YYY(_at_)bounce2(_dot_)pobox(_dot_)com
Received-spf: none (integer.pobox.com: domain of XXX(_at_)ZZZZZ does not
designate permitted sender hosts)
X-SPF-Guess: pass (seems reasonable for XXXX(_at_)YYY to mail through K.K.K.K)
I presume it already had a Recieved-spf header in it.. so it won't add
another one like you said in a few emails before.
Better to make it add X-Received-SPF at the moment on this side (or hack the
sendmail source?)
1 more thing..is there _anyway_ to make sendmail continue its job
processing email if the socketmap perl program dies.. it doesn't like it
when it does and will not access emails at all :-(
ThanksCraig