On Fri, Aug 22, 2003 at 05:07:56AM +0100, Karsten M. Self wrote:
> As I posted here yesterday, fetchmail was choking on ill-formed headers,
> which research suggested was actually exim puking and fetchmail handling
> the situation...ungracefully (fetchmail should, and may? have the option
> to simply delete or bounce such mails).
It's not exim. Everyone says that the fix for it is to tell exim to not
verify headers... well:
----- begin clip from /etc/exim/exim.conf -----
# The setting below would, if uncommented, cause Exim to check the syntax of
# all the headers that are supposed to contain email addresses (To:, From:,
# etc). This reduces the level of bounced bounces considerably.
# headers_check_syntax
----- end clip from /etc/exim/exim.conf -----
It's not active.
I thought perhaps it was default true, and forced it false.
That doesn't help either.
If you run fetchmail as verbose as you can get it to be, it looks like it
barfs when it goes looking for headers to rewrite. Often it's the To:
header, sometimes it's other things:
rei $ fetchmail -v -v pop.west.cox.net
fetchmail: 6.2.3 querying pop.west.cox.net (protocol POP3) at Fri 22 Aug 2003 09:53:57 PM PDT: poll started
fetchmail: POP3< +OK InterMail POP3 server ready.
fetchmail: POP3> USER msw
fetchmail: POP3< +OK please send PASS command
fetchmail: POP3> PASS *
fetchmail: POP3< +OK msw is welcome here
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 9 42594
fetchmail: POP3> LAST
fetchmail: POP3< +OK 0
9 messages for msw at pop.west.cox.net (42594 octets).
fetchmail: POP3> LIST
fetchmail: POP3< +OK 9 messages
fetchmail: POP3< 1 4128
fetchmail: POP3< 2 3520
fetchmail: POP3< 3 5325
fetchmail: POP3< 4 3321
fetchmail: POP3< 5 9888
fetchmail: POP3< 6 4213
fetchmail: POP3< 7 5000
fetchmail: POP3< 8 2453
fetchmail: POP3< 9 4746
fetchmail: POP3< .
fetchmail: POP3> TOP 1 99999999
fetchmail: POP3< +OK 4128 octets
reading message msw@pop.west.cox.net:1 of 9 (4128 octets)
About to rewrite Return-Path: <bounce-debian-user=msw=cox.net@lists.debian.org>
Rewritten version is Return-Path: <bounce-debian-user=msw=cox.net@lists.debian.org>
About to rewrite From: Arnt Karlsen <arnt@c2i.net>
Rewritten version is From: Arnt Karlsen <arnt@c2i.net>
About to rewrite To: debian-user@lists.debian.org
Rewritten version is To: debian-user@lists.debian.org
fetchmail: incorrect header line found while scanning headers
fetchmail: SMTP< 220 rei.moonkingdom.net ESMTP Exim 3.36 #1 Fri, 22 Aug 2003 21:54:00 -0700
fetchmail: SMTP> EHLO localhost
fetchmail: SMTP< 250-rei.moonkingdom.net Hello mwilson at localhost [127.0.0.1]
fetchmail: SMTP< 250-SIZE
fetchmail: SMTP< 250-PIPELINING
fetchmail: SMTP< 250 HELP
fetchmail: forwarding to localhost
fetchmail: SMTP> MAIL FROM:<bounce-debian-user=msw=cox.net@lists.debian.org> SIZE=4128
fetchmail: SMTP< 250 <bounce-debian-user=msw=cox.net@lists.debian.org> is syntactically correct
fetchmail: SMTP> RCPT TO:<mwilson@localhost>
fetchmail: SMTP< 250 <mwilson@localhost> verified
fetchmail: SMTP> DATA
fetchmail: SMTP< 354 Enter message, ending with "." on a line by itself
#fetchmail: message delimiter found while scanning headers
fetchmail: message msw@pop.west.cox.net:1 was not the expected length (1590 actual != 4128 expected)
fetchmail: SMTP>. (EOM)
fetchmail: SMTP< 250 OK id=19qQPY-0007pU-00
flushed
fetchmail: POP3> DELE 1
fetchmail: POP3< X-Return-Path: arnt@c2i.net
fetchmail: POP3> QUIT
fetchmail: POP3< X-MDaemon-Deliver-To: debian-user@lists.debian.org
fetchmail: client/server protocol error while fetching from pop.west.cox.net
fetchmail: 6.2.3 querying pop.west.cox.net (protocol POP3) at Fri 22 Aug 2003 09:54:00 PM PDT: poll completed
fetchmail: Query status=4 (PROTOCOL)
fetchmail: Writing fetchids file.
fetchmail: normal termination, status 4
fetchmail: Writing fetchids file.
Actually, fetchmail barfs twice. Once when it downloads the message, and a
second time when it tries the SMTP inject.
It's a VERY old fetchmail bug. Several merged Debian bugs. If you google
for it, you can even find lots of instances of ESR telling people they're
clueless and that it works correctly. :)
Unfortunately, there's no credible alternative to fetchmail, is there?
For completeness sake, the actual message it's barfing on is:
rei $ telnet pop.west.cox.net 110
Trying 68.6.19.2...
Connected to pop.west.cox.net.
Escape character is '^]'.
+OK InterMail POP3 server ready.
user msw
+OK please send PASS command
pass *
+OK msw is welcome here
retr 1
+OK 4128 octets
Return-Path: <bounce-debian-user=msw=cox.net@lists.debian.org>
Received: from murphy.debian.org ([146.82.138.6]) by lakemtai03.cox.net
(InterMail vM.5.01.06.04 201-253-122-130-104-20030726) with ESMTP
id <20030823042812.BZVK12767.lakemtai03.cox.net@murphy.debian.org>
for <msw@cox.net>; Sat, 23 Aug 2003 00:28:12 -0400
Received: from localhost (localhost [127.0.0.1])
by murphy.debian.org (Postfix) with QMQP
id: 26:40 -0500 (CDT)
Old-Return-Path: <arnt@c2i.net>
Received: from gjesdal.net (unknown [217.68.104.231])
by murphy.debian.org (Postfix) with ESMTP id 5EA521F75A
for: 26:30 -0500 (CDT)
Received: from arnt.mail.c2i.net ([80.239.32.254])
by gjesdal.net (gjesdal.net [217.68.104.231])
(MDaemon.PRO.v6.8.4.R)
with ESMTP id 12-md50000000013.tmp
for: 25:14 +0200
Date: Sat, 23 Aug 2003 06:29:38 +0200
From: Arnt Karlsen <arnt@c2i.net>
To: debian-user@lists.debian.org
Subject: ..OT, politics, was: SCO show must end!!!
Message-Id: <[🔎] 20030823062938.050edcff.arnt@c2i.net>
In-Reply-To: <[🔎] 003601c3691a$a1cf9d30$026fa8c0@crhome>
References: <[🔎] 003601c3691a$a1cf9d30$026fa8c0@crhome>
Organization: ing. Arnt Karlsen
X-Mailer: Sylpheed version 0.7.4 (GTK+ 1.2.10; i386-debian-linux-gnu)
User-Agent: 007 ;-)
X-Face: ;-)
X-Operating-System: ..that tux clad penguin known as Linux ;-)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Processed: gjesdal.net, Sat, 23 Aug 2003 06:25:14 +0200
(not: message from trusted or authenticated source)
X-MDRemoteIP: 80.239.32.254
X-Return-Path: arnt@c2i.net
X-MDaemon-Deliver-To: debian-user@lists.debian.org
X-Spam-Status: No, hits=-0.3 required=4.0
tests=IN_REP_TO,PLING_PLING,QUOTED_EMAIL_TEXT,REFERENCES,
REPLY_WITH_QUOTES,USER_AGENT
version=2.55-lists.debian.org_2003_08_19
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.55-lists.debian.org_2003_08_19 (1.174.2.19-2003-05-19-exp)
Resent-Message-ID: <NJfiFC.A.cR._zuR_@murphy>
Resent-From: debian-user@lists.debian.org
X-Mailing-List: <debian-user@lists.debian.org> archive/latest/295760
X-Loop: debian-user@lists.debian.org
List-Id: <debian-user.lists.debian.org>
List-Post: <mailto:debian-user@lists.debian.org>
List-Help: <mailto:debian-user-request@lists.debian.org?subject=help>
List-Subscribe: <mailto:debian-user-request@lists.debian.org?subject=subscribe>
List-Unsubscribe: <mailto:debian-user-request@lists.debian.org?subject=unsubscribe>
List-Archive: <http://lists.debian.org/debian-user/>
Precedence: list
Resent-Sender: debian-user-request@lists.debian.org
Resent-Date: Fri, 22 Aug 2003 23:26:40 -0500 (CDT)
On Sat, 23 Aug 2003 05:02:40 +0300,
"acatrineicatalin" <acatrineicatalin@hotmail.com> wrote in message
<[🔎] 003601c3691a$a1cf9d30$026fa8c0@crhome>:
<subsequent text deleted>
If someone would like to describe what's wrong with that set of mail
headers, I'd be exceedingly grateful (and it could be added to the current
bug report).
--
Marc Wilson | There is nothing stranger in a strange land than
msw@cox.net | the stranger who comes to visit.
Attachment:
pgphrUb7sU1ZQ.pgp
Description: PGP signature