From: David Abrahams <dave@boost-consulting.com>
Subject: Re: Attachments in forwarded messages garbled
Date: Wed, 08 Nov 2006 15:38:10 -0500 [thread overview]
Message-ID: <877iy58yj1.fsf@pereiro.luannocracy.com> (raw)
In-Reply-To: <m21wodesd4.fsf@sl392.st-edmunds.cam.ac.uk>
Leo <sdl.web@gmail.com> writes:
> On Wed, 08/11/06, David Abrahams wrote:
>
>> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>>
>>> Without *any* kind of information what is kind of problem the
>>> "garbled" message/attachment has, it's next to impossible to help you.
>>> You might send such a message to gmane.test or send us a gzipped mbox
>>> of the received message. Be sure not to include private stuff.
>>
>> If Gnus cooperates, this message should include two enclosures: an
>> inline image (the Boost logo) and a forwarded email message. The
>> original email message being forwarded contained a copy of the same
>> image (inline), and it was received cleanly.
>>
>
>
> I can't see the second image with Gnus 5.11.
Right, that's the whole point. If you look at the raw text of the
message (`C-u g') you'll see two instances therein of the following:
Content-Type: image/png
Content-Disposition: inline; filename=boost.png
Content-Transfer-Encoding: base64
but the 2nd one is garbled so as to be invisible (in this case). In
more recent Gnusen you'll see an empty box where the image should be.
--
Dave Abrahams
Boost Consulting
www.boost-consulting.com
prev parent reply other threads:[~2006-11-08 20:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 5:12 David Abrahams
2006-11-08 9:45 ` Reiner Steib
2006-11-08 17:19 ` David Abrahams
2006-11-10 0:27 ` David Abrahams
2006-11-08 17:28 ` David Abrahams
2006-11-08 17:54 ` Leo
2006-11-08 20:38 ` David Abrahams [this message]
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=877iy58yj1.fsf@pereiro.luannocracy.com \
--to=dave@boost-consulting.com \
/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).