Re: Possible bug/unwanted behaviour with broken pipe in IMAP retriever after long filter processing
Charles Cazabon <[email protected]>
| Newsgroups | gmane.mail.getmail.user |
|---|---|
| Message-ID | <[email protected]> |
[email protected] <[email protected]> wrote: > > In the log file I was seeing a whole bunch of errors: > getmailOperationError error (IMAP error (socket error: [Errno 32] Broken > pipe)) As you figured, this is the IMAP server dropping the connection. Perhaps your IMAP server doesn't allow IDLE for extended periods (related to your slow ClamAV filter)? Or perhaps you just have a lousy networking connection that causes drops? --idle is fundamentally not compatible with anything that causes dropped connections. --idle is in fact an ugly hack. > http://pyropus.ca/software/getmail/faq.html#faq-integrating-clamav, using > the first example without the daemon. I don't use ClamAV myself, but I understand is has a large startup cost, which is why it has the daemon option. I think you should probably try using it with the daemon (so your filter can complete in a few seconds) and see if that fixes the problem. If it still happens after that, you have unreliable connections to your server, and should avoid using --idle. Just poll on some reasonable interval instead. Charles -- ----------------------------------------------------------------------- Charles Cazabon GPL'ed software available at: http://pyropus.ca/software/ -----------------------------------------------------------------------