Gnus development mailing list
 help / color / mirror / Atom feed
From: Daniel Pittman <daniel@rimspace.net>
Subject: MML 'encoding' tag value ignored...
Date: 28 Feb 2001 14:31:24 +1100	[thread overview]
Message-ID: <87d7c3o54j.fsf@inanna.rimspace.net> (raw)

In trying to work out why a PDF file was being corrupted when sent from
Gnus to several Win32 mailers, I found two things.

Firstly, Gnus was selecting quoted-printable encoding for the PDF file.
This was then incorrectly decoded by both Outlook and Eudora on the
Win32 machine, resulting in a corrupt PDF file.

Specifically, LF => CRLF conversion was happening on the Win32 machine.
Now, I don't know the QP spec well, so I can't tell if this is correct
behaviour for the Win32 machines.

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


The second, and more serious (IMO) issue is that MML encoding ignores
the 'encoding' tag when encoding the buffer and relies exclusively on
detecting the encoding type.

This is wrong, as far as I can tell, when it comes to the arguments
passed to `mm-encode-buffer' from `mml-generate-mime-1'. The `encoding'
tag is not passed to `mm-encode-buffer' from the part definition.

This means that even if I specified base64 encoding in the MML tag
(as: <#part ... encoding=base64>), quoted-printable was chosen.

        Daniel

-- 
Sadness is but a wall between two gardens.
        -- Kahlil Gibran



             reply	other threads:[~2001-02-28  3:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-28  3:31 Daniel Pittman [this message]
2001-02-28 16:39 ` Toby Speight
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=87d7c3o54j.fsf@inanna.rimspace.net \
    --to=daniel@rimspace.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).