Check what happened to one message
Start with one message you expected. In Log search, search by its sender or recipient and the date. See Find a message and prove it was delivered.
| What Log search shows | Go to |
|---|---|
| Nothing at all | The message never reached SpamDuster |
| blocked / refused | The message was blocked |
| temp-failed | Your mail server did not take the message |
| delivered with a reply from your server | The message was delivered |
The message never reached SpamDuster
- Check the domain's MX records point at your Mail host (MX target): for example
nslookup -type=mx example.com. - If you changed them recently, wait for the old records to expire (their time-to-live). Until then some senders still deliver straight to your old server.
- Ask the sender for the error they received, if any.
The message was blocked
The domain may be missing from Mail domains: SpamDuster refuses mail for domains that are not listed. Add it. See Add your mail domains.
If the domain is listed, the filter judged the message to be spam, phishing or malware. See Wanted mail was blocked.
Your mail server did not take the message
SpamDuster could not deliver to your destination mail server, so the sending server will retry. Run the destination test: open Advanced and select Test without saving under Destination mail server. See The destination test fails.
The message was delivered
SpamDuster delivered the message and your mail server accepted it. The Destination reply shows your server's answer, which usually includes its own queue id. Look the message up in your mail server's logs, or ask whoever runs it: the message may be in a junk folder, filtered by a mailbox rule, or held by your mail server.
Mail for new senders arrives a few minutes late
That is greylisting working as intended. See Mail from new senders is delayed.