Doc updates
This commit is contained in:
+1
-1
@@ -14,7 +14,7 @@ by <a href="http://barry.wooz.org/">Barry Warsaw</a>. The mascot
|
||||
is by <a href="http://alphard.ethz.ch/hafner/lebl.htm">Christian Hafner</a>,
|
||||
or maybe his wife. I chose Maxwell's daemon because it tirelessly
|
||||
and invisibly sorts molecules, just as milters sort mail.
|
||||
Cristian has also provided a fun
|
||||
Christian has also provided a fun
|
||||
<a href="http://alphard.ethz.ch/hafner/PPS/PPS2002/Maxwell/simulation.htm">
|
||||
simulation</a> that lets you try your hand at sorting molecules.
|
||||
|
||||
|
||||
+12
-6
@@ -99,13 +99,14 @@ If you are running bms.py, then the block_chinese option in
|
||||
|
||||
<li> Q. Why does sendmail coredump with milters on OpenBSD?
|
||||
<p> A. Sendmail has a problem with unix sockets on old versions of OpenBSD.
|
||||
Use an internet domain socket instead. For example, in
|
||||
OpenBSD users report that this problem has been fixed, so upgrading
|
||||
OpenBSD will fix this. Otherwise, you can
|
||||
use an internet domain socket instead. For example, in
|
||||
<code>sendmail.cf</code> use
|
||||
<pre>
|
||||
Xpythonfilter, S=inet:1234@localhost
|
||||
</pre>
|
||||
and change sample.py accordingly.
|
||||
<p> OpenBSD users report that this problem has been fixed.
|
||||
<p>
|
||||
|
||||
<li> Q. How can I change the bounce message for an invalid recipient?
|
||||
@@ -139,10 +140,15 @@ Xpythonfilter, S=local:/var/log/milter/pythonsock, F=T, T=C:5m;S:20s;R:60s;E:5m
|
||||
</pre>
|
||||
<li> Q. There is a Python traceback in the log file! What happened to
|
||||
my email?
|
||||
<p> A. When the milter fails with an untrapped exception, a TEMPFAIL
|
||||
result (451) is returned to the sender. The sender will then retry every
|
||||
hour or so for several days. Hopefully, someone will notice the
|
||||
traceback, and workaround or fix the problem.
|
||||
<p> A. By default, when the milter fails with an untrapped exception, a
|
||||
TEMPFAIL result (451) is returned to the sender. The sender will then retry
|
||||
every hour or so for several days. Hopefully, someone will notice the
|
||||
traceback, and workaround or fix the problem. Beginning with milter-0.8.2,
|
||||
you can call <code>milter.set_exception_policy(milter.CONTINUE)</code>
|
||||
to cause an untrapped exception to continue processing with the
|
||||
next callback or milter instead. For
|
||||
completeness, you can also set the exception policy to
|
||||
<code>milter.REJECT</code>.
|
||||
|
||||
<li> Q. I read some notes such as "Check valid domains allowed by internal
|
||||
senders to detect PCs infected with spam trojans." but could not
|
||||
|
||||
+2
-1
@@ -5,7 +5,8 @@ DT { font-weight: bolder; padding-top: 1em }
|
||||
|
||||
<h1> Milter Log Documentation </h1>
|
||||
|
||||
The milter log has a variety of "tags" in it that indicate what it did.
|
||||
The milter log from the bms.py application has a variety of "tags" in it that
|
||||
indicate what it did.
|
||||
|
||||
<dl>
|
||||
<dt> DSPAM: honeypot SCREENED
|
||||
|
||||
@@ -2,6 +2,11 @@ Title: Python Milter Mail Policy
|
||||
|
||||
<h1> Python Milter Mail Policy </h1>
|
||||
|
||||
These are the policies implemented by the <code>bms.py</code> milter
|
||||
application. The milter and Milter modules do not implement any policies
|
||||
by themselves. Eventually, I'll get the bms.py milter moved to its
|
||||
own package.
|
||||
|
||||
<h3> Classify connection </h3>
|
||||
|
||||
When the SMTP client connects, the connection IP address is
|
||||
|
||||
+2
-2
@@ -7,13 +7,13 @@ Title: Requirements
|
||||
want to use python 2.0 or better. The python code uses a number of
|
||||
python 2 features. The email support requires python 2.4.
|
||||
<li> Python must be configured with thread support. This is because
|
||||
sendmail's libmilter requires thread support.
|
||||
pymilter uses sendmail's libmilter which requires thread support.
|
||||
<li> You must compile sendmail with libmilter enabled. In versions of
|
||||
sendmail prior to 8.12 libmilter is marked FFR (For Future Release) and
|
||||
is not installed by default.
|
||||
Sendmail 8.12 still does not enable libmilter by default. You must
|
||||
explicitly select the "MILTER" option when compiling.
|
||||
<li> Python milter has been tested against sendmail-8.11 and sendmail-8.12.
|
||||
<li> Python milter has been tested against sendmail-8.11 through sendmail-8.13.
|
||||
<li> Python milter must be compiled for the specific version of sendmail
|
||||
it will run with. (Since the result is dynamically loaded, there could
|
||||
conceivably be multiple versions available and selected at startup - but
|
||||
|
||||
Reference in New Issue
Block a user