spf-discuss
[Top] [All Lists]

RE: Email Forwarder's Protocol ( EFP )

2005-02-26 06:56:07

-----Original Message-----
From: owner-spf-discuss(_at_)v2(_dot_)listbox(_dot_)com 
[mailto:owner-spf-discuss(_at_)v2(_dot_)listbox(_dot_)com] On Behalf Of 
Lennon - Orcon
Sent: zaterdag 26 februari 2005 12:18
To: spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
Subject: Re: [spf-discuss] Email Forwarder's Protocol ( EFP )

Another problem (little)

Getting a few of these type of thing..

Feb 26 13:46:55 dbmail-mx4 sm-mta[16402]: j1Q0kopx016402: 
ruleset=check_mail, arg1=<rochelleandpeter(_at_)xtra(_dot_)co(_dot_)nz>, 
relay=[210.54.64.175], reject=451 4.7.1 Please see 
http://spf.pobox.com/why(_dot_)html?sender=rochelleandpeter(_at_)xtra(_dot_)co(_dot_)
nz&ip=210.54.64.175&receiver=dbmail-mx4.orcon.co.nz:DNS 
error while looking up 175.64.54.210.in-addr.arpa PTR:SERVFAIL

It is possible to make SPF not do this checking and allow 
sendmail do it?

As per the specs, rejecting is up to the MTA:

2.5.6  TempError

   A TempError result means that the SPF client encountered a transient
   error when performing the check. Checking software can choose to
   accept or temporarily reject the message. If the message is rejected
   during the SMTP transaction for this reason, the software SHOULD use
   an SMTP reply code of 451 and, if supported, the 4.4.3 DSN code.

Hmmm, I see somewhere along the line we apparently switched to the 4.4.3
("TEMP Routing server failure") Enhanced Status Code, instead of what we
used to have, 4.7.1 ("TEMP Delivery not authorized"). The latter still
seems to make more sense to me (after all, we can temporarily not
authorize the relay). But that is not really relevant now. :)

Since REJECT on TempFail is optional, now, when run with '-ie' (ignore
error) as second parameter, SPF socketmapd will not TEMPFAIL the SPF
TempError result (called 'error' in Mail::SPF::Query). Instead, the
message will be accepted, and you will now get the following Received-SPF
header (in your case):

Received-SPF: error (dbmail-mx4 sm-mta: problematic lookup of
        rochelleandpeter(_at_)xtra(_dot_)co(_dot_)nz allowed by local policy)
        receiver=dbmail-mx4.orcon.co.nz;
        client-210.54.64.175;
        envelope-from=<rochelleandpeter(_at_)xtra(_dot_)co(_dot_)nz>;
        helo=whatever.com;


HISTORY
--------------

26/02/2005:

Behavior-changes: When run with '-ie' (ignore error) as second parameter,
SPF socketmapd will not TEMPFAIL the SPF TempError result (called 'error'
in Mail::SPF::Query).

Code-changes:

- Added code to add extra 'policy' result macro, and an according switch.

- Changes in spf-socketmapd.m4 to H lines and macro settings.

- Changes to Enhanced Status Codes, to be in sync with
draft-schlitt-spf-classic-00.

Bug-fix: Mail::SPF::Query does not actually know PermError; void macro
removed.
--------------

Grab the latest and fastest at:

http://srs-socketmap.info/spf/SPF-socketmapd.0.30.tar.gz

Cheers,

- Mark 
 
        System Administrator Asarian-host.org
 
---
"If you were supposed to understand it,
we wouldn't call it code." - FedEx