we have lately journaling emails piled up on our hub servers which goes to mimecast
we have 7 hub servers and queues are piling on all.
earlier we had mcafee gateway but we switched to proofpoint gateway
after that journaling emails are using sendconnectors on our hub server
whoes next hop is proofpoint which is used by normal mail queues but instead it is being used by journaling emails
we have seperate mimecast journaling send connector which it should use
but instead it is taking send connector whose next hop is proof point
and PP is not having any send connector
For Journal email next hop is Edge server and that is different send connector for that, and edge IP is added to Mimecast , so now since PP gateway IP is not added to mimecast it is not making connection to send journal email to mimecast,
we spoke with microsoft he suggested to recreate the send connector but I did not agreed on this as it could lead to downtime for few min.
any other thoughts.
i took this from queue viewer.
Last Error: 400 4.4.7 The server responded with: 550 5.1.1 User Unknown. The failure was replaced by a retry response because the message was marked for retry if rejected.