-
-
Notifications
You must be signed in to change notification settings - Fork 271
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
Bugfix: Decoding missing in a few placed when parsing MimeMessage or sending an Email #293
Comments
I'm facing similar problmes. My filename is ignored, the recipient get's an attchament with =UTF-8BRWRlbmhhdXNlcl9LQjAwMDAwMDE2OQ=== =UTF-8BNF9CcmFuZHN0w6R0dGVyIEhhbnMucGRm= as filename?
|
@sbellan, could you please provide me with an example email? Even if you don't face this issue anymore or moved on to another library, I would like to analyse the problem and find a solution. Would be much appreciated! |
You can use this to fix it: |
Note that attachment name encoding was turned off deliberately due to #271. Not sure what the best solution is right now... |
What's the latest status here? |
Still waiting for an example. Will close this as non-actionable soon. |
Apologies for not following up. Attaching the email which is failing, (rename .txt to .eml) This is the code snippet,
|
…ttachment description properly when sending
Fixed in release 7.8.3, please verify. It was a bit of a pain to figure this one out, thanks again for helping me analyse this! |
Great!!. The fix looks quite involved. Thank you. |
Using Version 6.4.3
Couple of issues,
the content generated when seen using withTransportModeLoggingOnly looks like the following,
The filename and name are not encoded correctly. https://tools.ietf.org/html/rfc1342, https://tools.ietf.org/html/rfc1341
with code like this,
It fails with,
The text was updated successfully, but these errors were encountered: