On Sun, 2022-01-02 at 18:37 -0500, Wietse Venema wrote:
> Here is what happens on m system.
>
> As root:
>
> # chmod g-s /usr/sbin/postdrop
> # ls -l /usr/sbin/postdrop
> -rwxr-xr-x 1 root postdrop 44472 Dec 23 18:08 /usr/sbin/postdrop
For some reason, there is no write permission on postdrop, for anybody.
> # chmod 777 /var/spool/postfix/public
> # ls -ld /var/spool/postfix/public /var/spool/postfix/public/showq
> drwxrwxrwx. 2 postfix postdrop 4096 Jan 2 15:55
> /var/spool/postfix/public
> srw-rw-rw- 1 postfix postfix 0 Jan 2 15:55
> /var/spool/postfix/public/showq
> # su wietse
>
> As non-root:
>
> wzv$ strace -e connect postqueue -p |& grep showq
> connect(4, {sa_family=AF_UNIX, sun_path="public/showq"}, 110) = 0
syntax error near unexpected token `4,'
> wzv$ exit
command not found
> Back as root:
>
> # chmod 710 /var/spool/postfix/public
> # ls -ld /var/spool/postfix/public
> drwx--x---. 2 postfix postdrop 4096 Jan 2 18:30
> /var/spool/postfix/public
drwx--s--- 2 postfix postdrop 88 Jan 2 17:46 /var/spool/postfix/public
> # chmod g+s /usr/sbin/postdrop
> # ls -l /usr/sbin/postdrop
> -rwxr-sr-x 1 root postdrop 44472 Dec 23 18:08 /usr/sbin/postdrop
-r-xr-sr-x 1 root postdrop 22808 Sep 7 02:58 /usr/sbin/postdrop
I hope this makes sense to you. I can see permission differences, but
I don't know if they're responsible.
Ken
