-
Notifications
You must be signed in to change notification settings - Fork 58
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
Unicode characters not handled properly in attachment names #233
Comments
Filename not being written to queue with this character and bypassing scan.
|
Traced back to Explode function in Message.pm... |
Appears to be an issue with the MIME Parser... |
Filename is encoded and doesn't appear to be parsed...
|
Non unicode filename...
|
Appears to be a bug in MIME::Parser, reported bug, trying MIME::Fast instead. |
Bump...MIME::Fast seems to be stale... |
Stop gap measure: set decode_headers to 1 for now until the bug in MIME::Parser is resolved. Only option at the moment unless someone has a better idea. At least it will attempt to decode the header and create a file. |
Leaving issue open until permanent fix is found. |
Revisiting, may be related to faulty handler in WordDecorder I just discovered... |
Looks related, but is triggered internally in MIME::Parser and cannot intercept. Will need to keep researching this. |
Researching Email::MIME |
Yesterday me and my collega where solving simular problem. I hope you can use it, or give you ideas. on Debian 9 its :
|
the other option we use is :
this one is in my optinion the best, but im no coder.. |
Problem appears to be no longer present after commit 481eed1 using MIME::Tools version 5.509 with decode_headers turned off. Should have checked this again before all the hassle 😆 Preparing to disable workaround. |
Fix needed to fully resolve MailScanner#233
Fix needed to fully resolve #233
mailwatch/MailWatch#1109
The text was updated successfully, but these errors were encountered: