Bugzilla – Bug 147719
POSTFIX_RELAYHOST is not transferred to postfix/main.cf
Last modified: 2006-06-06 15:18:14 UTC
First I installed sendmail as it used to work (with previous Suse versions), for a permanent connection, providing an IP address for the mail server. It didn't work; after many hours we found out that the mail wouldn't go to the specified mail server. So looking up POSTFIX_RELAYHOST in Yast/etc/sysconfic editor, and there it is, it has the right IP address in it?! Then looking it up in /etc/postfix/main.cf we see that the Yast settings have no influence (at least regarding this variable) --- whatever we do with Yast the value for relayhost in main.cf is the empty string. Setting "relayhost = IP-address" directly in main.cf solved the problem.
*** Bug 147723 has been marked as a duplicate of this bug. ***
I suppose SuSEconfig should export this setting here, I take the postfix-maintainer into CC here.
reassigning to postfix maintainer
1. I've tested and it works fine. If you set this variable manual or with yast2-sysconfig, and execute subsequent SuSEconfig this variable will be set in /etc/postfix/main.cf. 2. The problem is, that yast2-sysconfig does not execute SuSEconfig. 3. If the variable MAIL_CREATE_CONFIG in the file /etc/sysconfig/mail ist set to "no" SuSEconfig will not change the mail system settings. Ladislav, closing yast2-sysconfig why will not executed SuSEconfig?
Ladislav ???
SuSEconfig should be started by Yast, at least it works for me (tested in 10.0 and 10.1Beta2): - Start "yast2 sysconfig" - Change POSTFIX_RELAYHOST value - Finish - check Confirm Each Activation Command, press OK - yast asks whether postfix SuSEConfig module should be started, press Continue to start it (If you do not check the confirmation option then yast starts all commands automatically.)
see the comment of ladislav