Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: 0.26: Bug in text of button
Date: 11 Sep 1998 16:50:22 +0200	[thread overview]
Message-ID: <m3r9xibt5d.fsf@sparky.gnus.org> (raw)
In-Reply-To: Jean-Yves Perrier's message of "11 Sep 1998 15:41:35 +0200"

Jean-Yves Perrier <perrier@nagra-kudelski.ch> writes:

> I've just got the following button:
> [application/msword (PV =?iso-8859-1?Q?r=E9union?= 18-8-98.doc)]
> 
> I suppose that the function call to decode =?iso-8859-1?Q?...
> is missing

Nope.  This is malformed.  Quoth RFC2047:

   These are the ONLY locations where an 'encoded-word' may appear.  In
   particular:

   + An 'encoded-word' MUST NOT appear in any portion of an 'addr-spec'.

   + An 'encoded-word' MUST NOT appear within a 'quoted-string'.

   + An 'encoded-word' MUST NOT be used in a Received header field.

   + An 'encoded-word' MUST NOT be used in parameter of a MIME
     Content-Type or Content-Disposition field, or in any structured
     field body except within a 'comment' or 'phrase'.

So decoding this would be naughty.

Although I don't understand how one is supposed to use non-ascii chars 
in the C-T header, then.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen


  reply	other threads:[~1998-09-11 14:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-11 13:41 Jean-Yves Perrier
1998-09-11 14:50 ` Lars Magne Ingebrigtsen [this message]
1998-09-11 15:27   ` Hrvoje Niksic
1998-09-11 15:54     ` Lars Magne Ingebrigtsen
1998-09-11 16:57       ` Jean-Yves Perrier
1998-09-12  3:31         ` Lars Magne Ingebrigtsen
1998-09-11 18:15       ` Hrvoje Niksic
1998-09-12  3:05         ` 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=m3r9xibt5d.fsf@sparky.gnus.org \
    --to=larsi@gnus.org \
    /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).