From: Vladimir Volovich <vvv@vvv.vsu.ru>
Subject: someone have broke removing non-base64 text at the end
Date: 03 May 2000 14:07:13 +0400 [thread overview]
Message-ID: <eybt2o2bhq.fsf@video.uic.vsu.ru> (raw)
Hi,
After Lars applied a patch for mm-decode-content-transfer-encoding:
2000-04-21 15:38:06 Vladimir Volovich <vvv@vvv.vsu.ru>
* mm-bodies.el (mm-decode-content-transfer-encoding): Remove
non-base64 text at the end.
i was able to read broken base64 parts.
With the current CVS version, this no longer works. I see wt least two
relevant log messages:
2000-04-21 19:38:43 Shenghuo ZHU <zsh@cs.rochester.edu>
* mm-bodies.el (mm-decode-content-transfer-encoding): Don't remove
non-base64 text at the end if not found.
2000-04-27 15:27:54 Shenghuo ZHU <zsh@cs.rochester.edu>
* message.el (message-send-mail-partially-limit): New variable.
(message-send-mail-partially): New function.
(message-send-mail): Use it.
* mm-bodies.el (mm-decode-content-transfer-encoding): Remove
all blank lines inside of base64.
* mm-partial.el (mm-inline-partial): Add an option. Remove tail
blank lines.
Could you please fix this? If a base64-encoded MIME part contains junk
after base64 body, it is now not decoded by gnus. :-(
Best,
v.
next reply other threads:[~2000-05-03 10:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-03 10:07 Vladimir Volovich [this message]
2000-05-03 12:45 ` Shenghuo ZHU
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=eybt2o2bhq.fsf@video.uic.vsu.ru \
--to=vvv@vvv.vsu.ru \
/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).