toad.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon server operated by David Troy, a tech pioneer and investigative journalist addressing threats to democracy. Thoughtful participation and discussion welcome.

Administered by:

Server stats:

211
active users

#dovecot

2 posts1 participant0 posts today

I don't understand. Dovecot refuses to issue the correct SSL cert. I've checked and triple checked the file name in /etc/dovecot/conf.d/10-ssl.conf. I've restarted the service multiple times and even rebooted.

Apache issues the correct cert. They are using the exact same files.

perplexing.

CLI command to check dovecot:
openssl s_client -connect mail.heerssen.net:465

And Apache
openssl s_client -connect mail.heerssen.net:443

Replied in thread

@marcuwekling Großartige Idee! Ich bin (eh schon) dabei! 🙃 #dutgemacht #ididit

Hier was ich derzeit schon so nutze:

- Eigener Mailserver #postfix #clamav #rspamd #roundcubemail #dovecot
- Notebooks auf #Linux
- #pfsense Firewall
- #thunderbird

Selber gehostete freie Dienste/Software derzeit:
- #Nextcloud
- #PaperlessNGX
- #Peertube
- #HomeAssistant
- #Mastodon
- #Matrix
- #Wordpress

Fremdgehostete freie Dienste:
- #pixelfed
- #bigbluebutton
- #letsencrypt

Leider kann ich meinen Windowsrechner noch nicht loswerden #gamer - aber das kommt bestimmt auch noch irgendwann... 🤞

That whole #dovecot breaking update (and from what I've seen the unreasonable pro version, at least for small setups) makes me question self-hosting my mail server…
I'm fine with investing time to setup something the first time - but updates (especially not minor) should never be breaking… - neither should they require quiet some time investment imho…
#SelfHosting #mailserver

Since Dovecot 2.4 is dropping replication, I'll definitely need to rework my mail servers and those for BSDMail. I think I'll be going back to Cyrus, which I last used over 20 years ago. The problem is my memories have long faded, so it'll be like studying it again from scratch. And that makes me happy, because it'll be like learning something totally new!

Special thanks to @h3artbl33d for the heads up!

Replied in thread

@oceanhaiyang

This is just after a reboot.
CPU: Intel Core 2 Quad Q9550 (4) @ 2.545GHz
Memory: 0.70GiB / 3.70GiB (18%)
Disk (/): 23G / 40G (61%)

It is running #Nextcloud, and so effectively does the cloud storage, calendar & contacts. I've been running this since before Nextcloud (I used to use OwnCloud).

This and SSH is all that is accessible outside of home. Both have MFA and China is currently blocked (I mean to expand this list).

However it also handles DHCP & DNS for the home LAN using #dnsmasq and I use it as an email archive (#dovecot). There is a functional #fetchmail install, but this is currently switched off.

It also has my #Subversion archive. That stays until I get around to having a proper look at #git.

With #USA going downhill I do have plans to get it do do more - but I'm playing with using #docker containers so if anything gets hacked, that will minimise the damage. I currently have too much running on the raw iron.

I'm using #borg for backups onto an external HDD that then occasionally is copied elsewhere (physical media off-site).

J’ai découvert que j’avais 2,8 millions de mails dans un seul dossier IMAP.
Je répète : deux millions. Huit cent mille.
Merci YunoHost pour les rapports de diagnostic par mail…

J’ai tout purgé en SSH depuis ma voiture, en 5G, pendant que la sono tournait.
Maintenant, iOS Mail et Apple Intelligence peuvent bosser sans convulser.

Je n’administre pas un serveur. Je dompte un fauve 🦁.

If you're planning on upgrading #Dovecot from 2.3 to 2.4, better take some days off. Did it yesterday evening and it broke in SO MANY WAYS! I don't know what they were thinking, the upgrade guide is... not very good and there is no config converter. The new config syntax is confusing (but that might only be me) and the daemons run with different permissions it seems? I had trouble with daemons not being able to access config files.

Down side of running #fail2ban: when you or one of the people you provide email service for gets a new device. Invariably, it means doing a "what's my IP" for the new device, then logging into the mail server and doing:

fail2ban-client set dovecot unbanip  
fail2ban-client set postfix unbanip  
fail2ban-client set postfix-sasl unbanip  
Before sending and receiving works. It's even more-problematic when the person with the new device doesn't remember the password they were using on their prior devices.

#linux
#postfix
#dovecot

#eMail #selfHosting gurus: I am looking for the simplest possible way to host myself a mailbox I can add to my email clients (Thunderbird, phone, etc.) as usual, so I can move mails there to free up space on the 3rd party "real" emails, then back them up separately on my server.

I do not want receiving or sending emails to work. Just an IMAP or whatever box I can shove emails in the face by dragging them in Thunderbird or with a script.

Ideally available in :nixos: #NixOS

#dovecot? 🤔

I just found out that Dovecot 2.4 is a crippled version of Dovecot 2.3: no more clustering support, the director function has been removed. If you want to do clustering now, you'll have to buy a Pro license.

https://doc.dovecot.org/2.4.0/installation/upgrade/2.3-to-2.4.html#removed-features

So, although I've used Dovecot for years, both private and for work, it seems like this is the end of the line for me.

At the same time I see what @Stalwart Labs can do. Yes, clustering, for one. And a whole lot more, including bayesian classification, analysis of DMARC reports and even a reputation database.

I'm really impressed by what it can do. Bit hesitant about the fact that it's still only version 0.11.5 though, smells alpha...

Looks like Stalwart is the future for me.

https://stalw.art/docs/cluster/overview

#Dovecot #Stalwart #E-mail #DMARC
doc.dovecot.org2.3 to 2.4 | Dovecot CEDovecot CE Documentation

I seem to have a #DNS problem (unheard of, right?).
I've got #nginx working with #HTTPS, using #certbot, and there's an A record that points at the IP address of the server. So I can go to mydomain.com and it's all dandy (thank you @eff).
Now I want a TLS certificate for the #Dovecot mail server. I've set up a virtual server for mail.mydomain.com like this:
```
server {
listen 80;
listen [::]:80;
server_name mail.mydomain.com;

root /usr/share/nginx/html/;

location ~ /.well-known/acme-challenge {
allow all;
}
}
```
But when I run certbot I get this:
```
NoRecords
Fatal
No valid A or AAAA records could be ultimately resolved for mail.mydomain.com. This means that Let's Encrypt would not be able to connect to your domain to perform HTTP validation, since it would not know where to connect to.
No A or AAAA records found.
```
On my domain registrar's dashboard it says that I don't need to set up a MX record if I have only one mail server and it is on the same IP address as my Domain Record. But I'm thinking the certbot error doesn't sound like it's looking for an MX record.
Should I temporarily make a subdomain record for mail.mydomain.com?
#ImSoConfused #AskFedi #FediTechSupport