Jan 16, 2025
UNI will be enabling the "reject" policy for DMARC
UNI will be enabling the "reject" policy for DMARC (Domain-based Message Authentication, Reporting & Conformance) on January 30th, 2025.
When the reject policy is in place, any email sent from a third-party service, using a @uni.edu email address, will be rejected by the recipient's email server. This means that the email will not be delivered to the intended recipient. It may or may not bounce back to the sender with a notification of the rejection. This policy helps to prevent email spoofing and phishing attacks, thereby enhancing the security and integrity of the university's email communications.
For users at UNI, this means that we need to ensure that any third-party email service that we are using are set to either use the service provided email address (possibly with a uni.edu reply-to) or we have set up and configured an (example).uni.edu subdomain. If this is not done, emails will fail DMARC checks and will not reach their recipients. Only officially supported and IT reviewed products will be allowed to use subdomains.
UNI Information Technology has been working diligently with campus users to correct DMARC issues that have been reported in our DMARC monitoring tool.
If you have any questions or need further assistance, please submit a service hub ticket.
When the reject policy is in place, any email sent from a third-party service, using a @uni.edu email address, will be rejected by the recipient's email server. This means that the email will not be delivered to the intended recipient. It may or may not bounce back to the sender with a notification of the rejection. This policy helps to prevent email spoofing and phishing attacks, thereby enhancing the security and integrity of the university's email communications.
For users at UNI, this means that we need to ensure that any third-party email service that we are using are set to either use the service provided email address (possibly with a uni.edu reply-to) or we have set up and configured an (example).uni.edu subdomain. If this is not done, emails will fail DMARC checks and will not reach their recipients. Only officially supported and IT reviewed products will be allowed to use subdomains.
UNI Information Technology has been working diligently with campus users to correct DMARC issues that have been reported in our DMARC monitoring tool.
If you have any questions or need further assistance, please submit a service hub ticket.
Any updates to this announcement will be located here: