Cannot send emails using Eudora as client getting error code 10060

I am using Eudora I have three email accounts. I can send emails from all three using Eudora as a client. When Eudora tries to send emails, I get errors. Here is the error I get for Yahoo. The other two are the same, only the names change:

Yahoo, Contacting [] [12:19 AM]
Could not connect to: "" Cause: connection timed out (10060)

I have looked all over the place for a joy
Any help here?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Do you have any mail filtering software installed on your machine? Try to disable it for testing purposes.
Can you resolve on your system, e.g. try to ping it.

To do this, click on "Start" -> "Run" and enter "cmd". Press Enter, a black box should appear.

Type "ping" in there and press enter.
Does the output look like "Response received" or "Connection timed out"?
Dave HoweSoftware and Hardware EngineerCommented:
That is a generic "can't connect" error. The usual cause of that is that you have installed antivirus that has a "pop3/smtp" filtering function, and that isn't working properly (symantec's solution is notorious for this issue, but there are plenty of other vendors that show the same problem). Really, I can't suggest any way to test this though other than trial-uninstalling your AV on one of the machines to see if the issue "goes away".

The other possibility is that you can't connect to the target server for network reasons - either your network setup doesn't permit port 25 (smtp) traffic to that host, or your provider (and bt internet here in the uk used to be notorious for this, no idea if they still are) blocks access on port 25 to all but their own mail servers "to prevent spamming".

to test this really, you need a telnet client - windows has a (fairly poor) one built in, but I usually use putty (

connecting to port 25 using a telnet client should give you an smtp banner page (or in the case of some AV packages, should show the AVs own banner)
Hello rdaves,

Can you receive but not send?  Are you setting up Eudora for first time to send?  Or has Eudora been working and suddenly stopped?

Try this troubleshooter from Eudora website

Hope this helps!
Become a CompTIA Certified Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

rdavesAuthor Commented:
I have pinged Eudora with 1 lost packet.  I have pinged Yahoo with 100% success.
I have been sending and receiving email on this computer successfully for years.
I am in an RV park that has WiFi, however, this signal is poor.
I can receive, but not send.
Last night, my wifh both sent and received email using Eudora.
Thereafter, I could only receive email.  I could not send any emails.
The Wifi is operating at 5.5. mbps with low signal.
I am wondering if this has something to do with the RV park's router.
I am getting on the raod momentarily and will check another WiFi venue today
Temporarily disable your antivirus check of outgoing mail and then test. If signal is weak, everything is slow.
Dave HoweSoftware and Hardware EngineerCommented:
It is possible that you are failing your TCP handshake due to packet loss - however, that should affect ALL traffic not just smtp.
rdavesAuthor Commented:
I have ddisabled my firewall and anti-virus and am still unable to send emails.
I am now in a different location, using a different WiFi service and am not getting "Connection Refused [10061] messages.
rdavesAuthor Commented:
Correction:  I am NOW getting Connection Refused [10061] messages.  I mistyped the word "now" in my previous posting.
rdavesAuthor Commented:
Here's a post from another source:
"It could very easily be that the WiFi connection that you are using is through an ISP that blocks outbound connections on port 25 (default SMTP port) that do not go through their own servers.My ISP does the same".
I'll bet that's it. As I said, I am in a different location and am still having a problem sending emails. I am now getting "Error talking to SMTP server [421 Cannot connect to SMTP server (64.9]"

I can ping the Yahoo and Hughes servers just fine. I can receive emails, but cannot send. I'll bet that last night's ISP and tonight's ISP are one and the same, or they have the same policies.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Clients

From novice to tech pro — start learning today.