"...complained to Amazon AWS about them to no avail...”
I’m not privy to your specific scenario but if you are using AWS to
provide unmanaged cloud VM services, such as EC2, then why would you
complain to AWS re: any EM issue such as spam, verification, etc.?
That’s not their job - that’s the sysadmins job.
- - -
On 22 May 2021, at 12:41, David D. Scribner wrote:
On 5/22/21 7:41 AM, PGNet Dev wrote:
On 5/22/21 8:25 AM, Simon Wilson wrote:
What am I missing,as a commercial email verification service what
are
they trying to validate?
...
Personally, I consider email-verification services parasites -- and
manage my server accordingly.
I fully agree, and have even complained to Amazon AWS about them to no
avail.
Postfix provides a _great_ set of tools to reject what you wish at
numerous transaction stages. Add to that option to firewall-off IP
addresses -- and enjoy the silence.
Not a choice/action everyone is willing/able to make.
I also fully agree with this, too, and use Postfix to can their
initial
tries (they usually make two attempts from two different IP addresses,
the first to a bogus user at the address, and the second to an "info"
,
"admin" or "postmaster" at the address. To date here are the IPs used
by
briteverify.com that I have marked to drop in my firewall...
## briteverify.com (Amazon AWS)
34.195.68.199
50.19.103.141
50.19.103.149
50.19.105.217
50.19.253.57
52.1.117.226
52.3.174.189
52.203.39.60
54.83.44.163
54.83.54.115
54.197.230.106
54.197.250.255
54.225.108.187
54.235.119.112
107.20.134.42
107.20.207.58
107.20.218.183
107.20.232.98
107.20.235.139
107.20.249.220
107.21.204.157
107.22.212.75
184.72.250.175
184.73.205.138
