The current version of Dovecot uses a different config type than the config automatically written with Webmin; so for example editing Dovecot ssl options with Webmin breaks Dovecot. Please update this so Webmin functions correctly with Dovecot.
We believe it was fixed in Webmin 1.955. If you still see this issue with the latest version, please provide steps to reproduce it, and show how your dovecot.conf file looks before and after the save.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok to duplicate the problem start with a blank conf file or with one line of "#" only on first line. Then edit the conf with webmin for example: edit the potocal then save once, then do a second edit, and add the cert files with diretory and cert info, this ads the incorrect old conf tags (ssl_cert_file , ssl_key_file ). In webmin 1.955.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
We believe it was fixed in Webmin 1.955. If you still see this issue with the latest version, please provide steps to reproduce it, and show how your dovecot.conf file looks before and after the save.
Ok to duplicate the problem start with a blank conf file or with one line of "#" only on first line. Then edit the conf with webmin for example: edit the potocal then save once, then do a second edit, and add the cert files with diretory and cert info, this ads the incorrect old conf tags (ssl_cert_file , ssl_key_file ). In webmin 1.955.
Angel, Dovecot itself seems to save directives correctly. I have just tested it over again upon your request.
Perhpas, the issue that you're seeing is related to a browser auto-filling fileds with old, previously used values?
What Dovecot version your server is running there?
Okay, I see an issue that
ssl_ca_fileis indeed added instead ofssl_cafor Dovecot v2. - this is confirmed.Does it also happen with
ssl_cert_fileandssl_key_filedirectves - that I cannot reproduce yet.Okay, I really found an issue after looking at the code.
Okay, fixed.
You are welcome to apply the patch and give it a try.
Thanks for reporting.