Hello Courier Users,
I have a user whose mail frequently triggers the following log message:
postfix/pipe[7826]: 14E261295F1: to=<u...@example.com>, relay=maildrop,
delay=2024, status=deferred (temporary failure. Command output: maildrop:
Timeout quota exceeded. )
In my system, Postfix hands off the message to Maildrop for delivery.
So far I've added a logfile statement to the user's .mailfiter file, but
(as might be expected) that only is logged to on successful delivery.
When stracing a long running maildrop process, maildrop seems to go through
the user's entire mailbox bouncing stat64 calls off files.
stat64("/PATH_HERE/mail/.Archive Old Emails/cur/
1443112974.M868311P11219.imap.example.com:2,", {st_mode=S_IFREG|0600,
st_size=29403, ...}) = 0
For kicks, I've disabled their filters (blacklist, whitelist, forward,
spam, vacation) so that in theory nothing should be active. Same timeout
message. I've hand commented out lines so only a few filters are active,
same timeout result. I moved aside their original .mailfilter file and
created a new one with only a logfile statement, same timeout result.
The user is not hand creating the rules, but instead generating them via
Horde Webmail filters. And they have quite a few whitelist (336 count) and
blacklist (33 count) entries.
I've done list archive research and made changes (as noted above) to try
and narrow down the cause.
https://sourceforge.net/p/courier/mailman/message/4591096/
https://sourceforge.net/p/courier/mailman/message/16309598/
I would appreciate suggestions for additional troubleshooting I can perform
to identify the problem causing timeout messages.
Thank you.
--
---~~.~~---
Mike
// SilverTip257 //
------------------------------------------------------------------------------
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
