Delivery Logs
Analytics → Delivery Logs is the message-by-message record of everything you send: campaigns, triggers, automations, and transactional email from your Bridges and the sending API. Each message appears once, with its latest status, and you can open it to see the full delivery detail.
Use it to answer questions such as:
- Did the password reset I sent to this customer arrive?
- Why did this message bounce, and what did the receiving server say?
- Which Bridge, pool and IP did this message go out from?
The page is titled Analytics Delivery Logs.
The Filters panel
The Filters panel is on the left. Set what you're looking for, then click Search.
| Filter | What it does |
|---|---|
| Search only with exact match | Under Search Option. Matches your keyword against the whole value instead of as part of a longer one. It matters most for Sender Email and Message ID, which otherwise search with Contains. |
| Duration | Today, Last 7 Days or Last 30 Days. Choosing one fills in the start and end dates and runs the search. The durations offered depend on your plan's log retention. |
| Start Date and End Date | The exact period to search, to the minute. Click a field to open the calendar, which goes back as far as your plan keeps logs. |
| Email Type | All, Newsletter (marketing email) or Transactional (Bridge and API email). |
| Status | Any Status, Received, Delivered, Bounced or Rejected. See Statuses. Opens and clicks aren't part of the delivery log: the note under the filter links to Engagements. |
If the start is later than the end, you'll see "Start date and time cannot be later than the end date and time."
More filters
Click View more filters to search on one field of the log. Choose the field in Filter By, and the controls for that field appear underneath:
| When you filter by | You choose |
|---|---|
| Bridge | Select Bridge: Any Bridge or one of your Bridges by name |
| Node Name | Select Node: Any Node or one of your pools |
| Bounce Type | Select Bounce Type: Soft or Hard |
| Any other field | Select Condition (is, isn't or Contains) and a Keyword |
Useful fields include Recipient Email, Recipient Domain, Sender Email, Sender Name, Sender Domain, Email Subject, Message ID, Response Code, Response Details, Bounce Category, Recipient MTA, Return Path, Node IP and Job ID.
For example, to find everything sent to one customer, choose Filter By → Recipient Email, is, and type their address.
A keyword is required once you've chosen a field; otherwise you'll see "This field is required." Click Close to hide the extra filters and clear them, and Reset Filters to put every filter back to its default.
The results
Results are listed newest first, ten per page. Use Previous and Next to page through. If nothing matches, the page shows "No data available."
Each row shows:
| Column | What it shows |
|---|---|
| From | The sender's name and email address |
| To | The recipient |
| Subject | The subject. Hover to see it in full. |
| Queued Time | When Mumara ONE accepted the message |
| Feed Type | Newsletter or Transactional |
| Status | The message's latest status |
Times are shown in your account's time zone, which you set under My Profile in the user menu.
Statuses
| Status | What it means |
|---|---|
| Received | Mumara ONE accepted the message and is still waiting for a final result. It's being delivered, or it's waiting in a queue to be retried. See Queues. |
| Delivered | The recipient's mail server accepted the message. |
| Bounced (soft) | The recipient's server rejected the message for a temporary or policy reason, or it couldn't be delivered before its retry time ran out. See Bounces. |
| Bounced (hard) | The recipient's server rejected the message permanently, for example because the address doesn't exist. |
| Rejected | Mumara ONE's mail server refused the message when it was submitted, so it was never sent. |
Opens and clicks aren't recorded in the delivery log. For every open and click event, with the device and location, use Engagements. Spam complaints are listed on Complaints.
Delivered means the recipient's server accepted the message. Whether it then went to the inbox or the spam folder is decided by the mailbox provider and isn't reported back to senders.
Message details
Click the arrow at the end of a row (Click to expand details) to open everything recorded about the message. Click it again to collapse it.
| Field | What it shows |
|---|---|
| To, Subject, Queued Time, Feed Type, Status | As in the row |
| Time Logged | When the final result, such as the delivery or the bounce, was recorded |
| Return Path | The envelope sender, an address on your bounce domain, where bounces are sent |
| Details | The receiving server's reply, for example 250 2.0.0 OK for a delivery or 550 5.1.1 User unknown for a bounce |
| Recipient MTA | The recipient's mail server |
| Received From | How the message reached the sending server. Support may ask for it. |
| Node IP | The IP address the message was sent from |
| Recipient MTA IP | The IP address of the recipient's mail server |
| Message Size | The size of the message |
| Sending Node | The pool the message was sent through. See Dedicated Pools. |
| Job ID | The sending job. For marketing email, the scheduled campaign send it belonged to. |
| Envelope ID | An internal delivery reference |
| Queue Name | The delivery queue the message went through: the recipient domain and the pool |
| Message ID | The message's unique ID. Quote it when you contact support about a message. |
| Bridge Name | The Bridge the message was sent through, for transactional email. See Bridges. |
| Event | Download Event JSON |
Download Event JSON
Download Event JSON saves the complete record of the message as a .json file named after its status, for example Delivered.json. It includes every field Mumara ONE holds for the message, which is handy for your own troubleshooting or to attach to a support request.
Export the results
Export, next to Search, saves the messages your filters find as a CSV file.
- Set the filters and click Search, so the list shows what you want.
- Click Export. A message confirms that the export has started.
- Open Tools → Exported Files. The file is listed with the type Delivery logs, with a spinner while it's prepared and then a download icon. See Exported Files.
The file has one row per message, with the columns From Name, From Email, To, Subject, Queued Time, Feed Type, Status, Time Logged, Return Path, Details, Recipient MTA, Node IP, Recipient MTA IP, Message Size, Sending Node, Job ID, Envelope ID, Queue Name, Message ID and Bridge Name.
- Each click starts its own export, so clicking twice gives you two files.
- A very large search stops at a maximum number of rows. To export more, split the period into shorter date ranges.
- A cell that starts with
=,+,-or@gets a leading apostrophe, so a spreadsheet doesn't run it as a formula.
How long logs are kept
Delivery logs are kept for as long as your plan's log retention. The durations and dates you can choose on this page stop at that limit, and the Log Retention card on the Dashboard shows how many days your logs are kept. To keep a record of individual messages for longer, use Download Event JSON, or receive every event in your own system with a webhook. To keep logs for longer, move to a plan with longer retention: see Mumara ONE pricing.
Common questions
A customer says they didn't receive my email. How do I check?
- Set Duration to cover the day you sent it.
- Click View more filters, choose Filter By → Recipient Email, is, and enter their address.
- Click Search and look at the Status:
- Delivered: their mail server accepted it. Ask them to check their spam folder and any filtering rules.
- Bounced: expand the row and read Details to see why.
- Received: it's still being delivered. Check Queues for their domain.
- Not listed: check the date range and the address, then check that your application actually sent it, for example in your Bridge's Sending Stats.
Can I search by the Message-ID my application generated?
No. Mumara ONE gives every message its own Message-ID, so the ID your application or the API response holds isn't the one in the log. Search by the recipient and the time instead. See Sending API.
To tie messages to your own records, send an X-Track header with your own reference when you relay the message. Mumara ONE keeps it and returns it as the track field on the delivery, open and click events it posts to your webhooks. This page doesn't search on it, so keep your own index of which reference went to which recipient. See Match events to your own records with X-Track.
Can I download the results as a spreadsheet?
Yes. Search, then click Export; the CSV file appears under Tools → Exported Files. See Export the results.
Why can't I find a message from a few months ago?
It's older than your plan's log retention. See How long logs are kept.
Why does a message show Received for a long time?
The recipient's server is deferring it, and it's waiting in a queue to be retried. Open Queues and read the last error for the recipient's domain.
Can I get these events in my own system as they happen?
Yes. Set up a webhook under Actions → Webhooks to receive delivery, bounce, open, click and complaint events. See Webhooks.
Related pages
- Analytics Summary: all your sending at a glance
- Bounces: bounced messages and their reasons
- Queues: messages waiting to be delivered
- Bridges: the credentials your applications send through