Author Topic: Incoming email protection  (Read 6563 times)

0 Members and 1 Guest are viewing this topic.

dragonhead

  • Guest
Incoming email protection
« on: January 03, 2005, 01:01:01 PM »
Hi!

Recieved error stating that Avast is now unable to protect incoming mail, error: 10022.  I restarted my WinXP SP. 2 system twice and still got the error.  Any thoughts would be most appreciated!

Perry

Offline Eddy

  • Avast Evangelist
  • Maybe Bot
  • ***
  • Posts: 31080
  • Watching (over?) you
    • Malware removal, Biljart and other things.
Re:Incoming email protection
« Reply #1 on: January 03, 2005, 01:07:41 PM »
Do you have (or did) another av installed?

Error 10022 means: An invalid argument was supplied (WSAEINVAL)

And have a look HERE
« Last Edit: January 03, 2005, 01:09:30 PM by Eddy »

dragonhead

  • Guest
Re:Incoming email protection
« Reply #2 on: January 03, 2005, 01:34:35 PM »
I had Panda up until Saturday.  I'll check out that link, thank you!

dragonhead

  • Guest
Re:Incoming email protection
« Reply #3 on: January 03, 2005, 02:00:47 PM »
Installed beta with same error on startup.  I have Outlook Express and McAfee firewall.  Two changes to my system yesterday, installed pc game and Avast found virus, Win32:Swen Wrm, sucessfully deleted.

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67195
Re:Incoming email protection
« Reply #4 on: January 03, 2005, 02:11:09 PM »
Installed beta with same error on startup.

avast beta? 4.5.549 is not a beta...

I have Outlook Express and McAfee firewall.

Maybe it'll be better to be off-line. Disable the firewall and then install avast.

Avast found virus, Win32:Swen Wrm, sucessfully deleted.

Did you send it to chest?
Do you have the name of the infected file (and path)?
The best things in life are free.

dragonhead

  • Guest
Re:Incoming email protection
« Reply #5 on: January 04, 2005, 02:27:55 AM »
Quote
Did you send it to chest?
Do you have the name of the infected file (and path)?

I did send the file to the chest and deleted it as well.  But here's the info on the virus and it's location.  

Win32:Swen[Wrm]
C:\documents and settings\Perry\local settings\application data\microsoft\msn\db\pmccork-msn-com.83\erfdcqm.exe

tinytina

  • Guest
Re:Incoming email protection
« Reply #6 on: January 04, 2005, 04:01:53 AM »
I have had the same problem.  Avast stopped protecting my email on all servers pop and imap.  It occured after I alowed avast to update to the new version just this past week.  I have been using avast since june, without any problems.  I have mcAfee firewall, windows xp, and use outlook express for mail.  Ive checked for other viruses and spyware since then and have come up nothing.  I already has the services updates to xp prior, and didn't have any problem with it.   The only thing i can think of is the recent update i alowed avast to do to the program.    

Offline vojtech

  • Avast team
  • Advanced Poster
  • *
  • Posts: 939
    • ALWIL Software
Re:Incoming email protection
« Reply #7 on: January 04, 2005, 10:36:17 AM »
Error 10022 could mean that the mail scanner is blocked by a firewall.

galooma

  • Guest
Re:Incoming email protection
« Reply #8 on: January 04, 2005, 11:34:40 AM »
hi and welcome tina
you will find that as a result of the upgrade there were changes to the way Avast! handles e-mail accounts.
Providing you are running win2k or later then your e-mail must now be configured as if avast didnt exist.
Previously e-mail was diverted through avast . this is no longer the case. looking around you will see hundreds of threads on this topic mostly around 3-5 weeks ago