Re: SMTP causes inetinfo.exe process to regularly produce high CPU

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Hello,

thanks for the answer.
In the case of our mail server it turned out to be the UCEArchive folder
where IMF archives spam mails that are not forwarded to the mailboxes. It
contained several hundred thousands of spam mails and was extremely
fragmented. This resulted in long access times when the SMTP server was
working with the folder. After turning off archiving (there was never the
need to check any of the mails that was sent to this folder) all is back to
normal.

--
Thorsten Abdinghoff



"Matteo Cilloni" wrote:

Hi,

if you don`t have any third party software installed the most probably cause
is a SMTP corruption.
You can reinstall SMTP components using step described on KB
http://support.microsoft.com/kb/312395/en-us

This KB is specific for Exchange2000, but you can use it for E2K3 as well.



"Thorsten Abdinghoff" <thabd@xxxxxxxxxxxxxxxxx> wrote in message
news:FE0D867A-D035-4CB2-B784-2382606BACA8@xxxxxxxxxxxxxxxx
The server is a Windows 2003 system that runs ISA 2004, WSUS 3.0 and
Exchange
2003. There is no antivirus software or any other third-party software for
Exchange installed. The system is patched with all available Windows
Updates.

Since a few weeks inetinfo is taking up 50 and more percent of both CPUs
every 10-20 seconds (sometimes it takes longer). After a few seconds all
is
back to normal until after 10-20 seconds it starts all over again.
During that high CPU usage internet access and other activities on the
server significantly slow down which begins to affect our business
activities.

Stopping the SMTP service immediately stops this behaviour from occuring.
Turning it back on immediately starts the described behaviour.

There are no large message queues or NDR messages waiting to be delivered
(Recipient Filtering is enabled and relaying is restricted to
authenticated
users). There are no hints for a password attack as there are no logon
failures in the Windows event logs. There are also no other error messages
in
the event logs. Exchange did also not show any noticeable malfunction
besides
the behaviour described above.

Has anybody any idea what could be causing this?

--
Thorsten Abdinghoff




.



Relevant Pages

  • Re: Duplicate email sent upon server reboot (Exchange 2003)
    ... Did it mention anything about the AV or about smtp? ... Here 's a procedure to reset the temptables. ... also occur that require that you restore Microsoft Exchange Server. ... Right-click the Recovery folder, ...
    (microsoft.public.exchange.admin)
  • Re: E-mail sent to public folder is being held up in queue
    ... > Exchange server to this new one. ... We use the public folder store on ... > SMTP Store Driver: Message Submitted from Store ...
    (microsoft.public.exchange2000.admin)
  • Re: Setup Exchange Server 2003
    ... My questions and concerns are to get my settings for SMTP correct to be ... Server. ... Perform reverse DNS incoming CHECKED ... Not Checked- Do not allow public folder referrals ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange - Huge Problem,SMTP Relay?
    ... I repeat SBS IS NOT a relayer. ... > When you set up sbs it set up the smtp server and it is ... > STOP your smtp service and set it manual not autonmatic so ... >>in that folder there is about 50 folders with each folder ...
    (microsoft.public.windows.server.sbs)
  • Re: Setup Exchange Server 2003
    ... Server. ... DNS via SMTP. ... Perform reverse DNS incoming CHECKED ... Not Checked- Do not allow public folder referrals ...
    (microsoft.public.windows.server.sbs)