On Mon, 22 Dec 2003 14:31:48 -0600 (CST)
Joe Laffey <jo...@laffeycomputer.com> wrote:
On Mon, 22 Dec 2003, Mirko Zeibig wrote:
On Sun, Dec 21, 2003 at 09:18:39PM -0500, Eric Livingston wrote:
Simple question, but one I can't seem to find a direct answer to:
How do you send a message into the abyss using .mailfilter rules?
I use SpamAssassin, and would like to auto-delete messages with
scores over a certain threshold.
Is "to /dev/null" the best bet, or is there some explicit action?
I've noticed that some other mail processors have "drop" actions
that explicitly kill a message - does maildrop?
Hello Eric,
I struggled with this as well a while ago, sending mails to
/dev/null will not work. Instead I have sth. like this in my
.mailfilter: if ( /^X-Spam-Level: \*\*\*\*\*\*\*\*/ )
{
EXITCODE=99
exit
}
I am wondering why my rule below is still delivering the spam BOTH to
the Maildir I specify as a cc (to collect spam for bayesian feeding)
AND to the original user's maildir:
if ( /^X-Spam-Level:
\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*/ ){
log "%% Utter spam rejected %%"
cc "/home/mail/spam/Maildir"
EXITCODE=99
exit
}
Shouldn't the mailfilter exit and NOT deliver to the default Maildir?
I see the log message above in the log.
I suppose it should, but I wander WHY delivering to /dev/null does not
work for you.
I have in my ".mailfilter"
-=-
# [EMAIL PROTECTED]
# SpamAssassin client called only if msgsize < 256kB
if ( $SIZE < 262144 )
{
exception {
xfilter "/usr/bin/spamc"
}
}
if ( /^X-Spam-Flag: *YES/ )
{
exception {
to "Maildir/.zspam/"
}
}
if ( /^Subject.*Cron <news@lothlorien>/ )
{
exception {
to /dev/null
}
}
The cron email vanishes into the nothingness ;-))
5 messages in net.sourceforge.lists.courier-usersRe: [courier-users] How to correctly ...
