From: Christoph Conrad <christoph.conrad@gmx.de>
Cc: bugs@gnus.org, zsh@cs.rochester.edu
Subject: Problems with attachment of zip files
Date: 04 Feb 2001 22:18:13 +0100 [thread overview]
Message-ID: <m34ryatczb.fsf@gmx.de> (raw)
Hi!
Whenever i attach a zip-file with the latest Oort Gnus and send it
from the company to my home account (where i also use the latest Oort
Gnus), i see no button for the attachment. It looks strange, and i
can't save it to a file properly. This behaviour is since at least a
few weeks, i remember that it to be a problem with pre-Oort CVS Gnus.
The headers before content and first/last lines of content follow.
The lines in [...] are skipped.
========================================================================
CUT HERE - CUT HERE - CUT HERE - CUT HERE - CUT HERE - CUT HERE - CUT HE
========================================================================
User-Agent: Gnus/5.090001 (Oort Gnus v0.01) Emacs/20.7
MIME-Version: 1.0
Content-Type: multipart/x-zip
Content-Disposition: attachment; filename=breton.zip
Content-Transfer-Encoding: base64
X-UIDL: 35d3a473ced5a0b6d7c0288cf1f0e883
UEsDBBQAAgAIAGlbRCovuRUlpQcAAEsbAAANAAAAbGlzcC1za2Vscy5lbKVZbW/bNhD+3AL9Dwf1
[...]
cHNnbWwuZWxQSwUGAAAAABQAFACUBAAA5NwCAAAA
-------
========================================================================
CUT HERE - CUT HERE - CUT HERE - CUT HERE - CUT HERE - CUT HERE - CUT HE
========================================================================
Gnus shows in the article buffer the plain lines of the content.
Best regards,
cu, -cc-
--
=> GNU Emacs Webring @ <http://www.gnusoftware.com/WebRing/> <=
Look Ma, this man can twist his fingers as if they were made of rubber,
isn't that amazing? -- Not really, he's been using emacs for years...!
reply other threads:[~2001-02-04 21:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m34ryatczb.fsf@gmx.de \
--to=christoph.conrad@gmx.de \
--cc=bugs@gnus.org \
--cc=zsh@cs.rochester.edu \
/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).