"The connection to the server has failed."

  • Thread starter Thread starter Guest
  • Start date Start date
According to SafeLink:

Outgoing Mail (SMTP): mail.safelink.net
Incoming Mail (POP3): mail.safelink.net

See http://www.safelink.net/help/newaccount.htm

--
Gary VanderMolen [MS-MVP WLM]


leah said:
safelink is my provider

Gary VanderMolen said:
Each e-mail provider has their own mail servers. Check your provider's
website for instructions, or alternatively, tell us who your e-mail provider
is, and we can look up that information for you.

--
Gary VanderMolen [MS-MVP WLM]


mhay said:
hi,i hv likewise prob.dont know what to write in server?tnx
Click to expand...
Click to expand...
Click to expand...
 
Usually, just send an email to yourself.

Note that if you post in ALL CAPITALS, you are likely to be treated
as shouting, and therefore get fewer answers.
 
We often need the complete error message to offer much help, not just
part of it. Right click on it, and copy it to your next message.

Also, many Windows Mail problems are due to interference from an
antivirus program, so it may save some time to tell us what if any
antivirus programs you have, and whether you have ever had a
Norton or McAfee antivirus program installed on that computer.
 
McAfee antivirus is among the top three troublemakers for Windows Mail.
Sometimes it takes a while before symptoms start showing up.
First of all, turn off email scanning in McAfee, although that is seldom sufficient.
Next, delete that email account (because it has been corrupted by McAfee),
restart Windows Mail, then recreate the account.

If the problem continues, the only way you can prove or disprove that
McAfee is the culprit is to uninstall it, followed by using their debris removal tool:
http://service.mcafee.com/FAQDocument.aspx?id=TS100507
If you decide to replace McAfee, we can recommend a free antivirus
program which is more compatible with Windows Mail:

Instead of switching to a different antivirus, another option is to upgrade
to Windows Live Mail (WLM), which is more resistant to the adverse effects
of overly intrusive antivirus products: http://download.live.com/wlmail

Even with WLM, you must disable email scanning in the antivirus,
for the reason explained here:
http://thundercloud.net/infoave/tutorials/email-scanning/index.htm
 
I went to Tools, Accounts, Properties, Servers and made sure that "Log on
using Secure Password Authentication" was unchecked. Then I did what you
advised, which is to uncheck the email attachment shield on my Webroot
Antivirus which immediately helped to solve my connection problems. Thanks
very much! Do you think I should contact Webroot to mention this problem?
 
The idea of checking incoming email is a "Feelgood Factor", it sounds
good but the time taken can cripple your email client due to timeout
errors, this is true for all versions of Windows and Linux as well. On a
good day it will work, on a bad day you're hosed and may suffer long
term damage.

Your AV should check anything placed on your system, but this is not
time limited like communicating with servers is.

Please post back if you find the solution, it helps others. Thanks.

Charlie Tame
 
The email scanning function is included in the AV product because all
the competitors include it, and it makes for another bullet on the box for
gullible buyers.

Even Symantec (Norton), the originator of the email scanning concept
admits that it is redundant and unnecessary:

"Is my computer still protected against viruses if I disable Email Scanning?
Disabling Email Scanning does not leave you unprotected against viruses
that are distributed as email attachments. Norton AntiVirus Auto-Protect
scans incoming files as they are saved to your hard drive, including email
and email attachments. Email Scanning is just another layer on top of this.
To make sure that Auto-Protect is providing the maximum protection, keep
Auto- Protect enabled and run LiveUpdate regularly to ensure that you have
the most recent virus definitions."

The above paragraph is from http://service1.symantec.com/SUPPORT/nav.nsf/docid/2002111812533106
 
Back
Top