From: David N. <na...@ma...> - 2007-09-07 13:34:57
|
We've been using fetchmail for a few years, but recently noticed that there was a delay of up to 20minutes in receiving messages sent to us from an external email address. We're using a POP3 multidrop mailbox, and fetchmail passes the retrieved mail to Trestlemail MDA which then drops messages into the correct user's inbox. It's all worked fine 'til now. I logged on to our domain's webmail service, and noticed that our multidrop inbox had a few thousand messages in it. I don't think this used to happen, but they've started to collect there. I cleaned them out, and we started to receive external mail instantaneously (obviously fetchmail was taking time to parse the thousands of messages). When new mail hits the multi-drop mailbox, its status is 'unread'. When fetchmail downloads from the multidrop, the mail is removed from the multidrop mailbox, with the exception of some messages where the status changes to 'read' but it is not downloaded. These are the ones that are building up. Some of the recipients are genuine users on our system, but many are not. From what I've been able to monitor, all these messages are SPAM. I've looked at the headers, and they seem to be pretty much the same as genuine messages, but they have X-IMAIL-SPAM-xxx lines in their header, eg X-IMAIL-SPAM-VALFROM. After all that explanation, I just wondered if fetchmail is looking at these header lines and choosing not to download the messages? I'm probably going to look at the 'flush' parameter to automatically delete them, once I've monitored it for a wee while to make sure that every message affected is genuinely SPAM. I don't really want to change fetchmail versions if I can help it! Output of fetchmail -V is: This is fetchmail release 5.8.17+SSL+NLS Linux scoms1.xxxxx.co.uk 2.4.13 #1 Thu Oct 31 02:32:23 EST 2002 i686 unknown Taking options from command line and /.fetchmailrc Poll interval is 300 seconds Idfile is //.fetchids Fetchmail will forward misaddressed multidrop messages to postmaster. Options for retrieving from xx...@xx...@xxx.net: True name of server is xxx.net. Protocol is POP3. All available authentication methods will be tried. Server nonresponse timeout is 300 seconds (default). Default mailbox selected. All messages will be retrieved (--all on). Fetched messages will not be kept on the server (--keep off). Old messages will not be flushed before message retrieval (--flush off). Rewrite of server-local addresses is enabled (--norewrite off). Carriage-return stripping is enabled (stripcr on). Carriage-return forcing is disabled (forcecr off). Interpretation of Content-Transfer-Encoding is enabled (pass8bits off). MIME decoding is disabled (mimedecode off). Idle after poll is disabled (idle off). Nonempty Status lines will be kept (dropstatus off) Delivered-To lines will be kept (dropdelivered off) Messages will be delivered with "~/trestlemail/bin/trestlemail ~/trestlemail/trestlemail.rc -F %F -- %T". Recognized listener spam block responses are: 571 550 501 554 Multi-drop mode: 1 local name(s) recognized. DNS lookup for multidrop addresses is enabled. Server aliases will be compared with multidrop addresses by name. Envelope header is assumed to be: Received Local domains: xxxx.co.uk No UIDs saved from this host. Thanks David Me |