Gnus development mailing list
 help / color / mirror / Atom feed
From: Toby Speight <streapadair@gmx.net>
Subject: Re: MML 'encoding' tag value ignored...
Date: 28 Feb 2001 16:39:12 +0000	[thread overview]
Message-ID: <s8wvaa4v9r.fsf@lanber.cam.eu.citrix.com> (raw)
In-Reply-To: <87d7c3o54j.fsf@inanna.rimspace.net>

0> In article <87d7c3o54j.fsf@inanna.rimspace.net>,
0> Daniel Pittman <URL:mailto:daniel@rimspace.net> ("Daniel") wrote:

Daniel> In trying to work out why a PDF file was being corrupted when
Daniel> sent from Gnus to several Win32 mailers, I found two things.
Daniel>
Daniel> Firstly, Gnus was selecting quoted-printable encoding for the
Daniel> PDF file.  This was then incorrectly decoded by both Outlook
Daniel> and Eudora on the Win32 machine, resulting in a corrupt PDF
Daniel> file.
Daniel>
Daniel> Specifically, LF => CRLF conversion was happening on the Win32
Daniel> machine.  Now, I don't know the QP spec well, so I can't tell
Daniel> if this is correct behaviour for the Win32 machines.

I think the fix for this is to quote LF and CR in non-text parts:

<LF>     ->  =0A=<CR><LF>
<CR>     ->  =0D=<CR><LF>
<CR><LF> ->  =0D=0A=<CR><LF>


Daniel> If it is, though, I think that 'application/.*' MIME entities
Daniel> should be encoded with base64 exclusively, to avoid this sort
Daniel> of problem.

I thought you could Configure that somehow?

[/me RTFMs]

`mm-content-transfer-encoding-defaults' is what you're looking for,
though it's not defcustom in 5.8.3.



  reply	other threads:[~2001-02-28 16:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-28  3:31 Daniel Pittman
2001-02-28 16:39 ` Toby Speight [this message]
2001-02-28 22:54   ` Daniel Pittman
2001-03-01 11:54     ` Toby Speight

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=s8wvaa4v9r.fsf@lanber.cam.eu.citrix.com \
    --to=streapadair@gmx.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).