We're having an issue where we are seeing delivery delay messages being sent to users who have sent messages that have already been delivered. The catch is that these delivery delay messages are only sent when the primary node is patched, rebooted and the passive node takes over.
For example. User A sends a message at 1:00 pm EST which is delivered at 1:05 PM EST. Server A is the primary node and is patched and rebooted at 10:00 PM EST the same day. Server B becomes the primary node ~10:05 PM EST. At 10:09 PM EST a message is sent to User A stating the message he sent at 1:00 pm EST is delayed and will be retryed until XX:XX.
Any ideas on this? Our transport settings are at the default and I can't think of why a passive node being promoted to active would do this? Only thing i can think of is the transport dumpster somehow impacts all this.