Unipark Email Compliance Guide

1. Introduction

Unipark enforces strict DMARC, SPF, and DKIM policies to enhance email security, prevent spoofing, and ensure reliable email delivery. These policies align with European Union regulations and industry best practices to reduce phishing risks and unauthorized email use.

This guide provides essential instructions for users and institutional IT teams to comply with Unipark’s email authentication policies. Institutions should not assume that making these changes without consulting Unipark Support will work correctly, as Unipark must also update SPF records in AWS SES to authorize the institution’s domain as a valid sending domain.


2. Why Compliance is Required

Many email providers and institutions reject emails that do not adhere to SPF, DKIM, and DMARC policies. To ensure users can send and receive email notifications, surveys, and responses through Unipark, institutions must configure their email domains correctly and coordinate with Unipark Support for SPF validation in AWS SES.


3. Understanding DMARC, SPF, and DKIM


A. SPF (Sender Policy Framework)

SPF prevents unauthorized email senders from impersonating a domain. Institutions must add Unipark’s SPF record to their DNS settings and notify Unipark Support so we can update AWS SES.

Required SPF Record:

v=spf1 include:_spf.unipark.com ~all


B. DKIM (DomainKeys Identified Mail)

DKIM ensures emails sent via Unipark are authenticated with a cryptographic signature.


C. DMARC (Domain-based Message Authentication, Reporting & Conformance)

DMARC builds upon SPF and DKIM to enforce email authentication policies and generate reports on unauthorized email use.

Recommended DMARC Policy:

v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@unipark.com


4. How Institutions Can Enable Compliance

  • Step 1: Check Current DNS Settings
    IT teams should verify existing SPF, DKIM, and DMARC records using tools such as:
    – MXToolbox (https://mxtoolbox.com/)
    – Google Admin Toolbox (https://toolbox.googleapps.com/)
  • Step 2: Request the Zone File from Unipark Support
  • Step 3: Add Unipark’s SPF & DKIM Records
  • Step 4: Coordinate with Unipark Support for AWS SES Validation
  • Step 5: Test Email Delivery


5. What Users Should Do

Users must ensure their institution supports DMARC compliance and must contact their IT department to request updates.


6. Alternative Solutions for Non-Compliant Institutions

If your institution refuses to implement Unipark’s email security policies, consider:

  1. 1. Using an alternative private domain email.
  2. 2. Registering with an email service provider that supports DMARC.
  3. 3. Manually exporting and importing survey responses within Unipark.


7. Conclusion

Unipark’s email security policies protect users from spoofing and improve email reliability. Institutional IT teams must configure SPF, DKIM, and DMARC records, request the Zone file from Unipark Support, and confirm changes with Unipark Support to allow seamless email communication with Unipark.

For further support, contact Unipark Support via:

🌍 Website: https://www.unipark.com/en/support/