Gnus development mailing list
 help / color / mirror / Atom feed
From: Norman Walsh <ndw@nwalsh.com>
Subject: Multipart/related vs. Multipart/alternative
Date: Thu, 02 Nov 2006 10:13:18 -0500	[thread overview]
Message-ID: <87slh1khkh.fsf@nwalsh.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1479 bytes --]

I have the following declarations in my ~/.gnus file:

(setq gnus-buttonized-mime-types '("multipart/encrypted" "multipart/signed" "multipart/related" "multipart/alternative"))

(custom-set-variables
 ;; Avoid text/html parts if possible (w3-mode is slow).  Also avoid
 ;; text/enriched, since it's often more difficult to read.
 '(mm-discouraged-alternatives '("text/html" "text/enriched"))

 ;; Buttonize text/html rather than display it automatically.  It's frequently
 ;; spam and I don't want to incur the wait to have it render.
 '(mm-automatic-display (remove "text/html" mm-automatic-display))
)

As a consequence, when a message arrives from someone that uses a
(stupid, useless) HTML mail reader, I see the text/plain alternative
by default, but I get a button so that I can tell that there is an
HTML alternative. (This helps for those rare cases where their client
botches the text/plain alternative).

However, I also get the occasional message where the text and HTML
parts aren't sent as alternatives, but rather as multipart/related. In
this case, I get the buttons, but the HTML is displayed by default.

How can I configure things so that the text/plain related part is
displayed by default in this case?

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | The present moment is a powerful
http://nwalsh.com/            | goddess.-- Goethe

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

                 reply	other threads:[~2006-11-02 15:13 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=87slh1khkh.fsf@nwalsh.com \
    --to=ndw@nwalsh.com \
    /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).