8 messages in net.sourceforge.lists.courier-maildrop[maildropl] How to debug a broken mai...
FromSent OnAttachments
David BorehamDec 9, 2002 12:11 pm 
Sam VarshavchikDec 9, 2002 2:39 pm 
Johannes ErdfeltDec 9, 2002 3:01 pm 
David BorehamDec 9, 2002 3:09 pm 
David BorehamDec 9, 2002 4:28 pm 
David BorehamDec 10, 2002 7:54 pm 
Sam VarshavchikDec 10, 2002 8:40 pm 
David BorehamDec 10, 2002 9:27 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:[maildropl] How to debug a broken maildrop configuration ?Actions...
From:David Boreham (davi@boreham.org)
Date:Dec 9, 2002 12:11:57 pm
List:net.sourceforge.lists.courier-maildrop

I'm sure this is a very stupid question, but here goes anyway:

I'm migrating all e-mail to a Postfix/maildrop/courier-imap/sqwebmail platform. I have one machine running ok. It uses /etc/password for user database.

Now I'm bringing a second machine up. It is intended for virtual domain hosting. I believe I understand how to do this, but it looks like I have screwed something up in the config. My current problem is that maildrop will not deliver mail. When run from the shell it typically exists throwing a signal (e.g. "maildrop: signal 0x0B"). I don't see anything in any syslog file to tell me what's going on. The -V <level> option supposedly doesn't work in delivery mode.

So...question is what's the best way to determine why this maildrop isn't able to deliver messages ? Clearly something is going wrong somewhere, it just isn't clear to me what and where.

Thanks much.