I have now encountered 2 ISP SMTP Servers that appear to have changed the way Emails containing TO and CC are handled.
Normally, an Email sent with TO and CC headers are sent as one EMAIL ... for some reason these 2 Servers are now splitting up the headers and sending TO as one Email transaction and then Sending CC as another separate Email transaction.
Speaking with the ISP's involved, they aren't willing to even discuss this as an issue?
At issue is one of my clients sends Emails with:
a) TO as the Prime Email address candidate
b) CC's using a GROUP Email address that normally contains the Prime Email Address
These Servers are causing the receipt of DUPLICATE INBOUND EMAILS when:
1) FROM/CC Internal originated Emails are Replied to externally with Reply ALL from these servers > TO/CC
2) New external Emails sent with TO/CC from these Servers
Exchange can normally remove duplicate Address Info when an Inbound Email contains both the TO and CC in the same transaction. However, when the Email is received in separate transactions I am not aware of any way it can determine these separate email transactions are related and therefore Users are receiving anoying duplicate traffic.
Has anyone bumped into this? Any ideas how to resolve this?
Normally, an Email sent with TO and CC headers are sent as one EMAIL ... for some reason these 2 Servers are now splitting up the headers and sending TO as one Email transaction and then Sending CC as another separate Email transaction.
Speaking with the ISP's involved, they aren't willing to even discuss this as an issue?
At issue is one of my clients sends Emails with:
a) TO as the Prime Email address candidate
b) CC's using a GROUP Email address that normally contains the Prime Email Address
These Servers are causing the receipt of DUPLICATE INBOUND EMAILS when:
1) FROM/CC Internal originated Emails are Replied to externally with Reply ALL from these servers > TO/CC
2) New external Emails sent with TO/CC from these Servers
Exchange can normally remove duplicate Address Info when an Inbound Email contains both the TO and CC in the same transaction. However, when the Email is received in separate transactions I am not aware of any way it can determine these separate email transactions are related and therefore Users are receiving anoying duplicate traffic.
Has anyone bumped into this? Any ideas how to resolve this?