Getting my mail hoster to accept my cron output emails

2019-02-14 Thread Cecil Westerhof
address for emails that send the output of a cron job? -- Cecil Westerhof

postfix check error and warning

2019-02-10 Thread Cecil Westerhof
, but I do not like that. I do not have a file: /etc/postfix/postfix-files I do have an empty directory: /etc/postfix/postfix-files.d/ This is on Debian 9.7. -- Cecil Westerhof

Can this SASL configuration be improved

2017-05-26 Thread Cecil Westerhof
this OK, or can it be improved?​ -- Cecil Westerhof

Re: scan_dir_push: open directory defer: Permission denied

2017-05-23 Thread Cecil Westerhof
2017-05-23 19:59 GMT+02:00 Bastian Blank < bastian+postfix-users=postfix@waldi.eu.org>: > On Tue, May 23, 2017 at 07:43:56PM +0200, Cecil Westerhof wrote: > > drw-r--r-- 2 postfix root 4.0K May 23 17:10 dev > > Please tell me you didn't see that this

Re: scan_dir_push: open directory defer: Permission denied

2017-05-23 Thread Cecil Westerhof
2017-05-23 19:57 GMT+02:00 Viktor Dukhovni : > > > On May 23, 2017, at 1:43 PM, Cecil Westerhof > 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

Re: scan_dir_push: open directory defer: Permission denied

2017-05-23 Thread Cecil Westerhof
2017-05-23 19:30 GMT+02:00 Viktor Dukhovni : > > > On May 23, 2017, at 1:22 PM, Cecil Westerhof > wrote: > > > > > > There are still some things I should look after, like: > > warning: unable to create missing queue directories > > > > But

Re: scan_dir_push: open directory defer: Permission denied

2017-05-23 Thread Cecil Westerhof
2017-05-23 19:30 GMT+02:00 Viktor Dukhovni : > > > On May 23, 2017, at 1:22 PM, Cecil Westerhof > wrote: > > > > > > There are still some things I should look after, like: > > warning: unable to create missing queue directories > > > > But

Re: scan_dir_push: open directory defer: Permission denied

2017-05-23 Thread Cecil Westerhof
e directories But it is probably not the most urgent. ​ -- Cecil Westerhof

Re: scan_dir_push: open directory defer: Permission denied

2017-05-23 Thread Cecil Westerhof
2017-05-23 16:49 GMT+02:00 Cecil Westerhof : > 2017-05-23 16:32 GMT+02:00 John Stoffel : > >> >>>>> "Wietse" == Wietse Venema writes: >> >> Wietse> DecebalICT: >> >> I went from an openSUSE system to a Debian 9 system. >&g

Re: scan_dir_push: open directory defer: Permission denied

2017-05-23 Thread Cecil Westerhof
r old system working. Not by > copying over the old config, but by instead just adding in the missing > parts to the NEW config. > ​I think that that is a very good idea.​ > I wonder if the openSUSE was in a chroot, and the Debian isn't? > ​I am reasonable sure it was not.​ -- Cecil Westerhof

Re: scan_dir_push: open directory defer: Permission denied

2017-05-23 Thread Cecil Westerhof
2017-05-23 14:26 GMT+02:00 Cecil Westerhof : > Now I get: > postfix: dict_lookup: html_directory = (notfound) > postfix: mac_parse: /usr/share/doc/postfix/html > postfix: dict_eval: const /usr/share/doc/postfix/html > postfix: dict_update: html_directory = /usr/sh

Re: scan_dir_push: open directory defer: Permission denied

2017-05-23 Thread Cecil Westerhof
2017-05-23 14:51 GMT+02:00 Geert Stappers : > On Tue, May 23, 2017 at 02:26:26PM +0200, Cecil Westerhof wrote: > > 2017-05-23 13:38 GMT+02:00 Wietse Venema : > > > > > Check the permissions of > > > > > > /var/spool/postfix > > > /var/spool/post

Re: scan_dir_push: open directory defer: Permission denied

2017-05-23 Thread Cecil Westerhof
r-xr-x 2004 root root 68K May 23 12:02 /usr/share/doc/ drwxr-xr-x3 root root 4.0K May 23 10:48 /usr/share/doc/postfix/ ​ ​I also created a dummy.html in the directory: -rw-r--r-- 1 postfix root 0 May 23 14:22 index.html But that did not help either. Are there certain files that need to be there?​ -- Cecil Westerhof

Re: scan_dir_push: open directory defer: Permission denied

2017-05-23 Thread Cecil Westerhof
p SeLinux permissions or labels. For a quick > check, turn off SeLinux and see if Postfix works better. Then fix > SeLinux or leave it off. > > 3) You have messed up AppArmor permissions, or some other 'security' > software. Same procedure. > ​Both are not installed.​ -- Cecil Westerhof