Saas 3 opw 608919 acl

This is not correct. This outstanding bug in Outlook.com causes it to add commas between previous References when replying to an email that **already has** a References header with **multiple values**. Here is an example of what you can get after a view roundtrips between Outlook.com and Thunderbird:

    In-Reply-To: <539AC885.4080608@openerp.com>
    References: <539AC70E.9040005@openerp.com>
     <BAY178-W144F8E4AE72E5FE6EA0295B6150@phx.gbl>,<539AC7BD.70303@openerp.com>
     <BAY178-W147B9A6310339E8E79BF83B6150@phx.gbl>,<539AC885.4080608@openerp.com>

In this example you would extract 3 values in msg_list, while you actually want 5 of them.

More fundamentally, I'm not so sure we should patch the system to fix obscure bugs in outlook.com, while RFC2822 (section 3.6.4) is extremely clear about the structure of the References header: the separator is CFWS (white-space only). The comma character is technically valid in the left side of a msg-id value too!

On the other hand the RFC is pretty clear about the fact that a Reference item has the form ``<msg-id>`` where msg-id cannot contain ``<`` and ``>`` signs. A valid patch would be to extract msg-id values from References using a compiled regex based on ``<[^<>]+>`` or something, and then re-add the ``< >`` wrapper around them before searching on the message_id values. This would make the parsing more robust without specifically addressing outlook.com bugs.

**Note**: This must be reported to the outlook.com support by the customer in any case!