SELF HOSTED MAIL

Self-Hosted Mail with DKIM, SPF and DMARC, Las Vegas NV

Self-Hosted Mail with DKIM, SPF and DMARC, Las Vegas NV — Las Vegas NV
Self-Hosted Mail with DKIM, SPF and DMARC, Las Vegas NV

Running your own mail for a regulated business: authentication, reputation, monitoring, and the failure modes that silently cost you enquiries.

Why self-hosted mail is hard now

Sending mail from your own server means proving to every major receiver, independently, that you are not a spammer. There is no shared reputation to inherit and no vendor to escalate to. Deliverability is earned per domain, per IP, and per sending pattern, and it is lost faster than it is earned.

The authentication floor

SPF, DKIM and DMARC are the floor, not the goal. SPF authorises sending IPs, DKIM signs the message, and DMARC tells the receiver what to do when either fails and gives you reports. Publish all three, start DMARC at none with reporting, read the reports, then move to quarantine and reject. Skipping the reporting stage is why most DMARC rollouts stall.

Alignment is the part people miss

DMARC passes on alignment, not on authentication alone. A message can pass SPF and DKIM and still fail DMARC because the authenticated domain does not align with the From domain. If you send on behalf of a domain through a third party, check alignment explicitly rather than assuming the vendor handled it.

IP reputation and warm-up

A new IP has no reputation, and sending a large volume from it immediately will be throttled or blocked. Warm up gradually over weeks, starting with your most engaged recipients, and keep volume steady. Reputation is per IP, so a shared IP inherits the behaviour of everyone else on it, which is the main argument for a dedicated address.

The feedback loops

Register for the major feedback loops and process the complaints. A complaint rate above roughly one in a thousand is a deliverability problem regardless of how good the content is. Suppress complainers immediately and permanently; arguing with a complaint is how a domain gets blocked.

Bounce handling

Separate hard bounces from soft. Remove hard bounces permanently and immediately. Retry soft bounces on a schedule with a cap, then remove. A list that keeps retrying dead addresses is a list that looks like a spam operation to every receiver.

Content and the spam filter

Filters score behaviour and structure as much as words. A message with a single large image, no plain-text alternative, a shortened link and a mismatched From name scores badly regardless of intent. Send multipart, keep links on your own domain, and make the From name match who actually sent it.

The blocklist problem

Check your IP and domain against the major blocklists weekly. Removal is possible but slow, and prevention is entirely about complaint rate and bounce handling. A blocklisted IP can take weeks to recover, so monitoring is cheaper than remediation.

What to measure

Measure DMARC pass rate by stream, complaint rate, hard bounce rate, and the proportion of mail landing in spam as reported by seed testing. These four numbers predict deliverability better than any vendor dashboard.

The adversarial test

Send to seed addresses at the major providers and inspect where the message lands, with headers. Then break DKIM deliberately and confirm DMARC reports it. If you cannot see the failure in your own reports, you will not see it in production either.

Sequencing

Publish SPF and DKIM, then DMARC at none with reporting, then fix alignment, then warm up, then move policy to quarantine. Each step is reversible and each produces evidence. Jumping straight to reject without reading reports is how a domain loses legitimate mail.

The outcome

A domain that authenticates, aligns, reports, and holds a complaint rate under one in a thousand, with a warm-up history and a blocklist check that runs weekly. That is deliverability you own rather than rent.

Transactional versus bulk

Transactional mail and bulk mail need separate streams, separate IPs and separate reputation. A password reset that shares an IP with a marketing blast inherits the blast reputation, and the reset is the message that must always arrive. Separate them before the first campaign, not after the first outage.

The receiving side is not uniform

Microsoft, Google and the smaller receivers apply different rules and different thresholds. A configuration that passes at one can fail at another, and the failure is often silent. Test against each major receiver separately and keep a per-receiver record of what passes.

Reverse DNS and HELO

Reverse DNS must match the HELO name and forward-resolve to the same address. This is trivial to configure and frequently wrong, and a mismatch is a strong negative signal at several receivers. Check it as part of the initial setup and again after any IP change.

TLS and the transport

Opportunistic TLS is the baseline; MTA-STS and DANE raise it. Publish MTA-STS with a policy and a valid certificate, and monitor the reports. Transport security is not deliverability, but a broken certificate on the receiving path produces failures that look like deliverability problems.

What good looks like

Separate streams, aligned authentication, a warm-up history, complaint rate under one in a thousand, hard bounces removed immediately, weekly blocklist checks, and seed testing against each major receiver. That is a mail system whose deliverability is a documented property rather than a hope.

The reputation you cannot see

Receivers do not publish their reputation scores. You infer them from delivery outcomes, complaint rates and seed placement. Build a weekly report that combines those signals into a single trend, and treat a worsening trend as an incident even when nothing has failed yet. Deliverability problems are visible in trends long before they are visible in failures.

When to stop self-hosting

Self-hosting is the right answer when volume is modest, the sending pattern is stable, and you want control of the path. It is the wrong answer when volume is large and bursty, when nobody owns the reputation, or when the team cannot respond to a blocklisting within a day. Being honest about that boundary is cheaper than discovering it during a launch.

The list is the other half

Authentication gets a message past the filter; the list determines whether anyone wanted it. A clean, consented, recently-engaged list delivers better than a perfect authentication setup over a stale one. Measure engagement by receiver, suppress the long-inactive, and never buy a list. Most deliverability disasters are list problems wearing an authentication costume.

Documenting the configuration

Write down every DNS record, every policy, every stream and every warm-up decision with the date it was made. When deliverability degrades, the first question is what changed, and the answer is only available if the configuration has a history. An undocumented mail setup cannot be debugged, only rebuilt.

The first week

In the first week, publish SPF and DKIM, set DMARC to none with a reporting address, send a small volume to engaged recipients, and read the reports daily. Do not change policy until the reports show alignment across every stream. The first week is entirely about learning what you are actually sending, which is usually more than the team believed.

The monthly review

Once a month, review the DMARC reports, the complaint rate, the bounce rate, the blocklist status and the seed results together. Any one of them alone can look fine while the others deteriorate. The review exists to catch the combination, and it takes under an hour if the data is collected automatically.

The failure modes that look like silence

A domain that loses its SPF record still sends. The messages go to spam, or are rejected at the receiving end without a bounce to the sender, and the first signal is a question weeks later about why an enquiry form stopped producing replies.

Monitor from the outside with a seed address at a major provider, check the authentication results in the received headers rather than the sending log, and alert on a DMARC report spike. The reports exist precisely so the failure is visible before a customer notices.

Keep the DNS change record. Records are configuration, and changing them without a trail is how a domain loses its mail during a migration nobody documented.

Where this work is delivered

Engagements run from Las Vegas and reach across the valley: clients in Las Vegas, NV; Las Vegas, Nevada; Henderson; Clark County, Nevada; and North Las Vegas, Nevada — plus remote delivery nationwide. Las Vegas, Nevada 89101.

How an engagement runs

1. Trace one real case

Follow a single patient or claim end to end with a timestamp at every hop, before any document is written.

2. Written findings

A findings list naming the defect, the system, the owner and the date.

3. Monthly review

Review the list monthly and check whether the dates held.

Frequently asked

What is this service?

This page describes self-hosted mail with dkim, spf and dmarc, las vegas nv — the scope, the failure modes it prevents and how the work is measured. It sits in the Cloud and Operations category at trinh.io.

Where is the work delivered?

Engagements run from Las Vegas, Nevada across the valley — Las Vegas, Henderson, North Las Vegas, Spring Valley, Paradise, Winchester, Sunrise Manor, Enterprise, Summerlin, Clark County — and remotely anywhere in the United States. On-site work in the Las Vegas valley, remote delivery elsewhere.

What does it cost?

Standard rate $195 per hour, committed $165 per hour at twenty hours or more per week for three months or more; $1,600 standard day, $1,350 committed day. Scoped in writing before work starts, fixed fee where the deliverable is defined.

Who is Charles Trinh?

A technology architect in Las Vegas, Nevada, working in healthcare identity, consent and interoperability. Not a physician, not a medical practice, and not affiliated with any other Charles Trinh.

How does an engagement start?

With one trace of a real case and a written findings list naming the defect, the system, the owner and the date. The first call is twenty minutes and free: 702-559-3489.

Engagement

Available for architecture review, conformance work and fractional leadership. Standard rate $195 per hour, committed $165 per hour at twenty hours or more per week for three months or more.

Talk to Charles

702-559-3489 · charles@trinh.io

Proof

  • ONC (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — public suite URL
  • 67 public hostnames, 51 serving, one AWS account
  • 104 clearinghouse enrolments across 53 jurisdictions
  • USCDI v7 proposal — Patient Digital Identity Credential — listed at isp.healthit.gov
  • SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564
  • AWS Business Associate Addendum active since 18 August 2026
TRINH — Charles Trinh, technology architect
TRINH

Charles Trinh

Fractional CTO/CIO and Technology Architect — Healthcare Data, Identity & Regulated Infrastructure · Las Vegas, NV

Las Vegas, Nevada · US citizen · Fractional and project engagements

(702) 559-3489 Email Charles Trinh

Record

Profile

Healthcare technology architect working where federal regulation becomes production infrastructure. Built and operates a FHIR R4 clinical platform — SMART App Launch authorization server, patient and provider portals, SQLite — on a hardened single-host AWS estate of 67 public hostnames. The platform returned a self-test PASS on the ONC (g)(10) Standardized API test suite in April 2026, 317 of 317 subtests, publicly verifiable. Designed a consent architecture in which a permissioned ledger records patient grant, refusal and revocation as immutable events while all clinical data stays off-chain and encrypted per patient — no PHI on the ledger by design. Filed a proposed USCDI v7 data element with ONC on verifiable patient identity. Translates the Federal Register, HHS/CMS guidance and HITRUST requirements into architecture, controls and audit evidence.

Selected engineering scale

  • Self-managed estate of 67 public hostnames, 51 serving, on one AWS account.
  • FHIR R4 API with a SMART App Launch authorization server; patient and provider portals; an AI service layer; Hyperledger Fabric peer, orderer and CA; IPFS; a 337-table SQLite clinical store.
  • Two permissioned distributed ledgers in production, one operating a consent registry that records grant, refusal and revocation with no PHI on chain.
  • X12 005010 pipelines across eight transaction sets.
  • Designed, built, deployed and operated end to end by one person.

Credentials and standards work

  • Inferno (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — the ONC Standardized API test suite. Standards validated: US Core 6.1.0, USCDI v3, SMART App Launch 2.0.0, Bulk Data 2.0.0. Public suite URL.
  • USCDI v7 public comment submission, April 2026 — proposed Patient Digital Identity Credential under the Provenance data class, listed publicly on the ONC Interoperability Standards Platform.
  • SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564. AWS Business Associate Addendum active 18 August 2026.

Technical environment

AWS us-east-1 (compute, storage, messaging, SMS, email, voice) · Linux and systemd hardening · nginx · Fabric and EVM ledgers · FHIR R4 · X12 005010 · HL7 · SQLite · self-hosted mail, drive, search and monitoring · Git-based change control and CI release gates.