Gnus development mailing list
 help / color / mirror / Atom feed
From: Mike Fabian <mike.fabian@it-mannesmann.de>
Subject: 0x0a is appended to attachments. pgnus 0.95 Bug?
Date: 29 Jul 1999 15:02:12 +0200	[thread overview]
Message-ID: <uiu73fw2z.fsf@it-mannesmann.de> (raw)

When trying to send a *.tar.gz file as an attachment, it seems that
an additional 0x0a character is appended to the end of the file.

For testing I  did send the speedbar-0.8.1.tar.gz as  an attachment to
my own address and used

    `Gcc: nnfolder+archive:archive'

to get a  copy in my archive. When  the test mail returns to  me and I
save the attachment to  the file test4-speedbar-0.8.1.tar.gz, the file
seems to be corrupted:

    ~$ gzip --test --verbose test4-speedbar-0.8.1.tar.gz 
    test4-speedbar-0.8.1.tar.gz:	
    gzip: test4-speedbar-0.8.1.tar.gz: unexpected end of file
        
The original file was OK:

    ~$ gzip --test --verbose speedbar-0.8.1.tar.gz 
    speedbar-0.8.1.tar.gz:	 OK

comparing yields:

    ~$ cmp -l test4-speedbar-0.8.1.tar.gz speedbar-0.8.1.tar.gz
    cmp: EOF on speedbar-0.8.1.tar.gz

    ~$ ll test4-speedbar-0.8.1.tar.gz speedbar-0.8.1.tar.gz
    -rw-r--r--   1 0        Everyone    48086 Jul 29 13:34 speedbar-0.8.1.tar.gz
    -rw-r--r--   1 0        Everyone    48087 Jul 29 14:30 test4-speedbar-0.8.1.tar.gz


i.e. the  received attachment  is one byte  longer than  the original.
Looking at the two files with Emacs I find that the only difference is
the last  byte of test4-speedbar-0.8.1.tar.gz which has  the hex value
0x0a.   After removing  this  byte  diff says  it's  identical to  the
original and I can gunzip it.

The copy of the mail which was  Gcc'ed to my archive does not have the
problem of the  extra 0x0a byte. When I save  the attachment from this
copy,  no 0xa  is appended  and  the saved  file is  identical to  the
original.

Is this a bug or am I doing something wrong? I am using

(version)
"GNU Emacs 20.3.11b.1 (i386-*-nt4.0.1381)
 of Mon Jul 12 1999 on gridlock"
(gnus-version)
"Pterodactyl Gnus v0.95"

Mike

-- 
Dr. Mike Fabian   <mike.fabian@it-mannesmann.de>
Mannesmann Datenverarbeitung 
Mathematische/Technische Systeme Verfahrenstechnik
Rehhecke 50, D-40885 Ratingen
Tel.: +49-2102 97 1763, Fax: +49-2102 97 1345



                 reply	other threads:[~1999-07-29 13:02 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=uiu73fw2z.fsf@it-mannesmann.de \
    --to=mike.fabian@it-mannesmann.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).