Announcement

Collapse
No announcement yet.

Tech Help - Email

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    Tech Help - Email

    Any help would be appreciated.

    Yesterday... my pop email accounts lost the ability to send email. I can receive, but not send. This is the case on all my accounts. Other people in the house on the network have no problems. I've rebooted... checked for viruses... and I still get the following error message.

    The connection to the server has failed. Protocol:

    SMTP, Port: 25, Secure(SSL): No, Socket Error: 10060, Error Number: 0x800CCC0E

    I have absolutely no clue what's going on.

    Help
    Keep on Civin'
    RIP rah, Tony Bogey & Baron O
    Tags: None
  • #2
    Sounds like a firewall problem to me.

    What has changed since it was last working in both the send and receive direction?
    Also, how do you connect to the internet (cable, DSL, modem). Finally, any software firewalls you have - this includes XP firewall if you have that enabled.
    I'm building a wagon! On some other part of the internets, obviously (but not that other site).

    Comment

    • #3
      Don't know if will help or not.

      http://www.propersupport.com/?menu=11&topicid=17
      Life is not measured by the number of breaths you take, but by the moments that take your breath away.
      "Hating America is something best left to Mobius. He is an expert Yank hater.
      He also hates Texans and Australians, he does diversify." ~ Braindead

      Comment

      • #4
        Do the other people in the house use the same email provider as you?
        If I'm posting here then Counterglow must be down.

        Comment

        • #5
          Yes, firewall. The error message (10060) says, that the connection timed out. Meaning, the SMTP server didn't answer within the expected time. Since you can fetch mail (port 110), but not send (port 25), it looks like a blocked port 25 either at your computer, network or ISP.

          Comment

          • #6
            Total of search:

            http://www.google.com/search?q=SMTP,+Port:+25,+Secure(SSL):+No,+Socket+Error:+10060,+Error+Number:+0x80 0CCC0E&sourceid=opera&num=0&ie=utf-8&oe=utf-8
            Life is not measured by the number of breaths you take, but by the moments that take your breath away.
            "Hating America is something best left to Mobius. He is an expert Yank hater.
            He also hates Texans and Australians, he does diversify." ~ Braindead

            Comment

            • #7
              That sounds like it too. What ISP are you with Ming?
              I'm building a wagon! On some other part of the internets, obviously (but not that other site).

              Comment

              • #8
                Other computers on the network use the same ISP, the same email server, the same software. They have no problems sending email. It seems isolated to just my machine. And started happening yesterday when I was the only one on the network. I wasn't doing anything but surfing the net... I sent an email early in the morning, and then tried sending another one about an hour later, and the problem started.
                Keep on Civin'
                RIP rah, Tony Bogey & Baron O

                Comment

                • #9
                  In addition... at the site sloww provided... it included a test so that I could check to see if port 25 is blocked. I ran the test, and it says that port 25 is not being blocked.
                  Keep on Civin'
                  RIP rah, Tony Bogey & Baron O

                  Comment

                  • #10
                    You can check, if the connection works, by getting a MSDOS window and typing "telnet your.mail.server 25". A window opens and shows the answer of the mail server.

                    If there is an answer the first line begins with 220, connection is ok and you should look if the settings in your mail client are screwed somehow. You can quit the test by typing "QUIT" and Enter.

                    If there's no answer, it's a port problem on your computer. Hard to help this out without being there. Look at Packet filtering in the TCP/IP properties.

                    Comment

                    • #11
                      Hmm...
                      could it somehow occur that you have accidentally changed the definitions in the mail program?

                      Comment

                      • #12
                        Yea, if the telnet test works, that would be my bet too.

                        Comment

                        Previous template Next
                        Working...
                        X