We have started getting this message as well. It started immediately after we upgraded from 6.0.4 to 6.0.7 last week. It only happens when messages are sent from one of our internal servers, but it happens on every single message from that server. We never saw this error before the upgrade. The messages still come through ok, so it is basically just an annoying error that I would like to get rid of. |