AWS ses documentation change
Summary
Clarified DNSBL monitoring responsibilities between SES shared IPs and dedicated IPs
Security assessment
Specifies that customers must handle delisting for dedicated IPs themselves, but does not address a specific security vulnerability or add new security features
Diff
diff --git a/ses/latest/dg/faqs-dnsbls.md b/ses/latest/dg/faqs-dnsbls.md index 5f43d2931..f83302fff 100644 --- a//ses/latest/dg/faqs-dnsbls.md +++ b//ses/latest/dg/faqs-dnsbls.md @@ -33 +33 @@ Our systems look for signs of abuse. If we detect sending patterns or other char -We actively monitor DNSBLs that could impact delivery across the entire Amazon SES service, or that could impact the ability to send email to recipients who use major email providers, such as Gmail, Yahoo, AOL, and Hotmail. The DNSBLs offered by Spamhaus fall into this category. When one of our IP addresses appears on a list that meets either of these criteria, we take immediate action to have that address removed from the DNSBL as quickly as possible. +For SES shared IPs, we actively monitor DNSBLs that could impact delivery across the entire Amazon SES service, or that could impact the ability to send email to recipients who use major email providers, such as Gmail, Yahoo, AOL, and Hotmail. The DNSBLs offered by Spamhaus fall into this category. When one of our IP addresses appears on a list that meets either of these criteria, we take immediate action to have that address removed from the DNSBL as quickly as possible. @@ -36,0 +37,2 @@ We don't monitor DNSBLs that are unlikely to impact delivery across the entire A +For dedicated IP address (managed or standard) listed in any RBL of recipient mail providers, it is not the responsibility of SES to delist the IPs and you must request removal yourself directly to the RBL administrator. +