Gnus development mailing list
 help / color / mirror / Atom feed
From: Unknown <unknown@unknown.invalid>
Cc: ding@ifi.uio.no
Subject: Mime unreadable stuff in headers?
Date: Thu, 4 Jul 1996 11:33:12 -0400	[thread overview]
Message-ID: <199607041533.LAA26347@sccon.com> (raw)
In-Reply-To: <0fbuhw9hw3.fsf@fraxinus.daimi.aau.dk>

>>>>> "Lars" == Lars Balker Rasmussen <gnort@daimi.aau.dk> writes:

    Lars> What happened to the decoding of the horrible
    Lars> "=?iso-8859-1?Q?Bj=F8rn?=" stuff, that some tortured and
    Lars> misguided souls put in headers?

i agree... it seems that this problem gets worse and worse... i just
had to turn off mime because i could not decode this type of
message...

i would be greatly interested in a fix to this problem as i enjoy and
use this package quite alot...

    Lars> I remember putting `gnus-mime-decode-quoted-printable' in
    Lars> `gnus-article-prepare-hook' and `gnus-parse-headers-hook' to
    Lars> decode it, but had to remove them again at some point as I
    Lars> got errors entering summaries and viewing articles :-/

    Lars> So, what alternative do I have to get rid of them?  Why
    Lars> isn't the decoding of them standard behaviour (it being the
    Lars> most convenient for all parties), or if it is the default,
    Lars> what did I somehow overwrite?  Lars Balker Rasmussen
    Lars> <URL:http://www.daimi.aau.dk/~gnort/>
    Lars> <URL:mailto:lars@rasmussen.org>

i to would be interested in a fix...

thanks in advance...
andreas

   Steller Computer Consultants	 	Andreas Kaempf
	P.O. BOX 3873			
     Nashua, NH 03062  USA	      akaempf@sccon.com



  reply	other threads:[~1996-07-04 15:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-07-04 15:07 Lars Balker Rasmussen
1996-07-04 15:33 ` Unknown [this message]
1996-07-05  7:29   ` Steinar Bang
1996-07-13 20:37     ` Unknown
1996-07-04 19:43 ` Steven L Baur
1996-07-05  1:17 ` Lars Magne Ingebrigtsen
1996-07-05 11:18   ` Lars Balker Rasmussen
1996-07-06  2:32     ` 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=199607041533.LAA26347@sccon.com \
    --to=unknown@unknown.invalid \
    --cc=ding@ifi.uio.no \
    /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).