7 messages in net.sourceforge.lists.courier-users[courier-users] courier or maildrop d...
FromSent OnAttachments
Plamen PetrovOct 17, 2007 11:49 pm 
Sam VarshavchikOct 18, 2007 4:05 am 
Plamen PetrovOct 18, 2007 4:24 am 
Sam VarshavchikOct 18, 2007 3:52 pm 
Plamen PetrovOct 18, 2007 11:24 pm 
Sam VarshavchikOct 19, 2007 4:03 am 
Plamen PetrovOct 19, 2007 4:07 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:[courier-users] courier or maildrop debugging output/logfilesActions...
From:Plamen Petrov (weba@tk.ru.acad.bg)
Date:Oct 17, 2007 11:49:08 pm
List:net.sourceforge.lists.courier-users

Hi, folks!

I am wondering, after reading for some time in the documentation of Courier, is there any way to enable some logging so that I can be sure maildrop is actually being run as delivery agent/filter ? The documentation says that if I am using the maildrop that comes with Courier, it will be used in "embedded" mode, which implies internal disabling of the "logfile" and "log" statements in maildroprc, as some others, too. I have a setup with a small number of virtual mail accounts, with all debug output enabled. It used courier's local delivery module. Now I want to redirect the mail through maildrop, so I can use SpamAssassin, but from what I am seeing in the logs, I can't tell maildrop is run at all! Can this be changed? How?

Thanks,

-------------------------------- this message is UTF8 encoded