From: David Abrahams <dave@boost-consulting.com>
Subject: Re: Attachments in forwarded messages garbled
Date: Wed, 08 Nov 2006 12:28:28 -0500 [thread overview]
Message-ID: <87psbxalvn.fsf@pereiro.luannocracy.com> (raw)
In-Reply-To: <v98ximmfui.fsf@marauder.physik.uni-ulm.de>
[-- Attachment #1: Type: text/plain, Size: 573 bytes --]
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.
[-- Attachment #2: boost.png --]
[-- Type: image/png, Size: 6308 bytes --]
[-- Attachment #3: Type: message/rfc822, Size: 9034 bytes --]
[-- Attachment #3.1.1: boost.png --]
[-- Type: image/png, Size: 6302 bytes --]
[-- Attachment #3.1.2: Type: text/plain, Size: 61 bytes --]
--
Dave Abrahams
Boost Consulting
www.boost-consulting.com
[-- Attachment #4: Type: text/plain, Size: 62 bytes --]
--
Dave Abrahams
Boost Consulting
www.boost-consulting.com
[-- Attachment #5: Type: text/plain, Size: 161 bytes --]
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
http://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2006-11-08 17:28 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 [this message]
2006-11-08 17:54 ` Leo
2006-11-08 20:38 ` David Abrahams
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=87psbxalvn.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).