mxhop

FAQ

The questions that decide whether this is for you.

Will my forwarded mail land in spam?

Not if DNS is right, and mxhop does its half. The two things that break forwarded mail are SPF (the message now comes from your server) and DKIM alignment (any change to the bytes invalidates the signature). mxhop handles the first with SRS and the second by not touching the body at all. Your half is MX, A, PTR, SPF and DMARC — all six records are on the docs page. Get PTR wrong and large receivers refuse you outright, whatever else is correct.

Can I reply from my alias?

No. mxhop is inbound only; it never authenticates a submission, so there is nothing to send as. Replies come from whatever mailbox you read the mail in. If you need to send as the alias, configure that in your provider — Gmail's "send mail as" works alongside mxhop and does not need anything from it.

How is this different from a provider's forwarding?

Functionally, barely. The difference is where the mail goes and who can read it: through your machine, in a spool you own, logged the way you chose, with no account to lose and no terms to change. If your registrar or provider already forwards mail in one setting, that is the simpler answer and you should use it. mxhop is for when you want the hop to be yours.

What happens when the destination is down?

The message goes to the spool, you keep the 250 you gave the sender, and the runner retries after 1, 5, 15, 60 and 240 minutes, then every four hours until the 48-hour lifetime runs out. If it never gets through, mxhop sends a delivery report — but only when it can prove who the sender was, because a bounce to a forged address is spam you are sending.

Can it lose my mail?

The design trades the other way: it would rather deliver twice than lose once. A message written to the spool is renamed into place, so a crash leaves either a complete message or a .tmp file that is ignored. A delivery that succeeds but whose queue entry cannot be removed is retried, producing a duplicate. You can delete a duplicate; you cannot read a message that is gone.

What it cannot survive is a spool on a disk that fills up, or a container without a spool volume.

Does it read my mail?

It parses headers to route and to verify, and it hands the body on without inspecting it. Nothing of the content is logged, stored beyond the queue, or put in a metric label — and that is enforced by a test that reads every logging call in the source and fails the build if one of them could print content. The overview lists exactly which fields go in a log line.

Does it filter spam?

No, and it will not. It authenticates identity: a message that fails DMARC against a p=reject domain is refused, because forwarding a forgery puts it on your reputation. A correctly signed message from a throwaway domain is delivered. Content filtering belongs where the mailbox is — Gmail and Fastmail are far better at it than anything that would fit in this binary.

How much does it need to run?

An 8 MB binary, a few megabytes of memory at rest, and disk only for messages actually waiting. The smallest VPS anyone sells is oversized for it. What it really needs is a static IP with a PTR record you control — which is the thing to check before you rent anything, because many cheap providers will not set one, and without it this does not work.

Is it ready?

It is v0.3.0 and runs in production on one install, handling real mail for several domains, with ARC confirmed accepted by Gmail. It has not been through a security audit, the release artifacts are not signed, and there is no connection rate limiting yet, so a public MX is exposed to whatever volume arrives. Judge it as careful software with a short track record, not as a proven one.

What is missing?

Connection blocklists and rate limiting (the next thing being built), signed release artifacts, and IMAP or submission support, which are deliberately out of scope forever. If you want something, the repository is where to say so.