Hi Alain, thanks for taking care.
[EMAIL PROTECTED] wrote: > On Wednesday, February 8, 2006 at 10:47:32 +0100, Tobias Stefan Richter > wrote: > > I just saved an attachment by the name > > =?ISO-8859-15?Q?=DCberraschung=2Ezip?= as it was received due to > > (improper?) encoding. > > Illegal encoding, explicitly prohibited by RFC 2047. Attachment > filenames have to use another encoding: RFC 2231. But you still can > persuade Mutt to decode this, by setting $rfc2047_parameters. > > RFC violation should be reported to the sender software. What is it? > Microsoft Outlook [Express]? No: User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) Maybe they fixed that already. > > I'm not sure if the = -> $MAIL expansion is desired in the attachment > > menu at all (I don't think so) > > I vaguely seem to recall from previous discussions that this is a > desired expansion. When explicily entered by the user, it could be expected to work that way. Ok. But I rarely want to save attachments inside my mail folder. > > but it should for sure not be used with filenames supplied by remote > > parties. > > Some sanitizing might be good, right. There is already bug #1719 > opened upstream since a long time about "attachments with =names stored > in $folder by default". Clearly said: Fixing this seems not to be seen > as an absolute priority. > > Do you want me to add you to the Notify-List of #1719? That'd be nice. Thanks again, tobias -- Tobias Richter LabPZ - AG Prof. Dr. P. Zimmermann TU-Berlin PN 3-2 Phone: +49-30-314-23020 Hardenbergstr. 36 Fax: +49-30-314-23018 10623 Berlin Germany http://atom.physik.tu-berlin.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]