Compliance built into every send.
Mailbox providers now reject mail that isn't authenticated, and regulators expect proof of consent. MailEnv makes the right way to send the default, so your critical email keeps arriving and holds up when someone asks questions.
Gmail, Yahoo, and Microsoft changed the rules. You're covered.
Since February 2024, Gmail and Yahoo require bulk senders to authenticate their mail and keep spam complaints low. Microsoft followed in 2025 for Outlook.com. Mail that falls short is filtered or rejected.
| Requirement | What providers expect | How MailEnv handles it |
|---|---|---|
| SPF & DKIM | Mail authenticated with both SPF and DKIM. | Both are configured on your domain during onboarding and checked before you go live. |
| DMARC | A published DMARC policy, with the From domain aligned to SPF or DKIM. | We help you publish DMARC and confirm alignment, then move toward enforcement when you're ready. |
| Low spam rate | Gmail says to stay below 0.1% and never reach 0.3%. | Complaint rates are monitored, and sending is throttled or paused before thresholds are reached. |
| Easy unsubscribe | Unsubscribes honored quickly, with one-click unsubscribe for subscribed mail. | Unsubscribes and complaints are suppressed automatically across every future send. |
| Valid DNS & TLS | Sending IPs with valid reverse DNS, and mail sent over TLS. | Delivered on Amazon SES infrastructure, with TLS used whenever the receiving server supports it. |
Tools that help you meet your legal obligations.
Anti-spam and privacy laws put the responsibility on the sender. MailEnv gives you the controls and records to meet it.
CAN-SPAM
Unsubscribes honored and suppressed automatically. Sender identity is authenticated on your own domain.
CASL
Double opt-in and timestamped consent records give you evidence of express consent for marketing.
GDPR
Message data kept only as long as needed. Clear terms for how recipient data is processed and retained.
SES policies
Bounce and complaint limits enforced for you, so your sending stays within Amazon's acceptable use rules.
Built so the safe path is the default.
Vetted senders
Every account is reviewed before it can send. No anonymous signups and no cold-outreach operations sharing your infrastructure.
Consent records
Double opt-in confirmations are logged with timestamps, so you can show when and how each subscriber agreed.
Quarantined imports
Uploaded lists can't be sent to until they're verified. Purchased, rented, and scraped lists aren't allowed.
Global suppression
Bounces, complaints, and unsubscribes are blocked across every send, every stream, and every integration.
Delivery history
A per-message event trail of accepted, delivered, bounced, and complained, for support tickets and audits.
Isolated environments
Dedicated plans run on private IPs and isolated infrastructure for teams with stricter requirements.
Who handles what.
Compliance is shared between you and us. Here's where the line is.
MailEnv handles
- Domain authentication setup and monitoring
- Bounce, complaint, and unsubscribe suppression
- List verification and import quarantine
- Throttling and pauses before provider limits
- Sender vetting and abuse enforcement
You handle
- Collecting valid consent for marketing email
- Accurate sender identity and message content
- A physical address and unsubscribe link where the law requires them
- Industry rules that apply to your data, such as healthcare or finance
- Following our acceptable use policy
This page is general information about MailEnv's features and isn't legal advice. Talk to your own counsel about the obligations that apply to your business.
Going through a vendor review?
Tell us what your security or compliance team needs to know. We'll walk you through how MailEnv handles your data and your domain.