From: jidanni@jidanni.org
To: ding@gnus.org
Subject: Re: Why won't gnus display certain messages
Date: Fri, 16 Nov 2007 03:52:35 +0800 [thread overview]
Message-ID: <877ikj477g.fsf@jidanni.org> (raw)
In-Reply-To: <87k5onc5m4.fsf@catnip.gol.com>
MB> Your example message has an _empty_ "text" alternative, along with
MB> a non-empty "html" alternative, and Gnus is displaying the (empty)
MB> text alternative (because you told it to with the above settings).
Which occurs about 50% of the Mime alternatives messages I receive too.
MB> The real problem of course is that the software that sent the message
MB> screwed up big-time by including an unusable text alternative.
Sure hope gnus has facilities to detect such, and roll with the punches.
next prev parent reply other threads:[~2007-11-15 19:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3362.1194893976.18990.info-gnus-english@gnu.org>
2007-11-13 1:10 ` Miles Bader
2007-11-13 1:51 ` reader
2007-11-13 7:47 ` Tassilo Horn
2007-11-16 14:38 ` reader
2007-11-15 19:52 ` jidanni [this message]
2007-11-15 23:51 ` Miles Bader
2007-11-16 14:04 ` reader
2007-11-12 18:50 reader
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=877ikj477g.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=ding@gnus.org \
/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).