SMTP2GO's Delivered event means the recipient's incoming server acknowledged the message. It does not specify the mailbox folder where the copy was placed. Match the exact Activity timeline with an LDM recipient observation to distinguish transport acceptance, an observed folder and an unresolved missing copy.
Find the individual message
Start with the recipient address, approximate send time, sender and subject. SMTP2GO documents investigation through Reports, Activity and the recipient's Timeline. Find the specific message rather than relying on an account-wide success percentage. A later resend with the same subject is another message and needs its own evidence.
Record the available service reference, timestamps and remote response. Keep the timezone explicit when comparing an application log with the dashboard. A seemingly missing event may simply fall outside a time filter or belong to another sender route used by the application.
Read the timeline in order
Separate an application job from submission to SMTP2GO, provider processing, remote acceptance and subsequent events. SMTP2GO's troubleshooting guidance explains how the timeline helps identify delivery, bounce or processing state. Preserve the actual response instead of replacing it with a vague failure label.
If the message is absent from Activity, investigate the submitting application and the intended SMTP or API route. Do not infer a recipient spam decision from a message the service may never have received. Conversely, a Delivered record provides useful transport evidence even if the recipient cannot find the message in the primary Inbox.
Obtain the mailbox observation
For a controlled check, create an LDM test using the intended sender and obtain its current recipient addresses. Generate a fresh original through the real application route that uses SMTP2GO. A manually composed message from another client can be useful only if labeled as a different route.
Use safe fixture data and keep the test recipients isolated from recurring jobs, campaigns and continuing automations. Retain the application's submission reference beside the SMTP2GO evidence. This article does not submit messages or assume a native LDM integration.
Match each LDM observation with the appropriate recipient and message. Record the observed folder and measurement time. A primary Inbox copy, a category-folder copy and a Spam copy are distinct received outcomes. A missing observation remains unresolved until further evidence supports a more specific conclusion.
Resolve common apparent contradictions
Delivered plus Spam is consistent: server acceptance and mailbox placement describe different stages. Delivered plus missing observation can require checking timing, recipient correctness, mailbox observation availability or recipient-side handling. It is not proof that either report is false.
A bounce followed by an observed copy might indicate mismatched message identities, a later retry or different recipients. Reconcile references before combining the facts into one history. The same subject is insufficient evidence that two records describe the same original message.
For a real customer complaint, ask an authorized recipient administrator to trace the exact message where appropriate. An LDM panel can examine your route with test recipients; it cannot reveal the private rules, quarantine or history of a customer's mailbox.
Report evidence without collapsing it
A useful record states the sender route, selected recipient, submission time, service event and response, observed location, observation time and any unresolved gap. Keep missing copies out of a confirmed Spam count and include the number actually observed.
A small panel cannot predict every recipient's experience or establish why a provider classified a message. Use it to narrow the next investigation. Do not repeatedly resend merely to obtain a preferred location without understanding the original transport and observation evidence.
Frequently asked questions
Why is Delivered compatible with Spam?
SMTP2GO documents Delivered as recipient-server acknowledgment. Folder classification is a separate recipient-side outcome.
What if Activity contains no matching message?
Check the application submission, account route, filters and timestamps. Do not call it a placement failure without evidence that the intended message reached the sending service.
Does an LDM Inbox copy resolve a customer's missing-message report?
It establishes an observation for the test recipient. The customer's specific message and recipient-side handling still need their own investigation.
Official references
Reviewed 2026-11-05; no customer incident or completed test is asserted.