Skip to content

Conversation

@Khoa-bit
Copy link

@Khoa-bit Khoa-bit commented Jul 20, 2024

Description

This PR introduces a new public field HasDSNExt to the email struct, which was previously private and named hasDSNExt. This change provides a way to determine whether an email was sent with "Fire and forget" or if it has been delivered.

Changes

  • Struct Field Update: Renamed the private field hasDSNExt to the public field HasDSNExt in the email struct.
  • Functionality: Exposed HasDSNExt to allow users to check if the email delivery status is tracked.

Motivation

The motivation for this change is to enhance the visibility of the delivery status flag for users who need to confirm whether an email was sent with "Fire and forget" semantics or if it has been delivered.

Impact

  • Public API: This change affects the public API by exposing the previously private field.
  • Backward Compatibility: No breaking changes. Existing functionality remains intact, but users now have access to the delivery status flag.

@Khoa-bit Khoa-bit changed the title Expose HasDSN Flag to know if we send with "Fire and forget" or "Email delivered" Expose HasDSN Flag to determine if email sent with "Fire and forget" or "has been delivered" Jul 20, 2024
@Khoa-bit Khoa-bit changed the title Expose HasDSN Flag to determine if email sent with "Fire and forget" or "has been delivered" Expose HasDSNExt Flag to determine if email is sent with "Fire and forget" or "has been delivered" Jul 20, 2024
@Khoa-bit Khoa-bit changed the title Expose HasDSNExt Flag to determine if email is sent with "Fire and forget" or "has been delivered" Expose HasDSNExt Flag to determine if email is sent with "Fire and forget" or "Has been delivered" Jul 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant