63
Do any of you bother writing abuse emails?
(lemmy.fmhy.ml)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 03 Jul 2023
63 points (98.5% liked)
Selfhosted
39677 readers
160 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
I’ve actually done this for a Microsoft owned IP before. Someone was Wordpress-scanning a particularly fragile application of one of my clients (which was not Wordpress) which was causing it to fall over. The scan stopped within an hour of sending the abuse email.
Edit to add: I used to work in a NOC for a tier 1 ISP. We had an “abuse department” (a couple people) that investigated these and opened tickets with the NOC. I’ve emailed customers and disconnected circuits as a result of abuse emails, so I wouldn’t say they’re totally useless, but I’m sure it depends on the company involved.
I also worked at an ISP for a period, actually worked at two different ones. The first one let the abuse mailbox go full, because no one was reading it. The second they were reading it, but mostly to find new places to download stuff :D
Wait, what? To their abuse@microsoft.com or whatever email (whatever's listed in whois)?
I've had Azure IPs absolutely hammering my VoIP server and absolutely none of the reports I sent were even acknowledged. Ended up just blocking the entire Azure CIDR range in the firewall.
AWS, OTOH, got back to me within about an hour and a resolution within 3.
Yep! Just for whatever the abuse contact was in whois. Could have been coincidence, or maybe just whoever was on shift in Azure town at the time. I don’t remember if I got a response or not from MS.