Quite simply, it's a lot easier to explain to users, "You must check
your mail before you send mail" than to take them through some of the
setups needed for the more secure, modern alternatives. Once they have
their configuration to receive mail, they're "set" for sending it
while on the road, or while on other dynamic IP lines.
Just because the technology has advanced does not mean that all users
have.
You hit the nail on the head in your very first point - it is *easier* -
but easier for *who*? The *sys* *admin*.
So, it is a matter of a lazy sys admin, nothing more.
How hard is it to write up instuctions for the user to switch to a
secure auth model for your critical business email systems?
Lazy, lazy, lazy...
I force my users to use strong passwords - 15 characters, no dictionary
words, must contain letters, numbers and special characters (at least
4)... they yelled - for about 5 minutes, then just accepted it.
Write up instructions for them on how to save the password in their
email client or web browser, so they only have to enter it once.
Every quarter they have to change it. Haven't heard one complaint.
It's simply a matter of explaining to them why it is necessary - do they
want their email to be secure, or not?
--
Best regards,
Charles
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
