From: "Richard M. Stallman" <rms@gnu.org>
Cc: bugs@gnus.org, emacs-devel@gnu.org
Subject: Re: base64 behavior is not MIME compliant
Date: Tue, 05 Jul 2005 00:35:56 -0400 [thread overview]
Message-ID: <E1DpfA4-0004pf-Gh@fencepost.gnu.org> (raw)
In-Reply-To: <t53vf3rcgja.fsf@central-air-conditioning.toybox.cambridge.ma.us> (message from Marc Horowitz on Mon, 04 Jul 2005 00:59:53 -0400)
I received a piece of email which passed through an older MTA. This
MTA inserted a ! and a newline after every 1000 characters of a very
long line of base64-encoded data, which used to be common behavior.
When Gnus tried to display this email, it failed, because the !
characters were not recognized as valid base64 encoding.
Maybe I misunderstood what you were asking for. I thought you
were asking us to make additional base64-decode-region signal
errors in cases where currently it does not. But now it looks
like you are asking for it to accept input that now gives
an error.
Could you give a self-contained description of the change that you are
requesting in the behavior of this function?
next prev parent reply other threads:[~2005-07-05 4:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <t53zmt4dce3.fsf@central-air-conditioning.toybox.cambridge.ma.us>
2005-07-03 20:43 ` base64 behavior is not MIME compliant Richard M. Stallman
2005-07-03 21:09 ` Nic Ferrier
2005-07-04 4:59 ` Marc Horowitz
2005-07-05 4:35 ` Richard M. Stallman [this message]
2005-07-05 21:35 ` Marc Horowitz
2005-07-05 22:10 ` Nic Ferrier
2005-07-05 23:55 ` Marc Horowitz
2005-07-06 1:06 ` Nic Ferrier
2005-07-06 1:15 ` Ken Raeburn
2005-07-06 1:48 ` Nic Ferrier
2005-07-05 22:52 ` Arne Jørgensen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1DpfA4-0004pf-Gh@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=bugs@gnus.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).