From: Karl Kleinpaste <karl@charcoal.com>
Subject: Patch needed: Defense against embedded ^M in Message-Id -- ow!
Date: Tue, 04 Sep 2001 08:00:10 -0400 [thread overview]
Message-ID: <vxk1ylnmaid.fsf@cinnamon.vanillaknot.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
I got another screwup in my spam-catcher "tomb" group this morning.
Same symptom as before, article expiry choking on an invalid numeric
comparison to `>'. I took a closer look, and what I found is fairly
horrifying.
There are spammers out there whose messages contain a literal carriage
return character in the Message-Id header. Take a peek below (and
maybe hit `i' twice on its MIME component to get it rendered as
text/plain). And that's ignoring entirely the fact that the
Message-Id header looks more like a Received header in the first
place.
[-- Attachment #2: header screwup with embedded carriage return --]
[-- Type: message/rfc822, Size: 1469 bytes --]
[-- Attachment #2.1: Type: text/html, Size: 17 bytes --]
From: enrda352@hotmail.com
To: <baseball@statesmail.com>
Subject: Targeted E-Mail Marketing Lists............. *f
Date: Sat, 25 Aug 2001 18:19:25 -0700
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>
[-- Attachment #3: Type: text/plain, Size: 556 bytes --]
This induces an overview file which contains 2 lines, because
somewhere along the way Gnus converts the carriage return to a
newline. The 2nd line makes for the malformed overview entry, because
it begins with that `>'.
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. Does anyone know precisely where this occurs? A
quick peek at nnheader.el wasn't terribly informative.
next reply other threads:[~2001-09-04 12:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-04 12:00 Karl Kleinpaste [this message]
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
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=vxk1ylnmaid.fsf@cinnamon.vanillaknot.com \
--to=karl@charcoal.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).