I've found a bug that causes SuSEconfig (and, presumably, Yast2, since it uses SuSEconfig) to fail to update Postfix configuration and then incorrectly report that it has done so successfully. More alarmingly, if any command `postconf' exists in a user's PATH when running the SuSEconfig postfix module, *that command*, (whichever one is found first; not necessarily the intended one) will be run by SuSEconfig. Worse yet, if SuSEconfig is run with superuser privileges (which is the only way it will work properly) then this arbitrary postconf command is executed with superuser privileges, and SuSEconfig will prepend any output from the command to /etc/postfix/main.cf. Scripts that execute a command without specifying the path to that command, *especially* those which are likely to be run as root, are extremely bad policy; surely this is an oversight on SuSE's part. Keyword and full-text searches of the SuSE support database for `postfix' result in no relevant information. I'm unable to find any mention of this bug on the Web. Concise description: In the SuSE Linux 9.0 Postfix package, version 2.0.14, release 54 (postfix-2.0.14-54.rpm), the SuSEconfig postfix module (/sbin/conf.d/SuSEconfig.postfix) incorrectly assumes that the command `postconf' will be found in its path (i.e., it assumes that /usr/sbin is in the PATH environment variable of the user executing SuSEconfig). It will execute the first executable file named `postconf' found in the users search path, and prepend any output to /etc/postfix/main.cf. Workaround: Manually ensure that Postfix's postconf command is the first postconf found in your search path for commands (i.e., examine the output of `which postconf' and adjust your PATH environment variable if necessary before running SuSEconfig). As of the current version (2.0.14-54) of SuSE's Postfix package, postconf is installed in /usr/sbin, so simply prepending /usr/sbin to your PATH before running SuSEconfig works for now, but there is no guarantee that this will not change in future releases, so this workaround cannot be relied upon after the next upgrade of postfix. Suggested fix: SuSE modifies its postfix package such that /sbin/conf.d/SuSEconfig.postfix does the following: * uses absolute path for any commands which it will execute * exits with a return code truly indicative of whether or not it completed successfully Details (plain text) of how to reproduce the error, as I submitted to SuSE, are attached as suse_postfix_suseconfig_bug. -- Phil Mocek