9 messages in net.sourceforge.lists.courier-maildrop[maildropl] Re: Yikes! default rule d...
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] Re: Yikes! default rule doesn't work after upgradeActions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Apr 24, 2004 11:31:40 am
List:net.sourceforge.lists.courier-maildrop

up@3.am writes:

After more testing, I've narrowed it down a bit. If the user has a .mailfilter file with default delivery instructions, regardless of whether they have a shell or not, the mail gets delivered. The question then becomes, why doesn't maildrop deliver to Maildir if we don't tell it to as the last filter instruction? The first line in /etc/maildroprc is: MAILBOX="$HOME/Maildir/"

Where do you see "MAILBOX" in the "predefined variables" section of the maildropfilter manual page?

The only thing you will find there is this:

DEFAULT The default mailbox to deliver the message to. If the filter file does not indicate a mailbox to deliver this message to, the message is delivered to this mailbox. The default mailbox is defined by the system administrator.