2017-05-23 19:57 GMT+02:00 Viktor Dukhovni <[email protected]>:
> > > On May 23, 2017, at 1:43 PM, Cecil Westerhof <[email protected]> > wrote: > > > > The directory itself looks also OK to me: > > drwx------ 2 postfix root 4.0K May 23 19:10 active > > drwx------ 2 postfix root 4.0K May 23 18:54 bounce > > drwx------ 2 postfix root 4.0K May 22 14:00 corrupt > > drwx------ 3 postfix root 4.0K May 23 17:36 defer > > drwx------ 3 postfix root 4.0K May 23 17:36 deferred > > drw-r--r-- 2 postfix root 4.0K May 23 17:10 dev > > drwxr-xr-x 3 root root 4.0K May 23 19:10 etc > > drwx------ 2 postfix root 4.0K May 22 14:00 flush > > drwx------ 2 postfix root 4.0K May 23 16:39 hold > > drwx------ 2 postfix root 4.0K May 23 19:10 incoming > > drwxr-xr-x 3 root root 4.0K May 23 17:10 lib > > drwx-wx--T 2 postfix postdrop 4.0K May 23 19:10 maildrop > > drwxr-xr-x 2 root root 4.0K May 23 17:36 pid > > drwx------ 2 postfix root 4.0K May 23 19:10 private > > drwx--s--- 2 postfix postdrop 4.0K May 23 19:10 public > > drwx------ 2 postfix root 4.0K May 22 14:00 saved > > drwx------ 2 postfix root 4.0K May 23 16:39 trace > > drwxr-xr-x 3 root root 4.0K May 23 16:53 usr > > > > Or am I missing something? > > Why is scan_dir_push failing for the "hold" subdirectory? > What do you mean? > Stop Postfix, then as root run "postsuper -s". Does that > log any errors. If so, find out why and fix. > No it does not > Or if your mail queue is empty, just uninstall Postfix, > delete the entire /var/spool/postfix directory and all > its content, then re-install Postfix, which will get > you a fresh /var/spool/postfix, presumably without > all the permission problems. > I could do that. Just need to be sure what to save. (At least main.cf.) But I think it is time for a break. ;-) -- Cecil Westerhof
