-
Notifications
You must be signed in to change notification settings - Fork 5
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
filenames of attachments are not properly encoded #1
Comments
brychcy
added a commit
to brychcy/libpst
that referenced
this issue
Dec 12, 2021
Thanks for the report.
Could you attach an example PST file? I will need it to verify the
current incorrect behaviour and review the changes that are made to the
behaviour by your patch.
…--
bye,
pabs
https://bonedaddy.net/pabs3/
|
Please also attach an example script using the Python email library.
…--
bye,
pabs
https://bonedaddy.net/pabs3/
|
brychcy
added a commit
to brychcy/libpst
that referenced
this issue
Jan 10, 2022
Parentheses and other characters were not being encoded. Fixes: pst-format#1
As requested, example PST file (compressed with gzip as required by github). The name of the attached file in the contained mail is "Hello-(123)-World.pdf" |
A simple python script for printing the file names of PDF attachments:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When reading the .eml files generated by readpst, the filenames of some attachments could not be retrieved with the python e-mail library, e.g if they contain parenthesis like
filename*=utf-8''Status_Announced_Invoice(s).pdf;
It turned out that rfc2231_string in readpst.c doesn't escape all characters as required.
Correct would be
filename*=utf-8''Status_Announced_Invoice%28s%29.pdf;
The text was updated successfully, but these errors were encountered: