Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
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 08:50:22 +0200	[thread overview]
Message-ID: <87fwjpoytt.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <b4m8vph6va2.fsf@jpl.org> (Katsumi Yamaoka's message of "Thu, 22 Sep 2011 13:44:21 +0900")

On Thu, Sep 22 2011, Katsumi Yamaoka wrote:

> Katsumi Yamaoka wrote:
>> I realized what we have to fix is `mml-compute-boundary-1'.  [...]
>> The function looks for ones that are the same as a MIME boundary
>> (e.g., =-=-=) in contents of MIME parts, and updates the boundary
>> pattern so as to be unique, if any.  Contents to be checked should
>> be encoded ones, however it doesn't so.  As for a file to attach,
>> it reads the file without binding `coding-system-for-read', doesn't
>> encode it, and looks for things like the boundary in it.  That is
>> the root cause of an XEmacs 21.5 error.
>
> 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.

Note that Aidan Kehoe added ".pdf" to `binary-file-regexps' in XEmacs
21.5 now[1].  If the slowdown is notable and the change is only
because of the reported XEmacs problem, it is not necessary, I think.
Or does your commit fix a more general problem?

[1] http://thread.gmane.org/gmane.emacs.xemacs.beta/35574

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



  reply	other threads:[~2011-09-22  6:50 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 [this message]
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

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=87fwjpoytt.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --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).