Legal and compliance
Notices, demands and disclosures where content, timing and destination must be evidenced.
- NOM-151 certificate
- WORM preservation
- Offline verification
Transactional and certified email · Mexico
Every message leaves a receipt that stands on its own.
mailack sends and receives email from owned infrastructure on Mexican soil, preserves the literal SMTP response from delivery and the unparsed DSN, and seals that evidence with a NOM-151 preservation certificate issued by an accredited PSC.
System under construction. We are working with pilot customers.
Powered by JAAK + PSC Codex
Message receiptmsg_01JQ4T7BWM6Z
Canonicalized message
9f2c41ab7d0e5b83c6a1f4e29d7b0c58ea3419f7d62b8c05a7e1f39b4c8d20a6
Merkle tree leaf
leaf 0x00 · index 3412 / 10000
SMTP response on delivery
250 2.0.0 OK 1753812004 d9-20020a17090a — queue id 4bK9Qz3Yx1z
Root sealed with the PSC
3a71e08cd4f9b26517ac0de83b45f912c7d60e4ab198f253c60ad7e194bf82c1
NOM-151 sealedSerial 04:9C:2F · 2026-07-29 11:04:16 CST
Two ways in
Start where it matters to you.
01Who it is for
Where an email has consequences.
Three operations where the send gets questioned later, and what stays on record in each one.
Fintech and collections
Statements, reminders and payment notices at volume, with traceability required.
- Idempotent ingestion
- Raw RFC 3464 DSN
- Per-tenant suppression
HR and payroll
Payslips and employment communications that leave no room for “it never arrived”.
- Literal delivery transcript
- VERP correlation
- mx-monterrey-1 residency
02Why it exists
A managed relay hands you the conclusion, not the proof.
When a delivery has to hold up in front of a third party, two things fail at once.
The bounce arrives pre-interpreted
The provider parses the DSN and hands you JSON with its reading of it. The original RFC 3464 message — the document — is not preserved. What remains is the provider's opinion about what happened.
The sending IP is neither yours nor local
A shared pool changes IP and jurisdiction without notice. If your contract or your regulator requires Mexican residency, there is no way to evidence it.
03Raw evidence
What the destination answered, untranslated.
The DSN is archived whole before parsing. This is what stays on file for each delivery attempt.
Reporting-MTA: dns; mail-out-01.mailack.comArrival-Date: Wed, 29 Jul 2026 11:04:14 -0600Final-Recipient: rfc822; user@domain.comAction: deliveredStatus: 2.0.0Remote-MTA: dns; mx.domain.comDiagnostic-Code: smtp; 250 OK queue id 4bK9Qz3Yx1zRaw evidence exactly as archived, before parsing. The original .eml is preserved in WORM storage; what you see is its literal content.
04How it works
Four moments, four records.
Nothing is re-serialized or reconstructed afterwards. What happened is preserved, at the moment it happened.
- Ingest
The message is fixed
The API accepts the send with an idempotency key, fixes Message-ID and Date, and hashes the exact byte stream that will go over the wire.
POST /v1/messages · Idempotency-Key
- Seal
Batched and sealed
Hashes enter a Merkle tree (RFC 6962) in windows of one hour or ten thousand leaves. The root is sealed with the PSC, not each message: same proof at a fraction of the cost.
batch · root + NOM-151 certificate
- Deliver
The literal SMTP response is kept
The owned MTA delivers and preserves the literal SMTP response from the delivery conversation, with its queue id. Not a translated code: the line itself.
250 2.0.0 OK · queue id
- Return
The raw DSN is archived
The VERP return-path correlates every bounce with its message. The .eml is archived before parsing and preserved in WORM storage.
bounce+<uuid>@mailack.com
05Residency
It leaves from Mexico, under its own IP and name.
Owned MTA on dedicated Oracle Cloud VMs in Monterrey, not a shared pool: fixed egress IP and its own HELO.
RegionOCI mx-monterrey-1 (Monterrey, N.L.)
OutboundKumoMTA · fixed egress IP
InboundPostfix · own MX for DSN and ARF
PreservationObject Storage with WORM retention
The distinction that actually matters
The Mexican IP is data residency and a contractual argument. Evidentiary value comes exclusively from the NOM-151 preservation certificate issued by the PSC. They are two different things and we treat them as such.
06Operations
Deliverability is run by an agent. On a short leash.
Warm-up, throttling, suppression and failover run on their own. A model does the diagnosis; code authorizes the dangerous decision.
The LLM is never in the delivery path. If the agent goes down, the MTA keeps sending at the last known good rate.
Full autonomy — all of these reduce risk
- Lower the sending rate, down to a pause
- Fail over to the backup provider
- Pull an IP from the pool
- Suppress an address
- Freeze warm-up and open an incident
Behind a deterministic gate — all of these raise risk
- Raise the sending rate
- Resume after a block
- Add a new IP to the pool
- Move up a warm-up step
07Questions
What people ask before the demo.
Does a certificate over the Merkle root cover my message?
The certificate attests that the root existed at that instant; the inclusion proof attests that your message was part of that tree. Both ship together in the proof bundle. For litigation we also issue an individual certificate for the message, on demand.
Can I verify without connecting to mailack?
Yes. The proof bundle carries the canonical hash, the inclusion path and the certificate. The command-line tool checks the hash and the inclusion proof offline, without querying our servers. The certificate itself is issued and backed by the accredited PSC.
What happens to deliverability if I switch providers?
There is no cutover. Sending is split by percentage between your current provider and mailack during warm-up, with deterministic per-ISP rules.
Is it for marketing?
No. Marketing traffic never shares an IP pool with transactional and legal mail. mailack is built for the latter.
Book a demo
We show you the send, the receipt and offline verification using a message of yours.