Gentle friends,
We're running SpamAssassin 2.53 on a FreeBSD server in conjunction
with omail-admin-1.0 and qmail-scanner-1.15. One of our customers is
having a problem whitelisting a sender's address, i.e., mail is
tagged as spam in spite of a whitelist entry for the sender,
[EMAIL PROTECTED
rule out the problems being
caused by the brand-new 2.31 version.
In the meantime, do any of you folks have any explanations for the
problems I'm seeing that do not involve the supernatural?
.\\ichelle
-
Michelle Brownsworth
System Administrator
PrimeLogic Corporation
http://www.primelogic
il recipes, you need
>something like
>
> formail -s procmail /home/$username/.procmailrc < /var/log/spam/$file
>
>(replacing /home/$username with the appropriate path).
Yes, the following did the trick:
($< = $>) = $uid; # Set process to run as recipient f
ist and how to remove
an entry.
.\\ichelle
----
Michelle Brownsworth
System Administrator
Willamette.Net
http://www.willamette.net
Phone (541) 465-3282
Fax (541) 465-1194
___
Don't miss the 2002 Sprint PCS Appli
m, just as it should, but non-spam is not being
delivered to /var/mail/mdb as the procmail.log entry above indicates.
And the mailbox is being zeroed out to boot.
However, the test filter identifies and redirects test messages as it
should and allows non-test mail to pass:
:0:
* ^Subject:.*test
