Hello Firstie Lastie, If doing so:
- 1. do not come at a big performance price and - 2. do not compromise overall correctness Then I do believe that such lenient behavoir contribution would be welcome. Don't hesitate to open a pull request regarding this on github. Regards, Benoit On 03/01/2023 22:16, Firstie Lastie wrote:
Hello, I've noticed that when I have a message header (for example 'subject') which has a mixture of ascii and utf-8 encoded-text, it requires a space for the encoded text to be properly decoded. This follows the spec, which says: "IMPORTANT: 'encoded-word's are designed to be recognized as 'atom's by an RFC 822 <https://www.rfc-editor.org/rfc/rfc822> parser." and RFC-822 states: "Atoms ... are delimited by the self-delimiting symbols and by linear-white-space." I'm wondering if the support could be expanded so that subjects which DO NOT contain the mandatory delineating space would also be supported. Cheers, fl
