Skip to content

Knowledgebase

Tracing a SpamExperts message by sender, recipient and time

email, security-ssl

Trace one message through SpamExperts before changing filters. The aim is to identify whether the service saw it, how it classified it and what happened during delivery to the next server.

01 Build a useful trace

  1. Collect the original sender and recipient, approximate time with time zone, and Message-ID if available.
  2. Choose incoming or outgoing log search according to the message direction.
  3. Select the correct domain and a narrow date range, then add sender or recipient filters.
  4. Open the matching entry and inspect status, classification and delivery response. Distinguish separate retries from separate messages.
  5. Record the relevant identifier and outcome for the mailbox or sending administrator.

02 Follow the next hop

If the filter delivered the message successfully, inspect the destination mailbox's rules, spam controls and logs. If no matching record exists, confirm that the sender actually used the filtering route and addressed the correct domain.

03 Example: provide a trace another administrator can repeat

A supplier says an invoice was sent, but Ada cannot find it. Start with a record like this, replacing the illustrative values and bracketed fields with the actual message evidence:

Code or configuration example
Direction: Incoming
Domain: example.com
Recipient: [email protected]
Sender: [email protected]
Search window: 10:00 to 10:20 UTC on [date]
Message-ID: [copy from original]
Filter state: [copy from log]
Destination response: [copy complete response]

If the filter records delivery to the mailbox server, pass that result to the mailbox administrator and check that server's folders and rules. If it records a queue or rejection, investigate that stage first. The expected result is a named next step supported by a matching message record, not a blanket change to spam settings.

Common questions

Does Delivered mean the recipient read it?

No. It establishes a delivery outcome at the recorded stage. It does not prove Inbox placement or that a human opened the message.

Why can I view metadata but not the body?

Content visibility depends on message state, retention, archiving and permissions. A delivered log record is not automatically a retained full message.

What should I send to support?

Provide the exact message details, selected direction, status and relevant response. Include an original EML only when needed through the approved channel.

Do not modify broad filtering settings merely because one message has an unfamiliar classification. Compare a working and failing example from the same route and identify the specific difference. That produces a narrower, more reliable correction than changing several policies at once.

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support