GoDaddy email authentication errors
Comments(4) 
GoDaddy offers a decent email account for a few dollars a month. These mail servers are picky about what ports are used to send outgoing messages based on where the message originates. I think I have cracked the case. If you are encountering either of the following errors, you are welcome.
When sending outgoing messages from an email client, you may get a server response:
553 Sorry, that domain isn't in my list of allowed rcpthosts
When creating outgoing messages in a server-side script, you may intermittently encounter:
error: -2147220973 The transport failed to connect to the server.
The problem in both cases is the port number. GoDaddy does not always favor port 25 standards. Try port 80 in your www script, and try port 3535 in your email client.
Or you can use Lame-o PowerTools from lame-o-powertools.com (with which I happily disclose a connection).
Yes, Ken Gordon, if you would like to throw money at your problems instead of learning why they exist, you can put a band-aid on your email woes and buy an email client like the one you are trying to sell here in my blog comments.
Throw money at your problems with Ken Gordon.
Anyone have a GoDaddy account? I need to migrate my shared servers to a dedicated server and not sure how all of that works.
I am having the second error issue (transport failed).
I am sending the email through ASP script from my website URL script.
I am sending thousands of emails, so that may be the problem.
I changed to port 80, but that did not work either. Not sure where to 3535 in my email client though. I tried again setting that 3535 port in my cdosendusing port code but that gave me a new error: fields update failed. Fieldupdate is a part of the ASP code script.