Mimecast Queue Management FAQs

Question 1

How does this skill identify delivery delays?

Accepted Answer

It tracks the 'oldestMessageAge' in both inbound and outbound queues; ages exceeding 300 seconds typically indicate a significant delay or backlog requiring investigation.

Question 2

Can I see why a message is stuck in the queue?

Accepted Answer

Yes, the skill retrieves the 'lastError' field for deferred messages, which contains the specific SMTP error code and reason provided by the recipient server.

Question 3

What is the difference between a 4xx and 5xx error in the queue?

Accepted Answer

A 4xx error indicates a temporary failure where Mimecast will automatically retry delivery, while a 5xx error is a permanent rejection that will eventually result in a bounce notification.

Question 4

Does this skill handle held messages?

Accepted Answer

It identifies messages in the 'held' state due to policy blocks, allowing administrators to review them and cross-reference with the message-tracking skill for release.

Question 5

How can I detect a recipient server outage?

Accepted Answer

By filtering the outbound queue for 'deferred' status and checking if multiple messages to the same destination domain are failing with similar SMTP errors.

Mimecast Queue Management

Key Features

Use Cases

Mimecast Queue Management

Key Features

Use Cases