Re: Questions about mail, MIME, etc.

[Eric Abrahamsen <eric@ericabrahamsen.net>]

Peter Davis <pfd@pfdstudio.com> writes:

> On Thu, May 08, 2014 at 10:34:26PM +0800, Eric Abrahamsen wrote:
>> Peter Davis <pfd@pfdstudio.com> writes:
>> 
>> Yeah I got that error too, a while ago, and your message prompted me to
>> look at it. It seems like org-mime is just a bit behind the state of
>> org-export, and fixing that one dead function link is enough to make it
>> work again. I've attached a patch.
>
> Excellent! That worked. Thank you!

Okay, I'll start a new thread and see if we can get the patch accepted.

>> 
>> Generating a message buffer is pretty much hard-coded into org-mime.
>> Once you're in that buffer, though, the (non-interactive) function
>> mml-generate-mime will return the fully encoded mime message as a
>> string -- you could save that to a file and do something else with it.
>> I'm not 100% confident that's the simplest way to do that.
>
> Ok, I was able to send the message through gnus, even though I don't (normally) use it as a mail reader.
>
>> >  3) What I'd really like is a multipart/alternative message where
>> > one part is text/plain, and looks exactly like the emacs buffer
>> > display, and the other part is text/html, and
>> >     looks like what org would export to html, complete with tables, images, etc.
>> 
>> As far as I know, that's exactly what org-mime does!
>
> Almost. It looks like org-mime puts the actual contents of the buffer
> into the text/plain part, including links, etc. that would normally be
> hidden on display. I think it would be
> more useful to make the text/plain part contain what would be output from exporting to text. But maybe that's just my preference.

org-mime assumes a native 'org export format for the plain text part of
the email. That looks like it's hard-coded in `org-mime-compose',
unfortunately.

Eric