Re: Duplicate email sent upon server reboot (Exchange 2003)

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

The smtp service is in IIS.
It could be caused by the AV.
Did you run the Best Practices Analyzer (health check)?
Did it mention anything about the AV or about smtp?

--

Regards,

Rene Frenger




"Tom" <tcatalini@xxxxxxxxxx> wrote in message
news:1187787866.714564.195730@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Aug 22, 3:25 am, "Rene Frenger" <rfms2...@xxxxxxxxxxx> wrote:
They might get stuck in the temptables of smtp.
Here 's a procedure to reset the temptables.

Reset temptables:

Warning:http://www.microsoft.com/downloads/details.aspx?familyid=55FDFFD7-187...
If you use the Mfcmapi.exe utility incorrectly, serious problems may
occur
that may require that you reinstall Microsoft Exchange Server. Serious
problems may
also occur that require that you restore Microsoft Exchange Server.
Microsoft
cannot guarantee that problems that result from using the Mfcmapi.exe
utility
incorrectly can be resolved. Use the Mfcmapi.exe utility at your own
risk.

Use the Mfcmapi.exe utility to save messages so that you can examine them
later
1. Stop the SMTP Service.
2. Double-click Mfcmapi.exe.
3. Click OK to close the About Mfcmapi dialog box.
4. Click Session, and then click Logon and Display Stores.
5. Log on by using an Administrator account. If the MAPI profile is
unavailable,
create one.
6. Click MDB, and then click Get Mailbox Table.
7. Confirm the server name, and then click OK.
8. Double-click the SMTP ( Servername GUID ) mailbox.
Note In this step, Servername represents the name of the Exchange Server.
GUID
represents the GUID.
9. Expand Root Container, and then click TempTable# (most of the time
there
's only a TempTable#0).
10. Right-click the MTS-OUT subfolder, click Create Subfolder, and then
name
the
new folder "Recovery."
11. Expand TempTable#
12. Select folders 0 through 19.
13. Right-click the range of folders that you selected, and then click
Copy.
14. Right-click the Recovery folder, and then click Paste.
15. Click to select the Paste folder contents only check box, and then
click
OK.
16. Click to select the Move Messages check box, and then click OK.
17. Confirm that the table from which you moved folders is empty. Examine
the
PR_CONTENT_COUNT row and the PR_CONTENT_UNREAD row (value must be 0).
18. Repeat steps 12 through 15 for all the folders that appear under the
appropriate TempTable (0 to 19). With right-click on Open Associated
Contents you can view the messages.
19. Right-click the TempTable in which you have been working, and then
click
Delete
Folder.
20. In the Delete Selected Folder dialog box, click to select the Hard
Deletion
check box, and then click OK.
21. Confirm that the TempTable folder has been deleted. To do this,
follow
these
steps:
a. On the Hierarchy Table menu, click Refresh View.
b. Expand Root Container. Verify that the TempTable folder does not
appear.
22. Restart the SMTP service. This rebuilds the TempTable object.
23. Follow steps 12 through 15 to move the message from the Recovery
folder
to the
TempTable# folder.

--

Regards,

Rene Frenger

<tcatal...@xxxxxxxxxx> wrote in message

news:1187720810.129379.301660@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

The last two times we have rebooted our Exchange server for routine
updates, duplicate email messages were sent out.

They all seem to be SMTP messages (no duplicates reported internally).

There is no obvious pattern, it is seemingly random, and there are
only a few reports (about 5 on a system with 200 users).

In each case, the original messages (some of them weeks old) were
successfully sent.

We have noticed that all users reporting this issue are on the same
server (we have 2 Exchange servers). Not sure what might be different
about the config of each server. They should be identical; we are
investigating this further.

We have checked our Symantec Antivirus config and confirmed that all
recommended directories are excluded from file scanning. The one
directory listed that we don't have on our system is IMCData. As we
are on Exchange 2003 we are not using any Internet Mail Connectors.
All our SMTP email is handled through SMTP virtual servers.

We do use a spam/virus filtering service, Postini, through which all
our inbound and outbound mail is filtered; we are also investigating
this issue with them directly.

Any help or suggestions would be appreciated.

Thanks,
Tom

Thanks... any theories on why they are getting stuck in the temp
tables in the first place? Sounds like this would not be as a result
of an AV program...

This is a relatively new phenomenon with our systems and it is only
happening to one of two servers. Ultimately, I'd like to get to the
root cause and resolve it.



.

Relevant Pages