Milter-greylist

--- In milter-greylist@yahoogroups.com, Benoit Branciard 
<benoit.branciard@...> wrote:
>
> manu@... a écrit :
> > 
> > 
> > Jim Hermann <hostmaster@... <mailto:hostmaster%40uuism.net>> 
wrote:
> > 
> >  > I can wait for the SPF upgrade to all the possible statuses. I
> >  > don't think it is a good idea to lump several statuses into 
one
> >  > status called fail. A SOFTFAIL is entirely different than a 
hard
> >  > FAIL.
> > 
> > What is a softfail? Is it just that you failed to obtain the SPF 
record?
> > (ie: DNS failure)
> 
> This would be "TempError".
> The "SoftFail" result indicates the sender host should not be 
> authorized, but not as categorically as a "Fail". This is matched 
bu a 
> "~" entry in the SPF record. Cf. 
http://www.openspf.org/RFC_4408#op-result.
>

The possible results are:

2.5. Interpreting the Result
2.5.1. None
2.5.2. Neutral
2.5.3. Pass - We also want PassAll for spammers who use +all
2.5.4. Fail
2.5.5. SoftFail - is often used for testing
2.5.6. TempError
2.5.7. PermError

2.5.5. SoftFail
A "SoftFail" result should be treated as somewhere between a "Fail" 
and a "Neutral". The domain believes the host is not authorized but 
is not willing to make that strong of a statement. Receiving 
software SHOULD NOT reject the message based solely on this result, 
but MAY subject the message to closer scrutiny than normal.

The domain owner wants to discourage the use of this host and thus 
desires limited feedback when a "SoftFail" result occurs. For 
example, the recipient's Mail User Agent (MUA) could highlight 
the "SoftFail" status, or the receiving MTA could give the sender a 
message using a technique called "greylisting" whereby the MTA can 
issue an SMTP reply code of 451 (4.3.0 DSN code) with a note the 
first time the message is received, but accept it the second time.

Jim