# Email logs
Source: https://docs.webgee.com/en/mail-delivery-center/email-logs









**Email Logs** is a searchable record of individual messages: who sent them, who
they went to, and what happened. Applies to all plans that send through the
[outbound relay](/en/email/outbound-mail-relay).

This is the page that answers &#x2A;"they say they never got it"*.

<img alt="Email Logs with the filter panel above the message table" src="__img0" />

## Filters [#filters]

| Filter                        | Use                            |
| ----------------------------- | ------------------------------ |
| **From Email**                | Narrow to one sender           |
| **To Email**                  | Narrow to one recipient        |
| **Subject Contains**          | Find a message by subject text |
| **Start Date** / **End Date** | Bound the search               |
| **Delivery Status**           | All, or one outcome            |

**Clear All** resets them.

Filter by **recipient and date** first. It is the fastest route to a single
message, and it avoids reading a table of a hundred rows to find one.

## Reading a row [#reading-a-row]

| Column            | Meaning                                    |
| ----------------- | ------------------------------------------ |
| **Date**          | When the relay handled the message         |
| **Status**        | Delivered, Failed or Unknown               |
| **From** / **To** | Envelope sender and recipient              |
| **Subject**       | The message subject                        |
| **Response**      | The receiving server's own reply, verbatim |
| **Origin**        | The relay IP the message left from         |

<img alt="Delivered messages in the log, one row per message" src="__img1" />

The **Response** column is the useful part, because it is the receiving server's
own words about why. **Delivery Status** filters to `Delivered`, `Failed` or
`Unknown`; the last covers messages the relay accepted but has no final outcome
for yet.

A **Delivered** status means accepted by the recipient's *server* — not that it
reached their inbox. A message can be delivered and still be filed as spam at
the far end.

<Callout type="info">
  That distinction matters when someone insists they never received a message
  that shows as delivered. The next place to look is their spam folder, not this
  page. See
  [Why your email is marked as spam](/en/email/why-are-my-emails-being-marked-as-spam).
</Callout>

## Reading a failure [#reading-a-failure]

Filter **Delivery Status** to `Failed` and the Response column names the cause:

<img alt="Failed messages, with the receiving server's rejection text in the Response column" src="__img2" />

Two responses account for most failures:

| Response                                                  | What it means                                    | What to do                                                                                                |
| --------------------------------------------------------- | ------------------------------------------------ | --------------------------------------------------------------------------------------------------------- |
| `452-4.2.2 The recipient's inbox is out of storage space` | The mailbox at the far end is full               | Nothing at your end. Tell the recipient, or wait and retry                                                |
| `Recipient was found from suppression list`               | The address bounced before and is now suppressed | Confirm the address is real, then release it in [Blocked emails](/en/mail-delivery-center/blocked-emails) |

The first is the recipient's problem. The second is yours: it means you kept
sending to an address that already failed, which is the pattern mailbox
providers read as a stale list.

## Details and Not Spam [#details-and-not-spam]

Some delivery responses carry **Details** and **Not Spam** links, which open the
receiving provider's own page in a new tab — to see why a message was flagged,
or to report it as legitimate.

Use **Not Spam** when a provider has wrongly filtered you. It is a signal to
that provider, not to WebGee, and it is one of the few direct ways to influence
how a large mailbox provider treats your domain.

## Working through a delivery complaint [#working-through-a-delivery-complaint]

1. Filter by the recipient's address and the date they expected it.
2. **No row at all** — the message never reached the relay. The problem is in
   your application or mail client, not delivery. See
   [Why mail from your PHP script fails](/en/email/why-am-i-not-able-to-send-mail-via-my-php-script-or-application).
3. **Failed** — read the response. It usually names the reason: unknown address,
   full mailbox, or a spam rejection.
4. **Delivered** — it reached their server. Ask them to check spam, and look at
   [Email Deliverability](/en/mail-delivery-center/email-deliverability) if it is
   happening repeatedly.

## Related [#related]

* [Email Deliverability](/en/mail-delivery-center/email-deliverability)
* [Blocked emails](/en/mail-delivery-center/blocked-emails)
* [Read email headers](/en/email/how-to-obtain-email-headers-a-step-by-step-guide)
