From: Ted Zlatanov <tzz@northernlight.com>
Subject: possible bug? or feature? with slurping DOS files under Unix
Date: Mon, 12 Nov 2001 14:00:46 -0500 [thread overview]
Message-ID: <m3vggfstk1.fsf@onyx.nimbus.northernlight.com> (raw)
I hesitate to post this as a bug, because it's definitely not
something you'd expect to see. Still, I almost lost mail because of
it.
For some reason, my fetchmail started writing messages in DOS format,
with the extra ^M at the end of the file. Gnus fetched that mail and
added "Lines: 0" and a X-Ref header at the end of the message, and
didn't show the message body itself when I selected it.
I panicked, of course, and got Gnus from CVS, but that didn't fix
anything (at this point, I just saw empty messages with ^M at the
end of every header line). I eventually figured the problem out and
restarted fetchmail, when I hit 't' and saw the message body in
between the headers.
If this is a feature, it should be documented. If this is a bug, I
hope it's fixed so others don't have the same fun I did :)
Thanks
Ted
next reply other threads:[~2001-11-12 19:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-12 19:00 Ted Zlatanov [this message]
2001-11-12 20:56 ` Simon Josefsson
2001-11-13 3:14 ` Samuel Padgett
2001-11-13 9:40 ` Simon Josefsson
2001-11-13 17:24 ` Samuel Padgett
2001-11-13 17:34 ` Ted Zlatanov
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=m3vggfstk1.fsf@onyx.nimbus.northernlight.com \
--to=tzz@northernlight.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).