Ask for the sender, recipient, approximate time with timezone and the message ID where available. Use a narrow timeframe and the actual envelope addresses when known. A subject alone can match unrelated messages, especially for automated notifications.

1. In the Admin console, open Reporting > Email Log Search with the Gmail Settings administrator privilege. Use Custom Search for the transaction you are investigating.
2. Enter the relevant time range and sender or recipient. Add the message ID for a more precise match, particularly for group-related investigations.
3. Run the search and open the matching result.
4. Review the delivery events, recipient details and any rejection, routing or post-delivery information available.
5. Compare the result with the sender's bounce and the recipient's mailbox search.

A rejected message needs its SMTP reason investigated. A message handed to another server may need that provider's logs. A message delivered to Gmail can still be affected by Spam, a filter, forwarding or a user's later action. Follow the evidence to the next responsible component.

If a customer asks about a message older than 30 days, obtain its actual Message-ID and the full recipient address, such as [email protected]. Google requires both for that older-message search. A Google Group address alone is not a supported search for this age range.

Use the message's real identifier from its headers, select the relevant older-message option and inspect the available result. Google provides post-delivery information for these older messages rather than the original delivery-status history. If the evidence needed is absent, compare the sender's retained receipt or the other provider's records. Do not interpret an unsupported or incomplete search as proof that the customer never sent the message.

Check the search window, address spelling and documented search limits. Confirm the message was actually submitted and whether another provider handled the domain at that time. A website claiming to have sent mail is not the same as a recorded SMTP acceptance.

Share only the necessary log details with support. Redact unrelated recipients and personal information, and keep full message content private unless it is needed and authorised. Record the final cause and fix so repeated delivery reports can be compared consistently.

• Creating Gmail filters that organise messages safely
• Reviewing Gmail forwarding and keeping an authorised copy
• Creating a Google Group for a team email address
• Moving business email without losing track of messages

• Google Workspace Email Log Search
• Google Workspace contact-form delivery troubleshooting