Gnus development mailing list
 help / color / mirror / Atom feed
From: kullstam@ne.mediaone.net
Subject: gnus sends corrupt attachments
Date: 18 Sep 1999 22:40:44 -0400	[thread overview]
Message-ID: <m23dwbipxv.fsf@sophia.axel.nom> (raw)


i am using pgnus 0.96 and am having some trouble with attachments.
when i attach a binary (e.g., pdf or zip file) the file gets
corrupted.  the problem is with sending since 1) i can receive
attachments sent with other MUAs (mutt or netscape), and 2) other MUAs
(mutt) receive the same corrupted attachment.

i notice by looking at the received binary that i get extra line
breaks preceeded by a !.

here is an excerpt from the tail of a pdf file.  (please excuse long lines)

orig ending

R^M/Info 1 0 R^M/ID [<5c657a9ab424633503301772053391a4><5c657a9ab424633503301772053391a4>]^M>>^Mstartxref^M21150^M%%EOF

gnus mangled ending

R^M/Info 1 0 R^M/ID [<5c657a9ab42463350!
3301772053391a4><5c657a9ab424633503301772053391a4>]^M>>^Mstartxref^M21150^M%%EOF

as you can see, the !<lf> got somehow inserted.  is this a gnus
configuaration problem i can fix by setting the proper variable?  is
this a known gnus sending problem?  i am happy to send my config upon
request.

i'll delve into it, if no one already has a quick solution.

-- 
J o h a n  K u l l s t a m
[kullstam@ne.mediaone.net]
Don't Fear the Penguin!


             reply	other threads:[~1999-09-19  2:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-19  2:40 kullstam [this message]
1999-09-19  8:27 ` Rene H. Larsen
1999-09-19 19:36   ` Johan Kullstam
1999-09-19 20:37     ` Kai Großjohann
1999-09-19 22:22       ` Johan Kullstam
1999-09-20 10:39       ` Robert Bihlmeyer
1999-09-20 19:49         ` Raja R Harinath
1999-09-22 21:19           ` Shenghuo ZHU
1999-09-25  9:35           ` Lars Magne Ingebrigtsen
1999-09-26  5:52             ` Shenghuo ZHU
1999-09-27 17:40               ` Lars Magne Ingebrigtsen
1999-09-25  9:37           ` Lars Magne Ingebrigtsen

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=m23dwbipxv.fsf@sophia.axel.nom \
    --to=kullstam@ne.mediaone.net \
    /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).