Concepts

Logs and troubleshooting

Use TraceMail, Email log analysis, request IDs, and message IDs to troubleshoot API and delivery issues.

  • For resource setup problems, inspect the Management API resource status and validation errors.
  • For email sent from an existing Delivery account, use Send API IDs with Delivery TraceMail.
  • For hosted mailbox traffic, use Email log analysis.

IDs to keep

When using the Send API, first make sure the message was sent with a token from the correct Delivery account. Then always store:

FieldWhy it matters
request_idCorrelates one API request across logs and support investigations.
message_idIdentifies the queued message and helps trace delivery events.
recipient emailHelps search TraceMail and suppression-list results.
your own order/user/campaign IDHelps reconcile API events with your application.

Delivery TraceMail

Use Delivery TraceMail endpoints in the Management API to inspect Delivery sending activity.

TraceMail can help answer questions such as:

  • Was the message accepted by the Send API?
  • Which Delivery account or domain sent it?
  • Was the recipient suppressed?
  • Was the message delivered, bounced, rejected, or delayed?
  • What are the counters for a domain or account?

Useful areas in the reference include:

  • Delivery dashboard.
  • Delivery TraceMail accounts.
  • Delivery TraceMail domains.
  • Delivery TraceMail mailouts.
  • Delivery TraceMail counters.
  • Delivery TraceMail daily statistics.

Email log analysis for Hosting

Use Email log analysis endpoints to inspect hosted email logs:

  • mailbox access logs;
  • incoming mail logs;
  • outgoing mail logs;
  • message folder lookup;
  • PDF export of a specific log.

Email log analysis is for Hosting mailbox traffic. Delivery TraceMail is for Delivery sending traffic.

Basic troubleshooting checklist

Send API request rejected

  1. Check the HTTP status.
  2. Check the error code and message.
  3. Confirm the Delivery account exists and is the right sender for this integration.
  4. Confirm the bearer token belongs to that Delivery account.
  5. Confirm the sending domain is configured for the account.
  6. Confirm the client IP is allowed by token and account allow-lists.
  7. Confirm the account is enabled and has quota.
  8. Confirm the payload respects size and batch limits.

Message accepted but not found in final delivery logs

  1. Confirm the request returned 202 Accepted.
  2. Store and search by request_id and message_id.
  3. Check account/domain assignment and DNS verification.
  4. Check suppression-list behavior.
  5. Check Delivery account status and quota.
  6. If the issue persists, contact support with request_id, message_id, timestamp, sender, and recipient.

Hosting domain or mailbox not active

  1. Check the resource status and status_detail.
  2. Confirm ownership and DNS checks.
  3. Confirm the authenticated user has access to the resource.
  4. For mailbox traffic, inspect Email log analysis access, incoming, and outgoing logs.

Internal queue endpoints

Some operational endpoints exist for Qboxmail staff to inspect and retry failed queue jobs. They are not intended for customer integrations.

For customer integrations, use Send API responses, Delivery TraceMail, resource status, and support when needed.

On this page