Outlook Express error - 0x800ccc67

Hi all.
I am a newbie to Avast.

Question

when sending a test message in Outlook Express i am encountering the following error :

An unknown error has occurred. Account: ‘mail.bigpond.com’, Server: ‘mail.bigpond.com’, Protocol: SMTP, Server Response: ‘421 Cannot connect to SMTP server 144.140.90.10 (144.140.90.10:25), connect error 10060’, Port: 25, Secure(SSL): No, Server Error: 421, Error Number: 0x800CCC67

so far I have:
recreated the mail profile
assured that OE is not set to block attachments
telnetted to my mail server successfully
created another identity in OE

Note: my ISP’s mails server doesn’t require secure password authentication to be enabled

aside from reinstalling my OE, is there anything else I should do with avast!? This program is different in layout to every other antivirus I’ve used, I think there is some functionality in there somewhere that has slipped my attention and is causing this.

Thanks for reading this :slight_smile:

While your ISP doesn’t require Secure password authentication to be enabled under Incoming mail, it may be that under “Outgoing Mail Server” settings you may have to tick off “My server requires authentication”.

Welcome to the avast! forum pondiferus.

To help us maybe you can give us a little more information about your system.

What operating system are you using? Are you using a firewall, if so, which one?

Check that your firewall (which is?) allows access for ashMaiSv.exe, the avast! email scanner.

yea, the same thing seems to be hapening tome, (XP, disabled firewall: ZONEAlARM)
but also, you might want to check, everytime I open Outlook, or check for new mail (aside from the error message) a recent e-mail gets deleted. I checked the “deleted” folder, and I found some, but soon after that they stopped showing up in there (weird) I started with 21 new e-mails, I’m down to 5 and affraid to open it any more. I hadnt realized it, but it started after I installed AVast…! this all started happening today bout 4 hours ago…anyone???

avast doesn’t delete email without them being infected and you have indicated that that is what you want it to do, it doesn’t take autonomous action unless you have set it up that way.

Even if avast deleted the email, it doesn’t delete it into the deleted emails (items) folder, avast scans your incoming email before it gets to your inbox and if an infected email is detected if you decide to delete it then it never gets to your email folders, deleted or otherwise unless you set it up that way. Outlook/Exchange, Customize, Inbound Mail, Move to the following folder and/or Virus Storing, Move it to the following outlook folder.

So if you haven’t done any of the above there is something else going on, especially if the emails being deleted aren’t ones that have been detected as infected.

yea, like I said, its weird. I’m going trough everything, so far me and a support tech (Verizon DSL, using an interface similar to pc-anywhere) where really suprised at what happened when we set up a different acount, and ran AVAST (with no key-registration), a lot of stuff changed, he said he had never seen anything like it. I really dont know if its because its not registered, or the combination of different programs I have running although all virus/firewalls are disabled at this time. But as for the original problem (pondiferus), its not hard to fix, sounds like what you’ve done so far should take care of the problem, if it hasn’t, you are probably missing some minor detail about creating a new account, and setting up the e-mail servers. One thing I learned, your mail settings may change after you run AVAST (wich you shouldnt do till you’re 100% sure OE is working properly again), to something like 127.0.0.1, for both incomming and outgoing, thats normal, your OE should still work, you might want to check the FAQs for OE in the AVAST self help section, it tells you all about it.

oh yea, changing the server settings is normal for the newest version of AVAST, its all in the FAQs. there are actually lots of new stuff in the latest versions, not in what it does, but in how it does it. Its actually pretty cool suff, it may take some getting used to for some of us. Hope this helps. Please tell more about what happens.

@neal63: How would I do this? I’m getting this error message whenever OE tries to send email, though I receive it just fine.

What is the ‘fully’ error text and not just the number in isolation ?

What is your OS ?
You have opened up a very old topic and now you shouldn’t have to make any manual setting changes for avast to scan your email depending on your OS.

Since you receive email just fine then this is probably not an OS issue (but please answer the question from DavidR to help us be sure).

It would also help us if you can tell us the name of the smtp server you are trying to connect to. If it is an ISP server you will be divulging no personal information and we may be able to check and see what the issue is with port 25. If it is a private server set up for you alone then ignore my request but we may need to question if you have the correct settings in OE.

Does terminating the Internet Mail provider in avast make any difference to the experience you have in sending mail?

I’m sorry for opening this topic again, but it’s the only result I got when I searched for the error number online. I’m running XP Pro, the error code is:

“An unknown error has occurred. Account: ‘mail.comcast.net’, Server: ‘smtp.comcast.net’, Protocol: STMP, Server Response: ‘421 Cannot connect to SMTP server 76.97.30.119 (76.97.30.119:25), connect error 10061’, Port: 25, Secure(SSL): No, Server Error: 421, Error Number: 0c800CCC67”

Terminating the Internet Mail thing in Avast changes the error message to:

“The connection to the server has failed. Account: ‘mail.comcast.net’, Server: ‘smtp.comcast.net’, Protocol: SMTP, Port: 25, Secure(SSL): No, Socket Error: 10061, Error Number: 0x800CCC0E”

If the avast Internet Mail provider is terminated and you are still getting an error the problem is likely to be with the email server.

Have you checked with comcast (support pages or server status, etc.) to see if they are experiencing any email server problems ?

A google search for comcast, the socket error number and Error number with avast disabled returns some hits, http://www.google.com/search?q=comcast+Socket+Error%3A+10061+Ox8000CCCOE. Check and see if there is anything which may help.

I am a Comcast user and have no problems with port 25 (with or without the Internet Mail provider scanning the mail).

There are cases where Comcast has blocked port 25 to individual users who have been using the port to send large volumes of spam (whether intentionally or without their knowledge due to a spambot infection).

The other issue for port 25 is that to use it you must be directly connected to the Comcast network. All to often these days folks are connecting wirelessly from their local coffee shop or if at home are using whatever wireless connection they can connect to whether it is their own or a that of a neighbor. To prevent spamming Comcast will not allow (quite reasonably) a port 25 connection that has not been authenticated as a Comcast customer by connecting from within the Comcast network.

There are alternate secured ports for sending mail to smtp.comcast.net where you must also specify your account and password to authenticate yourself. You can use these ports whether you are on the Comcast network or in your local coffee shop. However, avast cannot scan mail sent on a secured connection and does not try to do so.

If you need more advice on the secure ports please say.

None of the hits on that Google link panned out, in fact most of them were of the same post, hosted on different sites, about a problem similar to mine that was redirected to another forum that doesn’t exist anymore.

I don’t use wireless internet at all, so they wouldn’t block me for that reason, and Avast has sounded no alarms about sending spam mail. However, I’ll contact Comcast support and try to find out why my outgoing mail’s been blocked. Thanks anyway, all.

Here is the error on my machine XP/OS and problem in Outlook Express:
The server responded with an error. Account: ‘pop.peoplestel.net’,
Server: ‘pop.peoplestel.net’, Protocol: POP3, Server Response: ‘-
ERR Cannot connect to POP server 137.118.25.69 (137.118.25.69:110),
connect error 10061’, Port: 110, Secure(SSL): No, Server Error: 0x800CCC90,
Error Number: 0x800CCC90

Nothing has changed on my ISP end or the setting in OE (unless avast made changes without notifing me). The problem just started yesterday after Avast did an update. Another interesting point is that it is only affecting OE and not Outlook office running on the same machine connecting to the same ISP. I really think there is a new bug in the Internet mail in Avast! And sofar from what I read it is limited to OE. If I turn Internet mail scanning off OE works just fine. I think Avast needs to roll back the clock until they get this bug fixed. Just my 2 cents

I think this is unrelated to your issue and as mentioned in your other topic post, I think you should create a new topic and we can try to deal with ‘your’ problem.

I doubt it is a bug in the Internet Mail provider with OE as it would be swamping the forums as OE is still a very popular email client. I have avast and OE for almost 4 years and no problems.

avast has no need to change your email settings with XP to be able to scan your email.

avast does not change anything on XP systems.

At the same time? I mean, Outlook can connect at the same time OE can’t?

Not identical times but click send and receive on OE and I get the error. Click send and receive and Outlook Office and it will fectch the mail with no error. Same machine and the same settings in each. I have even tried to change the settings and OE still has an error message. I also run ZA firewall but turning off or on the mail scanning doesn’t affect either way. Only turning off internet mail scan in Avast corrects the problem.

On your suggestion I will creat a new post with my issue. I will copy and paste the two replies to my questions in that new post.