On 5/24/20 7:20 PM, Alan So wrote:
Really thanks for your hard work Mark! It is a bit strange that parseaddr behave differently with CRLF and LF. Maybe if the server is a Windows, the behavior is consistent.
It might be that on Windows, mailman inject would create the message
with CRLF line endings.
May I know when or whether will this patch be committed to the repository so that it will be effective in future release of Mailman? Thanks.
In the absence of an issue at <https://gitlab.com/mailman/mailman/-/issues>, probably never. <hint>
The bottom line is the original mail created by Outlook is defective.[1] While Mailman could defend against this defect, starting to do that opens the possibility that there are other areas of the code that need a similar defense.
Have you asked Microsoft to fix Outlook to not create these defective messages? That's the real solution.
That said, if an issue is filed, someone might consider adding something along the lines of <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/Y6DCI4Z2J57K5577MGFXUEUXXQVOIOBE/attachment/2/avoid_duplicates_patch.txt> to the code base.
[1] given an address of the form
display-name (comment) <addr-spec>
in a header, it can be folded either between the display-name and the (comment) or between the (comment) and the <addr-spec>, but if display-name (comment) is quoted as in
"display-name (comment)" <addr-spec>
"display-name (comment)" is now a phrase within which folding is not allowed and this can only be folded between the "display-name (comment)" and the <addr-spec>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan