Why some messages stop before becoming tickets, and what each hold reason tells you to fix.
Two separate questions are asked of every inbound message, and both have to
pass.
Which store is this for? Answered by the address the
message was delivered to.
Did this really come from the platform? Answered by the
signature the platform attaches to its own mail.
An address that resolves does not answer the second question. Forwarding
addresses leak — they sit in merchant portal configuration screens that
several people can see. If the address resolves but the signature does not, the
message is held and never imported.
Image needed · mpemail-held-01
Capture: The Held tab with at least two rows and different reasons - one that failed the sender check and one whose address could not be tied to a store.
Common hold reasons
Sender could not be confirmed. Almost always a manual
forward. Pressing Forward rewrites the message and breaks the signature.
Use an automatic rule instead, or have the platform send direct.
No store could be identified. The message reached the
mailbox without the original recipient address surviving, or it was sent
to an address that was never issued.
Image needed · mpemail-held-02
Capture: The detail of a held message showing the authentication result lines, with DKIM failing and SPF shown but not acted on.
One check is deliberately not enforced: the sending-server check fails by design on any forwarded mail, because the forwarding server is not on the platform list of approved senders. It is shown for information and nothing is held because of it.