From: Nick Papadonis <nick@coelacanth.com>
Subject: ^M in header problem?
Date: 27 Nov 2001 14:21:58 -0500 [thread overview]
Message-ID: <m3lmgsdnop.fsf@localhost.localdomain> (raw)
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)
next reply other threads:[~2001-11-27 19:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 19:21 Nick Papadonis [this message]
2001-11-27 20:59 ` Eric Hendrickson
2001-11-28 6:58 ` Nick Papadonis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3lmgsdnop.fsf@localhost.localdomain \
--to=nick@coelacanth.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).