Gnus development mailing list
 help / color / mirror / Atom feed
From: "Rene H. Larsen" <renehl@post1.tele.dk>
Subject: Re: gnus sends corrupt attachments
Date: 19 Sep 1999 10:27:43 +0200	[thread overview]
Message-ID: <87so4b71c0.fsf@post1.tele.dk> (raw)
In-Reply-To: kullstam@ne.mediaone.net's message of "18 Sep 1999 22:40:44 -0400"

kullstam@ne.mediaone.net writes:

> 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.

This is probably because pGnus by default attaches many binary files
using quoted printable encoding rather than the more robust base64
encoding.  Try putting this in your .gnus and see if it helps:

;;; Disable QP for unknown (binary) mime types.
(setq mm-content-transfer-encoding-defaults
  '(("text/x-patch" 8bit)
    ("text/.*" qp-or-base64)
    ("message/rfc822" 8bit)
    ("application/emacs-lisp" 8bit)
    ("application/x-patch" 8bit)
    (".*" base64)))

HTH.
-- 
#!/usr/bin/perl -w
for(0..12){$b[$_]="|".($_==6?"-":" ")x78}for(0..78){substr($b[-
(sin($_*3.1415/22)-1)*6.499],$_,1)="*"}print join "\n",@b,"";


  reply	other threads:[~1999-09-19  8:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-19  2:40 kullstam
1999-09-19  8:27 ` Rene H. Larsen [this message]
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=87so4b71c0.fsf@post1.tele.dk \
    --to=renehl@post1.tele.dk \
    /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).