Quoting Patrick Shanahan :

* Jeffrey L. Taylor [11-27-09 22:35]:

...

Quoting Patrick Shanahan :

...

I am consistently getting postfix updates which do not perform postmap against changed files, expecially relay, header-checks and generic, generating error entries in /var/log/mail.

SuSEconfig does *not* perform postmap against these files.

Have you modified these files by hand?

No, they are untouched as they were installed from the rpm. They contain *only* comments.

So there are no semantic changes. Why does postmap need to be run? Oh, error entries in /var/log/mail. How about posting the error messages. Jeffrey -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2009-11-27 at 23:15 -0600, Jeffrey L. Taylor wrote:

Quoting Patrick Shanahan <>:

...

...

...

I am consistently getting postfix updates which do not perform postmap against changed files, expecially relay, header-checks and generic, generating error entries in /var/log/mail.

SuSEconfig does *not* perform postmap against these files.

Have you modified these files by hand?

No, they are untouched as they were installed from the rpm. They contain *only* comments.

So there are no semantic changes. Why does postmap need to be run? Oh, error entries in /var/log/mail. How about posting the error messages.

All that is irrelevant. The moment one of those files is modified in any manner (date stamp) postmap has to be run on those modified files. This is known and documented. It is a failure of the installation script not to do that, or trigger a proces that does. And of course, postfix will notice and report in the log. I personally use a Makefile in /etc/postfix/, thus running "make" takes care of it. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAksSYT4ACgkQtTMYHG2NR9Wa4QCfYFge7N9hrAPxSj8SMzmA1AZt PGkAnRT0PeNkWrUmXY+S+VCn5Y8HDeQ/ =vrgZ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

* Per Jessen [11-30-09 07:45]:

Patrick, the list of files you sent:

/etc/postfix/relay.db /etc/postfix/canonical.db /etc/postfix/relocated.db /etc/postfix/transport.db

I would think they'd either be quite specific to your installation or just left with default values (=empty). Why are they being touched by an upgrade at all?

11:22 wahoo:~ > rpm -ql postfix |grep /etc/postfix /etc/postfix /etc/postfix/LICENSE /etc/postfix/TLS_LICENSE /etc/postfix/access /etc/postfix/bounce.cf.default /etc/postfix/canonical /etc/postfix/dynamicmaps.cf /etc/postfix/generic /etc/postfix/header_checks /etc/postfix/helo_access /etc/postfix/main.cf /etc/postfix/main.cf.default /etc/postfix/makedefs.out /etc/postfix/master.cf /etc/postfix/openssl_postfix.conf.in /etc/postfix/postfix-files /etc/postfix/relay /etc/postfix/relay_ccerts /etc/postfix/relocated /etc/postfix/sasl_passwd /etc/postfix/sender_canonical /etc/postfix/transport /etc/postfix/virtual The "upgrade" is "zypper dup", not a patch. The entire package is being reinstalled w/o changing altered files. The subject files not having postmap performed against are from the "upgrade". Postfix generates error messages when it detects a xxx.db file with an earlier date than its matching text file. The "upgrade" does not install xxx.db files, but has a post-install script which performs postmap against *specific* files and those subject files are not being included in the script. I filed a bug report, 555693, but have only received a query inferring that SuSEconfig was supposed to perform postmap. I does *not*! I have added comments to the bug report when subsequent postfix updates are issued and have failed to perform postmap against *all* of the changed files to no avail. My *last* comment: "I will not comment further on update failures to perform postmap." I have manually added the subject files to SuSEconfig/postmap so that I will no longer see the problem. BUT that ain't how it is supposed to work(tm)! Rocket Science? -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

* Per Jessen [11-30-09 12:44]:

Which makes me wonder how they are created on a plain installation. The post-install script is the same, but obviously(?) does different things depending on the situation?

I think not. The post-install script *should* compare creation times of text files that are normally converted to tables to the creation times of the xxx.db files and run postmap against those that do not conform. New install or update should make no difference. New install should not contain xxx.db files, but create them with the post-install script. This way the install/update is agnostic. -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On Tue, Dec 01, 2009 at 09:26:03AM +0100, Per Jessen wrote:

Patrick Shanahan wrote:

...

* Per Jessen [11-30-09 12:44]:

...

Which makes me wonder how they are created on a plain installation. The post-install script is the same, but obviously(?) does different things depending on the situation?

I think not. The post-install script *should* compare creation times of text files that are normally converted to tables to the creation times of the xxx.db files and run postmap against those that do not conform. New install or update should make no difference.

Agree - but isn't that what you're seeing: that your 'zypper dup' operation does not run 'postmap' to create the .db files despite having installed new text files?

The problem probably actually is in /etc/sysconfig/postfix that e.g. "relay" or some other maps are not listed in the POSTFIX_MAP_LIST variable. Ciao, MArcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On Tue, Dec 01, 2009 at 10:04:10AM +0100, Per Jessen wrote:

Marcus Meissner wrote:

...

On Tue, Dec 01, 2009 at 09:26:03AM +0100, Per Jessen wrote:

...

Patrick Shanahan wrote:

...

* Per Jessen [11-30-09 12:44]:

...

Which makes me wonder how they are created on a plain installation. The post-install script is the same, but obviously(?) does different things depending on the situation?

I think not. The post-install script *should* compare creation times of text files that are normally converted to tables to the creation times of the xxx.db files and run postmap against those that do not conform. New install or update should make no difference.

Agree - but isn't that what you're seeing: that your 'zypper dup' operation does not run 'postmap' to create the .db files despite having installed new text files?

The problem probably actually is in /etc/sysconfig/postfix that e.g. "relay" or some other maps are not listed in the POSTFIX_MAP_LIST variable.

Ah, that is interesting - so I guess it wouldn't work in a regular install either. I've done a few of those with 1.2, but I'm not sure I've checked the postfix setup.

A normal install will get the correct list from /var/adm/fillup-templates/... Just an upgrade from older SUSEs will have problems. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On Tue, Dec 01, 2009 at 09:08:41AM -0500, Patrick Shanahan wrote:

* Marcus Meissner [12-01-09 04:27]:

...

A normal install will get the correct list from /var/adm/fillup-templates/... Just an upgrade from older SUSEs will have problems.

Then, perhaps there is another reason that relay, virtual, relocated and canonical xxx.db files are not being generated as they appear in the fillup-templates/sysconfig.postfix file?

And this site is an upgrade from an early MileStone, but not an earlier distro.

This is done by the SuSEconfig postfix script, which should be run. So try a single run of SuSEconfig --module postfix Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org