John Fawcett:
> On 03/01/2022 00:37, 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
> > # 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
> > wzv$ exit
> >
> > 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
> > # 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
> >
> > If THAT postqueue command fails on your system with EACCES and there
> > is no AppArmor crap or the like, then your system has a nonstandard
> > permission system and I can't help you.
> >
> > Wietse
>
> Wietse if I'm reading it correctly there are a few typos there.
>
> /usr/sbin/postdrop
>
> ?should read
>
> /usr/sbin/postqueue
Indeed. I'd just run "postfix set-permissions" but in the past
some maintainers have broken that, so explcit commands will do.
Woietse
