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

RFC 5321 4.5.2 not fully implemented (double dot in message) #177

Open
benjamin-hg opened this issue Nov 20, 2023 · 0 comments
Open

RFC 5321 4.5.2 not fully implemented (double dot in message) #177

benjamin-hg opened this issue Nov 20, 2023 · 0 comments

Comments

@benjamin-hg
Copy link

benjamin-hg commented Nov 20, 2023

If a . (dot, period) in your message (e.g. in a domain name of an included link) happens to be the first character of a transmitted line, it must be prefixed with another dot, according to the spec.

But Mailslurper, on the receiving side, does not remove this extra dot, making some links randomly break.

But it's most annoying if you include non-minified css styles in your html, where all the classes start the line with a dot. Completely breaks things and it took me hours to diagnose that the issue is not my application (Keycloak in this case), but my testing tool Mailslurper.

@benjamin-hg benjamin-hg changed the title RFC 5321 4.5.2 not fully implemented RFC 5321 4.5.2 not fully implemented (double dot in message) Nov 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant