iPhone/iPad can't find mail.messagingengine.com

bplat · 22 May 2012, 04:30 PM

For some reason all of a sudden both my iPhone and iPad can't find mail.messagingengine.com anymore. I thought at first that IMAP was down, but Outlook has no problems. I didn't change a thing on either iPhone or iPad (I can hardly pry the latter out of my kids' hands...) and remove/re-add account doesn't help.

Anyone else seeing this? Better yet, does anyone have a suggestion?

norbs · 22 May 2012, 04:51 PM

Same for me... I just fixed it by tweaking my account settings on my iphone and turning off SSL on incoming mail server.
Working fine now. And it breaks when I turn SSL back on again...

Andy

jofallon · 22 May 2012, 04:53 PM

same for me, just this morning. No settings changed and of course the phone isn't jailbroken. Not shutting off SSL for this change.

Regular Apple mail and Outlook 2011 work the same as always.

thedudester · 22 May 2012, 05:03 PM

Getting a popup "cannot get mail: mail server "mail.messagingengine.com" is not responding, verify account info in Mail settings" now. Last successful update was at 7:53pm HST, which might be related to:
http://status.fastmail.fm/2012/05/21...o-all-servers/ ?
no changes to iphone or ipad in that time, just stopped working.
Saw email about the upcoming changes to SSL:
http://blog.fastmail.fm/2012/05/21/e...l-connections/
and now I can't connect.
All settings are correct, SSL on, correct ports, correct server, all double-checked.

Desktop Mail and web-based all work fine, so not a password thing.

bplat · 22 May 2012, 05:11 PM

Quote:

Originally Posted by norbs

Same for me... I just fixed it by tweaking my account settings on my iphone and turning off SSL on incoming mail server.
Working fine now. And it breaks when I turn SSL back on again...

Andy

Check. Switching off SSL does the trick. A web SSL connection still works fine, so it's just IMAP.

I created a support ticket.

Jose Marques · 22 May 2012, 05:11 PM

Me too. iPhone/iPad on 5.1.1 can't connect to IMAP since around 5AM BST. The devices are running stock software and I haven't changed the settings from their previous working state.

norbs · 22 May 2012, 05:22 PM

For info - fastmail are aware of it and are currenting working on a fix.

norbs · 22 May 2012, 05:24 PM

fixed for me now...

jofallon · 22 May 2012, 05:28 PM

Quote:

Originally Posted by norbs

fixed for me now...

Also for me. I wonder what it was...

brong · 22 May 2012, 05:31 PM

In the best Alanis traditions, it's ironic - doncha' think.

We had reports of the gnutls library complaining "key too short" when connecting to our servers, and decided to switch to 2048 byte DH parameters (a method of calculating session keys more securely).

The problem is, when presented with these supposedly "more secure" key exchange requests, some other clients (IOS devices) didn't cope and aborted! We're not sure why yet, and will do more testing.

Meanwhile, we have backed out the security "improvements". Do please switch back to using SSL.

We will make sure we test our next attempt against IOS first. I'm pretty sure IOS is in the wrong here... but that doesnt' help anyone.

Regards,

Bron.

drew · 22 May 2012, 05:39 PM

Bron much appreciated that you cared about this.
I have not tested but all of my four smartphones are
Android, Do they have same trouble too or only Iphone?

brong · 22 May 2012, 05:45 PM

Not sure actually. I'm not the one who worked on this - I'm just doing the emergency fix - the joy of timezones

I'm in the middle of other tasks, so I'll leave testing it more thoroughly and seeing which option is best for one of the Robs in Australia.

(we have Rob Mueller and Rob Norris now - known as robm and robn - no, it's never confusing, honest)

drew · 22 May 2012, 10:08 PM

Thanks Bron,

no hurry at all. Take it when you feel for it from within.
Or delegate it to someone else or wait for any questions
or complaint. Most likely it just works so just me being curious.

Re names. Robert and Robert shorten to robm and robn

Had you guys lived in USA then maybe one could be Rob and the other Bob?

robmueller · 22 May 2012, 10:09 PM

We've gone back to exactly what we had before, so everything should be working again.

I'm realy annoyed with iOS in this case. Nothing else had a problem with 2048 bit DH key parameters, no idea why iOS did, and searching the Internet doesn't turn up any other reports of problems.

Anyway, I don't intend to make any more changes as there's nothing really to do. 1024 bits is the default and everything seemed to work ok with that (apart from the gnutls issue), 2048 bits breaks iOS which has way more market share.

jofallon · 23 May 2012, 01:00 AM

When the mobile web interface and Apple Mail on my Mac worked fine, I figured it was some iOS limitation. They probably saved a few bytes of space by not including something. Thanks for fixing this so quickly!

22 May 2012, 04:30 PM	#1
bplat Cornerstone of the Community Join Date: Apr 2003 Location: Netherlands Posts: 507	iPhone/iPad can't find mail.messagingengine.com For some reason all of a sudden both my iPhone and iPad can't find mail.messagingengine.com anymore. I thought at first that IMAP was down, but Outlook has no problems. I didn't change a thing on either iPhone or iPad (I can hardly pry the latter out of my kids' hands...) and remove/re-add account doesn't help. Anyone else seeing this? Better yet, does anyone have a suggestion?

22 May 2012, 04:53 PM	#3
jofallon Junior Member Join Date: Nov 2007 Posts: 26	iphone settings same for me, just this morning. No settings changed and of course the phone isn't jailbroken. Not shutting off SSL for this change. Regular Apple mail and Outlook 2011 work the same as always.

22 May 2012, 05:03 PM	#4
thedudester Junior Member Join Date: May 2012 Posts: 1	same problem: iphone and ipad no longer working Getting a popup "cannot get mail: mail server "mail.messagingengine.com" is not responding, verify account info in Mail settings" now. Last successful update was at 7:53pm HST, which might be related to: http://status.fastmail.fm/2012/05/21...o-all-servers/ ? no changes to iphone or ipad in that time, just stopped working. Saw email about the upcoming changes to SSL: http://blog.fastmail.fm/2012/05/21/e...l-connections/ and now I can't connect. All settings are correct, SSL on, correct ports, correct server, all double-checked. Desktop Mail and web-based all work fine, so not a password thing.

22 May 2012, 04:51 PM	#2
norbs Essential Contributor Join Date: May 2002 Location: UK Posts: 435	Same for me... I just fixed it by tweaking my account settings on my iphone and turning off SSL on incoming mail server. Working fine now. And it breaks when I turn SSL back on again... Andy

22 May 2012, 05:11 PM	#6
Jose Marques Junior Member Join Date: Aug 2010 Posts: 4	Me too. iPhone/iPad on 5.1.1 can't connect to IMAP since around 5AM BST. The devices are running stock software and I haven't changed the settings from their previous working state.

22 May 2012, 05:22 PM	#7
norbs Essential Contributor Join Date: May 2002 Location: UK Posts: 435	For info - fastmail are aware of it and are currenting working on a fix.

22 May 2012, 05:24 PM	#8
norbs Essential Contributor Join Date: May 2002 Location: UK Posts: 435	fixed for me now...

22 May 2012, 05:31 PM	#10
brong The "e" in e-mail Join Date: Jul 2004 Location: Melbourne, Australia Posts: 2,696 Representative of: Fastmail.fm	In the best Alanis traditions, it's ironic - doncha' think. We had reports of the gnutls library complaining "key too short" when connecting to our servers, and decided to switch to 2048 byte DH parameters (a method of calculating session keys more securely). The problem is, when presented with these supposedly "more secure" key exchange requests, some other clients (IOS devices) didn't cope and aborted! We're not sure why yet, and will do more testing. Meanwhile, we have backed out the security "improvements". Do please switch back to using SSL. We will make sure we test our next attempt against IOS first. I'm pretty sure IOS is in the wrong here... but that doesnt' help anyone. Regards, Bron.

22 May 2012, 05:39 PM	#11
drew The "e" in e-mail Join Date: Jan 2006 Posts: 2,626	Bron much appreciated that you cared about this. I have not tested but all of my four smartphones are Android, Do they have same trouble too or only Iphone?

22 May 2012, 05:45 PM	#12
brong The "e" in e-mail Join Date: Jul 2004 Location: Melbourne, Australia Posts: 2,696 Representative of: Fastmail.fm	Not sure actually. I'm not the one who worked on this - I'm just doing the emergency fix - the joy of timezones I'm in the middle of other tasks, so I'll leave testing it more thoroughly and seeing which option is best for one of the Robs in Australia. (we have Rob Mueller and Rob Norris now - known as robm and robn - no, it's never confusing, honest)

22 May 2012, 10:08 PM	#13
drew The "e" in e-mail Join Date: Jan 2006 Posts: 2,626	Thanks Bron, no hurry at all. Take it when you feel for it from within. Or delegate it to someone else or wait for any questions or complaint. Most likely it just works so just me being curious. Re names. Robert and Robert shorten to robm and robn Had you guys lived in USA then maybe one could be Rob and the other Bob?

22 May 2012, 10:09 PM	#14
robmueller Intergalactic Postmaster Join Date: Oct 2001 Location: Melbourne, Australia Posts: 6,102 Representative of: Fastmail.FM	We've gone back to exactly what we had before, so everything should be working again. I'm realy annoyed with iOS in this case. Nothing else had a problem with 2048 bit DH key parameters, no idea why iOS did, and searching the Internet doesn't turn up any other reports of problems. Anyway, I don't intend to make any more changes as there's nothing really to do. 1024 bits is the default and everything seemed to work ok with that (apart from the gnutls issue), 2048 bits breaks iOS which has way more market share.

23 May 2012, 01:00 AM	#15
jofallon Junior Member Join Date: Nov 2007 Posts: 26	When the mobile web interface and Apple Mail on my Mac worked fine, I figured it was some iOS limitation. They probably saved a few bytes of space by not including something. Thanks for fixing this so quickly!