Release 0.8.3

This commit is contained in:
Stuart Gathman
2005-10-12 16:36:30 +00:00
parent ace3e13685
commit ea82d6d608
8 changed files with 276 additions and 13 deletions
+21 -6
View File
@@ -93,23 +93,38 @@ string blocking.
The sendmail access file, or another readonly database with that
format, can be used for detail spf policy. SPF access policy
record are tagged with "SPF-{Result}:". Results are
Pass, Neutral, Softfail, Fail, TempError, PermError. Currently supported
policy keywords are OK, CBV, REJECT, TEMPFAIL, ERROR:"550 description".
Pass, Neutral, Softfail, Fail, PermError. Currently supported
policy keywords are OK, CBV, REJECT. Currently, TempError always
results in TEMPFAIL.
The default policies are as follows:
The default policies are set in pymilter.cfg. The defaults
if none of the config options are set are as follows:
SPF-Fail: REJECT
SPF-Softfail: CBV
SPF-Neutral: OK
SPF-PermError: REJECT
SPF-TempError: TEMPFAIL
SPF-Pass: OK
The tag may be followed by a specific domain. For instance, to
require a Pass from aol.com:
SPF-Neutral:aol.com ERROR:"550 AOL mail must get SPF PASS"
SPF-Softfail:aol.com ERROR:"550 AOL mail must get SPF PASS"
SPF-Neutral:aol.com REJECT
SPF-Softfail:aol.com REJECT
The CBV policy requires a valid HELO name. If the EHLO name is
RFC2822 compliant, then a DSN is sent to the alleged sender. The
template for the DSN is selected according to the SPF result:
Fail: softfail.txt
SoftFail: softfail.txt
Neutral: neutral.txt
PermError: permerror.txt
None: strike3.txt
Pass: strike3.txt
The pass template doesn't make any sense - I assumed that CBV would
never be used with a Pass result.
To be continued.