Hello,
No, it does not make sense to block all email from Amazon SES. There are many legitimate SES users. They should not be lumped in with the bad users of AWS.
SES is used by some as an outgoing relay for web, mail, and other services hosted within EC2.
SES itself isn't doing the receiving, but some customers choose to use it for outgoing, similar to using ISP smtp relays instead of sending direct to the internet.
Blocking the EC2 ranges with generic PTR's makes more sense. Block unconfigured email leaving AWS like you would block email from residential IP space would be less likely to impact an email services that supports a large number of users.
The logic of blocking SES because it doesn't handle incoming is like blocking smtp.verizon.com becuase it doesn't handle incoming email. It doesn't make sense.
No, it does not make sense to block all email from Amazon SES. There are many legitimate SES users. They should not be lumped in with the bad users of AWS.
SES is used by some as an outgoing relay for web, mail, and other services hosted within EC2.
SES itself isn't doing the receiving, but some customers choose to use it for outgoing, similar to using ISP smtp relays instead of sending direct to the internet.
Blocking the EC2 ranges with generic PTR's makes more sense. Block unconfigured email leaving AWS like you would block email from residential IP space would be less likely to impact an email services that supports a large number of users.
The logic of blocking SES because it doesn't handle incoming is like blocking smtp.verizon.com becuase it doesn't handle incoming email. It doesn't make sense.
