From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 18792@debbugs.gnu.org
Subject: bug#18792: multipart/related with "cid:" image not shown
Date: Wed, 25 Jan 2017 21:32:58 +0100 [thread overview]
Message-ID: <87mveehocl.fsf@gnus.org> (raw)
In-Reply-To: <jwv61fcb3v2.fsf@iro.umontreal.ca> (Stefan Monnier's message of "Wed, 22 Oct 2014 10:01:21 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> [ This also affects trunk, and has probably been going on for a while
> now. ]
>
> I regularly receive emails that contain "a tiny bit of HTML text around
> a picture". Often these have the following MIME structure:
>
> multipart/related
> multipart/alternative
> text/plain
> text/html
> image/jpeg
>
> where the HTML refers to the image via a "cid:" URL.
>
> Here's the problem: Gnus seems to only show me the first element of the
> multipart/related and does not let me get access to the image.
>
> More specifically, I get a display such as:
>
> From: "Toto" <toto@gnu.ca>
> Subject: blabla
> To: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Wed, 22 Oct 2014 12:59:18 +0000 (47 minutes, 13 seconds ago)
>
> 1. (*) text/plain ( ) text/html
>
> Mira esto
> [cid:ED58E6891D72E141A6C22D4BAFEF436F@gnu.ca]
I haven't used "buttonised" article display in yonks, but I think cid:
basically works for me in the articles (I mean spam) I see, and they are
usually multipart/alternative wrapped in multipart/related, I seem to
remember from the last time I looked at it.
Could you forward a complete message that displays the issue?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2017-01-25 20:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 14:01 bug#18792: multipart/related with "cid:" image not shown Stefan Monnier
2017-01-25 20:32 ` Lars Ingebrigtsen [this message]
2017-01-25 21:44 ` Stefan Monnier
2017-01-25 21:51 ` Lars Ingebrigtsen
2018-04-12 21:24 ` Lars Ingebrigtsen
2017-01-26 9:16 ` Andreas Schwab
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mveehocl.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=18792@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.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).