Windows 7 - new error message in Mail

Asked By Marilyne

21-Nov-09 01:47 PM

Tried again to send a message in windows Mail and got this message this time.
Why?
An unknown error has occurred. Subject 'test', Account: 'pop.gmail.com',
Server: 'smtp.gmail.com', Protocol: SMTP, Port: 465, Secure(SSL): Yes, Error
Number: 0x800CCC0B
--
MEricksen

21-Nov-09 07:58 PM

The "Unknown error" symptom is often caused by interference from
an antivirus program. Which antivirus are you running?
As a minimum, email scanning in the antivirus should be turned off,
although that may not be sufficient to eliminate all bad effects.
In a worst case scenario, your antivirus may need to be uninstalled.

Email scanning in any antivirus should be disabled, for reasons
explained here:
http://thundercloud.net/infoave/tutorials/email-scanning/index.htm

If no improvement after disabling email scanning, consider upgrading
to Windows Live Mail, because it is less prone to suffering bad effects
from overly intrusive antivirus programs:
http://download.live.com/wlmail=20

--=20
Gary VanderMolen, Microsoft MVP (Mail)
http://mvp.support.microsoft.com/default.aspx/profile/vandermolen


this time.=20
'pop.gmail.com',=20
Error=20

22-Nov-09 12:27 AM

Antivirus program is Webroot and only scans email attachments.  I di manage
to get one and only one email to get sent after adjusting outgoing server
settings.  Tried to send again and got the following message:
Your server has unexpectedly terminated the connection. Possible causes for
this include server problems, network problems, or a long period of
inactivity. Subject 'Re: test', Account: 'pop.gmail.com', Server:
'smtp.gmail.com', Protocol: SMTP, Port: 465, Secure(SSL): Yes, Error Number:
0x800CCC0F

Now what?
--
MEricksen

22-Nov-09 01:33 PM

If it is scanning attachments of outgoing messages, then it has to do
something to get the message. Whether it is scanning the main message is
irrelevant to the fact that it is processing the messages. It must do
something extra besides what Windows Mail does in order to get the message.

There is something interfering with Windows Mail. It might be a bug in
Windows Mail but I have not seen any solid evidence of that in any of the
thousands of messages I have read in this newsgroup. I assume that Gray has
not either, and you will not find anyone in this newsgroup with more experience
relevant to this than Gary. Please read all of Gary's comments and comply
with his suggestions as best as possible. If anything else, you need to
eliminate Webroot as a suspect before trying to get help with other
possibilities, because the experts know from experience that the AV program
is the most likely cause.

22-Nov-09 09:23 PM

your antivirus program. I already told you previously how to resolve
that issue.
As a definitive test, uninstall Webroot, reboot, then try sending again.

--=20
Gary VanderMolen, Microsoft MVP (Mail)
http://mvp.support.microsoft.com/default.aspx/profile/vandermolen


manage=20
server=20
causes for=20
Number:=20
effects
this time.=20
'pop.gmail.com',=20
Yes, Error=20

24-Nov-09 12:12 AM

Why all of the sudden is Webroot the problem?  I have had it since I got the
computer in April and was able to send emails last Monday just fine, before
the updates that evening.
--
MEricksen

24-Nov-09 01:22 AM

Antivirus programs frequently receive program updates as well
as virus signature updates. Sometimes the antivirus program update
has not been fully tested, and it causes problems with Windows Mail.
The definitive test is to do a trial uninstall of your antivirus. If =
that
corrects the problem, you have found the culprit.

--=20
Gary VanderMolen, Microsoft MVP (Mail)
http://mvp.support.microsoft.com/default.aspx/profile/vandermolen


got the=20
before=20
again.
di manage=20
server=20
causes for=20

Error Number:=20
off,
uninstalled.
upgrading
effects
message this time.=20
'pop.gmail.com',=20
Secure(SSL): Yes, Error=20

24-Nov-09 11:48 AM

It is totally possible that there was an error in Vista that Microsoft fixed
but Webroot had written their program so it worked with Vista with the bug
in it but then did not work when the bug was fixed.