MIME garbage at end of composed messages

9 views
Skip to first unread message

Mathieu Boespflug

unread,
Apr 26, 2014, 12:43:51 PM4/26/14
to mu-di...@googlegroups.com
Hi,

using mu4e HEAD and emacs-24.3.1, MIME related garbage appears at the end of every message that I send. E.g.

User-agent: mu4e 0.9.9.6pre2; emacs 24.3.1
From: foo
To: bar
Subject: test message
Date: Sat, 26 Apr 2014 17:48:31 +0200
Message-ID: <87tx9g6...@tweag.net>

test body
--
Sent with my mu4e
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Essentially, the last two headers get tacked on to the end of the *message*, rather than to the end of the *existing set of headers*. Using compose-mail directly doesn't exhibit this behaviour. Has anyone else seen this too, and if so anyone know of any solution?

I ran this through the Emacs debugger and it seems that this issue is related to a problem with narrowing in message-encode-message-body.

Best,

Mathieu

Dirk-Jan C. Binnema

unread,
Apr 27, 2014, 3:06:47 AM4/27/14
to mu-di...@googlegroups.com
Hi Mathieu,

On Saturday Apr 26 2014, Mathieu Boespflug <mb...@tweag.net> wrote:

> Hi,
>
> using mu4e HEAD and emacs-24.3.1, MIME related garbage appears at the end
> of every message that I send. E.g.
>
> User-agent: mu4e 0.9.9.6pre2; emacs 24.3.1
^^^^

Note that mu4e HEAD actually has 0.9.9.6pre3.

> From: foo
> To: bar
> Subject: test message
> Date: Sat, 26 Apr 2014 17:48:31 +0200
> Message-ID: <87tx9g6...@tweag.net>
>
> test body
> --
> Sent with my mu4e
> MIME-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
>
> Essentially, the last two headers get tacked on to the end of the
> *message*, rather than to the end of the *existing set of headers*. Using
> compose-mail directly doesn't exhibit this behaviour. Has anyone else seen
> this too, and if so anyone know of any solution?
>
> I ran this through the Emacs debugger and it seems that this issue is
> related to a problem with narrowing in message-encode-message-body.


Do you still see this with the latests? (ie., after git pull, make
distclean and a full rebuild)? If so, please file an issue in github.

Thanks,
Dirk.


--
Dirk-Jan C. Binnema Helsinki, Finland
e:dj...@djcbsoftware.nl w:www.djcbsoftware.nl
pgp: D09C E664 897D 7D39 5047 A178 E96A C7A1 017D DA3C

Mathieu Boespflug

unread,
Apr 27, 2014, 3:38:26 AM4/27/14
to mu-di...@googlegroups.com
Same results with -pre3 from a clean build. Creating a ticket.
> --
> You received this message because you are subscribed to a topic in the Google Groups "mu-discuss" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/mu-discuss/gu36WXREDtU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to mu-discuss+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages