Most of the Amazon SES IP blacklisted by SpamCannibal

Re:Most of the Amazon SES IP blacklisted by SpamCannibal by _asciiker_ on Monday April 21, 2014 @10:56AM (#7621322)

You have all the right to mark it as SPAM of course. What I'm trying to get across here is that IP blocking is a bad solution. There are many cases where several domains share the same IP, specially with the shortage. So if domainA.com sends spam, why should domainB.com mail delivery on the same IP suffer from it?

[ Parent | on HN ]

Re:Most of the Amazon SES IP blacklisted by SpamCannibal by dredmorbius on Monday April 21, 2014 @11:10AM (#7621420)

Police the motherfuckingbejesus out of your users.

If it costs you when your IP is blocked, insist on a deposit that's forfeit in the event of spamming.

Sadly, I've worked for shops with poor practices. How bad? Sending thousands of emails to domains which no longer existed (let alone stale accounts at existing mail service providers). Simply not a priority.

[ Parent | on HN ]

Re:Most of the Amazon SES IP blacklisted by SpamCannibal by DanBC on Monday April 21, 2014 @11:38AM (#7621585)

You would have hated SPEWS.

[ Parent | on HN ]

Re:Most of the Amazon SES IP blacklisted by SpamCannibal by kaoD on Monday April 21, 2014 @11:08AM (#7621408)

> So if domainA.com sends spam, why should domainB.com mail delivery on the same IP suffer from it?

Because the mail servers both share seem to allow sending unsolicited email, i.e. spam. You're the one responsible for terminating the spamming user.

[ Parent | on HN ]