The 451 softfail response probably came from rfc 4408 section 2.5.5:
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.
so according to this it is suggested to handle spf results as:
spf pass -> further processing without greylisting (2xx)
spf softfail -> respond with greylisting test, if there is a 2nd try (passes
greylisting test) -> further processing
spf fail -> reject mail (5xx)
But since assp handles greylisting before spf-validation it has no use to
delay the message again.
Anyway, I also see no use for a softfail-error setting, only a use for
options to intentionally fail spf-softfail and spf-neutral transactions
which would mean using the spf-failed reply instead of accepting...
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Assp-user mailing list
Assp-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-user
