Choose your cart
Choose your cart
Receive up to $504 promo credit ($180 w/Welcome Unlimited, $360 w/ 5G Start, or $504 w/5G Do More, 5G Play More, 5G Get More or One Unlimited for iPhone plan (Welcome Unlimited and One Unlimited for iPhone plans can't be mixed w/other Unlimited plans; all lines on the account req'd on respective plans)) when you add a new smartphone line with your own 4G/5G smartphone on an eligible postpaid plan between 2/10/23 and 4/5/23. Promo credit applied over 36 months; promo credits end if eligibility requirements are no longer met.
$699.99 (128 GB only) device payment purchase or full retail purchase w/ new smartphone line on One Unlimited for iPhone (all lines on account req'd on plan), 5G Start, 5G Do More, 5G Play More or 5G Get More plan req'd. Less $699.99 promo credit applied over 36 mos.; promo credit ends if eligibility req’s are no longer met; 0% APR.
When changing account settings to use Verizon's new secure email settings, my iPhone keeps giving error " Can not get Mail, the mail server incoming.verizon.net is not responding.
I am using port 995 with SSL as instructed. Switching back to the standard port 110 with no SSL works fine.
Outgoing works fine with port 465 and SSL.
Also, same secure settings on Outlook 2010 work perfectly fine.
Anyone having this issue?
Solved! Go to Correct Answer
@gusverde wrote:When changing account settings to use Verizon's new secure email settings, my iPhone keeps giving error " Can not get Mail, the mail server incoming.verizon.net is not responding.
I am using port 995 with SSL as instructed. Switching back to the standard port 110 with no SSL works fine.
Outgoing works fine with port 465 and SSL.
Also, same secure settings on Outlook 2010 work perfectly fine.
Anyone having this issue?
A few other people have posted that after making the changes they had to reboot their iPhone/iPad in order for it to connect again. Have you tried restarting?
@gusverde wrote:When changing account settings to use Verizon's new secure email settings, my iPhone keeps giving error " Can not get Mail, the mail server incoming.verizon.net is not responding.
I am using port 995 with SSL as instructed. Switching back to the standard port 110 with no SSL works fine.
Outgoing works fine with port 465 and SSL.
Also, same secure settings on Outlook 2010 work perfectly fine.
Anyone having this issue?
A few other people have posted that after making the changes they had to reboot their iPhone/iPad in order for it to connect again. Have you tried restarting?
That was it !.
Thank you so much.
Gus
Greetings. I had the same thing happen to me as well. After setting the incoming port to 995 SSL, I was unable to receive incoming messages on my iPhone 4S. I tried resetting and at first it did not work. I then re-verified my e-mail settings, closed all of my open apps (incoming the Mail app) and then re-started the phone again. Now the phone is receiving incoming messages using 995 SSL.
My iphone4s does not give me the option to edit incoming mail server port number, it does for outgoing server???
When you open your account, drag you screen up and find "Advanced". That is where you will find your port and SSL settings for your incoming.
I have the same problem with my iPad. It worked the first time and now it does not. I get the same message as in other posts about the iPhone.
Last week, my wife and I noticed that we were no longer receiving messages on our iPhones and iPad. Email on our laptop works fine.
After several calls to the Verizon tech support, deleting the account, setting it up again with server and port information as provided by the rep, we can receive messages, but we've lost all our personal folders.
Also, whereas before, a message sent from one device would show up - sync - with the other devices, now that no longer happens.
I called Apple, and the rep there said it's a Verizon issue, not an Apple-device related issue.
Anyone have any suggestions?
Thanks.
PS Two separate Verizon reps said that they've been experiencing various problems with Verizon email for a couple of months now, but didn't have any idea of when/if they'd be resolved.