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
It seems that the mail package almost always puts double-quotes around the 'name' part of addresses e.g. in From, To, etc. headers - even for pure ASCII names without commas, etc. - and I believe it also always wraps the address part in < and >:
Example Name <name@example.org> ---> "Example Name" <name@example.org>
name@example.org ---> <name@example.org>
It would be nice if the package would make these transformations only if necessary, and otherwise keep the simpler forms.
The text was updated successfully, but these errors were encountered:
My reasoning was that if the slightly shorter/cleaner and more visually pleasing forms (very subjective, I know) are permitted by the RFC, then maybe we'd consider keeping them as-is, unless otherwise required. But I agree that always doing something is indeed inherently simpler than only sometimes doing it. I suppose the how much depends on the case at hand, and as the author/expert here you're arguably the best of judge that. 🙂 So if you think it's too much complexity or not worth it, I'd understand, please feel free to close this issue.
It seems that the mail package almost always puts double-quotes around the 'name' part of addresses e.g. in From, To, etc. headers - even for pure ASCII names without commas, etc. - and I believe it also always wraps the address part in
<
and>
:Example Name <name@example.org>
--->"Example Name" <name@example.org>
name@example.org
---><name@example.org>
It would be nice if the package would make these transformations only if necessary, and otherwise keep the simpler forms.
The text was updated successfully, but these errors were encountered: