Re: smtpsvc 402

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

And, one more update:

I contacted my Backup MX service tech support to see if they knew why all of
those connections from them were staying open... this is what they said:
****************************************************
We're getting a lot of messages like these when trying to deliver mail
to your server:

Operation timed out: SMTP timeout while connected to
myserver.mydomain.com [my-ip] after end of data (7076
bytes written)

This means we are waiting for a confirmation after sending the message
to your server, and it never happens so it eventually times out. The
time out is 10 minutes which means connections are staying open for
quite a long time.

You'll need to make sure there's no spam filter that is tarpitting our
servers, or any firewall that is doing anything to the connections. If
you have a spam filter on your mail server, you should either add our
servers to the white list or to a trusted forwarders list if you have
one.
*************************************************

I have Symantec Mail Security for Exchange for Antivirus and I'm using
Exchange's IMF for Anti-Spam.

Let me know. Thanks!!

"Rgarcia" wrote:

Another update:

I also noticed that there were around 450 errrors in my server report like
this:

A message could not be virus scanned - this operation will be retried later.
Internet Message ID
<6B909A01FBA732458FCEF70C0A141D2DD500@user-name.<domain>>, Error Code 0x0

I checked the queue and there were about 450 messages "pending submission".
I scanned through them and they were clearly spam so I delete them.

Just wondering if this could have something to do with my problem of not
receiving external e-mail every couple of days. I think this probably has
something to do with the inetinfo.exe allocating more memory than usual...
and, maybe they are all related?

Let me know what you think.

Thanks!

"Cliff Galiher" wrote:

You should be able to view the connections for your Virtual SMTP Server in
ESM. That first error (maximum connections reached) makes me think you are
probably...as the error indicated, just having too many connections. You
can verify this in the above mentioned snap-in though.

If you notice many connections open with a connect time in the thousands of
seconds, then that is your problem. Could be spammers trying to do a
DHA...resolveable by tarpitting or installing a good antispam gateway
product. Could be spammers using your server to relay. If unauthenticated
relaying is available to them, you can fix that. If they got ahold of
credentials to relay, you can fix that too...but with more effort.

Basically step one is to verify that your connections ARE maxed. You can
kill connections in the same snapin and see if mail starts to flow again.

Then step 2 will be to address the problems that are causing/allowing the
sessions to fill up in the first place. :)

-Cliff

"Rgarcia" <Rgarcia@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FE1A5BF0-713D-4CF4-8E01-00835D951175@xxxxxxxxxxxxxxxx
Hi,

I'm running SBS 2003 Premium (ISA 2004) with latest service packs.

The problem I'm having is that every few days we stop receiveing external
e-mails. We can send / receive internal e-mails and we can browse the
internet so I know we do have connection to the outside. A reboot will fix
the problem but it happens every couple of days. Here are some of the
errors
I get that on my server report:

smtpsvc Event 402 - Occurrences 30 *
Virtual Server 1: 204.13.249.74 maximum number of connections has been
reached. Connection being closed.

Process (inetinfo.exe) - The inetinfo.exe process is allocating more
memory
than usual. The following services are hosted by this process: IISAdmin,
POP3SVC, RESVC, and SMTPSVC.
For more detail, review the event logs for events related to these
services.
It may help to stop and then restart these services.
You can disable this alert or change its threshold by using the Change
Alert
Notifications task in the Server Management Monitoring and Reporting
taskpad.

I think I resolved the inteinfo.exe error by upgrading my version of
Symantec Mail Security for Exchange. But I'll find out for sure tomorrow
when
I check the logs again.

Any ideas on what to look for?

Let me know. Thanks!


.

Relevant Pages

  • Re: smtpsvc 402
    ... Since some spam botnets intentionally use the secondary MX record to try to bypass various spam filters, it causes the DynDNS servers "call ahead" feature to connect and verify. ... Having that list on their server prevents that call-ahead, so only legit messages are forwarded in the first place. ... those connections from them were staying open... ... I have Symantec Mail Security for Exchange for Antivirus and I'm using ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 IIS BASED SERVICES FAIL INTERMITTENTLY
    ... If I read your post correctly, you have a switch where the SBS ... Run DHCP server on your SBS, and set all client machine nics to dynamic. ... Once you have your nics configured, run the Connect to the Internet wizard, ... QUESTION1 - what is REFUSING CONNECTIONS? ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS Exchange 2003: too many "Current Sessions" opened
    ... So far everything is good and now I'm just monitoring my exchange. ... get the SMTP service to stop hanging in the first place. ... won't have dead connections. ... work for now until I put into production new server hardware with sbs 2003 ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS Exchange 2003: too many "Current Sessions" opened
    ... You really should go through the steps I posted and get the SMTP service to stop hanging in the first place. ... You'll be happier, you won't be clubbing your server every day with a kill script, and you won't have dead connections. ... You do *not* need to restart the server, ...
    (microsoft.public.windows.server.sbs)
  • Access 2007->SQL Server2005 "connection was forcibly closed",GNE 1
    ... I have a very big problem connecting an SQL ... changing number of clients using the SQL Server with this frontend at the ... connection pooling or if these connections are separated connections). ...
    (microsoft.public.sqlserver.connect)