You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to RFC 2047 an encoded word cannot be longer than 76 characters (including everything). So a longer subject line should be split and encoded into multiple encoded words.
Using the library mgs.setSubject('x'.repeat(100)) results in a single standard breaking encoded word. This leads to some Mail-Servers rejecting this message with an error.
The encoding should split and wrap longer encoded words to match the standard.
The text was updated successfully, but these errors were encountered:
As far as I can see, all compliant clients will perform the line break after 76 characters. And I haven't seen any email client in the wild which doesn't parse the soft line breaks correctly. I don't think you necessarily need a "loose" mode to recreate the broken non-standard-compliant behavior.
According to RFC 2047 an encoded word cannot be longer than 76 characters (including everything). So a longer subject line should be split and encoded into multiple encoded words.
Using the library
mgs.setSubject('x'.repeat(100))
results in a single standard breaking encoded word. This leads to some Mail-Servers rejecting this message with an error.The encoding should split and wrap longer encoded words to match the standard.
The text was updated successfully, but these errors were encountered: