Sometimes it displays as plain text as expected, but sometimes it displays the way characters are shown when the encoding is wrong – question marks within diamond symbols, question marks within squares, etc.
Hi there, could you send an example/screenshot of the issue? Thanks!
This sort of stuff: 6<�g8�����
It seems to show on “old destination address” and “invalid post” messages. I don’t have a lot to go on as there aren’t many to check.
1 Like
Are these messages sent from Exchange?
I ask because I’m familiar with this problem and 100% of the time I’ve seen it, Exchange was the sender and the culprit.
My guess is that it’s erroneously sending out an opaque reference to an internal data store via SMTP. In the cases where it’s been solved, the sender did something to fix it.
1 Like
Yes there are Exchange headers. I wonder what’s up.
Though not all Exchange emails appear like this. There are some “Bad destination address” rejected emails that appear as ordinary plain text.
bad software sending out bad emails
Indeed, not all Exchange emails are bad 
Should anyone come across this topic and actually administer such a bad server, I still want to monitor the wire protocol traffic to determine if it really is 100% bad data or of something else is going on.
(for weird problems like this, I never 100% trust everything until I see it with my own eyes)
1 Like