Well, yes, it is
The standards donât really say anything about it, so at the end of the day, the behavior is implementation-dependent. Each implementation should do what makes the most sense it its case.
If Zammad uses different Message-IDs in this case to prevent this from occurring, thatâs IMO perfectly fine.
But if @herzkerl wants Zammad to match customer replies to the BCCâd mail of his 3rd party system, and the 3rd party system prevents this by using different Message-IDs that seem to serve no other useful purpose, than the behavior of this 3rd party system is obviously not fine
Thank you for your email. Yes, the emails that get sent to BCC and CC recipients have a different Message-ID header than the email that gets sent to the TO recipient.
The reason for this is that, unlike a regular email client, the email body content is actually slightly different for CC/BCC and TO recipients. For example, the email body content for CC/BCC recipients will not have email open-and-click tracking tags.
However, we understand that this complicates your integration with your ticketing system. We may change how this works in a future update. In the meantime, perhaps you could add a custom âReply-Toâ header to your outgoing emails that would help your ticketing system match up the replies?
Is there any way to use custom âReply-Toâ headers to merge that second email automatically? If not, Iâll wait for a Direct Mail update
Iâm afraid thereâs not, unless you fiddle around with your reply-to headers on your mail server directly.
However, that in my opinion might lead to other issues you proberbly donât want to have.