Exporting mime email

Exporting mime email

[Mark Walters]

Hello

What is the best way of exporting/saving as text a mime-encoded email
from the emacs interface (e.g, if I want to save a mime-encoded
email containing a patch)?

For non-mime emails View-raw is fine, but with mime encoded emails such
as (picked pretty much at random)
id:"1325240897-27525-1-git-send-email-dme@dme.org"
I haven't found any non-hack method.

Many thanks

Mark

Re: Exporting mime email

[Jameson Graef Rollins]

[-- Attachment #1: Type: text/plain, Size: 356 bytes --]

On Fri, 06 Jan 2012 00:29:39 +0000, Mark Walters <markwalters1009@gmail.com> wrote:
> What is the best way of exporting/saving as text a mime-encoded email
> from the emacs interface (e.g, if I want to save a mime-encoded
> email containing a patch)?

Maybe you're looking for '|'?  That will pipe the raw message to
whatever command is specified.

jamie.

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

Re: Exporting mime email

[Mark Walters]

Hi

On Thu, 05 Jan 2012 16:44:10 -0800, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
> On Fri, 06 Jan 2012 00:29:39 +0000, Mark Walters <markwalters1009@gmail.com> wrote:
> > What is the best way of exporting/saving as text a mime-encoded email
> > from the emacs interface (e.g, if I want to save a mime-encoded
> > email containing a patch)?
> 
> Maybe you're looking for '|'?  That will pipe the raw message to
> whatever command is specified.

What I would like is a way of exporting the decoded text rather than the
raw message. As an explicit example I would like to be able to export a
mime encoded email containing a patch, and then do something like

patch -p1 < exported_file

Sorry for not making myself clear

Many thanks

Mark

Re: Exporting mime email

[David Edmondson]

[-- Attachment #1: Type: text/plain, Size: 662 bytes --]

On Fri, 06 Jan 2012 00:29:39 +0000, Mark Walters <markwalters1009@gmail.com> wrote:
> What is the best way of exporting/saving as text a mime-encoded email
> from the emacs interface (e.g, if I want to save a mime-encoded email
> containing a patch)?
> 
> For non-mime emails View-raw is fine, but with mime encoded emails such
> as (picked pretty much at random)
> id:"1325240897-27525-1-git-send-email-dme@dme.org"
> I haven't found any non-hack method.

That message is 8bit UTF-8 at my end. Saving it use '|' works just fine
for me. What encoding do you see?

(And you should use id:"1325599946-5936-1-git-send-email-dme@dme.org"
instead :-))

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: Exporting mime email

[Mark Walters]

Hello

On Fri, 06 Jan 2012 08:35:27 +0000, David Edmondson <dme@dme.org> wrote:
> On Fri, 06 Jan 2012 00:29:39 +0000, Mark Walters <markwalters1009@gmail.com> wrote:
> > What is the best way of exporting/saving as text a mime-encoded email
> > from the emacs interface (e.g, if I want to save a mime-encoded email
> > containing a patch)?
> > 
> > For non-mime emails View-raw is fine, but with mime encoded emails such
> > as (picked pretty much at random)
> > id:"1325240897-27525-1-git-send-email-dme@dme.org"
> > I haven't found any non-hack method.
> 
> That message is 8bit UTF-8 at my end. Saving it use '|' works just fine
> for me. What encoding do you see?

Does saving the message like this give you a file you can apply directly
with the patch command? When I save it (using | or from view-raw) I get
a message which looks like

(Delivery headers)
From: ...
To: ...
Subject: =?UTF-8?q?=5BPATCH=5D=20emacs=3A=20Improved=20printing=20support=2E?=
Date: ..
(some X and list headers)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: notmuch-bounces@notmuchmail.org
Errors-To: notmuch-bounces@notmuchmail.org

QWRkIHZhcmlvdXMgZnVuY3Rpb25zIHRvIHByaW50IG5vdG11Y2ggbWVzc2FnZXMgYW5kIHRpZSB0
aGVtIHRvZ2V0aGVyCndpdGggYSBzaW1wbGUgZnJvbnRlbmQuIE5vIGtleWJpbmRpbmcgaXMgY3Vy
cmVudGx5IG1hZGUgdG8gZW5jb3VyYWdlCnBhcGVyIHNhdmluZy4KLS0tCgpSZXN1cnJlY3Rpbmcg
.. for 100 lines or so

The saved file is identical to the file  in my maildir. But feeding it
to patch in the form  patch -p1 < exported_file does not work.

I have just discovered git am which solves this problem for patches but
I think it might be useful to be able to export the plain-text email
sometimes.

(If this is all some messed up utf-8 settings my end then many apologies
for the noise)

Many thanks 

Mark

Re: Exporting mime email

[David Edmondson]

[-- Attachment #1: Type: text/plain, Size: 820 bytes --]

On Fri, 06 Jan 2012 10:27:16 +0000, Mark Walters <markwalters1009@gmail.com> wrote:
> Does saving the message like this give you a file you can apply directly
> with the patch command? When I save it (using | or from view-raw) I get
> a message which looks like

Ahh. This particular message is a bad example for me to check, because I
have the version that I bcc'd rather than the one delivered by the
mailing list.

Presumably something is converting it from 8bit to base64 along the
path.

I scouted around for other messages that include © (which is what I
presume causes the encoding), but the ones I have are all still 8bit.

> I have just discovered git am which solves this problem for patches but
> I think it might be useful to be able to export the plain-text email
> sometimes.

Agreed.

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: Exporting mime email

[Mark Walters]

Hi

> Presumably something is converting it from 8bit to base64 along the
> path.

If it makes a difference my setup is gmail->offlineimap->notmuch

> I scouted around for other messages that include © (which is what I
> presume causes the encoding), but the ones I have are all still 8bit.

A different example which shows the same problem (for me) is
id:"m2fwg1uapw.fsf@gmail.com"

Many thanks

Mark

Re: Exporting mime email

[David Edmondson]

[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]

On Fri, 06 Jan 2012 10:51:47 +0000, Mark Walters <markwalters1009@gmail.com> wrote:
> > Presumably something is converting it from 8bit to base64 along the
> > path.
> 
> If it makes a difference my setup is gmail->offlineimap->notmuch

Mine is the same for the relevant messages.

> > I scouted around for other messages that include © (which is what I
> > presume causes the encoding), but the ones I have are all still 8bit.
> 
> A different example which shows the same problem (for me) is
> id:"m2fwg1uapw.fsf@gmail.com"

This one is encoded as quoted-printable. I agree that the output of
     | cat >/tmp/file
in the emacs UI produces the encoded file and that it is identical to
the file on disk.

Hence, I can reproduce the problem you reported :-)

(Maybe amusingly) the printing stuff that you originally mentioned
included some code to produce a 'text' version of a message for
printing. Maybe that could also be used to implement a simple
`notmuch-show-save-message' command?

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]