- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I searched and searched and called support for both Verizon and GoDaddy. Nobody could help me. Verizon even refused to escalate my issue because my issue was a "MS Outlook configuration issue." NOT TRUE.
This is what I had to do.
Add a new POP account to MS Outlook. (or modify if it already exists)
I used my GoDaddy e-mail address
For POP, I used my GoDaddy e-mail address and password
For POP server, I used pop.secureserver.net (GoDaddy's server) on port 110 (no SSL)
For SMTP server, I used outgoing.yahoo.verizon.net on port 587 (no SSL)
For SMTP authentication, I used my xxxxxxxx(at)verizon.net e-mail account. I am on Verizon FIOS and get e-mail accounts through that. So, I registered a new account...not fun, but manageable. The verizon web site is really bad.
==========
The FIX...I had to log onto the xxxxxxxx(at)verizon.net e-mail account via the WEBMAIL version for Verizon.
I then went to Options-->More Options on the top, right menu.
Go to the Accounts menu on the left.
Click Add Account button toward the top.
I only entered information for Sending Mail.
Account name (any name you like...I called it GoDaddy)
From Name = my display name
e-mail address = my GoDaddy e-mail address
I then moved my cursor to the username field in the Receiving Mail just so my cursor wasn't in the e-mail address field anymore.
Verizon couldn't even help me with this. This should be a standard check for them whenever they receive a call for SMTP issues. I think they are trying to get everyone to use their (at)verizon.net e-mail account as their primary account. This will help them retain or gain future business. I think it's bad for business overall.
==========
Note the "Test Account Settings..." button failed on the test send of a message, but all other tests passed fine. My messages are sent fine even with this part of the tests failing.
Solved! Go to Correct Answer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
godaddy accounts sometimes like port 80 vs 587 as well. just to piggy back on your thread.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
godaddy accounts sometimes like port 80 vs 587 as well. just to piggy back on your thread.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes. I saw that you can use ports (for GoDaddy SMTP): 25, 80, 3535, or 587 (non SSL) and 465 for SSL
I believe 25 and 587 would have worked once I did what I posted, but I left it at 587 because it worked and I stopped at that point. The behavior was the same for the "Test Account Settings..." for both 25 and 587..it failed to send the test message, but e-mail still went through (for 587 at least). I think 587 is more likely be left alone...when compared to port 25...from a Verizon acceptance perspective.
Ports 80, 3535, and 465 did not work for me at all.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
...just to follow-up...
I was able to configure my wife's laptop to use port 25.
So, I have one set to port 25 and one set to 587
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So I was very exceptical about this solution, sending your email using a different provider???, BUT IT WORKS
It even updated my goddady email folder in godaddy site ( BTW i dont know how it does that )
Thank you
ALL HAIL TO VERIZON for wanting to take over the email world... boozos forcing us to use their systems.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Why is the outgoing server outgoing.yahoo.verizon.net? You said "For SMTP server, I used outgoing.yahoo.verizon.net on port 587 (no SSL)"
What does this have to do with yahoo? Is this an error??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oh my word! I literally worked on setting up Outlook 7 for 12 straight hours yesterday. I found a ton of people with the same issue (enter network password), but could not seem to find a solution. The closest I came was someone who ended up having to delete their yahoo accessibility which means they lost all of their email. Thankfully, the incoming.yahoo.verizon.net WORKED!!! I can not believe that something that is suppose to make our lives easier took this much work. I'm glad I found this post. Thank you!
