> using the User-Agent to decide how to encode a file name sounds…wrong. Of course it's wrong, and web devs wouldn't have to do it in an ideal world. But when

> using the User-Agent to decide how to encode a file name sounds…wrong. Of course it's wrong, and web devs wouldn't have to do it in an ideal world. But when your Chinese users complain right now that their attachment names are getting jumbled, and when your conversion rate is going down right now because people don't run the files they've downloaded, does it really matter whose job it is to clean up Microsoft's mess? BTW, non-ASCII attachment names still come out weird from time to time because Outlook, Thunderbird, and various webmails follow different RFCs. Most email composing tools just use a compromise that works 99.9% of the time, but I've seen programs that let you customize the filename encoding.