From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: Fail to encode attachement filenames properly.
Date: Thu, 02 May 2002 05:40:16 +0200 [thread overview]
Message-ID: <m3n0vj8bfj.fsf@defun.localdomain> (raw)
In-Reply-To: <microsoft-free.3oit67xt8t.fsf@ournature.org> (novembre+dated+1020732359.ff68e2@ournature.org's message of "Thu, 2 May 2002 02:17:31 +0000 (UTC)")
novembre+dated+1020732359.ff68e2@ournature.org (Jinhyok Heo) writes:
>>>>>> "JH" == Jesper Harder <harder@ifa.au.dk> writes:
>
> JH> This is not standards compliant. The filename parameter should be
> JH> encoded using RFC 2231, not an RFC 2047 encoding as in your example.
>
> Well, I didn't know that which one is standard comliant. I appreciate
> your information.
>
> The above one was excerpted from a M$-outlook mail.
Mozilla used to have the same bug, but I think it was fixed recently --
see <http://bugzilla.mozilla.org/show_bug.cgi?id=63656>
> But people who use M$-outlook or many webmails have trouble with
> attachments I send to them.
>
> I just have to wait and see for M$-outlook to be standard compliant in
> the future?
That could be a long wait :-) In the mean time
(defalias 'mail-header-encode-parameter 'rfc2045-encode-string)
should make Gnus use the "wrong" encoding, which Outlook can decode.
next prev parent reply other threads:[~2002-05-02 3:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-30 3:16 Jinhyok Heo
2002-04-30 13:33 ` Jesper Harder
2002-05-02 0:56 ` Jinhyok Heo
2002-05-02 3:40 ` Jesper Harder [this message]
2002-05-02 9:04 ` Fail to encode attachment " Jinhyok Heo
2002-05-02 18:18 ` Jesper Harder
2002-05-05 23:55 ` Jinhyok Heo
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=m3n0vj8bfj.fsf@defun.localdomain \
--to=harder@ifa.au.dk \
/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).