Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 266941 - Mutt messes up names of attachments with non-English characters
Summary: Mutt messes up names of attachments with non-English characters
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-21 06:16 UTC by Lubos Kolouch
Modified: 2009-04-21 11:49 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lubos Kolouch 2009-04-21 06:16:12 UTC
When I receive in mutt attachments with non-English characters, the name of the attachments is destroyed - it looks like this :

=?iso-8859-2?Q?Seznam_adres=E1t=F9_News=F9.xls?=

This makes it difficult to save the attachment (must rename it) or forward - then the recipients on MS systems cannot open it as the file extension is not clear. I must save & rename each attachment and reattach again.

Reproducible: Always

Steps to Reproduce:
1.Receive email with attachment having non-English characters
2.Try to save or forward
3.No profit!

Actual Results:  
Attachment has wrong name
=?iso-8859-2?Q?Seznam_adres=E1t=F9_News=F9.xls?=

Expected Results:  
Attachment has name like
Seznam_adresátů_News.xls
Comment 1 Rafał Mużyło 2009-04-21 11:14:05 UTC
Google for "mutt rfc2047_parameters", read the manpage
and teach people, that send you such mails how to
properly configure their mail clients (or switch
to a different ones, if former is not possible).
Comment 2 Lubos Kolouch 2009-04-21 11:23:47 UTC
Thank you for, sorry to say, stupid comment.

Please switch your mind to real world where you have zero influence on your customers that want to send you email.
Comment 3 Lubos Kolouch 2009-04-21 11:49:22 UTC
OK, besides the second part, the rfc2047_parameters
indeed fixed the problem :)

thank you