On 10/12/06, Bowie Bailey <Bowi...@buc.com> wrote:
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.
Of course you are right. When I changed the file to deliver the
message directly to the folder "Spam", I did not change the brackets.
Even though the block is superfluous I find that it slightly improves
readability.
Best regards
Marcus
9 messages in net.sourceforge.lists.courier-usersRe: [courier-users] maildrop/.mailfil...
