Recently there are users who reflect the occasional 550 sent out of the Internet mail, the content for delayed sending of the 4.4.7 QUEUE. Expired; Message expired.
Environment for Exchange 2007, mail is routed to a branch hub server---headquarters HUB server---smg/edge.
Fault phenomenon for the sending outside the mail part can not be sent successfully, after testing the target is the same mailbox, multiple sends will also appear individual unsuccessful, and multiple extranet mailbox into (qq,126,163) line test, the results are the same
Query the MX record for the other mailbox to resolve normally.
Check queue Discovery The branch has 2 hub queues with retry mail, and the next station is the headquarters hub server.
650) this.width=650; "title=" 11111111.png "src=" http://s3.51cto.com/wyfs02/M01/5C/38/ Wkiom1ucpqsqz0dbaag57wgojji461.jpg "alt=" Wkiom1ucpqsqz0dbaag57wgojji461.jpg "/>
The two hubs were checked for sanity and found that the two servers were 6 minutes slower than the DC.
Cause of failure: The two hub servers are virtual machines, the host is not joined to the domain, the DC time cannot be automatically synchronized, the virtual machine automatically synchronizes the host time in the Hyper-V default settings, causing the time to exceed the tombstone time (5 minutes), the DC will not validate the request
WORKAROUND: The host sets the clock server as a DC, or the time synchronization is removed in the integration services of Hyper-V settings, so that the virtual machine synchronizes the DC automatically. Restart the Exchange Transport service.
This article is from the "Lixiangqian" blog, make sure to keep this source http://lixiangqian.blog.51cto.com/2848430/1627573
Delay sending 550 4.4.7 QUEUE. Expired; Message expired