Hi, I've noticed this problem, too. The worse is that mutt refuses to decode such encoded text in Subject/To/From/Cc if there is intervening spaces. (very sticky to the standard and not tolerant)
I use procmail to decode such text by myself before reading mail with mutt. But I only finished the work for the header part. If anybody is interested in such recipe, I may hurry up the part about attachment names. best regards, charlie On Mon, Mar 11, 2002 at 12:18:32PM +0100, Louis-David Mitterrand wrote: > > Hi, > > Often I receive attachements that carry quoted-printable names like > (screenshot follows): > > -- Mutt: Attachments > I 1 <no description> [text/plain, 8bit, iso-8859-1, 2.9K] > A 2 =?iso-8859-1?Q?Pr=E9vision_tr=E9so.xls?=[applica/vnd.ms-exc, base64, 4 > A 3 =?iso-8859-1?Q?Pr=E9visions_020304-3_ans[applica/vnd.ms-pow, base64, 1 > A 4 =?iso-8859-1?Q?Pr=E9visions_020304-3_ans[applica/vnd.ms-pow, base64, 1 > > When trying to save them Mutt doesn't try to decode their name and > convert them to accented characters. > > Is there a way to get > > Prévision_tréso.xls > > instead of > > ?iso-8859-1?Q?Pr=E9vision_tr=E9so.xls? > > as a suggested saved name? Or should I blame the remote MUA for not > complying to certain standards? > > Thanks in advance, >
