emailing photos

  • Thread starter Thread starter Ginny
  • Start date Start date
G

Ginny

I get an error message when I try to email a photo from any source as an
attatchment from Windows Photo gallery or any location that lets you email a
picture. This is the error message I got:
The connection to the server has failed. Subject
'Emailing:DSC00628(1),account ( My email address here;)Server'comline.com'
Protocol:SMTP, Port 25,Secure(SSL): No, socket error 10061 error
number:Ox800 CCCOE
Why isn't there a way windows could give us a list of all the error numbers
and ways to correct the problems. I have spent countless hours jumping from
one place to another to solve my problem. I hope there is someone out there
to HELP me.
I believe my problem is when I set up, it asked the question"SERVER" and I
did not understand what they wanted and I listed who my ISP was.but do not
know how to get back to that page to see if I could make a correction
 
In Windows Mail go to Tools, Accounts, select that account, Properties,
Servers. Change comline.com to mail.comline.com (two places). Click OK.
 
To research problems such as that, first be sure you get the error code
correct. It is 0x800CCC0E, not Ox800 CCCOE. There are no letter "O"s and no
space. Then go to:

http://www.microsoft.com/TechNet

And search for the error, as in:

http://social.technet.microsoft.com/Search/en-US?query=0x800CCC0E 10061 &ac=8

Note that I included the socket error (10061) in that. And that is a quick
and easy way to research problems such as this.

The first result is probably one that says "Exchange Server client". I think
Windows Mail is an Exchange Server client when the server it is connecting
to is an Exchange Server. That KB article ("Exchange Server client receives
an error message when it tries to send or receive e-mail: "Socket error:
10061, Error Number: 0x800ccc0e"") says the "client connects to a port that
is blocked or unavailable ". So if changing the server name does not work,
the problem could be the port number.
 
The Microsoft error codes like 0x800CCC0E are often quite misleading.
I pay no attention to them when diagnosing the issue.
The server error message is much more informative.
 
Then go ahead and explain to Ginny how to diagnose the problem.



The Microsoft error codes like 0x800CCC0E are often quite misleading.
I pay no attention to them when diagnosing the issue.
The server error message is much more informative.
 
I was trying to help Ginny understand how to diagnose the problem, since
that was part of the question. You did not answer that part of the question.
I would prefer to help someone understand how to solve a problem them self
and Ginny expressed an interest in doing that.


I told Ginny how to fix her problem in my response dated 12/31/09.
 
Oh, I see what you're saying.
It took me several years to acquire the knowledge I have about mail servers
and their error messages. I don't think it is something you can teach or
explain in a few sentences. To use an illustration, would you explain to a
handyman how to use a scalpel and then have him do open heart surgery?
 
Good.

In those situations in which the answers are not available elsewhere, then
obviously the best advice is to ask here. The results from searching TechNet
and other places can be confusing. I think it is best for people to try to
search for a solution before posting a question.

To use an illustration, you can't depend on your doctor to tell you
everything you need to know about medical conditions. Someone with diabetes
must spend time learning about the condition. There are many other details
that the doctors don't want to be bothered with. There are many details
about health that the doctors don't have time to tell us about that we can
learn from doctor shows such as Dr. Oz.

I don't provide much help in this group, but I have helped in programming
sites and developers should be able to research problems before asking for
help. Sometimes developers don't do adequate research and in case they don't
know how I explain how to. Some people are critical of that and say I should
just answer the question instead of explaining how to find the answer and
many more answers in the future. I certainly want to explain to someone how
to search for answers if they are interested in knowing how.


Oh, I see what you're saying.
It took me several years to acquire the knowledge I have about mail servers
and their error messages. I don't think it is something you can teach or
explain in a few sentences. To use an illustration, would you explain to a
handyman how to use a scalpel and then have him do open heart surgery?
 
Back
Top