Domain ownership verification
Receiving and sending activate only after the domain owner publishes the required verification records.
Security by design
Email handled like infrastructure.
Visible, restricted, recoverable.
MailerZ limits receiving and sending to verified domains and approved identities, records delivery outcomes, and keeps failure handling explicit instead of invisible.
TLS transport No open relay Restricted message access Operational audit trail
Layered controls
Reduce avoidable email-delivery risk.
Security covers domain authorization, SMTP identity, message acceptance, forwarding behavior, and access to operational records.
Authenticated SMTP
Outbound connections require credentials and remain limited to the verified identities allowed for that account.
No open-relay behavior
Unknown users cannot use MailerZ to send arbitrary mail through domains they do not control.
Store before acceptance
MailerZ records incoming content and metadata before returning SMTP 250 to the sending server.
Restricted operational access
Message access and important account activity are limited and recorded for investigation and recovery.
DNS health visibility
Misconfigured, incomplete, or conflicting records are surfaced so weak setup does not stay hidden.
Security lifecycle
Trust is checked at every boundary.
The service does not assume that a domain, recipient, credential, or delivery attempt is valid without a matching control.
Authorize the domain
Verify ownership before MailerZ activates any receiving or sending path.
Validate the requested identity
Apply recipient, alias, catch-all, and sender rules before routing a message.
Secure and record the event
Store required message and delivery data before confirming acceptance or sending.
Expose the delivery result
Keep the server response and outcome visible for monitoring, support, and recovery.
Control the path without running the server.
Use verified receiving and authenticated sending while MailerZ manages the delivery infrastructure.