Non-Authenticated SMTP and

Starting September 16th, will require all users authenticate using their username and password to send mail even when directly connected to our network.  This is the default configuration for most mail clients and will only affect a small group of users.  This change makes it easier for us to track and prevent spam from being sent using our mail infrastructure.  -Kelsey and Grant

9 comments for “Non-Authenticated SMTP and

  1. Michael, sorry, I can’t provide any specific help with Exchange but based on a minute with google I think you’ll need to enable SMTP Authentication for the “send connector” you have configured using the EMC.

  2. Do you mean that anytime I send an email from my account I’ll have to put in my user name and password even from within the account that I’ve already entered that info to get there? Instead of just going to compose to send one or reply from an email I’ve recieved? I do hope not. I know spammers must mess with the system but I don’t need to suffer for their bad behavior.

  3. We all suffer from spammers bad behavior. You haven’t said what mail client you are using but this is typically a one-time configuration thing unless you’ve configured your client to not save your passwords.

  4. If you use one of our webmail clients, this change has no affect since the webmail client is already authenticating on your behalf when it sends mail.

  5. Now that you’re requiring SMTP authentication, could you tell us which ports accept TLS connections, and which ones allow upgrading from cleartext to TLS using STARTTLS? I don’t see this information on the wiki’s quick reference.

  6. Forest, you can use the standard ports of 465 or 587 depending on your client and needs. Some people feel that using 465 and implicit ssl is more secure.

Leave a Reply

Your email address will not be published. Required fields are marked *