Message Center - Receipt And Delivery Views

This article lists the receipt and delivery views available for all inbound, outbound, or internal messages. For every processed message processed, the following views are provided:

  • Receipt View: This displays information relating to when Mimecast accepted/received the message.
  • Delivery View: This displays information relating to when Mimecast delivered the message.

These views are useful when troubleshooting message delivery or investigating a possible spam message. Both views provide the details of the sender, recipient, mail servers, dates, times, and message components. They also show an event (receipt or delivery) that ties in with how and why Mimecast either accepted the message or delivered it to the next mail server.

  • Receipt Event: This is useful to determine why Mimecast accepted a potential spam message.
  • Delivery Event: This can confirm that a message has been delivered to the next hop mail server. It also displays all the policies that matched traffic flow when the message was processed. This helps identify why a message was handled in a certain way or when testing new policies.

Email Receipt & Delivery Views

Transmission Data information is available for all messages processed by Mimecast, including emails in the archive. The date the email was processed determines where the email can be viewed.  These views are split between Received and Delivered with a Compare Views toggle option for further convenience.

Viewing Non-Archived Messages

To view the receipt/delivery view for a non-archived message:

  1. Log on to the Mimecast Administration Console.
  2. Navigate to Message Center | Accepted Messages. A list of messages is displayed.
  3. Click on a Message to open it and select the Transmission Data tab.

See the Email Security Cloud Gateway - Accepted Messages for full details.

Viewing Archived Messages

To view the receipt/delivery view for an archived message:

  1. Log in to the Mimecast Administration Console.
  2. Navigate to Archive | Archive Search. A list of messages is displayed.
  3. Click on the Message to open it. The message details are opened in the side panel.
    • The Message tab (default view) displays the message Summary, Spam Scanning, Message Body and Retention and Audit Information for the message.
    • The Analysis tab displays Spam Scanning, Processing Details and Spam Analysis details for the message.
    • The Header tab displays header details for the message.
    • The Transmission Data tab displays Envelope Details, Remote Server Details, Transmission Information and Transmission Components details for the message.
    • The Policies tab displays Policies Considered at Transmission. 

A message that contains more than one recipient is only listed once in the archive search results. All message recipients are listed in the "Message To" field displayed in the Message Information section of any view.

Transmission Data

Transmission Data information displays the details when Mimecast Received/Delivered the email. Each email has Event details indicating how the message was either Received and/or Delivered by Mimecast.

Transmission Data Received / Delivered Views

Details Description
ENVELOPE DETAILS
From (Envelope) The envelope FROM address (the sender).
From (Header) The Header FROM address (the sender).
To The envelope TO address (the recipient).
Transmission Event How the email was delivered (via MX lookup, routing policy, etc.).
Queue Detail Status Whether the email has been delivered or awaiting re-try, etc.
Processing Server The Mimecast server is responsible for processing the email.
Message Route How the email was received (internal, outbound, internal).
REMOTE SERVER DETAILS
Remote Server The hostname of the remote server that the mail was delivered to.
Remote IP The IP address of the remote server to which the email was delivered.
Remote Greeting The SMTP greeting banner that the remote server presented.
Receipt Acknowledgment The remote server's acknowledgment thread indicates if the data transmission was successful. Important when proving delivery of an email.
TRANSMISSION INFORMATION
SMTP Start Time The date and the exact time that the transmission of the email started.
SMTP End Time The date and the exact time that the transmission of the email ended.
SMTP Total Time The total email transmission time in milliseconds
Transmission Size The cumulative binary size in bytes of each component of the email transmission - including encoding.
Actual Size The binary size in bytes of the data package.
Encryption Information Details whether the email was sent using TLS encryption or not.
TRANSMISSION COMPONENTS
Component Type Components type of the email data package as examined by Mimecast.
Component Name Such as body.txt, transmission.eml, or attached file names.
Hash The hash of each component.
Size The size of each component.
RETENTION AND AUDIT INFORMATION (only seen from an Archive Search under the Message Tab)
Current Purge Date For further details, see the article Email Retention Information
Purge Based On For further details, see the article Email Retention Information
Litigation Hold For further details, see the article Email Retention Information
Original Purge Date For further details, see the article Email Retention Information

Delivery / Receipt Events

Delivery Event Description
Email Generated by File Archiving The message has been processed for File Archiving.
Email Delivery Aborted An obsolete event no longer used by the MTA.
Email Delivery Aborted - Soft Bounce Mimecast has attempted to deliver the message according to the retry schedule, but delivery hasn't been successful, and the message has timed out.
Email Delivery Aborted - Hard Bounce The remote mail server has rejected the message with an SMTP 500 error code. See the Mimecast SMTP Error Codes page for further details.
Email Delivery Aborted - Delivery Hold Dropped An obsolete event no longer used by the MTA.
Email Delivery Aborted - Damaged Email The message was marked as damaged and couldn't be exported or delivered. This may happen due to missing files, addresses, domains, etc.
Email Delivered An obsolete event no longer used by the MTA.
Email Delivered to Mailbox The message was delivered to the user's mailbox on the Mimecast server. Applies to POP3 domains only.
Delivered to Secure Messaging (SM) Isolation Area A  policy was applied to an outbound message, and the message was successfully delivered using SM. Here is how:  Secure Messaging - Definitions & Policies
Email Delivered to Mailbox Forwarding Address The message was forwarded to another mailbox in the Mimecast account. Applies to POP3 domains only.
Email Delivered via MX Resolution The message was delivered using the MX record of the recipient's domain.
Email Delivered to Forwarding Address via MX resolution The message was forwarded to another email address and was delivered using the MX record of the recipient's domain.
Email Delivered via Routing Rule The message was delivered using a Delivery Routing definition and policy in the Mimecast account.
Email Delivered to Forwarding Address via  Forwarding Address definition and policy in the Mimecast account.
Delivered to Space An obsolete event no longer used by the MTA.
Delivered to Space Command
Delivered to Journal The message was journaled and has been processed. The message isn't delivered to a remote server.
Delivery Dropped Message delivery couldn't be completed (e.g., the recipient's server wasn't available), and we won't try delivering the message again. This usually happens after 30 retries.
LFS Delivery Accepted Large File Send was used to transmit a notification with the original email body and a separate set of notifications to access the attachments
Email Received via RWL Greylist Bypass The message was not subjected to greylisting because the server sending the message is listed in Mimecast’s global bypass list.
Email Received - Perimeter Checks Not Set An email received when no Greylisting is enabled and no other policy is triggered, such as Auto-Allow, Permitted Sender, etc., will display Perimeter Checks Not Set.
Was this article helpful?
1 out of 1 found this helpful

Comments

0 comments

Please sign in to leave a comment.