I'm having increasingly frequent problems with fetchmail choking on
invalid email headers. The result is an error exit status (return code
= 2), and piling up of mail on my ISP's POP server. Given my mail load
and the limited storage offered, this can lead to bounces in a day or
so.
As a result, I'm forced to manually telnet to my POP server and clean
out the junk manually. That itslef is a pain, the other is that due to
limitations of the box processing mail (a 160 MHz hppa system), dropping
more than 40 or so messages at a time on it results in runaway
loadaverage (peaked today at 119 before losing access and pulling the
plug). We've addressed this by setting an nproc limit of 30 for user
mail, and --max-children of 10 for spamassassin.
Fetchmail version:
ii fetchmail 6.2.3-1 SSL enabled POP3, APOP, IMAP mail gatherer/f
Sample headers, from manual fetchmail session:
+OK kmself has 695 messages (10098044 octets).
retr 1
+OK 3465 octets
Status: RO
Return-Path: <f@168.com,kjaj>
Received: from 168.com ([202.102.142.16])
by eagle (EarthLink SMTP Server) with SMTP id 19OX1x38N3NZFji0
for <kmself@ix.netcom.com>; Mon, 18 Aug 2003 20:19:06 -0700 (PDT)
From: kjaj;f@168.com
Subject:
=?GB2312?B?SVDIureiyO28/qGqoaqhqsjDxOO1xM/7z6K0q7W9w7+49snPzfjIy7XE18DD?=
Message-Id: <200308182019.19OX1x38N3NZFji0@eagle>
Date: Mon, 18 Aug 2003 20:19:06 -0700 (PDT)
=?GB2312?B?5qOh?=
To: kmself@ix.netcom.com
Content-Type: text/plain;charset="GB2312"
Reply-To: kjafuiol@168.com
Date: Tue, 19 Aug 2003 11:19:30 +0800
X-Priority: 3
X-Mailer: FoxMail 3.11 Release [cn]
Suggestions or alternatives welcomed. I'm getting the general
impression that fetchmail is crufty.
No bug filed yet, suggestions on how to phrase this appreciated.
Peace.
--
Karsten M. Self <kmself@ix.netcom.com> http://kmself.home.netcom.com/
What Part of "Gestalt" don't you understand?
Ceterum censeo, Caldera delenda est.
SCO vs IBM Linux lawsuit info: http://sco.iwethey.org
Attachment:
pgplTp3TMQrxc.pgp
Description: PGP signature