From: Richard Riley <rileyrg@googlemail.com>
To: ding@gnus.org
Subject: Re: Embedded CID Images
Date: Tue, 12 Oct 2010 16:31:53 +0200 [thread overview]
Message-ID: <g7hbgrzdly.fsf@news.eternal-september.org> (raw)
In-Reply-To: <m3hbgrfslh.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Tue, 12 Oct 2010 15:28:26 +0200")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Richard Riley <rileyrg@googlemail.com> writes:
>
>> Then getting back to the original Q : what is the correct way to show CID
>> items? As I said in the snipped bit, all I see is (like the OP)
>> something like
>>
>> [cid:657420512@11102010-2DC7]
>>
>> I wont even pretend to even know wha CID items are : I just know, like
>> the OP, I cant see them ;)
>
> I don't know what they are, either. My guess would be that you're
> looking at a text/plain article that just has the string
> "[cid:657420512@11102010-2DC7]" in the text somewhere.
They are links to text blocks in some cases, images in others.
In fact, bringing up my sample email today it works.
http://www.myupload.org/viewer.php?file=35rn5x7w2i09c5a2k0aq.png
I need to figure out what changes were made to my settings to pinpoint
what triggered it working but I did tale a new git pull today.
next prev parent reply other threads:[~2010-10-12 14:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 12:21 Jake Colman
2010-10-11 12:27 ` Lars Magne Ingebrigtsen
2010-10-11 12:33 ` Richard Riley
2010-10-11 12:55 ` Frank Schmitt
2010-10-11 13:09 ` Richard Riley
2010-10-11 13:14 ` Frank Schmitt
2010-10-11 13:23 ` Richard Riley
2010-10-11 14:06 ` Steinar Bang
2010-10-11 18:22 ` Lars Magne Ingebrigtsen
2010-10-11 18:22 ` Lars Magne Ingebrigtsen
2010-10-11 19:02 ` Steinar Bang
2010-10-11 22:33 ` Dave Goldberg
2010-10-11 23:09 ` Richard Riley
2010-10-12 12:30 ` Lars Magne Ingebrigtsen
2010-10-12 13:20 ` Richard Riley
2010-10-12 13:28 ` Lars Magne Ingebrigtsen
2010-10-12 14:31 ` Richard Riley [this message]
2010-10-12 19:26 ` Dave Goldberg
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=g7hbgrzdly.fsf@news.eternal-september.org \
--to=rileyrg@googlemail.com \
--cc=ding@gnus.org \
/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.
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 NNTP newsgroup(s).