^M in header problem?

^M in header problem?

[Nick Papadonis]

I have recently been receiving header information with ^Ms inserted.
It has been happening on the ACPI mailing list.

The message body appears to be empty when viewed in gnus.  Everything
is interpeted as header information.

Anyone have any idea what is happening?  Thanks

SAMPLE MESSAGE FOLLOWING:

X-From-Line: nick  Sun Nov 25 16:55:12 2001
Envelope-to: nick@coelacanth.com
Received: from localhost.localdomain [127.0.0.1]
	by localhost with POP3 (fetchmail-5.9.0)
	for nick@localhost (single-drop); Sun, 25 Nov 2001 16:55:12 -0500 (EST)
Received: from mailrelay1.lrz-muenchen.de ([129.187.254.101])
	by sturgeon.coelacanth.com with esmtp (Exim 3.12 #1 (Debian))
	id 167aB2-00064B-00
	for <nick@coelacanth.com>; Sat, 24 Nov 2001 10:36:52 +0000
Received: from phobos.fachschaften.tu-muenchen.de by mailrelay1.lrz-muenchen.de with ESMTP; Sat, 24 Nov 2001 11:30:53 +0100
Received: from localhost
	([127.0.0.1] helo=phobos.fachschaften.tu-muenchen.de ident=list)
	by phobos.fachschaften.tu-muenchen.de with esmtp (Exim 3.33 #1 (Debian))
	id 167a5B-0006Cn-00; Sat, 24 Nov 2001 11:30:49 +0100
Received: from mailrelay1.lrz-muenchen.de ([129.187.254.101])
	by phobos.fachschaften.tu-muenchen.de with esmtp (Exim 3.33 #1 (Debian))
	id 167a21-0006B6-00
	for <acpi@phobos.fachschaften.tu-muenchen.de>; Sat, 24 Nov 2001 11:27:33 +0100
Received: from protactinium.btinternet.com by mailrelay1.lrz-muenchen.de with ESMTP for acpi@phobos.fachschaften.tu-muenchen.de; Sat, 24 Nov 2001 11:27:30 +0100
Received: from [213.122.193.24] (helo=there)
	by protactinium.btinternet.com with smtp (Exim 3.22 #8)
	id 167Zyy-00078Z-00
	for acpi@phobos.fachschaften.tu-muenchen.de; Sat, 24 Nov 2001 10:24:25 +0000
Content-Type: text/plain;\r charset="iso-8859-15"
From: Jeff <je4d@pobox.com>
Reply-To: je4d@pobox.com
To: acpi@phobos.fachschaften.tu-muenchen.de
X-Mailer: KMail [version 1.3.1]
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Gnus-Mail-Source: directory:~/incoming/
Message-Id: <E167Zyy-00078Z-00@protactinium.btinternet.com>
Subject: [Acpi] SMsC fdc37n3869 (successor to fdc37n869)
Sender: acpi-admin@phobos.fachschaften.tu-muenchen.de
Errors-To: acpi-admin@phobos.fachschaften.tu-muenchen.de
X-BeenThere: acpi@phobos.fs.tum.de
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:acpi-request@phobos.fs.tum.de?subject=help>
List-Post: <mailto:acpi@phobos.fs.tum.de>
List-Subscribe: <https://phobos.fs.tum.de/mailman/listinfo/acpi>,
	<mailto:acpi-request@phobos.fs.tum.de?subject=subscribe>
List-Id: The ACPI4Linux mailing list <acpi.phobos.fs.tum.de>
List-Unsubscribe: <https://phobos.fs.tum.de/mailman/listinfo/acpi>,
	<mailto:acpi-request@phobos.fs.tum.de?subject=unsubscribe>
List-Archive: <https://phobos.fs.tum.de/pipermail/acpi/>
Date: Sat, 24 Nov 2001 10:23:28 +0000
Hi
I've got a fdc37n3869 chip on my compaq laptop mb.. acording to smsc it is
 the successor to the fdc37n869 which i know is supported by linux-irda
when i run findchip, it detects a it as the old fdc36n869, and (apparantly) 
findchip dosen't recongnise or test for the 3869 variant..
However, when i boot the kernel with acpi, it gives me this horrible load of errors in dmesg (at end)

Re: ^M in header problem?

[Eric Hendrickson]

This happened to me too.  It was extremely annoying to determine what the
problem was, since I had been editing my .gnus and my .procmailrc all
around the same time this started happening.

It is a bug in fetchmail and I see you are running the same version I was.
I could swear I was running 5.9 for a while and all of a sudden it started
doing this ^M thing...  but backing out to an earlier version took care of
the problem.  I think I went back to 5.7 for the moment but I don't have
access to that machine to double check right now.

Eric

On 27 Nov 2001, Nick Papadonis wrote:

> I have recently been receiving header information with ^Ms inserted.
> It has been happening on the ACPI mailing list.
>
> The message body appears to be empty when viewed in gnus.  Everything
> is interpeted as header information.
>
> Anyone have any idea what is happening?  Thanks
>
> SAMPLE MESSAGE FOLLOWING:
>
> X-From-Line: nick  Sun Nov 25 16:55:12 2001
> Envelope-to: nick@coelacanth.com
> Received: from localhost.localdomain [127.0.0.1]
> 	by localhost with POP3 (fetchmail-5.9.0)
> 	for nick@localhost (single-drop); Sun, 25 Nov 2001 16:55:12 -0500 (EST)
> Received: from mailrelay1.lrz-muenchen.de ([129.187.254.101])
> 	by sturgeon.coelacanth.com with esmtp (Exim 3.12 #1 (Debian))
> 	id 167aB2-00064B-00
> 	for <nick@coelacanth.com>; Sat, 24 Nov 2001 10:36:52 +0000
> Received: from phobos.fachschaften.tu-muenchen.de by mailrelay1.lrz-muenchen.de with ESMTP; Sat, 24 Nov 2001 11:30:53 +0100
> Received: from localhost
> 	([127.0.0.1] helo=phobos.fachschaften.tu-muenchen.de ident=list)
> 	by phobos.fachschaften.tu-muenchen.de with esmtp (Exim 3.33 #1 (Debian))
> 	id 167a5B-0006Cn-00; Sat, 24 Nov 2001 11:30:49 +0100
> Received: from mailrelay1.lrz-muenchen.de ([129.187.254.101])
> 	by phobos.fachschaften.tu-muenchen.de with esmtp (Exim 3.33 #1 (Debian))
> 	id 167a21-0006B6-00
> 	for <acpi@phobos.fachschaften.tu-muenchen.de>; Sat, 24 Nov 2001 11:27:33 +0100
> Received: from protactinium.btinternet.com by mailrelay1.lrz-muenchen.de with ESMTP for acpi@phobos.fachschaften.tu-muenchen.de; Sat, 24 Nov 2001 11:27:30 +0100
> Received: from [213.122.193.24] (helo=there)
> 	by protactinium.btinternet.com with smtp (Exim 3.22 #8)
> 	id 167Zyy-00078Z-00
> 	for acpi@phobos.fachschaften.tu-muenchen.de; Sat, 24 Nov 2001 10:24:25 +0000
> Content-Type: text/plain; charset="iso-8859-15"
> From: Jeff <je4d@pobox.com>
> Reply-To: je4d@pobox.com
> To: acpi@phobos.fachschaften.tu-muenchen.de
> X-Mailer: KMail [version 1.3.1]
> MIME-Version: 1.0
> Content-Transfer-Encoding: 8bit
> X-Gnus-Mail-Source: directory:~/incoming/
> Message-Id: <E167Zyy-00078Z-00@protactinium.btinternet.com>
> Subject: [Acpi] SMsC fdc37n3869 (successor to fdc37n869)
> Sender: acpi-admin@phobos.fachschaften.tu-muenchen.de
> Errors-To: acpi-admin@phobos.fachschaften.tu-muenchen.de
> X-BeenThere: acpi@phobos.fs.tum.de
> X-Mailman-Version: 2.0.6
> Precedence: bulk
> List-Help: <mailto:acpi-request@phobos.fs.tum.de?subject=help>
> List-Post: <mailto:acpi@phobos.fs.tum.de>
> List-Subscribe: <https://phobos.fs.tum.de/mailman/listinfo/acpi>,
> 	<mailto:acpi-request@phobos.fs.tum.de?subject=subscribe>
> List-Id: The ACPI4Linux mailing list <acpi.phobos.fs.tum.de>
> List-Unsubscribe: <https://phobos.fs.tum.de/mailman/listinfo/acpi>,
> 	<mailto:acpi-request@phobos.fs.tum.de?subject=unsubscribe>
> List-Archive: <https://phobos.fs.tum.de/pipermail/acpi/>
> Date: Sat, 24 Nov 2001 10:23:28 +0000
> Hi
> I've got a fdc37n3869 chip on my compaq laptop mb.. acording to smsc it is
>  the successor to the fdc37n869 which i know is supported by linux-irda
> when i run findchip, it detects a it as the old fdc36n869, and (apparantly)
> findchip dosen't recongnise or test for the 3869 variant..
> However, when i boot the kernel with acpi, it gives me this horrible load of errors in dmesg (at end)
>

Re: ^M in header problem?

[Nick Papadonis]

Did you forward a bug report to the fetchmail list?

Eric Hendrickson <edh@mr.net> writes:

> This happened to me too.  It was extremely annoying to determine what the
> problem was, since I had been editing my .gnus and my .procmailrc all
> around the same time this started happening.
> 
> It is a bug in fetchmail and I see you are running the same version I was.
> I could swear I was running 5.9 for a while and all of a sudden it started
> doing this ^M thing...  but backing out to an earlier version took care of
> the problem.  I think I went back to 5.7 for the moment but I don't have
> access to that machine to double check right now.
> 
> Eric
> 
> On 27 Nov 2001, Nick Papadonis wrote:
> 
> > I have recently been receiving header information with ^Ms inserted.
> > It has been happening on the ACPI mailing list.
> >
> > The message body appears to be empty when viewed in gnus.  Everything
> > is interpeted as header information.
> >
> > Anyone have any idea what is happening?  Thanks
> >