Re: [maildropl] Yikes! default rule doesn't work after upgrade - up...@3.am - net.sourceforge.lists.courier-maildrop

9 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Yikes! default rule d...

From	Sent On	Attachments
up...@3.am	Apr 23, 2004 9:38 am
Sean Delk	Apr 23, 2004 10:01 am
up...@3.am	Apr 23, 2004 10:31 am
up...@3.am	Apr 23, 2004 11:35 am
up...@3.am	Apr 23, 2004 1:11 pm
up...@3.am	Apr 24, 2004 6:55 am
Ron Johnson	Apr 24, 2004 9:40 am
Sam Varshavchik	Apr 24, 2004 11:31 am
up...@3.am	Apr 25, 2004 6:21 am

	Permalink for this message Paste this link in email or IM:
	Permalink for this thread Paste this link in email or IM:
	Atom feed for this thread Paste this URL into your reader:

Subject:	Re: [maildropl] Yikes! default rule doesn't work after upgrade	Actions...
From:	up...@3.am (up...@3.am)
Date:	Apr 23, 2004 10:31:53 am
List:	net.sourceforge.lists.courier-maildrop

On Fri, 23 Apr 2004, Sean Delk wrote:

When you put the to "./Maildir/." line in the maildroprc file, all filtering stops because the mail has been delivered.

I understand that.

So the users' filters are ignored with your setup. You need to figure out why it wasn't working without that line in your maildroprc file.

That's basically my question. I'm trying to figure out whether or not something changed in the newer version of maildrop that would affect the default delivery. There are no .qmail files in the userdirs, because that caused maildrop to be ignored in the past. qmail is being invoked like this:

exec env - PATH="/var/qmail/bin:$PATH" \ qmail-start '|preline maildrop' splogger qmail

There are also no errors that I can see in the logs.

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!

	Start a set with this search
	Include this search in one of my sets
	Exclude this search from one of my sets
	Permalink to these results Paste this link in email or IM:
	Atom feed for tracking future search results Paste this URL into your reader: