Skip to content
Igor Kucurski
Menu

Email infrastructure

Self-hosted email that's set up right, and fixed when it stops delivering.

Email is my strongest specialty. I run my own Postal, MailWizz and mail servers, so the problems I fix for clients are ones I've already had to solve on my own infrastructure.

Services

What I do

Postal and MailWizz

Installation, connecting them through the API, bounce webhooks, multiple sending domains, and rebuilding a setup after a server loss.

EmailDelivery.com and Velocity MTA

Docker-based platforms: upgrades, domain changes, resets and repairs.

Authentication and DNS

SPF, DKIM and DMARC, rDNS and forward-confirmed rDNS, HELO hostnames, and moving to a new IP range without losing reputation.

Blocklists and blocks

Finding why mail is rejected, getting delisted, and dealing with provider-specific blocks and blocked port 25.

Warm-up

Planning warm-up for new domains and IPs, mailboxes for warm-up on your own server, and separating marketing mail on a subdomain.

Relays and mail servers

SMTP relays, Mail-in-a-Box and Mailcow, and sending from devices and apps that need to send mail.

From my own servers

Things that break deliverability quietly

SPF is checked twice

Receivers check SPF for the HELO hostname and for the MAIL FROM domain separately. A correct record for your domain doesn't help if the HELO hostname fails.

Mail-in-a-Box and hostnames without TXT

Mail-in-a-Box publishes v=spf1 -all for hostnames that have no TXT record of their own, which can make the HELO check hard-fail.

Postal and MailWizz need the API

Connect MailWizz to Postal through the API credential, not SMTP, if you want bounces and events to flow back properly.

Not every block shows up in public tools

Some provider blocks, like Microsoft's S3140, don't appear in MXToolbox. You see them only in the rejection message.

Straight talk

No inbox-rate guarantees

Inbox placement depends on your list, content, sending volume and history as much as on the server. I make sure the infrastructure isn't the reason you land in spam: correct authentication, clean IPs, proper bounce handling and a sensible warm-up. Anyone promising a fixed inbox percentage is guessing.

How it works

Audit, fix, then send

  1. 01

    Audit

    DNS records, authentication, rDNS, blocklists and the platform setup, checked against what receivers actually see.

  2. 02

    Fix

    Correct the records and configuration, connect the platform properly and handle bounces.

  3. 03

    Warm up

    A gradual ramp-up plan for new domains or IPs, so reputation is built instead of burned.

Real work

Recent email jobs

My own Postal mail server

Self-hosted Postal stopped delivering

Problem
Outgoing mail suddenly stopped reaching inboxes.
Cause
An SPF hardfail on the HELO hostname, and a firewall rule that had disappeared after a change.
What I did
  • Checked SPF for HELO and MAIL FROM separately, since receivers evaluate both
  • Published a correct SPF record for the HELO hostname
  • Restored the firewall rule and made it persistent
Result
Sending restored, and both fixes survive reboots.

Self-hosted bulk email platform

Email platform editor threw error 500

Problem
The campaign editor failed with a server error.
Cause
A bug in an outdated release of the platform.
What I did
  • Upgraded to the latest commercial release with a backup first
Result
Editor works.

Tools and stack

  • Postal
  • MailWizz
  • EmailDelivery.com
  • Velocity MTA
  • Mail-in-a-Box
  • Mailcow
  • SPF
  • DKIM
  • DMARC

Mail not landing where it should?

Send me the sending domain and what you're seeing. I'll check DNS, authentication and blocklists and tell you what I find.

Audit my sending setup →