9 messages in net.sourceforge.lists.courier-usersRe: [courier-users] maildrop/.mailfil...
FromSent OnAttachments
Stephen ReeseOct 10, 2006 8:17 pm 
Marcus IlgnerOct 11, 2006 12:51 am 
Stephen ReeseOct 11, 2006 6:30 pm 
Marcus IlgnerOct 12, 2006 7:13 am 
Bowie BaileyOct 12, 2006 7:41 am 
Mark ConstableOct 12, 2006 7:46 am 
Bowie BaileyOct 12, 2006 7:55 am 
Marcus IlgnerOct 12, 2006 8:19 am 
Mark ConstableOct 12, 2006 9:12 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: [courier-users] maildrop/.mailfilter questionActions...
From:Bowie Bailey (Bowi@BUC.com)
Date:Oct 12, 2006 7:55:16 am
List:net.sourceforge.lists.courier-users

Mark Constable wrote:

On Friday 13 October 2006 00:41, Bowie Bailey wrote:

Unless I'm missing something... Isn't that last 'else' block completely unnecessary? As I understand it, maildrop works like this:

- Process maildroprc file - Process $HOME/.mailfilter - Deliver to $HOME/Maildir

I thought it was... ?

- Process $HOME/.mailfilter - Process maildroprc file - Deliver to $HOME/Maildir

No, the maildroprc is processed first. If it specifies a delivery, it will override anything in the $HOME/.mailfilter files.

Here's the relevant part of the man page:

If the file /etc/courier/maildroprc exists, mail delivery or mail filtering instructions are read from that file. maildrop's delivery/filtering instructions may direct maildrop to save the message in specific mailbox, discard it, return it to sender, or forward it to a different E-mail address.

If /etc/courier/maildroprc does not exist, or its mail delivery instructions do not completely dispose of this message, maildrop then reads the mail delivery instructions from $HOME/.mailfilter. If it doesn't exist, or its mail delivery instructions do not completely dispose of the message, maildrop then saves the E-mail message in the default mailbox.

-- Bowie