From: Hobbit <werehobbit@yandex.ru>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: bugs@gnus.org, ding@gnus.org
Subject: Re: bug#8070: gnus damages attached file
Date: Sun, 20 Feb 2011 18:47:29 +0200 [thread overview]
Message-ID: <874o7yd55q.fsf@myhost.localdomain> (raw)
In-Reply-To: <m24o7yagtl.fsf@igel.home> (Andreas Schwab's message of "Sun, 20 Feb 2011 16:03:50 +0100")
[-- Attachment #1: Type: text/plain, Size: 45 bytes --]
>The contents of the file and the raw mail.
[-- Attachment #2: contents and raw mail --]
[-- Type: text/plain, Size: 1395 bytes --]
From: "Evgeny M. Zubok" <evgeny.zubok@tochka.ru>
Subject: Re: bug#8070: gnus damages attached file
Newsgroups: gnus.gnus-bug
Date: Sun, 20 Feb 2011 18:03:12 +0300
Organization: Gnus News User Services
Some additional information.
Orginal README.txt is attached. I've archived it in order to not break
its contents.
Raw mail shows that the same short file is encoded differently when we
use either "text/plane" or "application/msword". This is definetly not
the MTA bacause the raw mail has been saved from Gnus archive (Gcc:
Sent), not from the remote mailer.
X-From-Line: nobody Sun Feb 20 17:43:20 2011
To: "Evgeny M. Zubok" <zoubok@mail.ru>
Subject: Test
X-Draft-From: ("nntp+news.gnus.org:gnus.gnus-bug" "")
From: "Evgeny M. Zubok" <evgeny.zubok@tochka.ru>
Date: Sun, 20 Feb 2011 17:43:18 +0300
Message-ID: <87oc66bwc9.fsf@tochka.ru>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="=-=-="
Lines: 17
Xref: localhost sent:445
X-Gnus-Article-Number: 445 Sun, 20 Feb 2011 17:43:20 +0300
--=-=-=
Hello!
--=-=-=
Content-Type: application/msword
Content-Disposition: attachment; filename=README.txt
Content-Transfer-Encoding: base64
4OHi4+Tl5ucK
--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Disposition: attachment; filename=README.txt
Content-Transfer-Encoding: base64
w6DDocOiw6PDpMOlw6bDpw0K
--=-=-=--
[-- Attachment #3: Type: text/plain, Size: 37 bytes --]
Attachment from the above message:
[-- Attachment #4: README.tar.gz --]
[-- Type: application/octet-stream, Size: 144 bytes --]
next prev parent reply other threads:[~2011-02-20 16:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <871v34nwdn.fsf@myhost.localdomain>
[not found] ` <87aahss3yu.fsf@gnus.org>
[not found] ` <87hbbz6fg4.fsf@myhost.localdomain>
[not found] ` <87vd0fpvzv.fsf@gnus.org>
[not found] ` <874o7z662d.fsf@myhost.localdomain>
[not found] ` <87d3mnk1sy.fsf@myhost.localdomain>
2011-02-20 1:15 ` Lars Ingebrigtsen
2011-02-20 8:49 ` Andreas Schwab
2011-02-20 9:23 ` Hobbit
2011-02-20 9:46 ` Andreas Schwab
2011-02-20 10:46 ` Hobbit
2011-02-20 11:40 ` Andreas Schwab
2011-02-20 13:27 ` Hobbit
2011-02-20 13:41 ` Andreas Schwab
2011-02-20 14:03 ` Hobbit
2011-02-20 14:17 ` Andreas Schwab
2011-02-20 14:34 ` Hobbit
2011-02-20 15:03 ` Andreas Schwab
2011-02-20 16:47 ` Hobbit [this message]
2011-02-20 14:38 ` Hobbit
2011-02-20 15:04 ` Andreas Schwab
2011-02-20 15:25 ` Hobbit
2011-02-20 9:31 ` Hobbit
2011-02-20 9:48 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874o7yd55q.fsf@myhost.localdomain \
--to=werehobbit@yandex.ru \
--cc=bugs@gnus.org \
--cc=ding@gnus.org \
--cc=schwab@linux-m68k.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).