Account Settings & Security Policies

Created by Curtis Hammock, Modified on Sun, 15 Nov at 7:22 PM by Curtis Hammock

The Settings page (purelymail.com/manage/account) in your Account Admin portal contains administrative configurations that apply across all users, mailboxes, and domains on your account.


1. Sending Restrictions (Send-As Policies)

  • By default, sending restrictions are off (Let users send from whoever they want), meaning users on your account can send outbound email from any address on domains owned by your account.
  • Under Settings > Sending Restrictions, selecting Restrict who users can send as lets administrators create Send As Policies to limit which specific users or addresses can send as other user handles or domains across the account.
  • Sending as unowned third-party domains (such as @gmail.com) is always blocked to protect server deliverability. If a user attempts to send from an unauthorized address, Purelymail rejects the message with a 530 5.7.1 or 503 5.7.1 error. See Error: 530 5.7.1 "You are not authorized to send mail as...".

2. TLS Delivery Enforcement

Under Settings > TLS Delivery Enforcement, you can separately configure minimum TLS requirements for When receiving mail, require: and When sending mail, require::

  • Available Options: No encryption, TLS 1.0, TLS 1.1, TLS 1.2 (default on new accounts), and TLS 1.3.
  • No encryption (Opportunistic TLS): Attempts encrypted TLS delivery first, but falls back to unencrypted SMTP if the remote server does not support TLS.
  • TLS 1.0 / TLS 1.1 / TLS 1.2 / TLS 1.3: Emails will only be sent or accepted if the remote server establishes an encrypted connection at or above the selected TLS version.
    • If a remote server lacks TLS or only supports an older version during outbound delivery, Purelymail aborts delivery and returns a bounce notice with MinimumTlsRequirementNotMetError.
    • If an inbound server attempts to deliver mail below your minimum receiving TLS setting, Purelymail rejects the connection with 530 5.7.1 Recipient requires higher TLS security than was negotiated.
    • See Error: MinimumTlsRequirementNotMetError for troubleshooting steps.

3. DMARC Enforcement on Incoming Mail

  • By default, Purelymail enforces the sender's published DMARC policy (p=reject or p=quarantine) on incoming mail.
  • If you route incoming mail through an external spam filter, university forwarder, or mailing list that relays messages without SRS rewriting and triggers false DMARC rejections, you can uncheck DMARC Enforcement on Incoming Mail under Settings. See Using External MX Spam Filtering Services.

4. API Key

  • Generate or regenerate your programmatic REST API token under Settings > API Key to automate user provisioning, routing updates, or domain checks.
  • Full endpoint documentation and OpenAPI specifications are available at purelymail.com/docs/api.

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

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article