search for: setuid'ing

...ulting files are left with root ownership (I don't have 'service doveadm' 'user' set, so I guess it defaults to root). It's typically new m.* files as well as the dovecot.list.index and dovecot.list.index.log files. Looking at strace, no chown is done on them, nor was there setuid. The import had no trouble finding the correct user in the db, so I know that it knows the correct UID (I can see it just fine in debug logs too). And it will happily import to existing m.* files with no permissions issues (but considering it's running as root, I wouldn't expect it to). I&...

...th root ownership (I > don't have 'service doveadm' 'user' set, so I guess it defaults to root). > It's typically new m.* files as well as the dovecot.list.index > and dovecot.list.index.log files. > > Looking at strace, no chown is done on them, nor was there setuid. The > import had no trouble finding the correct user in the db, so I know that > it > knows the correct UID (I can see it just fine in debug logs too). And it > will happily import to existing m.* files with no permissions issues (but > considering it's running as root, I wouldn...

...> <div> It's typically new m.* files as well as the dovecot.list.index </div> <div> and dovecot.list.index.log files. </div> <div> <br> </div> <div> Looking at strace, no chown is done on them, nor was there setuid. The </div> <div> import had no trouble finding the correct user in the db, so I know that it </div> <div> knows the correct UID (I can see it just fine in debug logs too). And it </div> <div> will happily import to existing m.* file...