2 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Maildrop command outp...
FromSent OnAttachments
Sérgio A P FerreiraJun 22, 2005 1:55 pm 
moussJun 23, 2005 12:13 pm 
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] Maildrop command output errorActions...
From:mouss (use@free.fr)
Date:Jun 23, 2005 12:13:51 pm
List:net.sourceforge.lists.courier-maildrop

Sérgio A P Ferreira wrote:

Maildrop show me this:

*//**//**/ Jun 22 17:31:46 gaia postfix/pipe[3301]: 40C044C0E0: to=<ser@cultura.gov.br>, relay=maildrop, delay=0, status=deferred (temporary failure. Command output: /usr/bin/maildrop: Unable to open mailbox. )/**//**//*

leave postfix for a moment, and try to make maildrop work using the command line. something like: maildrop -V 6 -d foo@domain.example < msg.eml run this both as root and as the user you configured in master.cf.

It is probable that your mysql lookup doesn't return the right maildir. put DEBUG_LOGIN=2 in your authdaemonrc and restart authdaemon. you should then have lookup infos in your logs.

I belive it´s a permission problem. I check permissions on maildropmysql.config, maildroprc, .mailfilter and Mailbox home directory. Every thing seems to be fine, but itsn´t.

Most of the time, the wrong maildir is being used, and until you know which one is used, you can't fix it and we can't help you.

first find where it is trying to write. things like (added in your maildroprc) `echo $DEFAULT > /tmp/md.out` should tell you where it needs to write, and things like `echo blahblah > $DEFAULT/foo 2> /tmp/md.err` should tell you why it can't.

I have made some permissions changes... sometimes neither erros logs come out.

Somebody know how to fix it???

Thanks for while,

***Sérgio Ferreira*****