mailbox.auto ignores dovecot-uidlist.lock
I'm trying to lock down a maildir from modifications using dovecot-uidlist.lock, but when a user with mailbox.auto = create logs in, then the folder is created regardless of dovecot-uidlist.lock existing or not.
Is there no way to prevent dovecot from touching anything in a maildir folder?
-- Tom
On 18.05.2016 12:44, Tom Sommer wrote:
I'm trying to lock down a maildir from modifications using dovecot-uidlist.lock, but when a user with mailbox.auto = create logs in, then the folder is created regardless of dovecot-uidlist.lock existing or not.
Is there no way to prevent dovecot from touching anything in a maildir folder?
Could you provide more information, like:
what you are trying to achieve what did you do what you configuration looks like what version you are using
Aki
On 2016-05-18 11:52, Aki Tuomi wrote:
On 18.05.2016 12:44, Tom Sommer wrote:
I'm trying to lock down a maildir from modifications using dovecot-uidlist.lock, but when a user with mailbox.auto = create logs in, then the folder is created regardless of dovecot-uidlist.lock existing or not.
Is there no way to prevent dovecot from touching anything in a maildir folder?
Could you provide more information, like:
what you are trying to achieve what did you do what you configuration looks like what version you are using
I'm trying to move all files and folder from /foo.com/bar/ to /foo.com/bar/Maildir without moving .dovecot.svbin and .dovecot.sieve etc. (homedir files)
So I wanted to lock the folder, kick the user and the move the files/folders, but the user logs in just after I kick him and so the auto-folders are created and my migration script fails, locking the folder with dovecot-uidlist.lock and maildirlock does not work in this case.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wed, 18 May 2016, Tom Sommer wrote:
On 2016-05-18 11:52, Aki Tuomi wrote:
On 18.05.2016 12:44, Tom Sommer wrote:
I'm trying to lock down a maildir from modifications using dovecot-uidlist.lock, but when a user with mailbox.auto = create logs in, then the folder is created regardless of dovecot-uidlist.lock existing or not.
Is there no way to prevent dovecot from touching anything in a maildir folder?
Could you provide more information, like:
what you are trying to achieve what did you do what you configuration looks like what version you are using
I'm trying to move all files and folder from /foo.com/bar/ to /foo.com/bar/Maildir without moving .dovecot.svbin and .dovecot.sieve etc. (homedir files)
So I wanted to lock the folder, kick the user and the move the files/folders, but the user logs in just after I kick him and so the auto-folders are created and my migration script fails, locking the folder with dovecot-uidlist.lock and maildirlock does not work in this case.
Check out:
http://wiki2.dovecot.org/Authentication/RestrictAccess?highlight=%28user%29|%28deny%29
"deny passwd-file"
add user into this file, doveadm auth cache flush, # force reread credentials kick user migrate remove user from file either restart with next user or flush cache
Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1
iQEVAwUBVz1YPXz1H7kL/d9rAQK4nwf/aBuFTOhHS+hrGZS8ivTp/zOB4bfXYqaj LgqnGbivJq9ehkETpFe1ltl1LGs4HcesuEkF7/F4Qr2+HA5OfQ5UQ0HW76GBE9CG RBuQbeQPVWjMX7pjaToDMNkuZAt7KMTAft6uMQXuaSVAo31yR5MZhyBol1b7gfHU BB7MHErGJ2EufGRA2tfNuwnmEzpcIBDtVnUSscQkbozSM6sqkSbenMa/q4iZ0Lqp dw3GF18WZYEMSbYzOLUHpgK/WGfG2rGu8DxFJwB5xNo6tOs2hALSjLcXs7Zowptp Pms9qEAhoj95wjguCR/CYrB8jkoUazDzEiSNsZsG6kc/Uz7asqWgdA== =+v7x -----END PGP SIGNATURE-----
On 2016-05-19 08:07, Steffen Kaiser wrote:
On Wed, 18 May 2016, Tom Sommer wrote:
On 2016-05-18 11:52, Aki Tuomi wrote:
On 18.05.2016 12:44, Tom Sommer wrote:
I'm trying to lock down a maildir from modifications using dovecot-uidlist.lock, but when a user with mailbox.auto = create logs in, then the folder is created regardless of dovecot-uidlist.lock existing or not.
Is there no way to prevent dovecot from touching anything in a maildir folder?
Could you provide more information, like:
what you are trying to achieve what did you do what you configuration looks like what version you are using
I'm trying to move all files and folder from /foo.com/bar/ to /foo.com/bar/Maildir without moving .dovecot.svbin and .dovecot.sieve etc. (homedir files)
So I wanted to lock the folder, kick the user and the move the files/folders, but the user logs in just after I kick him and so the auto-folders are created and my migration script fails, locking the folder with dovecot-uidlist.lock and maildirlock does not work in this case.
Check out:
http://wiki2.dovecot.org/Authentication/RestrictAccess?highlight=%28user%29|%28deny%29
Yea, I was just hoping there was a way without having to mess with passdb
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, 19 May 2016, Tom Sommer wrote:
On 2016-05-19 08:07, Steffen Kaiser wrote:
On Wed, 18 May 2016, Tom Sommer wrote:
On 2016-05-18 11:52, Aki Tuomi wrote:
On 18.05.2016 12:44, Tom Sommer wrote:
I'm trying to lock down a maildir from modifications using dovecot-uidlist.lock, but when a user with mailbox.auto = create logs in, then the folder is created regardless of dovecot-uidlist.lock existing or not.
Is there no way to prevent dovecot from touching anything in a maildir folder?
Could you provide more information, like:
what you are trying to achieve what did you do what you configuration looks like what version you are using
I'm trying to move all files and folder from /foo.com/bar/ to /foo.com/bar/Maildir without moving .dovecot.svbin and .dovecot.sieve etc. (homedir files)
So I wanted to lock the folder, kick the user and the move the files/folders, but the user logs in just after I kick him and so the auto-folders are created and my migration script fails, locking the folder with dovecot-uidlist.lock and maildirlock does not work in this case.
Check out:
http://wiki2.dovecot.org/Authentication/RestrictAccess?highlight=%28user%29|%28deny%29
Yea, I was just hoping there was a way without having to mess with passdb
If you have easy Unix permission on disk:
# user cannot change anything chown -R root:root basedir migrate # make sure userdb is current flush cache # make user re-login to get changes in effect kick user # allow write access to user chown -R vmail:vmail basedir
Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1
iQEVAwUBVz18ynz1H7kL/d9rAQJ25gf9FY7Qbkpqj0frTQmFgRBbmM9sXwPFropt 5FO2snpNPQYA7Wnu3YjZFkJOpoqJcouC+DX5Vp9HRM2KiCz16o0ANfjf37zF+vVl sAGNvb5gFSL2B0diARqu1idUKlYe++wJ20coXjs+1/gc+IDmsam+RGjddpLqWhuo c+6OhDRYsBhB8OVLvQUwT/B20Q6vmJujZ9i6oGA1jW2Ul7ibiuRXah2dSn98FAlv T1671+Dw2M+Awh8/bftBZiRlZUQ7tXiaDHGgdaBhXorEAXqsGxU/dg+0//Bqyt3w 3Th9h6YO2nfmfBbvyz+mbG34jtdyGrfW3xXpeQmBcTd5M8LaKMZHeQ== =bsGE -----END PGP SIGNATURE-----
participants (3)
-
Aki Tuomi
-
Steffen Kaiser
-
Tom Sommer