TLS-RPT Settings
The TLS-RPT settings page will show options available for TLS-RPT & MTA-STS configuration. To enable MTA-STS/TLS, you need to implement both TLS-RPT and MTA-STS. Note that TLS-RPT and MTA-STS require multiple record verifications due to the requirements of the RFCs.
TLS-RPT Reporting
Additional TLS-RPT Recipients
You can add additional TLS-RPT recipients by clicking the 'Reports will be Sent To' option. This allows you to specify multiple email addresses that should receive TLS-RPT reports.
MTA-STS Record & Policy Hosting
Policy Enforcement Level
The policy of MTA-STS can be configured by changing the MTA-STS Enforcement Level:
| Level | Description |
|---|---|
| None | No enforcement of TLS for email transport. |
| In Testing | Default (Recommended) - Monitors TLS usage without enforcing it. |
| Enforced | Enforces TLS for email transport, blocking emails that do not meet the TLS requirements. |
MX Servers
This section displays where the MX records for your domain are currently located. This information is crucial for proper MTA-STS configuration.
Related Topics
Read more on TLS-RPT
- What is TLS-RPT? - Introduction to TLS-RPT and its purpose
- How Does TLS-RPT Work? - Technical details about TLS-RPT operation
- Why is TLS-RPT Important? - Benefits and significance of TLS-RPT
- How Does MTA-STS/TLS Work with DMARC? - Integration with DMARC
- TLS-RPT Reporting - Understanding TLS-RPT reporting
- TLS-RPT Domain Settings - Configure TLS-RPT Settings
- TLS-RPT Domain Report - Understanding TLS-RPT report interface