Skip to main content

ISESV2Bounce

Interface in AWS.SESV2

Interface for SESV2 Bounce.

Properties​

BounceSubType​

property BounceSubType: string

The subtype of the bounce, as determined by SES.

This property provides more specific categorization of the bounce beyond the general bounce type. The subtype offers additional detail about the nature of the delivery failure, helping to distinguish between different scenarios within the same bounce type category. Bounce subtypes provide granular information that can be used to implement more sophisticated bounce handling logic, such as determining whether to retry delivery or permanently suppress the recipient address based on the specific failure reason.

BounceType​

property BounceType: string

The type of the bounce, as determined by SES.

This property categorizes the bounce into one of three main types that indicate the nature and permanence of the delivery failure. Valid bounce types include:

  • UNDETERMINED – The bounce type could not be determined from the bounce message.
  • TRANSIENT – A temporary failure that may be resolved by retrying delivery later (soft bounce).
  • PERMANENT – A permanent failure indicating the email address is invalid or unreachable (hard bounce). Understanding bounce types is critical for sender reputation management. Permanent bounces should result in immediate suppression of the recipient address, while transient bounces may warrant retry attempts with appropriate backoff strategies.

DiagnosticCode​

property DiagnosticCode: string

The status code issued by the reporting Message Transfer Authority (MTA).

This property contains the technical diagnostic code provided by the receiving mail server that explains the specific reason for the bounce. The diagnostic code is extracted from the Delivery Status Notification (DSN) when available. This field only appears if a delivery status notification was attached to the bounce and the Diagnostic-Code was provided in the DSN. The codes typically follow standard SMTP response code formats and provide detailed technical information about the failure. Diagnostic codes are valuable for technical troubleshooting and can help identify specific mail server configurations, policy restrictions, or infrastructure issues that caused the delivery failure.