Bad ticket CCs for RFC822 compliant emails

[sergiosainz]

We found an issue related to ticket CCs, email piping and named email addresses (like "Full name" <test@email.com>).

Context:
The system contains a client with the email client1@test.com. Most of the communications with that client must include a couple of CCs.

Steps to reproduce it:
1) Send an email from client1@test.com adding, as CC, a named email address containing a comma: "Doe, John" <john.doe@somecompany.com>
2) The ticket is opened properly, but the CC is parsed as two different CCs:

• "Doe, John
• john.doe@somecompany.com

Issues:
- A single CC gets splitted into two different ones. One of them is not a valid email.
- When using multiple CCs, this prevents some CCs from being notified because a malformed email address is found.

[sergiosainz]

Can anyone check this out, please?