Re: Re: using orgmode to send html mail?

["Eric Schulte" <schulte.eric@gmail.com>]

Hi,

Given the current setup, sending messages with multiple multipart
sections is simply one optional way of using the `org-mime-htmlize'
function.  By default when `org-mime-htmlize' is called without an
active region the entire message body is encoded as a single MIME
multipart/alternative -- the simpler approach you advocate below.

That said, I'm not sure what you are arguing for.  Are you arguing that
the option to send multiple multipart/alternative sections be removed?
This is an option which could only be used intentionally, hopefully in
full knowledge the potential risks and drawbacks.

In my opinion it is bad design to go out of your way to remove choice
and functionality from a program.  Additionally I don't like the idea of
limiting the functionality of a tool to the level of the lowest common
denominator of it's peers.  That is not how progress is made.

Thanks -- Eric

David Maus <dmaus@ictsoc.de> writes:

> Dan Davison wrote:
>
>>[...]
>
>>> It just makes no sense to create such a nested message: If the
>>> recipient requires html markup than send him html markup.  Why such a
>>> nested message?
>
>>Hi David,
>
>>What about if I'm sending an email containing some org-mode elements
>>like tables, and also some code. I want the reader to he able to see the
>>plain text structure of the tables, so that they know exactly what's
>>going on. But for the code, I would like those using webmail clients to
>>see nicely formatted, fontified code.
>
>>Is that a potential justification?
>
> I cannot answer this question because the whole idea of sending just
> some parts of the entire document is based on a horrible mistake:
>
>> But for the code, I would like those using webmail clients to see
>> nicely formatted, fontified code.
>
> I understand this idea, but: MIME is about message transport, not
> message display.  You want the message displayed in a certain way but
>
>   You have little control over how the content is displayed on the
>   recipients side.
>
> To give an example: I've sent one of the "complex" MIME messages to a
> mail account at GMX, a quite popular german mail hoster and opened it
> in the web interface.
>
> The message was constructed like this (using mml like markup):
>
> < #part type="text/plain">
> First MIME entity
> < #multipart type="alternative">
> < #part type="text/plain">
>   Second in plain text
> < #part type="text/html">
>   <b>Second</b> in HTML
> < /#multipart>
> < #part type="text/plain">
>   Third MIME entity.
> < #part type="text/plain">
>   Fourth in plain text
> < #part type="text/html">
>   <b>Fourth</b> in HTML
> < /#multipart>
>
>   - when I first opened the message I had to toggle the NoScript
>     extension to allow iframes:
>
>     http://s10.directupload.net/file/u/15851/wydtca3n_png.htm
>
>   - after that the html was shown, but... totally messed up
>
>     http://s10.directupload.net/file/u/15851/j43xqkjt_png.htm
>
>   - and finally I chose "plain text" display
>
>     http://s1.directupload.net/file/u/15851/plz64u4a_png.htm
>
>     And the second and fourth part was silently dropped.
>
> Sending a simple message with a plain text body followed by it's html
> representation was displayed fine:
>
> http://s10.directupload.net/file/u/15851/ojdn8pdl_png.htm
>
> See what I mean?
>
>  -- David
>
> --
> OpenPGP... 0x99ADB83B5A4478E6
> Jabber.... dmjena@jabber.org
> Email..... dmaus@ictsoc.de
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode