Daniel,
We have been having Dr. Watson errors on the SMTP32.EXE process, and
lately they've been MUCH MUCH more frequent (2-3 times Per/Day). I noticed
your post regarding the Aliases being over the value of 50, however you
recommended scanning through all domains/aliases to find the problem. With
over 1800 domains, and average of 3-4 aliases per/domain, we're talking many
many many many hours that should be spent at IPSwitch's side fixing the
problem so a user can't mess up our mail system.
Any further ideas as to why our smtp32.exe process is consuming 50%
of the CPU utilization x2 (two processes of it running, each consuming 50%).
The server shortly thereafter will hang on the SMTP and fail to deliver any
messages.
-Mark McDonald
[EMAIL PROTECTED]
The Siteserver Network!
Voice: 800.610.9856, Ext. 231 - Fax: 888.333.2710
-----Original Message-----
From: Daniel Donnelly [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 09, 2000 1:02 PM
To: [EMAIL PROTECTED]
Subject: Re: [IMail Forum] BIG Problem/Dissatisfied Customer
Frank,
Mentioning SMTP32 processes and Lists (.lst files) together, immediately
brings to mind known difficulties with Aliases of the List type, that have
too many (more than 50) email addresses or have incomplete addresses. An
Alias that calls other aliases, that cause the 50 value to be exceeded,
could also cause this problem. Please check ALL the Aliases in all the
domains, to see which ones might cause this.
The .lst files in the Queue are a clue to which aliases are the likely
cause. If you do a 'Send One' and the SMTP32 task used for that delivery,
does not close after some time, that message is the 'cause' of your trouble.
Setting the MaxQueProc to a different value, will only change the duration
of your server working correctly after a restart, i.e. if set to 10, it
might take 5 hours before you reach 10 open SMTP32 processes, if set to 30,
maybe 15 hours (Example times!). Of course, if there is no mail in the queue
that causes this, then the time could be MUCH greater. SMPT 'Number of
tries' has an effect, too. If set low, then no more that that number of
attempts will be made to deliver the 'problem' message, so there cannot be
more than this number of 'hung' SMTP32 processes.
Daniel Donnelly
Ipswitch Technical Support
________________________________________________________
See our Knowledge Base at http://support.ipswitch.com/kb
----- Original Message -----
From: "Frank Tanner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, May 09, 2000 3:07 PM
Subject: RE: [IMail Forum] BIG Problem/Dissatisfied Customer
> Again, I will re-iterate.....It is not the machine. However, it COULD be
> the number of SMTP threads causing it. The CPU Utilization ONLY goes that
> high when iMail is running.
>
> I can completely shut down iMail and run other types of apps on the
server,
> and they run just fine w/o eating the CPU cycles.
>
> I have set the number of SMTP threads to 10, 15, and 30 in the registry.
I
> get pretty much the same results all the way across the board. It seems
> like the more threads I use the more the CPU gets used, which stands to
> reason.
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> [EMAIL PROTECTED]
> Sent: Friday, July 10, 2893 4:44 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [IMail Forum] BIG Problem/Dissatisfied Customer
>
>
> > Sometimes up to four hours.
>
> Given that your CPU utilization is around 75%, it sounds like you may have
> your maximum # of SMTP threads being used, and when new E-mail comes in,
it
> can't be sent out right away, so it has to wait another 10 minutes (or
> whatever it is configured to) before being sent again. It make take a
> number of "bumps" before it finally finds a free thread.
>
> Of course, that would raise the question as to why you have 75% CPU usage.
> That I can't answer. You might want to try making a backup, and running
it
> on a test machine to see if the CPU usage is so high. It may be an issue
> with the machine.
>
> > There was nothing I could find in the logs as to why they were
> > being delayed.
>
> There has to be *some* information there. If it says that it receives the
> mail at 03:23:10, and sends it at 03:23:15, and the user complains that it
> takes 4 hours to get it, it's time to have a little chat with your user.
> Logs never lie, only people do. :)
>
> Seriously, though, the logs should show the time the E-mail came in and
the
> time it finally left, plus any attempts in between. If it just shows it
> coming it at, say, 03:23:10 and the next entry is at 07:04:20, that too
> tells you a lot.
> -Scott
> Please visit http://www.ipswitch.com/support/mailing-lists.html
> to be removed from this list.
>
> Please visit http://www.ipswitch.com/support/mailing-lists.html
> to be removed from this list.
>
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
