Security Updates Being Made to Improve Deliverability of ÐÇ¿Õ´«Ã½ Emails

On August 1, [U]Tech will make necessary security changes to which will improve deliverability of authentic mail. The change involves removing the legacy authentication of all email flowing through the ÐÇ¿Õ´«Ã½ mail system via by no longer automatically applying a DKIM signature. DKIM (DomainKeys Identified Mail) is a standard email authentication method that adds a digital signature to outgoing messages.

Email clients and applications that have their SMTP service still configured to use will no longer benefit from having their email authenticated by default through the ÐÇ¿Õ´«Ã½ mail system servers. Industry-wide, it is now expected that every system sending for a given email address is properly authenticating those messages to ensure their integrity and is not being impersonated.

If you are using your ÐÇ¿Õ´«Ã½ NetID with an email client besides webmail, it is recommended that you follow the suggestions as outlined on item #6 on the Google Mail Authentication Change FAQ | University Technology webpage to configure the client’s SMTP settings. If you have already made the recommended change, or are using ÐÇ¿Õ´«Ã½ , there is nothing further you need to do.

Third-party vendors who are configured to use to send email are expected to provide their own email authentication after August 1 to ensure deliverability. If you have contracted with a third-party vendor and have not already done so, please follow the recommendations as outlined on the Google Mail Authentication Change FAQ | University Technology webpage to ensure your vendor is properly configured to send mail on behalf of ÐÇ¿Õ´«Ã½.

For assistance with any technology product or service at ÐÇ¿Õ´«Ã½, contact the University Technology Service Desk at help@case.edu, 216.368.HELP (4357) or visit .