8 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] No luck with mysql + ...
FromSent OnAttachments
Sunil William SavkarSep 16, 2002 11:45 am 
Rolan YangSep 16, 2002 12:14 pm 
Sunil William SavkarSep 16, 2002 12:26 pm 
Sunil William SavkarSep 16, 2002 1:54 pm 
Sunil William SavkarSep 16, 2002 2:30 pm 
Rodolfo GonzalezSep 17, 2002 2:40 pm 
Sunil William SavkarSep 18, 2002 4:26 am 
Rodolfo GonzalezSep 18, 2002 9:55 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] No luck with mysql + maildrop + postfix setup... recompiled but errorsActions...
From:Sunil William Savkar (sav@inthespace.com)
Date:Sep 16, 2002 1:54:42 pm
List:net.sourceforge.lists.courier-maildrop

I'm not sure. Maybe your maildrop didn't compile correctly? Maildrop should output to your syslog (/var/log/maillog?). I did several things to test. One was finding a previously sent email in one of my maildir's and cat'ing it directly to maildrop from the command line.

Oddly upon more research, I am not seeing any communication by maildrop, whether i try on the command line or I try otherwise. I always get the same nasty message 0x0B signal from Maildrop.

This is extremely frustrating. I wish there was a better debug mode where I could see a stream of messages.

Alhtough I have enable-syslog=1, I do not see any messages in syslog either.. perhaps it is crapping out immediately. Coudl it be something to do with who needs to run it?

Sunil