postfix upgrade-configuration

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

postfix upgrade-configuration

@lbutlr
Looking at Postfix 3.3 and upgrade-configuration I get:

Note: the following files or directories still exist but are
    no longer part of Postfix:

     /usr/local/etc/postfix/access /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

All well and good, but what has replaced them, especially virtual and alias which are a pretty basic part of my mail configuration for local users.

I looked around on postfix.org for 3.3 info and didn't stumble across it.

http://www.postfix.org/postfix-release/experimental/ didn't load anything or show up on google searches, though I did have an old link to a page there.

Reply | Threaded
Open this post in threaded view
|

Re: postfix upgrade-configuration

Viktor Dukhovni


> On Dec 31, 2017, at 1:45 PM, @lbutlr <[hidden email]> wrote:
>
> Note: the following files or directories still exist but are
>    no longer part of Postfix:
>
>     /usr/local/etc/postfix/access /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
>
> All well and good, but what has replaced them, especially virtual and alias which are a pretty basic part of my mail configuration for local users.

The message simply says that Postfix no-longer includes (empty apart
from comments) templates for these files, and if you're *not* using
them, you can delete them.  If you choose to use one of these files
for tables of your own, that's of course fine.  You can store your
file-based tables in any file of your choice.

--
        Viktor.

Reply | Threaded
Open this post in threaded view
|

Re: postfix upgrade-configuration

Wietse Venema
In reply to this post by @lbutlr
@lbutlr:

> Looking at Postfix 3.3 and upgrade-configuration I get:
>
> Note: the following files or directories still exist but are
>     no longer part of Postfix:
>
>      /usr/local/etc/postfix/access /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
>
> All well and good, but what has replaced them, especially virtual and =
> alias which are a pretty basic part of my mail configuration for local =
> users.

Ask your maintainer-in-the-middle? As distributed, the postfix-files
file declares that the following directories and files are obsolete:

$sample_directory
$daemon_directory/main.cf
$daemon_directory/master.cf
$config_directory/cidr_table
$config_directory/generics
$config_directory/install.cf
$config_directory/pcre_table
$config_directory/regexp_table
$config_directory/tcp_table
$config_directory/postfix-script
$config_directory/postfix-script-sgid
$config_directory/postfix-script-nosgid
$config_directory/post-install
$manpage_directory/man5/generics.5
$manpage_directory/man8/nqmgr.8
$sample_directory/sample-aliases.cf
$sample_directory/sample-auth.cf
$sample_directory/sample-canonical.cf
$sample_directory/sample-compatibility.cf
$sample_directory/sample-debug.cf
$sample_directory/sample-filter.cf
$sample_directory/sample-flush.cf
$sample_directory/sample-ipv6.cf
$sample_directory/sample-ldap.cf
$sample_directory/sample-lmtp.cf
$sample_directory/sample-local.cf
$sample_directory/sample-mime.cf
$sample_directory/sample-misc.cf
$sample_directory/sample-pcre-access.cf
$sample_directory/sample-pcre-body.cf
$sample_directory/sample-pcre-header.cf
$sample_directory/sample-pgsql-aliases.cf
$sample_directory/sample-qmqpd.cf
$sample_directory/sample-rate.cf
$sample_directory/sample-regexp-access.cf
$sample_directory/sample-regexp-body.cf
$sample_directory/sample-regexp-header.cf
$sample_directory/sample-relocated.cf
$sample_directory/sample-resource.cf
$sample_directory/sample-rewrite.cf
$sample_directory/sample-scheduler.cf
$sample_directory/sample-smtp.cf
$sample_directory/sample-smtpd.cf
$sample_directory/sample-tls.cf
$sample_directory/sample-transport.cf
$sample_directory/sample-verify.cf
$sample_directory/sample-virtual.cf
$readme_directory/HOSTING_README
$readme_directory/MACOSX_README
$readme_directory/QMQP_README
$html_directory/CYRUS_README.html
$html_directory/QMQP_README.html
$html_directory/ULTRIX_README.html
$html_directory/generics.5.html

        Wietse
Reply | Threaded
Open this post in threaded view
|

Re: postfix upgrade-configuration

@lbutlr
In reply to this post by Viktor Dukhovni
On 31 Dec 2017, at 16:32, Viktor Dukhovni <[hidden email]> wrote:

>> On Dec 31, 2017, at 1:45 PM, @lbutlr <[hidden email]> wrote:
>>
>> Note: the following files or directories still exist but are
>>   no longer part of Postfix:
>>
>>    /usr/local/etc/postfix/access /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
>>
>> All well and good, but what has replaced them, especially virtual and alias which are a pretty basic part of my mail configuration for local users.
>
> The message simply says that Postfix no-longer includes (empty apart
> from comments) templates for these files, and if you're *not* using
> them, you can delete them.  If you choose to use one of these files
> for tables of your own, that's of course fine.  You can store your
> file-based tables in any file of your choice.

Ah, thank you for the clarification.

Perhaps "are no longer part of the default Postfix install. If you are not using them, they may be removed."?


--
Something wonderful, if you took the long view, was about to happen. If
you took the short or medium view, something horrible was about to
happen. It's like the difference between seeing a beautiful new star in
the winter sky and actually being close to the supernova. It's the
difference between the beauty of morning dew on a cobweb and actually
being a fly. --Reaper Man

Reply | Threaded
Open this post in threaded view
|

Re: postfix upgrade-configuration

@lbutlr
On 31 Dec 2017, at 16:41, @lbutlr <[hidden email]> wrote:
> Perhaps "are no longer part of the default Postfix install. If you are not using them, they may be removed."?

--
'Where's the gritsucker? And the rock?' 'Ah,' said Vimes, 'you are
referring to those representative members of our fellow sapient races
who have chosen to throw in their lots with the people of this city?' 'I
mean the dwarf and the troll,' said Quirke. --Men at Arms
Reply | Threaded
Open this post in threaded view
|

Re: postfix upgrade-configuration

Wietse Venema
@lbutlr:
> On 31 Dec 2017, at 16:41, @lbutlr <[hidden email]> wrote:
> > Perhaps "are no longer part of the default Postfix install. If you are =
> not using them, they may be removed."?

Per my previous email, Postfix 3.3 as distributed by me never reports
the 'access' file as obsolete.

Concrete example:

% ls -l /etc/postfix/access /etc/postfix/transport /etc/postfix/virtual
-rw-r--r--  1 root  wheel  5532 May 10  2005 /etc/postfix/access
-rw-r--r--  1 root  wheel  7516 Dec  5  2010 /etc/postfix/transport
-rw-r--r--  1 root  wheel  3883 May 22  2015 /etc/postfix/virtual
% pwd
/home/wietse/postfix-3.3-20171229
% make -j8
...
% su
Password:
# make upgrade
...
Skipping /usr/local/doc/postfix/trivial-rewrite.8.html...
Skipping /usr/local/doc/postfix/verify.8.html...
Skipping /usr/local/doc/postfix/virtual.5.html...
Skipping /usr/local/doc/postfix/virtual.8.html...
# postfix upgrade-configuration
#

No messages about obsolete files named access, transport, virtual.

I suspect that you have a modified release.

        Wietse
Reply | Threaded
Open this post in threaded view
|

Re: postfix upgrade-configuration

@lbutlr
On 1 Jan 2018, at 11:18, Wietse Venema [hidden email]> wrote:
>
> @lbutlr:
>> On 31 Dec 2017, at 16:41, @lbutlr <[hidden email]> wrote:
>>> Perhaps "are no longer part of the default Postfix install. If you are =
>> not using them, they may be removed."?
>
> 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


--
WHO KNOWS WHAT EVIL LURKS IN THE HEART OF MEN?  The Death of Rats looked
up from the feast of potato. SQUEAK, he said. Death waved a hand
dismissively. WELL, YES, OBVIOUSLY *ME*, he said. I JUST WONDERED IF
THERE WAS ANYONE ELSE. --The Truth

Reply | Threaded
Open this post in threaded view
|

Re: postfix upgrade-configuration

Wietse Venema
@lbutlr:

> On 1 Jan 2018, at 11:18, Wietse Venema [hidden email]> wrote:
> >=20
> > @lbutlr:
> >> On 31 Dec 2017, at 16:41, @lbutlr <[hidden email]> 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' or some other command?

I frequently install Postfix on a development machine, and I would
certainly have noticed messages about an obsolete 'access' file
(the access file on my development machine dates from 2005).

        Wietse
Reply | Threaded
Open this post in threaded view
|

Re: postfix upgrade-configuration

Viktor Dukhovni


> On Jan 2, 2018, at 12:24 PM, Wietse Venema <[hidden email]> wrote:
>
> I frequently install Postfix on a development machine, and I would
> certainly have noticed messages about an obsolete 'access' file
> (the access file on my development machine dates from 2005).

Indeed there have been very few additional "obsoleted" files in
config_directory:

    postfix-2.6-20080207
+$config_directory/postfix-files:f:root:-:644:o
+$config_directory/postfix-script:f:root:-:755:o
+$config_directory/post-install:f:root:-:755:o

    postfix-2.3-20051112
+$config_directory/generics:f:root:-:644:o

    postfix-2.2-20050211
+$config_directory/generics:f:root:-:644:o

    postfix-2.0.17-20040120
+$config_directory/cidr_table:f:root:-:644:o
+$config_directory/pcre_table:f:root:-:644:o
+$config_directory/regexp_table:f:root:-:644:o
+$config_directory/tcp_table:f:root:-:644:o

    postfix-2.0.16-20031202
+$config_directory/install.cf:f:root:-:644:o
+$config_directory/postfix-script-sgid:f:root:-:755:o
+$config_directory/postfix-script-nosgid:f:root:-:755:o

The only remotely related change (which would not cause
the reported messages absent changes by the downstream
package maintainer) is a change to support multiple
instances in postfix-2.6-20090114:

-$config_directory/LICENSE:f:root:-:644
-$config_directory/TLS_LICENSE:f:root:-:644
-$config_directory/access:f:root:-:644:p
-$config_directory/aliases:f:root:-:644:p
-$config_directory/bounce.cf.default:f:root:-:644
-$config_directory/canonical:f:root:-:644:p
-$config_directory/generic:f:root:-:644:p
-$config_directory/header_checks:f:root:-:644:p
-$config_directory/main.cf.default:f:root:-:644
-$config_directory/makedefs.out:f:root:-:644
-$config_directory/relocated:f:root:-:644:p
-$config_directory/transport:f:root:-:644:p
-$config_directory/virtual:f:root:-:644:p
+$config_directory/LICENSE:f:root:-:644:1
+$config_directory/TLS_LICENSE:f:root:-:644:1
+$config_directory/access:f:root:-:644:p1
+$config_directory/aliases:f:root:-:644:p1
+$config_directory/bounce.cf.default:f:root:-:644:1
+$config_directory/canonical:f:root:-:644:p1
+$config_directory/generic:f:root:-:644:p1
+$config_directory/header_checks:f:root:-:644:p1
+$config_directory/main.cf.default:f:root:-:644:1
+$config_directory/makedefs.out:f:root:-:644:1
+$config_directory/relocated:f:root:-:644:p1
+$config_directory/transport:f:root:-:644:p1
+$config_directory/virtual:f:root:-:644:p1

The files in question are required only in the primary Postfix
instance.

--
--
        Viktor.
Reply | Threaded
Open this post in threaded view
|

Re: postfix upgrade-configuration

@lbutlr
In reply to this post by Wietse Venema
On 2 Jan 2018, at 10:24, Wietse Venema [hidden email]> wrote:

>
> @lbutlr:
>> On 1 Jan 2018, at 11:18, Wietse Venema [hidden email]> wrote:
>>> =20
>>> @lbutlr:
>>>> On 31 Dec 2017, at 16:41, @lbutlr <[hidden email]> 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.

Reply | Threaded
Open this post in threaded view
|

Re: postfix upgrade-configuration

Wietse Venema
Postfix as distributed by me has never nagged about obsolete 'access'
files, and I suggest that any complaints about such behavior are
directed at the downstream maintainer who introduced that behavior.

        Wietse