Intermittent send failure using GoDaddy POP account.

I have been having EXACTLY the same problem.

Oddly, Entourage often cuts through whatever is hanging Mail and succeeds at sending on the first try.

Sure would like to know what the problem is.

Cameron Reddy

I believe it is a GoDaddy problem, for all the reasons already discussed. As an alternative to the Gmail solution, best solution I have seen is to simply go to settings, mail, accounts, outgoing mail server. Then, turn off your GoDaddy server as the outgoing server. Next, turn on the ATT Server listed in the category "Other SMTP Server." You will then send via the ATT server. This solution works and it avoids the need to set up a Gmail account and avoids the whole mess of the junk mail flagging with Gmail and the need to set up alternate "send as" addresses.

I have found that when you send an email through a different server,
the person you are sending to
receives your email with the address
that is linked to that server.

In other words,
if I want to send to someone
from my godaddy email address
and I set up an email using that godaddy email address
BUT I use my smtp for google
instead of secureserver.net
then the person I am sending to
sees my email as having come from gmail
and not from my godaddy address.

Not so, in my experience, with the solution I suggested above: use the ATT server as your outgoing mail server. No email address "associated" with that. I tried and tried to get the Gmail solution to work in terms of reflecting the address to be one other than the dummy Gmail address, i.e., my normal address. It will not work with iPhone in my experience, in other words, Gmail will always reflect the Gmail address. And, the real problem is that when people reply to emails sent from your iPhone, they just to to the Gmail address and are reflected only in your phone's inbox and not in your computer's Outlook/Entourage/Mac Mail inbox. Again, using the ATT server seems to avoid all this. Anyone experience any problems with the ATT outgoing mail server solution?

Sorry...I wasn't talking about iphone...i was talking about godaddy email with Apple Mail. I wasn't aware that this thread was concerned only with godaddy email and iphone.

I also have the issue when online at my local coffee shop on my MacBook Pro. They need to resolve this if people are going to start jumping ship.

Michael Day3 wrote:
I have found that when you send an email through a different server,
the person you are sending to
receives your email with the address
that is linked to that server.

NO THIS IS INCORRECT.. This is only an issue with gmail! I think they have a way for you to setup that.. But typically an smtp server does NOT change the outgoing email address.

Michael Day3 wrote:
Sorry...I wasn't talking about iphone...i was talking about godaddy email with Apple Mail. I wasn't aware that this thread was concerned only with godaddy email and iphone.

What are you talking about?!?!? This thead IS about godaddy's horrid smtpout server and ANY PLATFORM, ANY MAIL program.. or even just TELNETing to the smtpout server you can reproduce the problem.... Mail, iphone, osx, windows, linux, etc.. It is in NO way iphone specific.. maybe you should read the thread before you go confusing people...

I too pay for their e-mail services, so it's quite frustrating.

As long as people keep paying they don't have a lot of incentive to fix it.

a PROPERLY CONFIGURED SMTP server doesn't behave that way.

Look - the guy I replied to kept referring to using ATT instead and he mentioned iPhone so I misunderstood. I HAVE been following this thread...I have also had email with godaddy for over ten years...I am well acquainted with the problems.
Sorry - flu got in the way of clear thinking.

Is anyone able to telnet to the smtp server on port 465?

telnet smtpout.secureserver.net 465

Support asked me to try it. It always hangs for me.

I can telnet successfully on ports 80, 3535, etc., but 465 always hangs. They have not responded to this information yet, but I am wondering if this is normal, or part of the problem.

By the way, I noticed that smtpout.secureserver.net resolves to smtp.starfieldtech.com.

Question for you tech types. I remember a couple of years ago that I had to play w/ the MTU settings on my Belkin router- as receives worked fine, but sends would time out on larger attachments at 95% send--- outlook express and thunderbird were guilty. Think I lowered my setting- and everything worked. Is it possible that the send probs we are all experiencing could be related to MTU? I may tweak some settings to see if it helps.

Also, I wonder- since I haven't seen thousands complaining on the message boards- and GoDaddy has to have a ton of people using hosted email (and, not going through their web i/f) if everyone is experiencing the send problem we are or if these are isolated???

I had the same problem, called godaddy's customer support etc. I could not get it to work. So instead of using godaddy's smtpout.secureserver.net I am using Gmail's smtp server to send my godaddy emails. It works for both Apple Mail and Mail on my iPhone. You will need an [free] account with Gmail. The settings are
servername: smtp.gmail.com
check use: default port
check: Use Secure Sockets
authentication: Password
user name: yourusername@gmail.com
password: yourgmailpassword

I recently signed up with GoDaddy for email. While it seems to be "working", I had to use port 3535 and disable SSL on my outgoing server. (I'm too nervous to switch the outgoing info). Two pointers for setup: 1. when you initially enter your outgoing server information, it spins and spins. I found that if I hit Cancel, retyped the User/Password, then resent, it went through immediately. 2. If you use forget to change the outgoing port initially and your test mail seems to get stuck before Mail has a chance to setup a Sent file where you could delete it, don't panic. It will go eventually, just let it spin (it took mine 10 minutes). The first time, I deleted the Account, closed mail, and it still tried to send. Again, though, it did eventually "go" (from somewhere). I also forwarded this thread to the support person I was working with at GoDaddy, with whom I had a pleasant, yet similar, experience as previous posters. Fingers crossed.