Email & SMTP

Complete Email Server Health Check

A full top-to-bottom check of a self-hosted mail server: authentication, queues, logs, security and performance.

The Problem

You run your own mail server (Postfix, Exim, etc.) and it mostly works, but you've never had a proper look under the bonnet — queued mail, open relays, weak TLS config and bloated logs tend to pile up quietly.

About this problem

Self-hosted mail servers (Postfix, Exim, etc.) don't send alerts when something's quietly wrong — a growing mail queue, an open relay nobody noticed, a weak TLS cipher configuration, or logs bloating the disk all tend to accumulate silently until something more serious forces a closer look.

This is typically requested as a periodic check-up for a server that's never been properly audited, or after noticing something feels "off" without a specific error to point to.

What's Included

What's NOT Included

How It Works

  1. Check the mail queue for stuck, backlogged, or repeatedly failing messages.
  2. Review SPF, DKIM and DMARC configuration on the server side for correctness.
  3. Check TLS configuration strength and confirm the server isn't acting as an open relay.
  4. Review logs for repeated errors, authentication failures, or signs of abuse attempts.
  5. Compile findings into a written report ranked by urgency, not just a raw list of observations.

In practice: you buy the service, send over whatever access or details the job needs, I investigate and do the work, and you confirm it's resolved before we call it done.

Frequently Asked Questions

How do I know if my mail server is an open relay?
An open relay accepts and forwards mail from anyone, not just authenticated users on your domain — this is checked directly by testing relay behaviour against the server rather than assuming based on configuration alone.
What does a stuck mail queue mean?
Messages that can't currently be delivered (due to a temporary failure, a misconfiguration, or a full queue) stack up rather than disappearing — large queues often point to a deeper deliverability or configuration issue.
How often should a mail server health check be done?
Roughly annually for a stable, well-maintained server, or any time something feels different (slower sending, more bounces, unexplained log entries) without an obvious cause.
Can a health check find security vulnerabilities in my mail server?
It checks for the most common mail-specific issues — open relay, weak TLS, authentication gaps — though it isn't a full penetration test of the server's wider security.
Does this check include fixing what's found?
No, it's diagnostic — findings come with a ranked written report, and fixing them is quoted and scheduled separately once the scope is clear.
What mail server software does this cover?
Common self-hosted options like Postfix and Exim are the most frequent, but the same principles (queue, auth, TLS, logs) apply to most mail server software.
Please note: the price shown applies to a standard case matching the description above. Every situation is different, and if your request falls outside the normal scope of this service, I will explain this before doing any additional chargeable work. I will never silently turn a small job into an expensive project.
Running into an issue with a service you've already bought, or unsure which one fits your problem? Message me directly on WhatsApp — no ticket system, no bot.