-
Notifications
You must be signed in to change notification settings - Fork 13
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
S/MIME signed mails have signature issues in outlook and apple mail with specific subject length #32
Comments
Thanks for the investigation! I won't have to to dive into in the following days but I'm definitely interested into solving this. |
Just a side note.. M2Crypto seems to be without maintenance and they are proposing a migration path: https://m2crypto.readthedocs.io/en/latest/howto.migration.html# maybe it might make sense to tackle the issue by migrating to the modern lib? |
My colleague is just finishing the migration. Would you mind to check if the proposed branch is working for you? |
Yeah, sure! Thank you for taking the time and working on this! I've got a development environment at hand that could be used for testing. |
Hi, I've given the task to a colleague due to a upcoming vacation. Can you please notify us here once the branch is available? Regards |
Hi there! first of all, thank you very much for the effort that you've put into the migration. A S/MIME signed message was successfully sent out. However, S/MIME encrypted and signed HTML messages are not working as they should. The mail is encrypted for the sender, not for the recipient. |
Thanks a lot for having this sorted out! |
The mail was sent from A to B&C, was signed by A and encrypted only for A. In general, it makes sense that the mail is also encrypted for A because the sender would like to read his mail. However, B&C won't be able to read it, because only the first item in the list is being used. Located in line 1400 in Envelope.py |
pycryptograpy is using CRLF instead of LF and this results in not being correctly rendered in HTML mails. Therefore, I changed the encoding to binary. |
Hi,
I just figured out that the s/mime signature seems to be wrong if the email-subject has got a length >= 70 and <= 77 characters.
How to reproduce?
However, S/MIME encrypted mails don't seem to have this issue.
Do you have any clue what is wrong here? I guess is must be something with the maximum characters allowed and line breaks in SMTP communication?
Have a nice day!
The text was updated successfully, but these errors were encountered: