9 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Re: Yikes! default ru...
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:Re: [maildropl] Re: Yikes! default rule doesn't work after upgradeActions...
From:up...@3.am (up@3.am)
Date:Apr 25, 2004 6:21:41 am
List:net.sourceforge.lists.courier-maildrop

On Sat, 24 Apr 2004, Sam Varshavchik wrote:

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?

It's in the "variable substitution" section. I must have just misunderstood what "predefined" meant, which I took as "I don't need to define it or invoke it". In any case, either it worked on the older version, or something else was telling maildrop that default delivery was to a users Maildir.

In any case, switching to the "DEFAULT" predefined variable worked great.

Thanks!

James Smallacombe PlantageNet, Inc. CEO and Janitor up@3.am http://3.am =========================================================================