From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: Attachments in forwarded messages garbled
Date: Fri, 10 Nov 2006 10:37:14 +0100 [thread overview]
Message-ID: <v98xijod6d.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87y7qk4042.fsf@pereiro.luannocracy.com> (David Abrahams's message of "Thu\, 09 Nov 2006 19\:27\:25 -0500")
[ Redirecting this bug report to ding.
See http://thread.gmane.org/87psbyed2i.fsf%40pereiro.luannocracy.com
or http://thread.gmane.org/gmane.emacs.gnus.user/8168/focus=8176
for the complete thread. ]
On Fri, Nov 10 2006, David Abrahams wrote in gnu.emacs.gnus:
> David Abrahams <dave@boost-consulting.com> writes:
>> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>>> On Wed, Nov 08 2006, David Abrahams wrote:
>>>> Ever since I made the switch to Linux for my main machine, I've been
>>>> having the problem that when I forward (gnus-summary-mail-forward) a
>>>> message that contains an attachment, the recipent gets a garbled
>>>> version of the original attachment.
>>>
>>> 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.
>>
>> I will arrange such a test in a follow-up message.
>
> Was there insufficient information? Is there anything else I
> should do?
Thanks, the information should be sufficient now. I can confirm that
the two base64 encoded parts...
$ ll boost?.base64
[...] 8523 [...] boost1.base64
[...] 8515 [...] boost2.base64
... and the resulting images differ:
$ ll boost?.png
[...] 6308 [...] boost1.png
[...] 6302 [...] boost2.png
Saving in Thunderbird gives the same PNG files (also checked with
cmp):
$ ll boost?.TB.png
[...] 6308 [...] boost1.TB.png
[...] 6302 [...] boost2.TB.png
Could someone look into this problem, please?
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next parent reply other threads:[~2006-11-10 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87psbyed2i.fsf@pereiro.luannocracy.com>
[not found] ` <v98ximmfui.fsf@marauder.physik.uni-ulm.de>
[not found] ` <87mz71c0uh.fsf@pereiro.luannocracy.com>
[not found] ` <87y7qk4042.fsf@pereiro.luannocracy.com>
2006-11-10 9:37 ` Reiner Steib [this message]
2006-11-14 11:55 ` Katsumi Yamaoka
2006-11-14 12:27 ` Reiner Steib
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=v98xijod6d.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
/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).