Skip to content

Support RFC 2231 data format #50

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jkbzh opened this issue Jun 12, 2018 · 1 comment
Open

Support RFC 2231 data format #50

jkbzh opened this issue Jun 12, 2018 · 1 comment

Comments

@jkbzh
Copy link
Contributor

jkbzh commented Jun 12, 2018

Hypermail fails to find and save the attachment filename when a mail client is using newer MIME attachment standards than hypermail recognizes. Newer Mail clients may split the filename into several fields following the procedure in RFC 2231. hypermail does not recognize this data format, so it failed to find the filename, generated its own, and as a consequence the browser doesn't know to display the file as a PDF. In my personal opinion, we should teach Hypermail to read filenames and other attachment data following RFC 2231.

@vivienlacourba
Copy link

FYI I believe that roundcube pushed a similar changes in their latest 1.5.0 release.
roundcube/roundcubemail#6783

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants