Postfix permissions messed up after clean-system and recompile/install with sbo-git
 

Solution:
New config files I must have stashed for later.
Ran slackpg new-config and it did have updated postfix configs, after the merge and all that it is now working again.

drwx------ 2 root root 4096 Apr 30 02:33 active
drwx------ 2 root root 4096 Apr 30 02:33 bounce
drwx------ 2 root root 4096 Apr 30 02:33 corrupt
drwx------ 2 root root 4096 Apr 30 02:33 defer
drwx------ 2 root root 4096 Apr 30 02:33 deferred
drwx------ 2 root root 4096 Apr 30 02:33 flush
drwx------ 2 root root 4096 Apr 30 02:33 hold
drwx------ 2 root root 4096 Apr 30 02:33 incoming
drwx-wx--- 2 root root 4096 Apr 30 02:33 maildrop
drwxr-xr-x 2 root root 4096 Apr 30 02:33 pid
drwx------ 2 root root 4096 Apr 30 02:33 private
drwx--x--- 2 root root 4096 Apr 30 02:33 public
drwx------ 2 root root 4096 Apr 30 02:33 saved
drwx------ 2 root root 4096 Apr 30 02:33 trace

is the permission listing.
The postfix user and postdrop group existed from before.

Neither the 14.1 slackbuilds repo nor Ponces git repo didn't fix it upon rebuilding either.

I don't know if the permissions have been like this all the time with it somehow working or if the system cleaning after the big Slackware current update did it.
(Don't know why it should do that, though).

I'll post configurations on demand since this is too odd for me to think of snippets on my own.

Edit:
Removing all directories and having the package create them doesn't fix it, either. That's why I'm wondering if it had always been this way.

Edit:
chown: cannot access '/usr/doc/postfix-2.10.2/README_FILES': No such file or directory

Is what it gives me when I try "postfix set-permissions"
My installed version is 2.11.4 (ponce)

There are two topics related to your postfix problem, as your second topic is here. Common practice is to clearly describe your problem in a single thread to not confuse things.

As you've marked this thread as solved I assume you want this thread to go out of views, which this reply should take care off (topics with 0 replies stay at the top).

That's the reason why I made the second thread.
The problem of permissions is different from the problem of the program complaining about Cyrus despite it not being set in the configs or being compiled into the binary.