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.
Under [1] my config file for .mailfilter
Have a nice week-end. :o)
Patrick
[1]
# shell to exec the commands
SHELL="/bin/bash"
MAILBOX="$HOME/.maildir"
DEFAULT="$MAILBOX"
logfile "$HOME/.maildrop/maildrop.log"
### run spamassassin and virus detection
xfilter "/usr/bin/spamc"
xfilter "/usr/local/bin/virusscan"
### filters
if (/^Subject: .*\[gull\]/)
to $MAILBOX/.infos.gull/
if (/^To: .*lin...@lugs.ch/)
to $MAILBOX/.info.lugs/
if (/^Subject: info:/)
to $MAILBOX/.infos/
if (/^Subject: linux/)
to $MAILBOX/.infos.linux/
if (/^Subject: Cron /)
to Maildir/.Cron/
### spam
if (/^X-Spam-Flag: Yes/)
to $MAILBOX/.Junk/
### files with virus to Infected folder
if (/^X-Virus: Yes/)
to $MAILBOX/.Infected/
4 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Re: dot-lock
