Uw opmerkingen

Make sure you restart Ajenti service after editing the templates.py!
Make sure you restart Ajenti service after editing the templates.py!
For those who care, I was able to find out where ajenti-v-mail stores the template where they build the exim4.conf file from.

In my debian installation it was found in this file:
/var/lib/ajenti/plugins/vh-mail/templates.py
For those who care, I was able to find out where ajenti-v-mail stores the template where they build the exim4.conf file from.

In my debian installation it was found in this file:
/var/lib/ajenti/plugins/vh-mail/templates.py
It may be useful to note that I am running Debian, so the users for courier may be different depending on setup.
Upon further investigation leaving the socket ownership to root:root is ok. To make the permanent change to fix this issue for me I changed the permission of the authdaemon directory to 755 which will probably remain fixed (even after reboot) until there is an update to courier-authdaemon.
I just got the same issue. It appears my /var/run/courier/authdaemon/socket was set as root:root 777.

I ran # chown daemon:daemon on the socket file and it appears to be working again.

Update: I rebooted the server and it appears that /var/run/courier/authdaemon/socket was run as root:root again. Anybody have any idea how to make it so it is run as a different user:group when courier service starts?