Types of Events

The internal database identifier for this event.

A universally unique identifier for this event. If you want to track an identifier for events to prevent duplicate event handling, this is the value you should use.

The type of event (in this case, bounce_lite).

The time the event was generated as a UNIX timestamp.

The value of the server_id configuration directive.

The code of the bounce rule that this bounce matched.

The text within the bounce message that caused bounce_code to be determined. This text will begin at the first newline before the matched text and end at the newline after the matched text. This text may be quoted-printable encoded, if the original message was quoted-printable encoded.

Whether or not this bounce represents a synchronous bounce (i.e. was it generated during the delivery attempt’s SMTP conversation).

The email address that received this bounce. This is not the original message recipient email address, instead this is the email address to which this bounce was delivered.

If lite_bounce_processor_include_report_text is not disabled, this will be the full text of the bounce message as it was received by GreenArrow.

The internal database identifier for this event.

A universally unique identifier for this event. If you want to track an identifier for events to prevent duplicate event handling, this is the value you should use.

The type of event (in this case, scomp_lite).

The time the event was generated as a UNIX timestamp.

The value of the server_id configuration directive.

The recipient address of the email that generated the complaint, as included in the ARF complaint report. This is information submitted as part of the FBL complaint and may not always be accurate. Also, due to forwarding or wildcarding, this may not be the email address to which you actually sent. Some FBLs will anonymize the recipient email address. For these reasons, we recommend that you instead rely on a custom header to encode recipient information.

This field is typically parsed from the (optional) Original-Rcpt-To header in ARF complaint reports and may not always be present. The first Original-Rcpt-To header is used if multiple copies are found. If Original-Rcpt-To is not present in the report and the X-HmXmrOriginalRecipient header is included in the original message section of the report, then the email address from the X-HmXmrOriginalRecipient header will be used.

The name and version of the software program that generated the report. This is information submitted as part of the FBL complaint and may not always be accurate.

The headers parsed from the complaint message as configured by the directive lite_fbl_processor_headers. Each key of the hash is the configured header name, each value is an array of strings representing each instance of that header in the original message (as received back to GreenArrow in the complaint report).

The email address that received this complaint. This is not the original message recipient email address, instead this is the email address to which this spam complaint was delivered.

If lite_fbl_processor_include_report_text is not disabled, this will be the full text of the FBL report message as it was received by GreenArrow.

The MAIL FROM / Return-Path address (RFC5321.MailFrom) used to send the email that generated the complaint, as included in the ARF complaint report. This is information submitted as part of the FBL complaint and may not always be accurate. We recommend that you instead rely on a custom header to encode sender information.

This field is parsed from the (optional) Original-Mail-From header in ARF complaint reports and may not always be present. The first Original-Mail-From header is used if multiple copies are found.

The type of event (delivery_attempt).

The time that the delivery attempt happened, in seconds past the Unix epoch.

Server ID as configured by server_id.

A unique identifier for this event.

The email address that this message was to.

The identifier for the mailing list that this message is a part of.

The internal identifier for the send.

The click tracking ID is specified using the X-GreenArrow-Click-Tracking-ID header and can be used to trace an event back to a specific message.

The time that the delivery attempt happened, in seconds past the Unix epoch.

local if the delivery attempt is to a local mailbox or remote if the delivery attempt is to a remote mail server.

Result of this delivery attempt. Can be success, failure, failure_toolong, deferral or connmaxout.

0 if this is the first delivery attempt and 1 otherwise.

Internal unique ID of the message. IDs are not repeated unless the system clock goes backward. This is not the same as the Message-ID.

The Return-Path of the message. This is also called the envelope sender, MFROM address, bounce address, or RFC5321.MailFrom.

The identifier for the VirtualMTA / Mail Route of this message. This is set at the time of message injection.

This field determines what IP address the message is delivered from.

mtaid may be altered at the time of injection by set_virtualmta on header_pattern. If the VirtualMTA is later changed on retry due to the evaluate_on_retry option, this field will still contain the VirtualMTA as determined at the time of injection.

Primary key of the VirtualMTA that the message is assigned to.

The name of the VirtualMTA that the message is assigned to.

The time that the message was injected into GreenArrow’s queue, in seconds past the Unix epoch.

The success, failure, or deferral message for this delivery attempt. This message will be in the Queue Logfile Format with non-UTF8 characters removed.

Primary key of the VirtualMTA that the delivery attempt took place with. This can be, but isn’t always the same as the mtaid. For example, if mtaid is a Routing Rule, then outmtaid will be the VirtualMTA within that Routing Rule that was actually used for the delivery attempt.

The outgoing IP address used for this delivery attempt (see note below).

The hostname used for this delivery attempt’s SMTP conversation (see note below).

The name of the IP address used for this delivery attempt (see note below).

Internal use Studio feature that’s not yet documented.

Blank if the delivery attempt took place using an SMTP Relay Server or the default Throttling Rule. Otherwise, it contains the ID of the Throttling Rule that was used when making the delivery attempt.

The hostname to which this delivery attempt occurred (whether or not it came from an actual MX record).

The IP address to which this delivery attempt occurred (whether or not it came from an actual MX record).

The first email address in the From header as it was originally injected into GreenArrow.

A JSON object containing the values of the headers as configured in the log_header configuration directive.

Folded headers will simply contain the folding newlines/whitespace. As a header may be included in an email multiple times, the value of the JSON object is an array of strings.

The size of the message (in bytes), if loaded from storage.

CSV list of SMTP timings of the delivery attempt. See the log_smtp_timings configuration directive for more information.

This is the bounce code for this delivery attempt. Blank when status is success or connmaxout.

The SMTP or HTTP client IP address that injected the message into GreenArrow.

If a SimpleMH mail class was used for this message, this is that mail class.[^1]

If a SimpleMH InstanceID was specified for this message, this is that InstanceID.[^1]