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

[jcardinal]

I am using Outlook 2016 on Win7 SP1. I am unable to use SMTP with the updated FutureQuest mail server. I can use SMTP with legacy-tls.futurequest.net.

I followed the instructions to enable TLS 1.2 by following the directions here:

https://blogs.technet.microsoft.com/...-on-windows-7/

... but after installing the patch and modifying the registry as directed, Outlook 2016 still refuses to connect to the updated FutureQuest mail server.

Has anyone with this combination (Win7 SP1 / Outlook 2016) succeeded in configuring the OS and email client properly?

[Tom]

My sister with iOS 9.3.4 followed the instructions and can receive but not send on her iPhone. Related to the TLS or something else?

[Bob]

Hello Tom,

Originally Posted by Tom

My sister with iOS 9.3.4 followed the instructions and can receive but not send on her iPhone. Related to the TLS or something else?

Yes most likely related...

She would to set her outgoing server to the same legacy-tls.FutureQuest.net server and make sure she has SSL set as well as for Authentication: Password set.

-Bob

[richpee]

I'm a little behind the curve and just now figuring out why my email's been acting weird.

I found the futurequest email from December. I changed some settings. I am now able to send (mac mail program, macbook air, OS 10.9.5; mail v7.3 ... on my testing computer, macbook air).

I am able to receive, it looks like, but unable to send. I receive this:

Cannot send message using the server [server name]
The sender address [user]@[domain].com was rejected by the server legacy-tls.futurequest.net.

The server response was: Unknown command, authenticate first

Select a different outgoing mail server from the list below or click Try Later to leave the message in your Outbox until it can be sent.

my settings are:
description: [user]@[domain].com
email address: [user]@[domain].com
full name: [user]@[domain].com
incoming server: legacy-tls.futurequest.net
user name: [user]@[domain].com
password: (painstakingly reset and rechecked)
outgoing mail server (SMTP): legacy-tls.futurequest.net

What am I missing?

___
I want to make sure this is working on the one device before I tackle things like routing through gmail (chrome for macbook air) and gmail (iOS app). Hopefully figuring out the one will inform the rest of my actions.

[Bob]

I am now able to send (mac mail program, macbook air, OS 10.9.5; mail v7.3 ... on my testing computer, macbook air).

Is the problem on another device?

One setting I have seen mised is in your SMTP settings make sure you have "Use SSL" selected. It should be under advanced settings.

-Bob

[richpee]

OK, that wasn't the problem; SSL was already selected, but I appear to have solved it, with your guidance.

I went to

--> Edit SMTP server list,
-->Advanced
and there are two options:
-->-->"Use default ports 25, 465, 587"
and
-->--> "use custom port"

I changed from "default" which included the "465" proscribed, to "custom port" and typed in 465 manually.

With this success, I am confident I can move mountains (reconfigure the rest). I hope I don't come back, eating my words.

[Bob]

Good Deal

-Bob