Delivery Analytics

MailFleet delivery analytics are built from logs collected from monitored servers. The page separates two concepts:

• Report range: which stored data you are viewing.
• Collection schedule: when MailFleet connects to servers to collect new logs.

Changing one does not change the other.

Prerequisites

• At least one server asset with monitoring enabled
• Authorized SSH connection information
• A supported server type and log format
• Mail activity on the remote server

Collect logs now

1. Open Delivery analytics.
2. Select a report range: today, 3 days, 7 days, 30 days, or a custom range up to 30 days.
3. Choose all servers or one server.
4. Select Collect now.
5. Watch the connected/total progress.
6. Wait for collection to finish.
7. Review the refreshed metrics.

MailFleet avoids starting another collection while one is already running.

Configure automatic collection

1. Turn on Automatic collection.
2. Choose the available frequency, such as 5 minutes, 15 minutes, or 1 hour.
3. Keep the application and network available when collection should run.
4. Review the last-collection time.

Automatic collection does not change the selected report range.

Read the KPI strip

The summary can include:

• sent;
• delivered;
• deferred;
• rejected;
• hard bounced;
• other failures;
• success rate;
• change compared with the previous equal-length period.

Interpret a rate only after checking the selected range, server filter, and whether collection is current.

Analyze trends

Switch between:

• Volume: total and delivered counts over time.
• Rate: delivery success percentage over time.

The x-axis uses hours for short ranges and dates for longer ranges.

Review bounce categories

MailFleet groups recognized failures into:

• hard bounce;
• soft bounce;
• blacklist;
• authentication failure;
• rate limit;
• content filter;
• unknown.

Expand a category for its explanation. Unknown means the available log text did not match a more specific category.

Compare domains and servers

Recipient domains shows sending volume and bounce rate for the leading domains.

Server performance compares volume, success rate, and failure count by server. Lock the view to one server when investigating a node.

These metrics describe recorded delivery attempts; they do not guarantee inbox placement or recipient engagement.

Export

1. Select the time range and server scope.
2. Open Export.
3. Choose KPI summary, trend, bounce detail, server performance, and/or recipient domains.
4. Export the current range as CSV.
5. Store the file according to your organization's data policy.

Troubleshooting

No data

Run Collect now, confirm monitoring is enabled, and verify that the remote server has mail logs for the selected range.

A server is skipped

Check SSH credentials, connectivity, monitor status, and server type.

Collection stops or reports an error

Test the asset connection, confirm log permissions and available disk space, then retry a small server scope.

Next steps

• Inspect server assets
• Configure notifications and troubleshooting