Don,Thanks for your reply. I don't see how it helps, however, so could you please bear with me and run through the questions I've raised below?
I mailed a simple e-mail to myself and it was scanned. Why? Everything >I can find on the web says that by default this e-mail should not be scanned >but it is, look at the headers:By default spamass-milter has a /etc/default/spamass-milter which has a -i 127.0.0.1, which will not scan mail sent from the localhost. However, as you've edited spamass-milter's configuration file, this is no longer the case.
From the man page:
-i networks
Ignores messages if the originating IP is in the network(s)
listed.
It does not say "but only if you don't change the default configuration
file". According to the man page if I have -i 127.0.0.1 it should not
scan from the localhost. I don't see how the fact that I've changed the
configuration file would break anything.
>-- Configuration Files: >/etc/default/spamass-milter changed: >OPTIONS="-u spamass-milter -i 127.0.0.1 -i 192.168.1.0/8 -i 208.113.207.5 -i 208.113.189.44 -r 8 -I" >SOCKET="inet:10783@127.0.0.1" >SOCKETMODE="" >SOCKETOWNER="" >OPTIONS="-r 6"You want OPTIONS="$OPTIONS -r 6" or similar. [Or better, just delete this line, and change the -r 8 above it to -r 6.]
I don't understand this either. How does changing the -r level prevent scanning of locally sourced e-mails? According to the man page -r is to do the the rejection level, it has nothing to do with white-listing the localhost.
If fixing that doesn't address this bug, feel free to reopen.
Re-opening. Regards, -Nigel
smime.p7s
Description: S/MIME Cryptographic Signature
