Simply put, this collection allows you to know which emails have left the server, whether they have been delivered correctly, and what happened during the delivery process.

It allows you to investigate delivery incidents, verify that messages have arrived correctly to their recipients, and detect possible problems in email configuration or reputation.

For example, this collection allows you to:

• Verify email deliveries: check if a message has been accepted and delivered by the remote server. This is useful when a user indicates they have sent an email but don't know if it arrived correctly to the recipient.
• Investigate sending errors. When an email cannot be delivered, this collection records information that helps identify the cause of the problem.
• Analyze sending activity: It allows you to know which accounts are sending emails and the volume of activity associated with each one. This is useful for audits or for detecting anomalous behavior.
• Detect possible abuses: An unusual volume of messages sent from an account may indicate compromised credentials or misuse of an email account.
• Review recipients and destination domains: It allows you to identify which recipients or domains emails are being sent to and analyze possible recurring delivery incidents.

• one row = one sent email,
• a sender = who sent the message,
• a recipient = who received the message,
• a status = delivery result,
• a date = when the sending was made,
• a reason = explanation of the result obtained.

If you want to know what happened with a sent email or investigate delivery problems, the appropriate collection is Email History.

Identifies the client or system that initiated the sending of the message.

It normally contains information about the origin of the connection that generated the email.

It can be useful to identify where a specific sending originated.

Indicates the date and time when the delivery result of the message was recorded.

It allows you to reconstruct chronologically the sending activity and analyze incidents in specific periods.

Data type: categorical text

Corresponds to the DSN (Delivery Status Notification) code.

These codes are standards used by mail servers to indicate the result of a delivery.

They help classify whether a message was delivered correctly or if an error occurred.

Unique identifier associated with the email message.

It allows you to locate a specific email and relate different events associated with the same sending.

It is one of the most useful fields for detailed investigations.

Internal identifier used by the mail server during message processing.

It is useful for support tasks and technical investigation.

Data type: categorical text

Describes the reason associated with the delivery result.

When there is an error, this field usually contains relevant information about the cause of the problem.

It is one of the most important fields for diagnosing email incidents.

Data type: categorical text

Indicates the recipient's email address of the message.

It allows you to identify who was supposed to receive the email and analyze incidents associated with specific recipients.

Data type: categorical text

Indicates the remote server responsible for receiving or processing the email.

It is useful for analyzing the message's journey and detecting problems associated with specific servers.

Data type: categorical text

Identifies the remote host involved in the delivery process.

It can be used to investigate incidents related to specific destination servers.

Data type: categorical text

Indicates the authenticated user who made the message sending.

This field allows you to know which email account actually originated the sending.

It is especially useful for audits and activity analysis.

Data type: categorical text

Indicates the sender's email address.

It allows you to identify from which account the message was sent.

Data type: categorical text

Indicates the final result of the delivery process.

Some common examples are:

• sent
• deferred
• bounced
• rejected

This field allows you to quickly identify if the email was delivered correctly or if any problem occurred.

• If a user indicates that an email has not arrived: You can search for the message using the sender, recipient, or message_id and review the status field to check what happened.
  
• If you need to know the reason for a delivery failure: You can analyze the status, reason, and dsn fields to identify the exact cause of the problem.
• If you suspect unauthorized mass sending: You can group by sasl_user or sender to detect accounts with unusual sending volumes.
• If you want to verify that an email was sent correctly: You can review the delivery status and confirm if the remote server accepted the message.
• If you want to analyze recurring problems with a destination domain: You can review the recipient, relay, and remote_host fields to detect error patterns associated with specific servers.