Skip to content
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

Make bodyparsing hashing work for more mail clients #187

Open
Divide-By-0 opened this issue Mar 31, 2024 · 0 comments
Open

Make bodyparsing hashing work for more mail clients #187

Divide-By-0 opened this issue Mar 31, 2024 · 0 comments
Labels
bug Something isn't working medium

Comments

@Divide-By-0
Copy link
Member

Thanks to MV for the bug report.

Apparently apple mail automatically splits strings with the soft returns, and uses = for them, while also replacing the = in base64 padding with =3D

you can sidestep it by enforcing line lengths

Skiff and some other clients don't introduce any breaks, gmail web client introduces hard returns every 75 chars, apple mail introduces these weird soft returns every 75 chars.

Seems like it would be really hard to account for all of these things in one circuit

Apple mail is specifically annoying because the simplest version of this email is just a base64 string of the encoded tx, and introducing random = padding chars really messes stuff up

@Divide-By-0 Divide-By-0 changed the title Make bodyparsing more diverse Add options to bodyparsing hashing to enable compatibility with more mail clients May 16, 2024
@Divide-By-0 Divide-By-0 changed the title Add options to bodyparsing hashing to enable compatibility with more mail clients Make bodyparsing hashing work for more mail clients May 16, 2024
@Divide-By-0 Divide-By-0 added bug Something isn't working medium labels May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working medium
Projects
None yet
Development

No branches or pull requests

1 participant