We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello! I help maintain a program that parses emails for specific attachments which uses this library.
I came across a unique email where the Content-Disposition filename looks like this: "=?iso-8859-1?B?cmVwb3J0XzE4TUFZMjAuY3N2?="
"=?iso-8859-1?B?cmVwb3J0XzE4TUFZMjAuY3N2?="
If I use the Header function ContentDisposition() and get the value from key "filename", I would expect it to look like this: report_18MAY20.csv
report_18MAY20.csv
I was able to work around this for now using code similar to this:
mimeDecoder := mime.WordDecoder{} _, params, _ := message.Header.ContentDisposition() filename, _ := mimeDecoder.DecodeHeader(params["filename"])
Should params be decoded via this library, the mime package's ParseMediaType(), or an end user like myself?
Thanks!
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello! I help maintain a program that parses emails for specific attachments which uses this library.
I came across a unique email where the Content-Disposition filename looks like this:
"=?iso-8859-1?B?cmVwb3J0XzE4TUFZMjAuY3N2?="
If I use the Header function ContentDisposition() and get the value from key "filename", I would expect it to look like this:
report_18MAY20.csv
I was able to work around this for now using code similar to this:
Should params be decoded via this library, the mime package's ParseMediaType(), or an end user like myself?
Thanks!
The text was updated successfully, but these errors were encountered: