smtp problem

smtp.exe will not stop automatically after collecting mail. Using NT4 sp5, Exchange server 5.5 and have just installed a new ISDN TA. Everything works fine, emails come & go, but smtp is hogging my CPU when it does not need to be running. If left alone task manager reports numerous instances of smtp running together. Any ideas?
paulmarshAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jhanceCommented:
SMTP is a service and runs all the time.  The only option is to open the MMC or the Services Control Panel and stop the SMTP service.  Of course when it's stopped, you won't be able to receive any mail.

This behavior is by design and is one reason why MS recommends that an NT Server running Exchange Server be dedicated to that purpose.  (The other reason they recommend it is that it sells them more NT Server licenses!)
0
paulmarshAuthor Commented:
Thanks for that but why was it working fine before I installed a TA and terminating itself automatically, whereas now it does not stop even when the connection drops. What is bothering me is that it is hogging my CPU. Usually with multiple occurances of smtp!
0
Steve RoseCommented:
SMTP is a mail transfer protocol not an application. You should not see it in the task manager as a running application, nor will you see it listed as a process. I do not have a SMTP.EXE on my exchange servers, but I am running the Internet mail connector which uses SMTP.

The SMTP service does start automatically when the system starts. Windows NT and 2000 will only allow one instance of a service to exist on the machine at one time.

I agree with jhance that a mail server should be just that and nothing more. Running any other services or application on the server is just asking for problems. If you were to call MS for support they would tell you to call back when you remove the other applications.

It sounds like you have some sort of TSR running, such as something that came with and installed during the installation of the ISDN TA. It almost sounds like the ISDN device installed some sort of SMTP mail server of its own. Read into and check out any other software that may have installed during the installation of the ISDN TA. With out more knowledge of the product I do not know but I do know Exchange server does not cause this.


0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

andyalderCommented:
My exchange server does not have a program called SMTP.EXE, it has an mseximc.exe though.
0
Tim HolmanCommented:
Is your MTA queue hung ?
Do all the correct entries appear in your GWART ?
SMTP could still be 'open' if there's a routing loop maybe, so this is worth checking.
Do you mean IMS as opposed to SMTP ?
Do you have an SMTP mail server installed on your system - like mdaemon or sendmail ?

0
TooKoolKrisCommented:
SMTP is an Upper-Layer interface that runs in the TCP/IP protocol stack. That's why you don't see it as a process in itself, but you will find services that run on a Protocol level as a whole. Don't ask me exactly which ones they are because I don't know right off the top of my head.
0
paulmarshAuthor Commented:
Thanks for that. Quite helpful but does not solve my problem. I have inherited the present system and am trying to rectify all the problems with it. This is the most urgent one! (at the moment). I need to know how to stop smtp from running more than once as a process in task manager.
0
Tim HolmanCommented:
This question's now closed (you've answered it).
You'll need to post another if you need any more help.
0
paulmarshAuthor Commented:
thanks for all the help. I have now solved the problem! It appears that the smtp.exe supplied by my ISP was not sending the 221 close connection command thus leaving smtp running. In itself not a problem but since Kapersky AVP was configured to collect by ftp the latest update whenever a clint logged on and exchange server was set to look for email every 15 minutes I ended up with lots of smtp processes listed in task manager. Easy really ;)
0
andyalderCommented:
Guess SMTP.EXE is FTP puller that gets via FTP and sends to exchange via SMTP like pullmail etc for POP3??
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.