I too have encountered this issue and did not find the chmod command mentioned above to be of much help. A better way in my view is to fix the init.d script. The directory containing the socket file should be owned by the user running milter-greylist only writeable by that user.
Around line 61 of /etc/init.d/milter-greylist I changed it to read:
if [ ! -d /var/run/$PNAME ]; then
mkdir /var/run/$PNAME
chown greylist /var/run/$PNAME
fi
This is in line with the recommendations contained in the README which ships with the milter-greylist sources:
"The default directory is /var/milter-greylist and it should be chmod 0755 and owner smmsp, if you are running the milter as smmsp."
I too have encountered this issue and did not find the chmod command mentioned above to be of much help. A better way in my view is to fix the init.d script. The directory containing the socket file should be owned by the user running milter-greylist only writeable by that user.
Around line 61 of /etc/init. d/milter- greylist I changed it to read:
if [ ! -d /var/run/$PNAME ]; then
mkdir /var/run/$PNAME
chown greylist /var/run/$PNAME
fi
This is in line with the recommendations contained in the README which ships with the milter-greylist sources:
"The default directory is /var/milter- greylist and it should be chmod 0755 and owner smmsp, if you are running the milter as smmsp."