Is it possible to configure Smartermail autodiscover to prefer POP but allow IMAP?

I propose a +1 for a feature request for autodiscover to support the preference of POP over IMAP (or vice versa) on a per domain / per mailbox basis. 

 

I've added this as a reply to thread so it can be voted up if others are interested.

 

Would also be nice if we had the option to eliminate POP altogether.

 

We have only 1 user who still uses POP, and he forwards all of his e-mail to an AO:L account.   When he gets spam, he sometimes blocks the forwarding account and that causes all kinds of headaches.

 

I know, tell him not to block his SmarterMail domain account, but he doesn't remember that - he's 82 years old, and does contextual analysis.  Very well respected,and literate with the written word, but not tech savvy at all.   Fortunately, I've known him for many years and have access to his AOL account, so I can go unblock (mark as NOT SPAM) what he gets wrong.

 

Additionally, we've eliminated plain text authentication for user's clients.  We're 100% TLS now, from client to SmarterMail and, when the connections support it, to other MX servers as well.  That was a simple check box in the SMTP IN configuration:

 

We notified our hosted clients six months in advance of the implementation, giving them the option to make the changes at their convenience.  We repeated the notification at 3 months, 2 months, and 1 month.

Two weeks out, we reminded them that, as of a given date, anyone not connecting via a TLS encrypted connection would not be able to use their MX client to connect to our SmarterMail server.   When the actual date arrived, we had only a handful of subscribers who could not connect, and their situation was easily resolved.

Hi Bruce,

 

Welcome back to the SmarterMail community!  I've been working with the SmarterMail dev team on tweaks to the SMTP In Autodiscover settings and they've added an "Encryption" dropdown to choose either "None", "TLS", or "SSL", which is working great.

 

My question to you, since you know way more about this stuff than most people, is what *should* be used for SMTP in.  My network guys have suggested that for SMTP In, using SSL on 465 is no longer recommended best practice and instead should be TLS on 587.  So that's what we've setup and again with the changes SmarterMail made a couple weeks ago this works perfectly.  What's your opinion on this?

 

Shaun