Re: [Bug: 21.5-b29] gnus can't send in 21.5.29 but in 21.4.22
Reiner Steib wrote:
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].
I knew it. Aidan's change seems generally useful. But I realized
today, avoiding the error in question is not a solution in this case.
The root cause is that `mml-compute-boundary-1' was mis-designed.
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?
Yes, it is necessary for not only XEmacs. If the slowdown is not
disregarded, I think we will possibly be able to make a change so
as to make the mml functions encode a part only once. Though it
will need major changes on those functions and will take much time.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta