dovecot control files cause problems

Hi,

When we had the dovecot control files (dovecot-index/username, dovecot-control/username) under /home we realized that the user would be unable to login via IMAP/POP/Usermin if the quota limite was reached.

We then reconfigured dovecot to store them under /var.

Now the problem is that when a Virtualmin user is deleted the dovecot control files remain there. If the user is recreated afterward (after some new servers were added for example) it will get a different user ID but dovecot will try to reuse the existing files and fail due to wrong user ID.

We would need the script that deletes the user to also get rid of the dovecot control files. What's the best way to do it?

Status: 
Closed (fixed)

Comments

This is really a Virtualmin bug .. it should be cleaning up those dovecot index and control files.

I will fix this in the 3.75 release.

You have to determine where the files are. Remmember that their location is configurable no dovecot.conf.

Yes .. my code will extract the location from the INDEX= and CONTROL= settings in dovecot.conf

Automatically closed -- issue fixed for 2 weeks with no activity.

How com this bug got automatically closed? How can I find what's the currently available version of Virtualmin to check if it was updated already?

Bugs get closed if they have been marked as fixed for 2 weeks.

The fix will be included in Virtualmin 3.75, which isn't out yet ... but should be in a few days.

Bugs get closed if they have been marked as fixed for 2 weeks.

The fix will be included in Virtualmin 3.75, which isn't out yet ... but should be in a few days.

Is there a way to check on Virtualmin.com what is the latest available version?

3.75 is out now. Also, if you have a standard Virtualmin install, you will be notified if a newer version is available when you login, on the System Information page.

3.75 is out now. Also, if you have a standard Virtualmin install, you will be notified if a newer version is available when you login, on the System Information page.