Dovecot permission error on new production server (moved from previous server) - Please help

We launched our new server tonight using Virtualmin Pro and wouldn't you know it one of our main webmail clients has a permission issue accessing their mail through the default (using installed script) roundcube webmail. Using Usermin is no problem and other users do not have this problem only so far one user.

From the mail log:

Oct 29 22:53:23 ns-atl2 dovecot: imap(customerservice-customer.com): Error: open(/var/lib/dovecot-virtualmin/control/customerservice-customer.com/.INBOX/dovecot-uidlist) failed: Permission denied Oct 29 22:53:23 ns-atl2 dovecot: imap(customerservice-customer.com): Error: lstat(/var/lib/dovecot-virtualmin/control/customerservice-customer.com/.INBOX/dovecot-uidlist.lock) failed: Permission denied Oct 29 22:53:23 ns-atl2 dovecot: imap(customerservice-customer.com): Error: file_dotlock_create(/var/lib/dovecot-virtualmin/control/customerservice-customer.com/.INBOX/dovecot-uidlist) failed: Permission denied (euid=666(customerservice@customer.com) egid=616(customer) missing +x perm: /var/lib/dovecot-virtualmin/control/customerservice-customer.com, dir owned by 548:616 mode=0700)

Any guidance would be great.

Thanks, Andrew

Status: 
Closed (fixed)

Comments

Title: Dovecot permission error on new production server (moved form previous server) - Please help » Dovecot permission error on new production server (moved from previous server) - Please help

Turns out I am just having a ton of bad luck with backup and restores. I deleted and restored this virtual twice with still the same permissions issues so decided to use the feature "re-allocate UIDs and GID" (its default is no) and that solved my issue. The customer can once again login to their mail now using roundcube script.

I agree, it does look like you're running into a variety of issues there, sorry about all the trouble!

I'm glad you were able to get that working. It definitely shouldn't be necessary to re-allocate the UIDs, but it's excellent that it's working now.

Please let us know if you run into any further issues!

Status: Active » Fixed