3 ms·
Thank you! So, not a targeted attack against me. Any suggestions on how to fight back, if that's possible?
by mwcampbell 5y ago
Thank you! So, not a targeted attack against me. Any suggestions on how to fight back, if that's possible?
- h2odragon 5y agoCrack the relays they're using, hunt for evidence of the previous system they're going through, lather rinse repeat :) I dunno if "fight back" is necessary or desirable here; the places sending the "confirm" messages obviously have a from out somewhere that accepts an address; they'll have seen spurious use of it before and have their own level of concern about that. I dunno who the target would be, if there is one; this could be someone fucking around and thinking they're raining misery or it could be an unconsidered side effect of something so silly we'll never comprehend it. its easy enough to filter and mitigate the impact it has on us.
- mwcampbell 5y agoI decided to try emailing the abuse contact for that IP range, abuse@m247.ro. I realize that the most authentic evidence of the attack would have to come from the Mailman administrators, but I'm doing what I can. I got a prompt response from the abuse team telling me that they forwarded the report to the customer that's using that IP address, and to let them know if it's not resolved within 48 hours. So let's see what happens.
- LinuxBender 5y agoNot to sound negative but they aren't going to do anything. That's a boiler plate response to dismiss complaints. That network has been allowing open proxies, spammers and skiddies since forever.