Conversation

Notices

1. Embed this notice
   Codeberg.org (codeberg@social.anoxinon.de)'s status on Wednesday, 05-Jun-2024 23:00:16 JST Codeberg.org

   Hi guys, our email server was locked by the provider due to "abuse" it seems. We're working on it, please be patient.

   Email delivery is currently unavailable.

   • Embed this notice
     Aral Balkan (aral@mastodon.ar.al)'s status on Wednesday, 05-Jun-2024 23:00:13 JST Aral Balkan

     in reply to

     • reidrac

     @Codeberg @reidrac Sorry you have to deal with such bullshit.

   • Embed this notice
     Codeberg.org (codeberg@social.anoxinon.de)'s status on Wednesday, 05-Jun-2024 23:00:14 JST Codeberg.org

     in reply to

     Okay, the whole story, according to our research:
     In Dec 2023, an " IT professional" joined Codeberg with a valid email address. In the meantime, they apparently changed something with their server, because the email address is no longer available.
     They are also a very active contributor to abuseipdb.com, reporting every server which sends mail to nonexistent email addresses on their personal server to.
     This report triggered the abuse department of our ISP to take down our server.
     Thank you!

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Codeberg.org (codeberg@social.anoxinon.de)'s status on Thursday, 06-Jun-2024 20:51:39 JST Codeberg.org

     in reply to

     Blocklists are not only community-maintained resources, but often charge for monitoring and removal services.

     There is an imbalance between small and large operators, and the fact that many people suggested us to just use service from $$company$$ instead of self-hosting emails indicates the terrible situation.

     We have written about our position in detail previously: https://blog.codeberg.org/how-blocklists-prevent-the-internet-to-be-decentralized-and-safe.html

   • Embed this notice
     Codeberg.org (codeberg@social.anoxinon.de)'s status on Thursday, 06-Jun-2024 20:51:41 JST Codeberg.org

     in reply to

     In the responses to this thread, many users started to blame the IT admin who automatically put our IP address to the blocklist.

     Please note that we don't want to blame a single party. Reporting spam and reacting to abuse reports is a good thing.

     However, we are concerned about the fact that automation based on accusations from single parties escalates to regular headache for network operators.

     This is also far from the utopy of an Internet, where everyone can easily host their own services.

     this.ven repeated this.
   • Embed this notice
     Codeberg.org (codeberg@social.anoxinon.de)'s status on Thursday, 06-Jun-2024 20:51:43 JST Codeberg.org

     in reply to

     • netcup

     @netcup The issue is resolved with the help of our provider. Thanks for this and all your patience.

     Most of the email was successfully delivered, only few remains in the queue.

   • Embed this notice
     Codeberg.org (codeberg@social.anoxinon.de)'s status on Thursday, 06-Jun-2024 20:51:44 JST Codeberg.org

     in reply to

     • netcup

     We're still waiting for a response from the abuse department about a potential unlock. We apologize for the inconvenience caused.

     We have blogged about the problem when providers like @netcup (in our case) rely on blocklists as the single source of truth, without second thought or verification.

     This caused much trouble and headache for us, but the person who put us on the list due to a config error will likely never know it happened, after all.

     https://blog.codeberg.org/how-blocklists-prevent-the-internet-to-be-decentralized-and-safe.html