Author Topic: Sending Email Problem! Serious!  (Read 10427 times)

0 Members and 1 Guest are viewing this topic.

rjsampsonjr

  • Guest
Sending Email Problem! Serious!
« on: December 09, 2004, 11:24:46 PM »
In my Imail web logs, mail is not being sent and I am seeing this message:

421 concurrent connections limit in avast exceeded

How do I fix this??

RJ

Offline Eddy

  • Avast Evangelist
  • Maybe Bot
  • ***
  • Posts: 31210
  • Watching (over?) you
    • Malware removal, Biljart and other things.
Re:Sending Email Problem! Serious!
« Reply #1 on: December 10, 2004, 12:03:38 AM »
What exact OS?
What exact version of Avast?
What email client?
What settings?

Did you install Avast when logged in as administrator (XP Pro) or when logged in as user with admin rights (XP Home)?
« Last Edit: December 10, 2004, 12:08:04 AM by Eddy »

rjsampsonjr

  • Guest
Re:Sending Email Problem! Serious!
« Reply #2 on: December 10, 2004, 02:13:53 AM »
Windows 2003 Server
Avast Version 4.5.345
Email clients various, I know about Outlook Express 6
I was logged in as administrator when I installed Avast.


Offline Eddy

  • Avast Evangelist
  • Maybe Bot
  • ***
  • Posts: 31210
  • Watching (over?) you
    • Malware removal, Biljart and other things.
Re:Sending Email Problem! Serious!
« Reply #3 on: December 10, 2004, 02:23:34 AM »
Are you using the server edition of Avast?

rjsampsonjr

  • Guest
Re:Sending Email Problem! Serious!
« Reply #4 on: December 10, 2004, 02:28:02 AM »
Yes.

This started 12/7 around noon.  Here is an example from the IMail logs. I have bolded the lines below.

12:07 12:21 SMTP-(0990022F)
  • looking up msn.com in HOSTS and MX

12:07 12:21 SMTPD(05B401F8) [216.154.192.100] connect 216.154.192.100 port 4608
12:07 12:21 SMTP-(0990022F)
  • looking up bellsouth.net in HOSTS and MX

12:07 12:21 SMTP-(0990022F) Trying bellsouth.net (0)
12:07 12:21 SMTP-(0990022F)
  • Connecting socket to service <SMTP> on host <bellsouth.net> using protocol <tcp>

12:07 12:21 SMTP-(0990022F)
  • using source IP for mail.yourcareerfair.net [216.154.192.133]

12:07 12:21 SMTP-(0990022F) Connect bellsouth.net [205.152.59.32:25] (1)
12:07 12:21 SMTP-(0990022F) 421 concurrent connections limit in avast exceeded
12:07 12:21 SMTP-(0990022F) SMTP_DELIV_FAILED
12:07 12:21 SMTP-(0990022F) >QUIT
12:07 12:21 SMTP-(0990022F) [E] didn't send "QUIT
": connection aborted12:07 12:21 SMTP-(0990022F) rl-recv: connection aborted
12:07 12:21 SMTP-(0990022F)
12:07 12:21 SMTP-(0990022F) closing socket (u)
12:07 12:21 SMTP-(0990022F) Trying msn.com (0)
12:07 12:21 SMTP-(0990022F)
  • Connecting socket to service <SMTP> on host <msn.com> using protocol <tcp>

12:07 12:21 SMTP-(0990022F)
  • using source IP for mail.yourcareerfair.net [216.154.192.133]

12:07 12:21 SMTP-(0990022F) Connect msn.com [64.4.50.239:25] (1)
12:07 12:21 SMTP-(0990022F) 421 concurrent connections limit in avast exceeded
12:07 12:21 SMTP-(0990022F) SMTP_DELIV_FAILED
12:07 12:21 SMTP-(0990022F) >QUIT
12:07 12:21 SMTP-(0990022F) [E] didn't send "QUIT
": connection aborted12:07 12:21 SMTP-(0990022F) rl-recv: connection aborted
12:07 12:21 SMTP-(0990022F)
12:07 12:21 SMTP-(0990022F) closing socket (u)

rjsampsonjr

  • Guest
Re:Sending Email Problem! Serious!
« Reply #5 on: December 10, 2004, 03:06:59 AM »
Looking at the logs some more it seems to happen on mails with attachments.

How can I turn off Avast when it comes to sending mail through Imail.  I do not see a setting for this?

Please help!

Offline Vlk

  • Avast CEO
  • Serious Graphoman
  • *
  • Posts: 11664
  • Please don't send me IM's. Email only. Thx.
    • ALWIL Software
Re:Sending Email Problem! Serious!
« Reply #6 on: December 10, 2004, 10:52:17 PM »
I don't understand your setup. So you're using the avast Internet Mail provider to scan email on your server? Or avast SMTP Server Edition?
If at first you don't succeed, then skydiving's not for you.

GhostDream

  • Guest
Re: Sending Email Problem! Serious!
« Reply #7 on: January 31, 2005, 12:04:42 PM »
I have the excact same problem, my setup is:

Windows sbs 2003 server, with exchange and a smtp connector relaying mail to remote host. when avast has been running for some days, it will eventually begin to drop connections to the virtual smtp server, saying: conenction limit in avast has been reached.

a restart of avast services seems to fix the problem until the service has run for a couple of more days.

I'm using Avast server edition for sbs servers. With network shield, exchange scanner and internet mail / pop3 scanner running, all without errors, and they do find virus, so they work ;o).

This problem is rather serious, as it is not only remote mailsending that is beeing halted, when smtp service is hindered in functioning, it will not route mail internally in the exchange server, hence all communication in the company stops.

And help, thoughts and ideas are greatly appreciated. ;o)

Offline Vlk

  • Avast CEO
  • Serious Graphoman
  • *
  • Posts: 11664
  • Please don't send me IM's. Email only. Thx.
    • ALWIL Software
Re: Sending Email Problem! Serious!
« Reply #8 on: January 31, 2005, 12:22:02 PM »
Guys, I don't understand why you're using the Internet Mail provider on a server. Is this a terminal server? The provider is primarily meant for clients only.

GhostDream, you should be using the "MS SMTP 2000/2003" and "Exchange 2000/2003" providers, not Internet Mail. They will take care of mail scanning much better on a SBS.


Thanks
Vlk
If at first you don't succeed, then skydiving's not for you.

GhostDream

  • Guest
Re: Sending Email Problem! Serious!
« Reply #9 on: January 31, 2005, 12:32:42 PM »
oki - internet mal scaning was running mainly just because I didn't understand what it did ;o) -. i will disable it.

but this still does not take care of the "concurrent connection" problem, ay ideas about that?


Offline Vlk

  • Avast CEO
  • Serious Graphoman
  • *
  • Posts: 11664
  • Please don't send me IM's. Email only. Thx.
    • ALWIL Software
Re: Sending Email Problem! Serious!
« Reply #10 on: January 31, 2005, 12:34:35 PM »
Why not? It's an Internet Mail provider thing (the Internet Mail provider is returning this error).
There's a hard limit on the number of concurrent connections in the Internet Mail provider.
If at first you don't succeed, then skydiving's not for you.

GhostDream

  • Guest
Re: Sending Email Problem! Serious!
« Reply #11 on: January 31, 2005, 12:42:47 PM »
uh oh - wow okay :o) didn't realise that, thanks! ill pray things work now.

mdbj

  • Guest
Had same issue- suggestion
« Reply #12 on: February 20, 2006, 04:38:36 PM »
I came to the forum because I had the same issue and was looking for the solution

I had avast keeping all my email from heading outbound aswell unless I stopped and restarted the mail client mentioned above.


how about-  #1

identifying which components do not belong running on the server or not including them on he server install
some people like to see X providers total, X running.... not x-2 running


#2
if the server installation includes the mail scanner, than it should be able to run, and not disable outbound email for everyone
it should not install or identified as 'not needing to be run' for the server itself clearly when selected/started or
what if someone is foolish enough to send & recieve email from the server itself?  they can't use the client side scanning for themselves...


Offline Vlk

  • Avast CEO
  • Serious Graphoman
  • *
  • Posts: 11664
  • Please don't send me IM's. Email only. Thx.
    • ALWIL Software
Re: Sending Email Problem! Serious!
« Reply #13 on: February 20, 2006, 11:22:53 PM »
mdbj, as you can see, this thread is more than a year old. The latest version of avast! Server Edition should already check for this condition and disable the Internet Mail provider automatically (if the Exchange shields are active).


Thanks
Vlk
If at first you don't succeed, then skydiving's not for you.

mdbj

  • Guest
Re: Sending Email Problem! Serious!
« Reply #14 on: February 22, 2006, 04:13:57 PM »
vik, as you can see, I had this same problem (and recently)

 so it's not detecting it as you suggest it should.

-at least in my installation-downloaded in november, kept current.
I have stopped the service, so my problem is solved.
however, I hate seeing 8 providers, 6 running....

I imagine others have the same issue, and haven't come here and seen the solution.