Hi, Every once in a while I get non-delivery reports delivered by our exchange serverthe moment our server (running Microsoft Windows Small Business Server 2003 SP 2) reboots (after updates have been installed). These NDRs are generated for some outbound e-mails thatwere sentin betweentheprevious reboot and the current reboot of the server. This puzzles me as NDRs should be delivered after 1 day: the SMTP virtual server isset to give adelaynotification after 1 hour andthe expiration time out is set to 1 day. Furthermore, the queue does not show any messages that are still pending to be delivered. Finally the log files of the exchange server indicate that the message when originally sent, was succesfully delivered (event IDs 1027, 1019, 1025, 1024, 1033, 1034, 1020, 1031). The event IDs immediately after reboot of the server for the same message are: 1019, 1025, 1024, 1033, 1034, 1030. The latter indicates delivery of an NDR.I checked and the messages have really not been delivered.Is there an explanation for this behavior? Can it be fixed? And most importantly, is there a way to track if messages have indeed get stuck other than the tracking mechanisms I mentioned above? Regards