Ricoh copier email transmission fail with Go Daddy

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • COPIERMAN
    Senior Tech

    500+ Posts
    • Jun 2009
    • 559

    #16
    Re: Ricoh copier email transmission fail with Go Daddy

    thank you everyone for the posting. Looking into email relay also will try port 80 with go daddy

    Comment

    • sandmanmac
      Field Supervisor

      Site Contributor
      2,500+ Posts
      • Feb 2009
      • 3978

      #17
      Re: Ricoh copier email transmission fail with Go Daddy

      Originally posted by COPIERMAN
      thank you everyone for the posting. Looking into email relay also will try port 80 with go daddy
      For what it's worth, and as far as I can remember, I only have 2 clients that are configured via Go Daddy server -both using port 80 (non-ssl)
      However, One of those clients has machines in 5 different offices around the City, all scanning under the same user account and they've not had a problem in years.

      Comment

      • Santander
        Senior Tech

        Site Contributor
        500+ Posts
        • May 2009
        • 768

        #18
        Re: Ricoh copier email transmission fail with Go Daddy

        Originally posted by slimslob
        My experience is that when email transmission fails intermittently it is usually that your ISP is blocking the SMTP port. This can happen with the size of GoDaddy when other email providers get numerous spam complaints about one of their customer the entire SMTP is black listed. GoDaddy is very quick at correctly the issue.

        So now the question is with GoDaddy what SMTP port have you been using? Like I said above it is the port that is being blocked. So if you are using the one of the normal SMTP ports (25, 465 or 587) it can be blocked. One f the nice things with GoDaddy is that their SMTP server, smtpout.secureserver.net, can use port 80. Port 80 is the same port that every browser uses to access the internet and so cannot be blocked.
        GoDaddy Email Settings
        Your assessment is correct. Don't forget that smtpout.secureserver.net also utilizes port 3535, which they do not block. Since using the 3535 port we have not had any issues.

        Comment

        Working...