Casper

fyi: in my setup, no execute permission is missing: ``` root@mail:/var/mail# ll total 20K drwxr-xr-x 4 docker docker 4.0K May 29 00:55 domain1 drwxr-xr-x 3 docker docker 4.0K Mar 4...

It's up to you 😃. If you think, a broader audience will benefit from that, implement it in full with ENVs etc. If you think, only a small group will...

I don't understand this PR. So there is an issue with permissions/ownership when LDAP is involved. Fixing an LDAP issue, while introducing possible issues for existing non LDAP setups doesn't...

> It wasn't clear what chown -R on /var/mail was "Fixing permissions" for. If you migrate to a new server/storage etc, or forget to backup permissions as well, the permissions...

> You may consider adding an ENV to ignore applying the chown -R, it should be opt-in by default. When I look in `/var/mail/example.com/postmaster/new`, I see that new mails have...

> I don't like having this chown -R at all, which may ruin my permissions somehow in the future, while we don't really know why it is needed. From my...

Addition to my last statement, in case I were misunderstood. This was just my conclusion, why `chmod -R` was introduced in the first place (when there was no LDAP support...

Regarding watchexec: If I understand correctly, we would also need a work-around for at least NFS. I think we should aim a one-for-all solution (if possible).

I've updated my post above, I hope this makes it clearer 😉 There is nothing wrong with this PR from my point of view.

As always, good summary @polarathene 👍 >>Regarding watchexec: If I understand correctly, we would also need a work-around for at least NFS. I think we should aim a one-for-all solution...