Adam,
 
we had same issues since upgrading to 7.06; we posted the question and got back several helpful tips....one of which was to change the "files" value in config.nt and add a shell command line also.....
 
Here's a copy of that email  below - this suggestion worked great for us - of course as the old saying goes - try it at your own risk.... 
 
 
> Randy,
>
> Friday, September 13, 2002 you wrote:
> RA> We get the same SMTP.exe and ntvdm.exe errors on more occasions than I would
> RA> prefer as well, and we are running declude ; we have
>
> I fought this problem for a long time.  Since taking the following
> steps I've not had a single alert box and that's been about a month
> now:
>
>     I found this from Microsoft
>     http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q196453
>     I edited my Config.nt file
>     and set  files=60
>              shell=%SystemRoot%\system32\command.com /e:4096
>
>     changed registry per
>     http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q184802
>     My last change to SharedSection was 1024,3072,128 but I'd tried all
>     other numbers.  I've reset it to SharedSection=1024,3072,512.
>
>     My SMTP processes is at 30.
>
>     also see http://www.declude.com/dq.htm
>
> Terry Fritts
 
Sincerely,
 
Randy Armbrecht
Global Web Solutions�, Inc.
804-346-5300 x102
877-800-GLOBAL (4562) x102
----- Original Message -----
Sent: Monday, September 23, 2002 1:51 PM
Subject: [IMail Forum] Smtp fails and spool keeps growing

We have recently been having problems sending mail with our smtp server. At times it crashes and will not send mail. When this happens, we ussually have to restart the server for without the smtp service started, make a new empty spool directory, start the smtp service, and then start moving the files from the old spool over. I have a couple questions.
 
1) Is anyone else having the same problem. Smtp sevices craashes and spool directory builds while noe mail is sent and there is no warning given on the server.
 
2) What is the best way to solve this problem. Do we have to shut down the server to fix this, or is there another way to do it? We really don't like shutting down the server, but it seems like that is the only way to do it.
 

Reply via email to