Gnus development mailing list
 help / color / mirror / Atom feed
From: Karl Kleinpaste <karl@jprc.com>
Subject: p0.12 errors out on 7bit,base64
Date: 31 Aug 1998 20:36:40 -0400	[thread overview]
Message-ID: <vxkg1ecis87.fsf@pocari-sweat.jprc.com> (raw)

Pterodactyl Gnus v0.12
XEmacs 20.4 "Emerald" [Lucid] (i386-pc-linux) of Sun May 31 1998 on threepwood.idb.hist.no
200 news.jprc.com InterNetNews NNRP server INN 1.7.2 08-Dec-1997 ready (posting ok).

A recent message from Andrew Cosgriff (Message-Id:
<rui1zpw1xyl.fsf@goaway.cc.monash.edu.au>) caused p0.12 to choke:

Signaling: (error "Can't decode encoding 7bit, 7bit, base64")
  signal(error ("Can't decode encoding 7bit, 7bit, base64"))
  cerror("Can't decode encoding %s" 7bit\,\ 7bit\,\ base64)
  apply(cerror ("Can't decode encoding %s" 7bit\,\ 7bit\,\ base64))
  error("Can't decode encoding %s" 7bit\,\ 7bit\,\ base64)
  mm-decode-body(US-ASCII 7bit\,\ 7bit\,\ base64)
  gnus-article-decode-charset()
  run-hooks(gnus-article-decode-charset)
  apply(run-hooks gnus-article-decode-charset)
  gnus-run-hooks(gnus-article-display-hook)
  gnus-article-prepare(18074 nil)
  gnus-summary-display-article(18074)
  gnus-summary-next-page(nil)
  call-interactively(gnus-summary-next-page)

I thought perhaps there was a problem with there being two
"Content-Transfer-Encoding" headers, so I edited one of them out of
the message and tried again, but it errors out the same way with
"Can't decode encoding 7bit, base64".

My XEmacs 20.4 is the RedHat-contributed *rpm, mule-less.


             reply	other threads:[~1998-09-01  0:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-01  0:36 Karl Kleinpaste [this message]
1998-09-01  8:25 ` Lars Magne Ingebrigtsen

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=vxkg1ecis87.fsf@pocari-sweat.jprc.com \
    --to=karl@jprc.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).