From: "Bjørn Mork" <bmork@dod.no>
Subject: Re: Another problem with rfc2047 encoding
Date: Thu, 01 May 2003 10:15:57 +0200 [thread overview]
Message-ID: <hvn0i7f5fm.fsf@rasputin.ws.nextra.no> (raw)
In-Reply-To: <8765ovcgt1.fsf-theta-@daphne.gnuu.de> (Thomas =?iso-8859-1?q?H=FChn's?= message of "Thu, 01 May 2003 08:49:58 +0200")
ding@daphne.gnuu.de (Thomas Hühn) writes:
> In the following article...
>
> From: Ralf =?ISO-8859-1?Q?D=F6blitz?= <=?iso-8859-1?q?d=F6blitz?=@doeblitz.net>
> Newsgroups: de.admin.news.misc
> Subject: Re: Reflektoren und RFC822
> Date: 16 Apr 2003 19:01:20 GMT
> Message-ID: <b7k9a0$he6$3@msgids.netzverwaltung.net>
>
> ...the localpart seems to be interpreted, though it shouldn't.
>
> RFC 2047 states in section 5(3):
> "An 'encoded-word' MUST NOT appear in any portion of an 'addr-spec'."
True, but I wonder... How should Gnus handle an illegal address like
that? Quote it, warn the user and try to send anyway if the user
insists? Or just refuse it unconitionally to avoid having people
believe they can get away with such addresses?
But there are cases where Gnus will happily violate RFC2047 even when
fed valid input. For example, if I reply to myself (not that I really
*do* that :-), Gnus will create an In-Reply-To field like this:
In-Reply-To: <hvsmrzf65l.fsf@rasputin.ws.nextra.no>
=?iso-8859-1?q?(Bj=F8rn?= Mork's message of "Thu, 01 May 2003 10:00:22
+0200")
The In-Reply-To field is a structured field, and the text added after
the message-id is a comment. Which is perfectly OK, given that CFWS
is allowed there. But when encoding it, Gnus screws up and the result
is a violation of RFC2047 and RFC2822. The comment delimiters should
not be part of the encoded word.
One strange thing to notice is that Gnus will correctly encode a
comment in the From field (and possibly other structured fields?) I
don't know why.
Bjørn
--
It takes a homosexual sexist like you to say that you're religious.
next prev parent reply other threads:[~2003-05-01 8:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 17:20 Reiner Steib
2003-04-28 20:47 ` Reiner Steib
2003-05-01 6:38 ` Lars Magne Ingebrigtsen
2003-05-01 6:49 ` Thomas Hühn
2003-05-01 7:14 ` Lars Magne Ingebrigtsen
2003-05-01 7:39 ` Thomas Hühn
2003-05-01 14:48 ` Lars Magne Ingebrigtsen
2003-05-04 19:42 ` Christoph Garbers
2003-05-08 22:49 ` Dave Love
2003-05-15 17:26 ` Christoph Garbers
2003-05-16 16:42 ` Dave Love
2003-05-20 12:42 ` Christoph Garbers
2003-05-22 17:01 ` Dave Love
2003-05-01 8:15 ` Bjørn Mork [this message]
2003-05-01 8:42 ` Lars Magne Ingebrigtsen
2003-05-01 12:46 ` Simon Josefsson
2003-05-01 13:28 ` Bjørn Mork
2003-05-02 16:10 ` Lars Magne Ingebrigtsen
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=hvn0i7f5fm.fsf@rasputin.ws.nextra.no \
--to=bmork@dod.no \
/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).