Mail isn't forwarding

Start with the message timeline

Before changing anything, open the dashboard and look for the message. Every message JoltMx receives has a timeline showing exactly how far it got: received → authenticated → routed → forwarded → delivered. Where the timeline stops tells you where to look.

• No message at all? It never reached JoltMx - jump to "Check your DNS".
• Received but rejected at authentication? See "Authentication failures".
• Routed but not forwarded? See "Check the destination".
• Forwarded but not in your inbox? See "Forwarded but missing".

Click to enlarge

Check your DNS

If JoltMx has no record of the message, mail isn't reaching it. Confirm your DNS:

• Your MX records point to JoltMx (mx.joltmx.io / mx2.joltmx.io) and any old provider's MX records are removed.
• The domain shows as verified and active in the dashboard.
• You haven't recently changed DNS - propagation can take up to a few hours.

Need to redo this? Follow Add and verify your domain.

Check the destination

JoltMx only forwards to verified destinations. If a message is routed but not forwarded:

• The destination address is verified (re-check in Destinations - a pending one won't receive mail).
• The destination on the rule is the address you actually meant - watch for typos.
• The rule's action is Forward, not Store or Reject.

Check your routing rules

• There's a rule covering the address - an exact alias or a catch-all.
• A more specific rule isn't quietly winning. Remember exact aliases take priority over the catch-all - see How routing rules work.
• The local part matches exactly (support, not suport).

Authentication failures

If the timeline shows the message was rejected at authentication, the sender's domain likely failed SPF, DKIM, or DMARC - and if they publish p=reject, JoltMx honours it. The message detail shows which check failed. This usually points to a problem on the sending side, not yours. Background reading: SPF, DKIM & DMARC explained.

Forwarded but missing

If JoltMx forwarded the message but you can't find it:

• Check the destination's spam / junk folder.
• Look at the timeline's delivery status - a response code from the receiving server shows whether it accepted, deferred, or bounced.
• Temporary failures are retried automatically with backoff, so a deferred message may still arrive shortly.

Still stuck?

If you've worked through the list and mail still isn't arriving, contact support with the affected address and roughly when the message was sent - the timeline lets us trace it quickly.