If your outbound email bounces with MinimumTlsRequirementNotMetError: Expected at least TLS1_2 but got TLS_NONE (or an inbound sender receives 530 5.7.1 Recipient requires higher TLS security than was negotiated), your account is configured to require a minimum TLS encryption version that the remote mail server did not meet.
Why Did This Happen?
Purelymail allows accounts to enforce minimum TLS versions for both incoming and outgoing mail (new accounts default to TLS 1.2). When enabled, our servers refuse to transmit or accept messages over unencrypted plain text or older TLS versions. If an external mail server does not support TLS (or only supports an older protocol), Purelymail aborts the connection rather than downgrading security.
How to Fix
If you need to exchange email with a legacy mail server that does not support modern TLS:
- Log into the Account Admin portal at purelymail.com/manage/login.
- Go to the Settings tab (purelymail.com/manage/account) in the left navigation sidebar.
- Locate the TLS Delivery Enforcement section (see Account Settings & Security Policies).
- Under When sending mail, require:, change the dropdown to No encryption (or lower When receiving mail, require: if an incoming server is being rejected).
- Click Save changes.
- Resend the bounced email.
Still Need Help?
If you've followed these steps and are still running into trouble, check our Purelymail Support guide.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article