On 2 Jan 2018, at 10:24, Wietse Venema wie...@porcupine.org> wrote: > > @lbutlr: >> On 1 Jan 2018, at 11:18, Wietse Venema wie...@porcupine.org> wrote: >>> =20 >>> @lbutlr: >>>> On 31 Dec 2017, at 16:41, @lbutlr <krem...@kreme.com> wrote: >>>>> Perhaps "are no longer part of the default Postfix install. If you = >> are =3D >>>> not using them, they may be removed."? >>> =20 >>> Per my previous email, Postfix 3.3 as distributed by me never reports >>> the 'access' file as obsolete. >> >> The current version of 3.3 does not. I was testing against the September = >> version previously but have now installed the current build: >> >> postfix 3.3-20171229: >> /usr/local/etc/postfix/aliases /usr/local/etc/postfix/canonical >> /usr/local/etc/postfix/generic /usr/local/etc/postfix/relocated >> /usr/local/etc/postfix/transport /usr/local/etc/postfix/virtual > > What is the above list of pathnames? Is that output from 'postconf > upgrade-configuration'
Yes. > I frequently install Postfix on a development machine, and I would > certainly have noticed messages about an obsolete 'access' file I no longer have the september build I was looking at to compare, though I think it was from freeBSD-ports. No matter, I use aliases and virtual and have removed the others since they contained only comments. Unless there is a reason to eliminate virtual/aliases I'll keep them as long as I am delivering mail to users with a $HOME directory. -- Hamburgers. The cornerstone of any nutritious breakfast.
