Jump to content

Bad ticket CCs for RFC822 compliant emails

Recommended Posts

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

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

- 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.

Link to comment
Share on other sites

  • 3 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated