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: Thu, 22 Sep 2011 10:59:07 +0900 [thread overview]
Message-ID: <b4md3et9w2c.fsf@jpl.org> (raw)
In-Reply-To: <m3obyd7qdf.fsf@stories.gnus.org>
Lars Magne Ingebrigtsen wrote:
> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>> There you may find a possible solution[1] or a workaround[2] there. I
>> don't know why[1] hasn't been implemented.
>>
>> ,----[ http://thread.gmane.org/gmane.emacs.gnus.general/68154/focus=68185 ]
>>| Gnus should bind `coding-system-for-read' then to the value of
>>| `mm-binary-coding-system' that defaults to `binary'. However,
>>| it seems to have been set to nil or `undecided':
>> `----
> I don't know why, either. Katsumi?
I realized what we have to fix is `mml-compute-boundary-1'. It
may take a couple of days (or shorter?). I'll work on it.
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.
next prev parent reply other threads:[~2011-09-22 1:59 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 [this message]
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
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=b4md3et9w2c.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).