9 messages in net.sourceforge.lists.courier-maildrop[maildropl] Yikes! default rule doesn...
FromSent OnAttachments
up...@3.amApr 23, 2004 9:38 am 
Sean DelkApr 23, 2004 10:01 am 
up...@3.amApr 23, 2004 10:31 am 
up...@3.amApr 23, 2004 11:35 am 
up...@3.amApr 23, 2004 1:11 pm 
up...@3.amApr 24, 2004 6:55 am 
Ron JohnsonApr 24, 2004 9:40 am 
Sam VarshavchikApr 24, 2004 11:31 am 
up...@3.amApr 25, 2004 6:21 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[maildropl] Yikes! default rule doesn't work after upgradeActions...
From:up...@3.am (up@3.am)
Date:Apr 23, 2004 9:38:45 am
List:net.sourceforge.lists.courier-maildrop

I'm running qmail with maildrop as the MDA to filter out Spamassassin tagged messages and give some users custom filtering capabilities. I recently built a new server using the latest everything and Maildrop isn't behaving the way it used to.

in the /etc/maildroprc on the old box (maildrop 1.5.0), I had:

MAILBOX="$HOME/Maildir/"

if ((/^X-Spam-Status: Yes/)) { to "./Maildir/.Spam/." }

-----------

On the old server, this worked fine and still allowed shell users (there are no virtual users on this system, although I run vpopmail for pop auth) to create custom filters that got read after the /etc/maildroprc

After the upgrade (maildrop 1.6.3), local deliveries for non-shell users (for which custom filters obviously don't work) stopped working, so I had to put this in the /etc/maildroprc's last line:

to "./Maildir/."

Which solved that problem, but now none of the local, custom ($HOME/.mailfilter) filters work. What the he/ll did I miss??

TIA!