From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: Patch needed: Defense against embedded ^M in Message-Id -- ow!
Date: Tue, 04 Sep 2001 11:46:17 -0400 [thread overview]
Message-ID: <m33d63c61s.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <vxk1ylnmaid.fsf@cinnamon.vanillaknot.com> (Karl Kleinpaste's message of "Tue, 04 Sep 2001 08:00:10 -0400")
Karl Kleinpaste <karl@charcoal.com> wrote:
> There are spammers out there whose messages contain a literal carriage
> return character in the Message-Id header.
...
> Message-ID: <00004f9a34c1$00001d6e$00006e46@myrop (ew6.southwind.net [216.53.98.70]) by onyx.southwind.net from homepage.com (114.230.197.216) by newmail.spectraweb.ch from default (m202.2-25.warwick.net [218.242.202.80]) byhost.warwick.net (8.10.0.Beta10/8.10.0.Beta10) with SMTP id e9GKEKk19201\r>
Eww. That's ugly, all right.
> I would guess that what's needed for this is a patch to turn carriage
> returns into bland space characters, the way that I expect all headers
> have tabs converted to spaces to prevent screwing up the tab-separated
> overview files.
I just fixed this same bug in the last version of nnmaildir. It's ok
to leave the carriage returns unchanged, but to prevent them from
becoming newlines, you have to do this:
(let ((nnheader-file-coding-system 'binary) ...) ...)
when writing your NOV file.
paul
next prev parent reply other threads:[~2001-09-04 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-04 12:00 Karl Kleinpaste
2001-09-04 13:50 ` Kai Großjohann
2001-09-04 14:19 ` Karl Kleinpaste
2001-09-04 17:02 ` Kai Großjohann
2001-09-04 15:46 ` Paul Jarc [this message]
2001-09-04 16:05 ` Paul Jarc
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=m33d63c61s.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
/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).