4 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Re: dot-lock
FromSent OnAttachments
patrick jayetJul 3, 2004 10:14 am 
Sam VarshavchikJul 3, 2004 10:51 am 
patrick jayetJul 3, 2004 3:15 pm 
Devin RubiaJul 5, 2004 9:01 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: dot-lockActions...
From:Devin Rubia (dev@thezone.net)
Date:Jul 5, 2004 9:01:38 am
List:net.sourceforge.lists.courier-maildrop

On Sun, Jul 04, 2004 at 12:17:17AM +0200, patrick jayet wrote:

maildrop is attempting to deliver to an mbox file, not a maildir, and is unable to create a dot-lock file.

I don't think so, because the problem doesn't appears from the beginning. Maildrop can deliver mails for a while to the different maildirs (according the rules) but then after a few hours or 1/2 days, I get that message about the dot-lock. So I suppose that it delivers alright to the maildirs.

You must determine what part of your mail filter is responsible for the delivery instruction, and fix it accordingly.

I don't see in the mailfilter file from where the problem could come. I have done some test with e-mails and the different filter instructions have done their job without problem. [SNIP] if (/^Subject: linux/) to $MAILBOX/.infos.linux/

if (/^Subject: Cron /) to Maildir/.Cron/

[SNIP]

That last one there is different. Should it be:

to $MAILBOX/.Cron/

perhaps?