Re: Ownership question

2019-07-04 Thread @lbutlr
On 4 Jul 2019, at 06:46, Rich Shepard wrote: > On Thu, 4 Jul 2019, @lbutlr wrote: > >> Slackware issue? > > Likely not. I've used the same build script for years. Well, something has changed and it is not the permissions that postfix expects on the folder. If it cannot launch with proper permi

Re: Ownership question

2019-07-04 Thread Wietse Venema
Rich Shepard: > On Thu, 4 Jul 2019, Wietse Venema wrote: > > > Don't adjust ownership or permissions of Postfix files/directories. Let > > 'postfix set-permissions' do what needs to be done. > > Wietse, > > This is the first thing I do. When starting postfix throttles and displays > errors I fix

Re: Ownership question

2019-07-04 Thread Rich Shepard
On Thu, 4 Jul 2019, Wietse Venema wrote: Don't adjust ownership or permissions of Postfix files/directories. Let 'postfix set-permissions' do what needs to be done. Wietse, This is the first thing I do. When starting postfix throttles and displays errors I fix them. This lead me to store corr

Re: Ownership question

2019-07-04 Thread Rich Shepard
On Thu, 4 Jul 2019, @lbutlr wrote: Slackware issue? Likely not. I've used the same build script for years. All the directories in /var/spool/postfix are owned by postfix except for pid, which is owned by root. Thank you. That's why the logwatch warnings puzzled me. Regards, Rich

Re: Ownership question

2019-07-04 Thread Wietse Venema
Rich Shepard: > Currently running 3.4.5 on Slackware-14.2. After each upgrade I run 'postfix > set-permissions upgrade-configuration' then adjust ownerships as needed. Don't adjust ownership or permissions of Postfix files/directories. Let 'postfix set-permissions' do what needs to be done.

Re: Ownership question

2019-07-04 Thread @lbutlr
On 3 Jul 2019, at 17:23, Rich Shepard wrote: > Currently running 3.4.5 on Slackware-14.2. After each upgrade I run 'postfix > set-permissions upgrade-configuration' then adjust ownerships as needed. > > When I upgraded to 3.4.5 last weekend I found that when /var/spool/postfix > has owner.group o

Ownership question

2019-07-03 Thread Rich Shepard
Currently running 3.4.5 on Slackware-14.2. After each upgrade I run 'postfix set-permissions upgrade-configuration' then adjust ownerships as needed. When I upgraded to 3.4.5 last weekend I found that when /var/spool/postfix has owner.group of root.postfix the server would not start. Changing the

Re: Ownership question: version 3.2.2

2017-06-25 Thread Rich Shepard
On Sun, 25 Jun 2017, Wietse Venema wrote: See comment above: run "postfix set-permissons". Thanks, Wietse. I ran 'chown -R root /var/spool/postfix/pid/' with postfix stopped. When re-started nor warnings were displayed. Regards, Rich

Re: Ownership question: version 3.2.2

2017-06-25 Thread Rich Shepard
On Sun, 25 Jun 2017, Wietse Venema wrote: Must be owned by root, mode 755. All that is taken care of with "postfix set-permissions", which should happen automatically as part of the installation procedure. Wietse, OK. Of course no such warranties exist if you do things by hand. I use

Re: Ownership question: version 3.2.2

2017-06-25 Thread Wietse Venema
Rich Shepard: >I just upgraded postfix from 3.1.2 to 3.2.2. When I chown postfix of the > /var/spool/postfix/ tree I get these warnings: > > # /etc/rc.d/rc.postfix start > postfix/postfix-script: warning: not owned by root: /var/spool/postfix/. Must be owned by root, mode 755. All that is ta

Ownership question: version 3.2.2

2017-06-25 Thread Rich Shepard
I just upgraded postfix from 3.1.2 to 3.2.2. When I chown postfix of the /var/spool/postfix/ tree I get these warnings: # /etc/rc.d/rc.postfix start postfix/postfix-script: warning: not owned by root: /var/spool/postfix/. postfix/postfix-script: warning: not owned by root: /var/spool/postfix/pi