Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: reader@newsguy.com
To: info-gnus-english@gnu.org
Cc: ding@gnus.org
Subject: Why won't gnus display certain messages
Date: Mon, 12 Nov 2007 12:50:00 -0600	[thread overview]
Message-ID: <87pryfl2nb.fsf@newsguy.com> (raw)

I got a recent email I suspect was generated on a webmail setup.
Gnus displays it in a completely unusable form.   (Included at the
end)

I've been using w3m to display html emails and mostly it has worked ok
but in this case it fails miserably.

From ~/.gnus
  (setq mm-automatic-display (remove "text/html" mm-automatic-display)
       mm-discouraged-alternatives '("text/html" "text/richtext"))  
  (setq mm-text-html-renderer (quote w3m))

I forwarded the message from my linux setup to a machine running
windows XP and forte-agent.   That `agent' displays the message fine. 

In gnus there actually is nothing displayed for body.  But viewing the
message with `C-u g' shows these mail and mime headers. I've chopped
out or mangled some headers and all but two lines of what gnus has
displayed for the body.

Can anyone tell from this information why gnus would be unable to
display the body?

  X-From-Line: wilson@somewhere.com  Thu Nov  8 17:18:56 2007
  [...]
  To: reader@newsguy.com
  From: wilson@somewhere.com
  Date: Thu, 08 Nov 2007 19:40:34 GMT
  Subject: Land on Shawnee-Egypt rd
  X-Gnus-Mail-Source: directory:/home/reader/spool/
  Message-ID: <a2fe90e1781443f5a219eb167245dae5@Certmail.com>
  X-Priority: 3
  MIME-Version: 1.0
  Content-Type: multipart/mixed;
  	boundary="----=_NextPart_e4af4cf4_7979_47c9_91e9_88249be61961"
  X-UIDL: a,2"!QG>"!i\W"!gE*#!
  Xref: reader.local.lan move.WilsonB:7
  Lines: 69
  
  This is a multi-part message in MIME format.
  
  ------=_NextPart_e4af4cf4_7979_47c9_91e9_88249be61961
  Content-Type: multipart/alternative;
  	boundary="----=_NextPart_771a874f_62e4_4eec_8d4a_cd940bc67c6f"
  
  ------=_NextPart_771a874f_62e4_4eec_8d4a_cd940bc67c6f
  Content-Type: text/plain;
  	charset="utf-8"
  Content-Transfer-Encoding: base64
  
  
  ------=_NextPart_771a874f_62e4_4eec_8d4a_cd940bc67c6f
  Content-Type: text/html;
  	charset="utf-8"
  Content-Transfer-Encoding: base64
  
  SXRzIGRlZmluaXRlbHkgZ29vZCB0byBoZWFyIGZyb20geW91LiZuYnNwOyBJIHdhcyB0YWxraW5n
  IHRvIHNvbWVvbmUgYWJvdXQgeW91IGp1c3QgdGhlIG90aGVyIGRheSBhbmQgc3RhcnRlZCB0byBn
  [...]
  ------=_NextPart_771a874f_62e4_4eec_8d4a_cd940bc67c6f--
  
  ------=_NextPart_e4af4cf4_7979_47c9_91e9_88249be61961--

             reply	other threads:[~2007-11-12 18:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-12 18:50 reader [this message]
     [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

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=87pryfl2nb.fsf@newsguy.com \
    --to=reader@newsguy.com \
    --cc=ding@gnus.org \
    --cc=info-gnus-english@gnu.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).