Matthew via Postfix-users:
> *Aug 26 15:09:28 SMTP postfix[1037]: postfix/postlog: warning:
> /var/spool/postfix/etc/resolv.conf and /etc/resolv.conf differ
> Aug 26 15:09:28 SMTP postfix/postfix-script[1037]: warning:
> /var/spool/postfix/etc/resolv.conf and /etc/resolv.conf differ*
That would explain why DNS results are different for Postfix amd
for OS utilities. Turn off chroot and the problem goes away.
> Looks like it's exactly as you suspected "is the file
> /var/spool/postfix/etc/resolv.conf up-to-date BEFORE Postfix is
> started?" it would appear not.
>
> For completeness, as you requested:
>
> root@SMTP:~# postconf -F smtp/inet/chroot smtp/inet/chroot = y
> root@SMTP:~# postconf -F submissions/inet/chroot submissions/inet/chroot
> = y
>
> Running Postfix chrooted on Linux is like fighting windmills. Don't
> waste your time on that.
Can you file a request to Debian maintainers to make non-chroot
Postfix the default? Upstream Postfix turned off chroot a decade
ago (in 2015), and it's time that Debian catches up. Your struggles
are unnecessary, and they make Postfix adoption difficult.
Wietse
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
