Ask Slashdot: Should I Publish My Collection of Email Spamming IP Addresses?
An anonymous reader writes: I have, for a while now, been collecting IP addresses from which email spam has been sent to, or attempted to be relayed through, my email server. I was wondering if I should publish them, so that others can adopt whatever steps are necessary to protect their email servers from that vermin. However, I am facing ethical issues here. What if the addresses are simply spoofed, and therefore branding them as spamming addresses might cause harm to innocent parties? What if, after having been co-opted by spammers, they are now used legitimately?
I wonder if there's a market for all the thousands of webmail addresses that send Slashdot nothing but spam.
I think you answered your own question. The only situation might be to share it privately with others, but publicly, no!
As is, nobody cares about your list. Use an adaptive blacklist and join Project Honey Pot.
You can't shut us down! The Internet is about the free exchange and sale of other people's ideas!
There are hundreds of blacklists out there: https://mxtoolbox.com/problem/blacklist/
No, really, go talk to them... they've been doing just that as a community for a lot longer, and probably have nearly all the stuff on your list and then some.
Quo usque tandem abutere, Nimbus, patientia nostra?
.
Many, many spamming IP addresses are hijacked hosts that are cleaned up eventually. Are you planning to ban those IP addresses permanently?
So I ask the question, how frequently do you plan top re-validate the addresses that are on your list as still spamming?
http://www.projecthoneypot.org...
This is more of an individual asking a yes/no question than a publication asking an inflammatory question just to get clicks.
Also, Yes, you can spoof an IP, which means that you can make packets that you send look like they came from another IP address than they actually did. This may be fine for the one-off UDP packet or such, but email is sent using SMTP, which requires a TCP connection. If your return IP address is spoofed, the 3-way handshake cannot be completed, and therefore, the TCP connection will never be made. If the TCP connection is never completed, then certainly the SMTP email will never be sent.
While the poster's list may contain IPs that were spoofed, none of the spoofed IPs actually SENT any email.
A 1 person maintained blacklist!! Sign me up!
If you think you can spoof a TCP connection you have no business running a RBL.
No sir I dont like it.