bug#28671: 25.2; double transfer-encoding in rmailedit for complex mime messages

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

bug#28671: 25.2; double transfer-encoding in rmailedit for complex mime messages

Ken Olum
When rmail-edit-current-message gets a mime message which is too complex
for it to handle (i.e., anything but one "text/plain" part), it just
gives you the raw message to edit.  If you do so, rmail-cease-edit then
applies the transfer-encoding even though the message wasn't decoded,
and so on.  It also in some circumstances it also moves the marker for
the beginning of the following message.

The attached patch modifies rmail-cease-edit to check the
rmail-old-mime-state flag set by rmail-edit-current-message when it is
editing the raw message.  If set, rmail-cease-edit inserts the
already-encoded body without further processing.  It also deletes the
old body after inserting the new, rather than before, to avoid moving
the next message's marker.

                                        Ken

In GNU Emacs 25.2.2 (x86_64-unknown-linux-gnu, X toolkit, Xaw scroll bars)
 of 2017-05-29 built on olum.org
Windowing system distributor 'The X.Org Foundation', version 11.0.11804000
System Description: Ubuntu 16.04.3 LTS

Configured features:
XPM JPEG TIFF GIF PNG SOUND NOTIFY FREETYPE XFT ZLIB TOOLKIT_SCROLL_BARS
LUCID X11


rmailedit.patch (2K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

bug#28671: 25.2; double transfer-encoding in rmailedit for complex mime messages

Eli Zaretskii
> From: Ken Olum <[hidden email]>
> Date: Mon, 02 Oct 2017 11:37:46 -0400
> Cc: [hidden email]
>
> When rmail-edit-current-message gets a mime message which is too complex
> for it to handle (i.e., anything but one "text/plain" part), it just
> gives you the raw message to edit.  If you do so, rmail-cease-edit then
> applies the transfer-encoding even though the message wasn't decoded,
> and so on.  It also in some circumstances it also moves the marker for
> the beginning of the following message.
>
> The attached patch modifies rmail-cease-edit to check the
> rmail-old-mime-state flag set by rmail-edit-current-message when it is
> editing the raw message.  If set, rmail-cease-edit inserts the
> already-encoded body without further processing.  It also deletes the
> old body after inserting the new, rather than before, to avoid moving
> the next message's marker.

Thanks.  Could you please send a small mbox file which could be used
to reproduce the problem and test the solution?

A couple of minor comments to the patch:

>   ;; Re-apply content-transfer-encoding, if any, on the message body.
> - (cond
> - ((string= character-coding "quoted-printable")
> -  (mail-quote-printable-region start (point-max)))
> - ((and (string= character-coding "base64") is-text-message)
> -  (base64-encode-region start (point-max)))
> - ((and (eq character-coding 'uuencode) is-text-message)
> -  (error "uuencoded messages are not supported")))
> +        (unless mime-state              ; if set, already transfer-encoded
> +          (cond
> +           ((string= character-coding "quoted-printable")
> +            (mail-quote-printable-region start end))
> +           ((and (string= character-coding "base64") is-text-message)
> +            (base64-encode-region start end))
> +           ((and (eq character-coding 'uuencode) is-text-message)
> +            (error "uuencoded messages are not supported"))))

You could easily make the change less intrusive by simply adding the
mime-state condition as the first alternative in 'cond' with no
action, right?

Also, please add a commit log message for the changes formatted as a
ChangeLog entry (e.g., using "C-x 4 a").



Reply | Threaded
Open this post in threaded view
|

bug#28671: 25.2; double transfer-encoding in rmailedit for complex mime messages

Ken Olum
Here is a test file.  Edit the first message and make some change (e.g.,
to the subject header).  Then the body will end up base64 encoded
twice.  If you then go to the next message, the headers will have extra
lines at the top due to marker problems.  The patch should fix these
problems.

Here's a new patch with the simplified code as you suggested, and
here's a change log entry:

----------------------------------------------------------------------
2017-10-02  Ken Olum  <[hidden email]>

        Fix problems when editing raw message (Bug#28671)

        * lisp/mail/rmailedit.el (rmail-cease-edit): if rmail-old-mime-state
        is set, meaning that we are editing the raw message, do not
        encode it again.  Delete old body after, not before, inserting
        new, to avoid moving marker at beginning of next message.
----------------------------------------------------------------------

                                        Ken


rmail-test (1K) Download Attachment
rmailedit.patch (2K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

bug#28671: 25.2; double transfer-encoding in rmailedit for complex mime messages

Eli Zaretskii
> From: Ken Olum <[hidden email]>
> Cc: [hidden email], [hidden email]
> Date: Mon, 02 Oct 2017 13:47:20 -0400
>
> Here is a test file.  Edit the first message and make some change (e.g.,
> to the subject header).  Then the body will end up base64 encoded
> twice.  If you then go to the next message, the headers will have extra
> lines at the top due to marker problems.  The patch should fix these
> problems.
>
> Here's a new patch with the simplified code as you suggested, and
> here's a change log entry:

Thanks, pushed to the release branch.