Hello,When I reboot one of my exchange server it will randomly resend some messages. From the research that I have done almost all of the messages were delivered originally when sent and there are only a few that the users can't remember if the recipient actually received the messages at the time the messages were originally sent. Also, I have found that if I restart the SMTP service the same thing happens. I have looked online at several places and haven't found any possible solutions that seem to fit but I have seen others that say they have a similar problem.Thanks for your help in advance.(The system is Exchange 2003 on SBS 2003 and uses Symantec Endpoint Protection and Symantec Mail Security)

On Wed, 3 Mar 2010 18:06:00 +0000, Zman51 wrote:>>>Hello,When I reboot one of my exchange server it will randomly resend some messages. From the research that I have done almost all of the messages were delivered originally when sent and there are only a few that the users can't remember if the recipient actually received the messages at the time the messages were originally sent. Also, I have found that if I restart the SMTP service the same thing happens. I have looked online at several places and haven't found any possible solutions that seem to fit but I have seen others that say they have a similar problem.Thanks for your help in advance.(The system is Exchange 2003 on SBS 2003 and uses Symantec Endpoint Protection and Symantec Mail Security) This should fix the problem:http://support.microsoft.com/kb/950757/en-us---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP

Hi, The most probable cause of this issue should be the SMTP temp table: "Temp Table" is a subfolder of the SMTP logon mailbox root in a particular messaging database. This folder is used to process messages for bifurcation, for content conversion, and for distribution list expansion purposes. Additionally, this folder is used to periodically remove messages from the "Send Queue" folder. This process helps prevent an issue in which messages appear to be stuck in the Microsoft Outlook Outbox folder. If some emails are corrupted, they may been moved into the temp table. However, every time starting the SMTP virtual server, these emails will be delivered again. So after restarting the Exchange Server, the related emails still tries to be sent out. We can use the method in the following article to clean the temp table regularly: How to use the Mfcmapi.exe utility to view and work with messages in the SMTP TempTables in Exchange 2000 Server and in Exchange Server 2003http://support.microsoft.com/?id=906557 Another thing should be noticed: Please never run File-Based Antivirus Software scanning against the program and database files of an Exchange computer. For more information: Recommendations for troubleshooting an Exchange Server computer with antivirus software installedhttp://support.microsoft.com/kb/245822/en-us Last but not least, please always keep your OS and Exchange server with the latest updates installed. Hope this helps. Thanks, Elvis

Rich, Thank you for the response. I have read the KB article and it appears to match my problem. I have installed the hotfix and will let you know if it resolves the issue. It will take a few days to see if it works.

Elvis, I have installed the hotfix recommended by Rich (Thank you) as it was a good match to the problem I am having. It will take some time to determine if this has completely fixed the problem since the users do not know until a recipient tells them that they have gotten a duplicate or a message sent from some time ago or for that matter a missing message. As I continue to test this I will keep everyone updated however it may take some time to be absolutely sure that the problem is fixed, but no one has mentioned anything for the two business days since I installed the hotfix (I usually only hear about this problem a handfull of times each year).

Hi Zman51, That's all right. Let's wait and see the result. The issue is a "famous" issue and the root cause is the message in SMTP temp table. Please keep us posted. If anything is unclear, please let us know. Thanks Elvis

Since I have installed the hot fix recommended by Rich a week ago I have restarted the smtp service twice and also rebooted the server once and no one has complained about messages being resent. So far this looks like it has resolved the problem however I will continue to periodically test this and let everyone know the results...thanks.

Hi Zman51,Is there any update on this issue? If so, feel free to let us know. Thanks,Elvis

Exchange 2003: We just ran into similar problem yesterday. We used the recommended Mfcmapi.exe utility to clear stuck messages in the TempTables, but found no messages in subfolder that is labeled #0 through #19. We assume that whatever in there had been sent out. Is there a way to check which message was sent out? I dont assume they are the user's Sent folder? Any advice would be appreciated.

On Wed, 9 Jun 2010 15:03:01 +0000, Zecontech wrote: > > >Exchange 2003: > >We just ran into similar problem yesterday. We used the recommended Mfcmapi.exe utility to clear stuck messages in the TempTables, but found no messages in subfolder that is labeled #0 through #19. We assume that whatever in there had been sent out. > >Is there a way to check which message was sent out? I dont assume they are the user's Sent folder? > >Any advice would be appreciated. If you haven't done so already, install this: http://support.microsoft.com/kb/950757/ --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

As a follow-up after 3 months of testing for others out there that are experiencing this problem. I have installed the fix (http://support.microsoft.com/kb/950757/en-us) that was recommended by Rich Matheisen on all of my servers that I maintain that I could identify as having the problem that I initially described. After testing all of my servers that I maintain I found that 17 out of 23, 2003 Small Business Servers were experiencing this problem. Since I have installed this fix on all of the effected servers in March I have not had a single complaint of this problem happening again as of the time of this posting.