Suggestions for a more privacy conscious email provider

Edwin Pers EPers at
Mon Dec 4 11:19:56 CST 2017

As an anecdotal aside, approx. 70% of incoming portscanners/rdp bots/ssh bots/etc that hit the firewalls at my sites are coming from AWS.
I used to send abuse emails but eventually gave up after receiving nothing beyond "well, aws ip's are dynamic/shared so we can't help you"

-----Original Message-----
From: NANOG [mailto:nanog-bounces at] On Behalf Of Rich Kulawiec
Sent: Monday, December 4, 2017 2:27 AM
To: nanog at
Subject: Re: Suggestions for a more privacy conscious email provider

On Sun, Dec 03, 2017 at 05:08:33PM +0000, Filip Hruska wrote:
> I personally run my own mail server, but route outgoing emails via Amazon
> SES. 

Not a good idea.  Amazon's cloud operations are a constant source of
spam and abuse (e.g., brute-force SSH attacks), they refuse to accept
complaints per RFC 2142, and -- apparently -- they simply don't care to
do anything about it.  I've had SES blacklisted in my MTA for years (among
other preventative measures) and highly recommend to others.


More information about the NANOG mailing list