Alas, it is 2011, and Quoted-Unreadable is not yet dead!

Messages from this list are encoded in it if they contain even the 
slightest non-ASCII character or long line.  Only, it doesn't put a 
header on the message telling modern clients to do the decoding 
automatically.

Fortunately, I use a text-based client called mutt, which allows all 
kinds of folder and other kinds of hooks.  I do not know if anybody 
else can benefit from this but I offer it in case it might be useful 
to someone:

In my .muttrc:

folder-hook . 'unset display_filter'
folder-hook '+Gmail/ham\.blind-hams' \
	'set display_filter="~/Library/bin/quoted-unreadable"'


For any folder, the first line un-sets the display_filter option.  
Without this, all messages would be assumed to be in quoted-printable 
format and thus decoded.  We don't want that, since it is only this 
list that uses QP without telling the client about it!

The second line (and third via continuation backslash) matches on the 
precise name of the folder "Gmail/ham.blind-hams" located in my mail 
directory.  It then sets the display filter for this list alone to be 
the script named quoted-unreadable in ~/Library/bin (which kind of 
mixes the UNIX and Mac paradigms a little, but I couldn't think of a 
better name for a bin directory than, well, bin.)

Anyway, here's the script, written using Python:

#! /usr/bin/env python

import sys
import quopri

# Mutt sends displayed headers through this hook, ignore them!
show_header = True
while show_header:
	hdr_line = sys.stdin.readline()
	sys.stdout.write(hdr_line)
	if len(hdr_line.rstrip('\r\n')) == 0:
		show_header = False

# The entire body of the message is filtered with a single line:
quopri.decode(sys.stdin, sys.stdout)


Yup, that's it.  The heavy lifting is done by quopri, which is 
apparently something you probably already have installed if you've 
got a full Python library.

If you can filter the body alone, you need just the two import lines 
and the call to quopri.decode.

I haven't the faintest idea how you'll use this on anything other 
than Mutt, and yes I know the way I handle headers could be improved.  
Much could be done if I were to make the header handling optional, so 
that I could make effective use of this one-line-wonder elsewhere 
(because for example I have seen on this list the occasional 
double-QP which my filter makes no attempt to solve.  But there you 
have it.

It finally got annoying, so I fixed it on my end.  It's taken longer 
to share the result than it did to fix the problem and test it, so I 
hope it's useful to somebody.  *grin*

Joseph - KF7QZC