9 messages in net.sourceforge.lists.courier-maildrop[maildropl] Problem with maildroprc a...
FromSent OnAttachments
AdminMar 3, 2004 12:40 pm 
Devin RubiaMar 3, 2004 1:04 pm 
Sam VarshavchikMar 3, 2004 3:54 pm 
AdminMar 4, 2004 9:52 am 
Jeremy KitchenMar 4, 2004 10:05 am 
AdminMar 4, 2004 10:10 am 
Brook HumphreyMar 4, 2004 10:16 am 
AdminMar 4, 2004 10:34 am 
Brook HumphreyMar 4, 2004 12:39 pm 
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] Problem with maildroprc and Postfix virtual usersActions...
From:Admin (adm@gcmuni.net)
Date:Mar 3, 2004 12:40:47 pm
List:net.sourceforge.lists.courier-maildrop

I've got Postfix setup with virtual users in a MySQL database. Maildrop is the transport. Everythign works fine, mail is delivered likes it's supposed to be.

I would like to have a filter that puts all mail marked as "spam" (via SpamAssassin/Amavisd-new) to be delivered to a "Junk Mail" folder in each users maildir.

The problem is the maildroprc file. As it is now, each users can create (via Squirrelmail plugin) their own .mailfilter file, which works. However, my maildroprc file seemingly DOES NOT process the "if" statements.

Here's my maildroprc:

if (/^X-Spam-Status: Yes/)

{ to "$HOME/.Junk Mail" }

What happens is, ALL mail is delivered to the Junk Mail folder. It's as if the if statement is being completely ignored. I tested this theory by replacing the "X-Spam-Status" stuff with garbage text, and the same thing still happens- all mail goes to Junk Mail.

So, in a nutshell, why won't if statements get processed in my maildroprc file? Or is it something else?

Thanks, Sean Delk