From: deskpot@despammed.com (Vasily Korytov)
Subject: Re: Charset encoding brokenness
Date: Wed, 29 Oct 2003 15:39:01 +0300 [thread overview]
Message-ID: <871xswjk0q.fsf@unix.home> (raw)
In-Reply-To: <87n0bkfrvf.fsf@unix.home>
On Wed, 29 Oct 2003 10:03:00 +0300, Vasily Korytov wrote:
>> Outlook has no problem with viewing base64. I don't know about Fido,
>> but I'd consider any client which doesn't do base64 to be extremely
>> obsolete.
>
> I know no MUA, that handle such constructions properly. Even Gnus.
What a shame on my head. =))
But I still consider this behaviour somewhat broken.
--
I accept RFC3156 and RFC2440-compatible encrypted mail.
PGP key fingerprint: 123A 7CCE 6E26 6233 0D87 E01A A0F8 3524 FCD8 1841
next prev parent reply other threads:[~2003-10-29 12:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 21:49 Jesper Harder
2003-10-28 0:48 ` Simon Josefsson
2003-10-28 1:42 ` Jesper Harder
2003-10-28 3:01 ` Jesper Harder
2003-10-28 7:07 ` Vasily Korytov
2003-10-28 16:41 ` Jesper Harder
2003-10-29 7:03 ` Vasily Korytov
2003-10-29 12:39 ` Vasily Korytov [this message]
2003-10-29 21:22 ` Simon Josefsson
2003-10-29 21:30 ` Simon Josefsson
2003-10-29 21:17 ` Simon Josefsson
2003-10-31 16:29 ` Simon Josefsson
2003-10-31 22:23 ` Jesper Harder
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=871xswjk0q.fsf@unix.home \
--to=deskpot@despammed.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).