Notices by disroot (disroot@social.weho.st), page 15

✉️ Emails to gmx.de and web.de blocked for disroot.org users ✉️

Due to a spammer attack originating from our servers disroot.org domain has been blocked by gmx.de and web.de email services.

We've spent last days trying to understand and find a way to eliminate that attack. We hope we've finally managed, but we are still blocked.

https://state.disroot.org/incident/113

@TakuyaSama
What does it offer?

@TakuyaSama
One thing might be u are using username@disroot.org which is wrong and should be just your username, the other could be server details. Have a looks here:
https://howto.disroot.org/en/email/email-clients
(Sorry for not covering kmail yet)

⚙️ Nextcloud upgrade and maintenance work⚙️

This Friday/Saturday night we will be working on our nextcloud instance. This includes nextcloud upgrade to the latest version, upgrading the operating system and php to version 7.2 as well as some other minor changes. This means that nextcloud will be offline for some time within a span of about two hours. We’ll try to plan our work so that the downtimes are as short as possible.
#disroot

https://state.disroot.org/incident/112

@Shadowstreik
Not the same maintenance. This was done by the data center so out of our control (and unannounced) - luckily it didn't last very long :)

@Shadowstreik
If you refer to disroot services going off and on for few minutes earlier, it was due to some maintenance work done at the data center where we have our srevers.

💾 Server update (second attempt)💾

Due to an anomaly that occurred yesterday, where our eyelids closed causing our bodies to go into suspend mode, we have not manage to commence the update operation.

This is why we are attempting to do it today.

So dont get spooked and lets hope @muppeth does not need to go to the datacenter to kickstart the servers like last time :P

#disroot
https://state.disroot.org/incident/111

@arele
It is only temporary block for 15 minutes so it should work fine once you fixed the issue.

If its still blocked send us support_at_disroot.org an email containing your username and we can tell you which app is causing trouble.

🔩 Server update 🔩

Tonight we will be commencing routine weekly OS updates. This weeks update to out host server infrastructure require server reboot. This will cause few minutes downtime, so don't freak out when your favourite services are offline for a moment.
(around 1:30 am Amsterdam Local Time)

https://state.disroot.org/incident/110

@hugo
We are also planning deploying server side mailbox encryption complient with imap.

Amd there is also autocrypt, new standard beinfg adopted and implemented by many mail clients which will do gpg by default will minimal effort. So there might be soon proper trully end to end standard.
@paulfree14

@hugo
We provide custom domain linking and mail aliases to our regular contributors https://disroot.org/en/services/email

As for e2e since we want to stay true to IMA and POP protocol there is not way to also do e2e encryption that said you are free to use gnupg yourself. You can also have a look at easycrypt.co which offers zero knowledge e2e encryption on top of existing mail such as disroot
@paulfree14

@hugo
If you need help, shout! Welcome.
@paulfree14

@orbifx
Fiy. We do custom domains and email aliases for regular contributors.
@ignitionigel @KrokR

@sheogorath
👋
@amiloradovsky

@avizini
We enabled it to lower the mistake rate, but in order to stay consistent (most services we offer does not support it) we would rather stay with just username

@avizini
Yes. We've enabled it to lower the mistake rate😃

Hi guys.

We've now deployed fail2ban which temporarily bans users who mistyped their password (or try to brute force).
Later tonight we will deploy it on remaining services.

Please if you are banned (specially nextcloud) make sure all your apps and all your devices are configured properly (check howto.disroot.org). We mostly see error with people putting username@disroot.org while its only: username!
You're killing our server!

@xosem @donaervilha @Tutanota
Nice to hear! Enjoy!

@asaka @href @sheogorath
👋

🚑 Problems accessing webmail? 🚑

Due to update which overwritten some cusotm values in startup script, our system was not allowing new connections to the server over the default limit. This caused logging in to webmail hard as your request had to wait for free connection.

Thanks to user reports, the issue was spotted and fixed. The fix was added to our automation templates so we should not run into this issue in the future.

Sorry for the hiccup.

https://state.disroot.org/incident/109