From: Simon Josefsson <sj@extundo.com>
Cc: ding@gnus.org
Subject: Re: attachment names
Date: 02 Nov 2000 14:44:23 +0100 [thread overview]
Message-ID: <ilubsvyxzd4.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <eysnpams31.fsf@video.uic.vsu.ru>
Vladimir Volovich <vvv@vvv.vsu.ru> writes:
> The button which gnus displayed was:
>
> [2. application/x-zip-compressed; =?koi8-r?B?5MzRINDFzsnRLnppcA==?=]...
>
> I wonder if gnus behaved correctly not decoding the encoded-words
> (i.e. if outlook incorrectly encoded the filename in the headers)?
No, gnus is correct, outlook is violating MIME specs. However, it
doesn't seem to be alone in this behaviour, so perhaps we should try
to support QP encoded parameter values anyway. (The "proper" solution
would be to make every other client support rfc 2231.)
MIME spec says:
+ 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'.
next prev parent reply other threads:[~2000-11-02 13:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-02 13:17 Vladimir Volovich
2000-11-02 13:44 ` Simon Josefsson [this message]
2000-11-03 11:50 ` Christoph Conrad
[not found] ` <ud7gd9sw1.fsf@cli.de>
2000-11-03 12:26 ` Simon Josefsson
2000-11-03 13:13 ` Kai Großjohann
2000-11-03 14:40 ` Per Abrahamsen
2000-11-03 13:19 ` Christoph Conrad
2000-11-03 13:37 ` Christoph Conrad
2000-11-03 14:39 ` Per Abrahamsen
2000-11-03 15:31 ` Simon Josefsson
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=ilubsvyxzd4.fsf@barbar.josefsson.org \
--to=sj@extundo.com \
--cc=ding@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).