From: Uwe Brauer <oub@mat.ucm.es>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org, xemacs-beta@xemacs.org
Subject: Re: [Bug: 21.5-b29] gnus can't send in 21.5.29 but in 21.4.22
Date: Thu, 22 Sep 2011 11:39:15 +0200 [thread overview]
Message-ID: <87vcskhq64.fsf@gilgamesch.quim.ucm.es> (raw)
In-Reply-To: <b4m8vph6va2.fsf@jpl.org> (Katsumi Yamaoka's message of "Thu, 22 Sep 2011 13:44:21 +0900")
>> Regarding Re: [Bug: 21.5-b29] gnus can't send in 21.5.29 but in 21.4.22; Katsumi Yamaoka <yamaoka@jpl.org> adds:
> Done. Not yet tested with XEmacs 21.5 though.
> 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.
> In addition, it assumes that signing and encrypting will never
> generate a boundary pattern in data.
Hm Aidan already committed a patch to Xemacs which takes care
of the problem. Given that the sending function is already
not very fast, I would recommend not to implement your
solution, but this is just a personal opinion.
Uwe Brauer
next prev parent reply other threads:[~2011-09-22 9:39 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 [this message]
2011-09-26 19:19 ` Lars Magne Ingebrigtsen
2011-09-26 23:25 ` Katsumi Yamaoka
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=87vcskhq64.fsf@gilgamesch.quim.ucm.es \
--to=oub@mat.ucm.es \
--cc=ding@gnus.org \
--cc=xemacs-beta@xemacs.org \
--cc=yamaoka@jpl.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).