AWS ses documentation change
Summary
Removed Spamhaus-specific reference and clarified RBL removal responsibility for managed IPs
Security assessment
Clarifies operational responsibilities but does not indicate security vulnerabilities or introduce new security controls
Diff
diff --git a/ses/latest/dg/faqs-managed-dips.md b/ses/latest/dg/faqs-managed-dips.md index 5ecbcb0e2..3cb0cf4f9 100644 --- a//ses/latest/dg/faqs-managed-dips.md +++ b//ses/latest/dg/faqs-managed-dips.md @@ -15 +15 @@ These FAQs address common misconceptions about the feature's scope and clarify t -If the RBL is offered by Spamhaus, SES can take action to have the address removed from the RBL. However, if your dedicated IP address (managed) is listed in any other RBL, it is not the responsibility of SES and you must request removal yourself directly to the RBL administrator. It's important to monitor your dedicated IPs (managed) by tracking both bounce notifications and SMTP response messages to identify blocks. This monitoring helps protect your email sending reputation and allows you to quickly address any RBL incidents that may occur, ensuring consistent email deliverability. +If your dedicated IP address (managed) is listed in any RBL of recipient mail providers, it is not the responsibility of SES and you must request removal yourself directly to the RBL administrator. It's important to monitor your dedicated IPs (managed) by tracking both bounce notifications and SMTP response messages to identify blocks. This monitoring helps protect your email sending reputation and allows you to quickly address any RBL incidents that may occur, ensuring consistent email deliverability.