emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-orgmode@gnu.org
Cc: ding@gnus.org
Subject: Re: org-mime-htmlize: visual representation (thunderbird)
Date: Thu, 12 Apr 2012 13:59:38 +0200	[thread overview]
Message-ID: <87bomxxis5.fsf@mat.ucm.es> (raw)
In-Reply-To: 87vcl64cd5.fsf@gmx.com

>> On Wed, 11 Apr 2012 09:38:46 -0400, Eric Schulte <eric.schulte@gmx.com> wrote:

   > Hi Uwe,
   > Uwe Brauer <oub@mat.ucm.es> writes:

   > OK, for my own edification I had changed the message body from
   > (I'm hoping these are sufficiently quoted to survive mailing)

   > ,----[original]
   > | 
   > | 
   > |   text alternative...
   > | 
   > | html alternative... |

   > |   images for html...
   > `----

   > to

   > ,----[revised (and more broken in TB)]
   > | 
   > | 
   > |   text alternative...
   > | 
   > |

   > |   html alternative...
   > |   images for html...
   > | 
   > | 
   > `----

   > which wraps the html and images into a multipart/related type.

   > Why is this later structure illegal?  Are nested multi type parts not
   > allowed?  Also, it seems that everything I've tried works in gnus and in
   > most web user agents.  Is thunderbird simply a stickler for the letter
   > of the RFC law?

I cannot answer this. However I rechecked everything and the
issue is the following.
   >> Which brings me to the good news. After I wrote to you
   >> I received a message from the TB developers which
   >> emphasised that, besides the information I have gave
   >> you, the main point is the header, which should be
   >> Content-type: multipart/related; boundary="=-=-="
   >> and the thunderbird developers insist that this is the 
   >> RFC 2387 standard.
   >> Gnus actually generate  via the mml-generate-mime function
   >> the header 
   >> Content-type: multipart/mixed; boundary="=-=-="
   >> which is wrong.

   > OK, I've just reverted my change, but I'm keeping the change of image
   > disposition to "inline".

I own you an apology!  If I leave mml-generate-mime
untouched, that is I neither use my modification nor do I
use  use Lars new code, but  I use your *new* code then the
generated and sent message is displayed *correctly* in

The resulting  message contains 

Content-type: multipart/alternative; boundary="=-=-="

Instead of 

Content-type: multipart/related; boundary="=-=-="

As it would in my case, but it seems that thunderbird is OK
with that.

The reason I wrote you earlier that your changes made things
worse was that I did make a mistake in my modification of
mml-generate-mime. I also thought I checked your code with
the old mml function but  for some reason the old version was
not used even after a restart.

Sorry for the trouble!


  reply	other threads:[~2012-04-12 12:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-27 11:01 org-mime-htmlize: visual representation (thunderbird) Uwe Brauer
2012-03-31 17:13 ` Eric Schulte
2012-04-01 15:19   ` Uwe Brauer
2012-04-01 16:38     ` Eric Schulte
2012-04-10 13:00       ` Uwe Brauer
2012-04-11  4:23         ` Eric Schulte
2012-04-11  9:44           ` Uwe Brauer
2012-04-11 13:38             ` Eric Schulte
2012-04-12 11:59               ` Uwe Brauer [this message]
2012-04-12 12:21                 ` Eric Schulte

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bomxxis5.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --cc=ding@gnus.org \
    --cc=emacs-orgmode@gnu.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).