[FQuest Alert] Removal of DES/3DES Encryption Support

[Syneryder]

In case it helps others, I think I've had a related problem with outgoing email from my Nexus 5 phone using the Gmail app. Since about 23 September it's been silently queuing outgoing email without actually sending it. Incoming was still working though, which is why I didn't notice.

I was finally able to resolve it by using the legacy-tls.futurequest.net settings, but the real key was to completely delete the IMAP account from the phone and set it up again. (The catch is that this also deletes any queued outgoing email.) Another option is to install Microsoft Outlook on the Nexus 5, which seems to work well too.

On the desktop on my Mac, Postbox has been working perfectly the whole time. (It's a commercial app derived from Thunderbird, which is probably why it's been fine all along.)

[Bob]

As of 1:00 PM ET today Dec 06, 2016 DES/3DES and TLS 1.0 Support has been removed from Mail Services.

-Bob

[Bob]

We have had a number of Apple users that are having issues with changing their Mail Server names as the box is Greyed out.

It appears you have to First disable a setting in your Advanced Settings:

"Select the Advanced Tab, uncheck the box to “Automatically detect and maintain account settings”, save change."

Then Go back into Preferences > Accounts, and you should be able to update the Incoming Mail Server.

-Bob

[hobbes]

I did not change the settings on my iPhone and have not noticed any issues. Could settings have somehow been cached, or does this point to latest iOS actually removing old algos?

[Bob]

That would seem to indicate that the latest iOS supporting TLS 1.2...

-Bob

[jestaguy]

Looks like my IOS devices on IOS 10.1 are running great. With Apple Mail in Sierra, I'm getting an error when attempting to manually enter the server information for IMAP (port 993 & 465 respectively for SSL):

The identity of "pop.xxxxxx.com" cannot be verified. The certificate for this server is invalid.

(I get the same error for mail.xxxxxxxx.com as well for the SMTP.) The only way I can save the profile is to allow Apple Mail to "Automatically manage connection settings". Though as near as I can tell, this simply disables the SSL settings behind the scenes. I don't think this is necessarily related to the current server changes--I'm assuming this has more to do with the certificate mismatch. Though in this case, there's no opportunity to accept the mismatch. Mail won't save account profile.

Anyone else seeing this?

*Update*
I just tried the legacy server with SSL and didn't get any errors. Looks like Sierra mail won't allow you to have a certificate mismatch and keep custom settings. Am I missing something? Seems pretty nuts.

Thanks,
jesta

[Bob]

It appears that Outlook under Windows 7 is also unable to use TLS 1.2 and those users would need to use the legacy-tls.FutureQuest host name for secure mail.

-Bob

[artemis]

thank you the info about how to fix the grey-out out box was Very Helpful -- was just able to help a client with Mail (and I am not a Mac user)

re eventually discontinuing this - I have a half dozen approx. that have needed to change their settings - mostly Mac users but not all. I need to use the new settings with Outlook 2007 in order for SSL to work. When testing ahead of time I only did one account of each type, and deliberately left the others so I could 'fully experience' the change .

thanks again for making this as painless as possible

[jamesm]

A trivial and likely simple question. Anyone have any tips of how Postbox should be set up - particularly ports? I can receive but can't send. Thanks.

[artemis]

re Mac Mail

in addition to the issue with the grayed out boxes (which on some systems depending on os version and mail version I think) which are grayed out for the pop server and on some are for the smtp servers (but never both so far), and which require having user find two different advanced tabs (I am supporting this via phone without seeing screens so can't be too specific) there is also a problematic setting for some mail users for smtp -- one of mine people had to specifically select "custom port" and enter the port #

just a heads up in case it helps someone else