From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Cc: xemacs-beta@xemacs.org
Subject: Re: [Bug: 21.5-b29] gnus can't send in 21.5.29 but in 21.4.22
Date: Tue, 27 Sep 2011 08:25:52 +0900 [thread overview]
Message-ID: <b4m1uv251j3.fsf@jpl.org> (raw)
In-Reply-To: <m339fjxgaa.fsf@stories.gnus.org>
Lars Magne Ingebrigtsen wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> Done.
> Great; thanks.
>> The new function definition encodes every part in the same way
>> practicing when actually sending them in advance and then looks
>> for things like a MIME boundary. So it may slow message sending.
> But it should be done -- otherwise we can't be sure of successfully
> sending these messages, so I think your fix is totally the right thing.
But encoded data made for only computing a boundary can be used
for sending, too. So, the mml functions for sending may be
rearranged so as to encode all parts of a message first, compute
a boundary, and combine them. It seems not easy to achieve, though.
>> In addition, it assumes that signing and encrypting will never
>> generate a boundary pattern in data.
> True. Hm... is that possible?
I'm not quite sure of it. I was only worried a user who has no
caching mechanism will be bothered by being prompted for
a passphrase twice a part if performing signing or encrypting
for computing a boundary.
prev parent reply other threads:[~2011-09-26 23:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <877h53i7um.fsf@gilgamesch.quim.ucm.es>
[not found] ` <87ty86bqwj.fsf@uwakimon.sk.tsukuba.ac.jp>
2011-09-21 7:20 ` Reiner Steib
2011-09-21 17:32 ` Lars Magne Ingebrigtsen
2011-09-22 1:59 ` Katsumi Yamaoka
2011-09-22 4:44 ` Katsumi Yamaoka
2011-09-22 6:50 ` Reiner Steib
2011-09-22 11:10 ` Katsumi Yamaoka
2011-09-22 9:39 ` Uwe Brauer
2011-09-26 19:19 ` Lars Magne Ingebrigtsen
2011-09-26 23:25 ` Katsumi Yamaoka [this message]
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=b4m1uv251j3.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
--cc=xemacs-beta@xemacs.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).