I'm observing a rather extrange behaviour (or maybe a configuration
error) in the latest courier (0.52.2) build.
I'm filtering using maildrop and a custom perl filter which right now
it's taking a lot more than 5 minutes (the default watchdog), so I put
"30m" in my localtimeout file as man courier says:
localtimeout
This file specifies the watchdog timer for local mail
deliveries. If a local mail delivery attempt does not complete in the
proscribed time interval, the delivering process ID is killed. The time
interval in localtimeout is specified in the same way as queuetime (see
queuetime for more information).
Well, this isn't happening, as I see this on the logs:
Jan 17 13:14:41 localhost courierd: started,
id=006B85BB.43CC1C7B.00007CCA, from=<[EMAIL PROTECTED]>, module=local,
[EMAIL PROTECTED]/home/mail/dosalcubo.com/test!!,
addr=<[EMAIL PROTECTED]>
Jan 17 13:19:41 localhost courierlocal: id=006B85BB.43CC1C7B.00007CCA,
from=<[EMAIL PROTECTED]>, addr=<[EMAIL PROTECTED]>: maildrop: Timeout
quota exceeded.
I'm clueless...
Could be that the accounts are virtual and the timeout is only for local
deliveries?
Any help?
Thanks.-
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
