> Hello list, may I pick the accumulated wisdom and experience?
>
> any useful traffic from these subnets:
>
> 18.32.0.0 - 18.255.255.255 Amazonaws.com
18.236.68.227 has been in our block-and-forget list since
2021-Jul-12 for excessive/high-bandwidth POP3 and IMAP4 hacking, and
for being a spam sewer.
> 34.4.5.0 - 34.63.255.255 Googleusercontent.com
We don't currently block anything from this range.
> I am thinking of just dropping them at the firewall and call it a day.
> I have not yet advertised my super clean new mail server and there is
> already a stream of abuse.
>
> also from:
>
> 64.62.197.0/24 shadowserver.org
We don't currently block anything from this netblock.
> 141.98.10.0/24 hostbaltic / tiscali.it?
141.98.10/24 has been in our block-and-forget list since 2022-Mar-21
for SMTP hacking (from Lithuania, and still located there according
to RDAP/WHOIS).
> I know rspamd could deal with that, but in the cloud compute resources
> have cost and I am looking for the most radical, simple,
> compute-efficient solution to keep bad networks out. Are there
> community-maintained efforts, like the
> https://github.com/StevenBlack/hosts for hosts?
I've been thinking about building something like this as a hobby,
but haven't had the time. (I also don't want to use GitHub for it
due to problems I have with their Terms-of-Service that circumvent
open source licensing {when I checked into it a few years ago}.)
> Thank,
>
> Yuv
> --
> Ontario-licensed lawyer
>
> _______________________________________________
> mailop mailing list
> [email protected]
> https://list.mailop.org/listinfo/mailop
--
Postmaster - [email protected]
Randolf Richardson, CNA - [email protected]
Inter-Corporate Computer & Network Services, Inc.
Vancouver, Beautiful British Columbia, Canada
https://www.inter-corporate.com/
_______________________________________________
mailop mailing list
[email protected]
https://list.mailop.org/listinfo/mailop
