I am getting the following error when trying to start it: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: Missing ‘}’ (section started at /etc/dovecot/dovecot.conf:107) I did not touch Dovecot configuration. And Virtualmin did not start automatically after reboot when one …

Hi, [image] eug: And Virtualmin did not start automatically after reboot when one of recent updates of Usermin happened. I had to start it with command: “service webmin start” That doesn’t look good. However, we believe that all Dovecot issues are sorted out with Virtualmin 6.10+ for new ins…

Looks like issue happened because I did manual certificate renewal with certbot, and not because of updates. The end of /etc/dovecot/dovecot.conf is the following: It should look like this: local_name domain.com { ssl_cert = </home/user/ssl.combined ssl_key = </home/user/ssl.key } local_n…

Heya. I’ve had the same error, I hope it’s not perceived as thread hijacking. In my case, I didn’t mingle with certbot, however I noticed that the dovecot’s conf file began being messily wrong at a precise point: the part where, approx. a month before the latest update, I manually replaced .cert w…

Oh boy. For unrelated reasons, I requested new certificates in letsencrypt for a domain, and after this, I noticed dovecot was down again. This time I have detailed “evidence” of the maximum mixup that happened in the dovecot.conf file, if it may help, here is what it became afterwards: https://p…

Get rid of the ssl_ca lines. They are never right. They should all be gone. Really.

Mine became buggered up today with the same issue as eug, must be a bug of some sort. Thanks for posting your resolution helped me!

I am facing the same issue. I did resolve this issue yesterday by manually adding missing “}” where required but today it looks like it has happened again!

I too am getting dovecot.conf corrupted on multiple servers with Virtualmin, missing a } after random host entries. Easy enough to fix by editing the config file and putting the } back in, but annoying as it prevents dovecot restarting.

Also have the same problem, I do use the lets encrypt system and up until recently it has not casued this issue. I will backing up the dovecot.conf manually, and pre fixing it before any reboots now so I can copy it back stright after.

After recent update Dovecot IMAP / POP3 Server stopped working

Virtualmin

Joe September 4, 2020, 12:13am 11

If you’re still seeing a problem with Dovecot with Webmin 1.955 and Virtualmin 6.12, it has to be something different (I think), assuming you read the release announcement and did what was recommended.