From: Eric Schulte <eric.schulte@gmx.com>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-orgmode@gnu.org, Eric Schulte <eric.schulte@gmx.com>
Subject: Re: org-mime-htmlize: visual representation (thunderbird)
Date: Wed, 11 Apr 2012 00:23:54 -0400 [thread overview]
Message-ID: <87d37e6gmd.fsf@gmx.com> (raw)
In-Reply-To: <871unv7ncy.fsf@gilgamesch.quim.ucm.es> (Uwe Brauer's message of "Tue, 10 Apr 2012 15:00:45 +0200")
Uwe Brauer <oub@mat.ucm.es> writes:
>>> On Sun, 01 Apr 2012 12:38:12 -0400, Eric Schulte <eric.schulte@gmx.com> wrote:
> >>
>
> > I'm not clear on how this differs from the messages produced using
> > org-mime-htmlize, and it has been a while since I've looked into email
> > mime mechanics. However, since the emails generated using
> > org-mime-htmlize display correctly in Gmail and in gnus I'm inclined to
> > say that this is a Thunderbird issue and leave it for them to debug.
>
> I send a bug report to the Thunderbird developer and the
> answer was that *one* source of the problem is
>
> ,----
> | Here, the message has a multipart/mixed structure at the top
> | with "cid:" references to the image/png part which is inside
> | that structure (the text/html part is correctly in a
> | multipart/alternative but there is no multipart/related;
> | both images are in the multipart/mixed context). Also, the
> | images have a "Content-Disposition: attachment", both
> | reasons to show them as attachment as Thunderbird does it.
> |
> | Now it seems that Gmail completely ignores multipart/related
> | vs. mixed and simply takes the reference regardless of that
> | context, which would explain what you see. Strictly
> | speaking, the message is incorrectly formed. Please file a
> | bug with Emacs, the latexit structure appears to be correct.
> `----
>
>
> So how could "Content-Disposition: attachment" be changed to
> "Content-Disposition: inline" in your code? I can't find the
> relevant piece of code.
>
> Thanks
>
> Uwe
>
Hi Uwe,
Thanks for sending along this helpful review. I've just pushed two
changes to org-mime so that it now (1) wraps html and images in a
multipart/related mime structure and (2) marks images as "disposition
inline" so that they don't show up as attachments.
I can confirm this new version works in gnus and in the gmx webmail
client as expected, but I don't have access to Thunderbird to check the
behavior there. Please let me know if this fixes the problem.
Thanks,
--
Eric Schulte
http://cs.unm.edu/~eschulte/
next prev parent reply other threads:[~2012-04-11 6:25 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 [this message]
2012-04-11 9:44 ` Uwe Brauer
2012-04-11 13:38 ` Eric Schulte
2012-04-12 11:59 ` Uwe Brauer
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=87d37e6gmd.fsf@gmx.com \
--to=eric.schulte@gmx.com \
--cc=emacs-orgmode@gnu.org \
--cc=oub@mat.ucm.es \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).