Sometimes a message looks like it sent successfully — your sending tool shows no error, and the mail server even confirms it accepted the message — but the recipient never sees it, and you never get a bounce or failure notice either. Here's how to work through that.

Check this before anything else, especially if the problem affects every message from every mailbox — including messages sent between two of your own Maildoso mailboxes.

There is one SMTP submission endpoint for every Maildoso mailbox on every account:

Your IMAP server is a different host, and it's specific to the mail server your mailbox lives on — it looks like imap.<name>.maildoso.com. That host is for reading mail. It is not an SMTP endpoint. If your SMTP settings point at an imap.*.maildoso.com host, the connection can still succeed and the server can still answer with 250 OK: queued as ..., but the message never enters our delivery system — so it's never delivered, and no bounce is ever generated. That is exactly the no-error, no-delivery, no-bounce pattern this article is about.

Two things worth knowing while you check:

If your SMTP setting pointed anywhere other than smtp.maildoso.com, correct it, send one fresh test, and confirm the result before troubleshooting further — the rest of this article assumes SMTP is already correct.

Once SMTP is correct, a "no bounce" outcome almost always means the message left successfully and was accepted by the recipient's mail server. From that point, delivery issues usually happen on the receiving side, not before your message left. Common reasons a message can go quiet after being accepted:

A newly created mailbox or domain can take up to 24 hours to finish provisioning after it first shows as set up. Messages sent during that window can be accepted by our system (so your sending tool sees no error) without being fully routed yet, and that kind of hold doesn't generate a bounce. If the affected mailbox or domain is less than a day old, that's the first thing to rule out — wait for provisioning to complete and re-test before assuming it's a spam-filter issue.

For a domain that was just connected or provisioned, there can be a brief window where DMARC is already active with a reject policy before DKIM has fully finished publishing on our side. During that window, some receiving mail servers accept the message during the SMTP conversation and then silently discard it afterward because DKIM alignment fails — which produces exactly this pattern: no error on send, no bounce back, and the recipient never sees it.

These two situations point to different causes, so it helps to test them separately: sending between two of your own Maildoso mailboxes rules out most recipient-side spam filtering, and points more toward a sending-configuration or provisioning issue if it fails. Sending to an outside address (Gmail, Outlook, a prospect's domain) is where recipient-side filtering, quarantine, and corporate mail security are the more likely explanation. If you're troubleshooting a no-bounce report, try both and tell us which one you tested — it narrows down where to look considerably faster than a single example.

In a small number of cases, messages sent through Maildoso can sit in an internal delivery queue longer than expected — for example during a backend slowdown. This is much rarer than the causes above and is not the first thing to suspect. In particular, if nothing at all is being delivered from any mailbox, including mailbox-to-mailbox tests, that points to the SMTP-host problem at the top of this article rather than to a queue delay — a genuine queue delay clears on its own and the messages do eventually arrive. Before reporting one, confirm your SMTP server is smtp.maildoso.com and re-check the recipient well after the original send time. If you've done both and several sends across different recipients and domains are still missing with no bounce, let us know — and mention that you've already verified the SMTP host — so we can check it as a platform issue rather than a one-off.

For mailboxes sending through Maildoso, we can look up the delivery record for a specific message and confirm whether it was successfully handed off to the recipient's mail server. If our record shows it was accepted on the receiving end, the message was delivered, and the rest of the journey (spam folder placement, internal routing, etc.) happens inside the recipient's own mail system, which we can't see or control from our side. If we have no record of the message at all, that normally means it never reached our delivery system — which again points back to the SMTP settings at the top of this article.

With one concrete example, we can pull the delivery record for it and let you know exactly what happened on our end.

Still stuck after checking the above? Contact us with the details above and we'll review your specific case.

Related: My domain shows "missing MX records" or I'm not getting replies · My CC or BCC recipients didn't receive the email.