Bug 147719

Summary: POSTFIX_RELAYHOST is not transferred to postfix/main.cf
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Oliver Kullmann <O.Kullmann>
Component: YaST2Assignee: Peter Varkoly <varkoly>
Status: RESOLVED INVALID QA Contact: Klaus Kämpf <kkaempf>
Severity: Normal    
Priority: P5 - None CC: varkoly
Version: unspecified   
Target Milestone: ---   
Hardware: 64bit   
OS: SuSE Linux 10.0   
Whiteboard:
Found By: Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Oliver Kullmann 2006-02-02 17:23:37 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.
Comment 1 Christian Boltz 2006-02-02 17:46:27 UTC
*** Bug 147723 has been marked as a duplicate of this bug. ***
Comment 2 Michael Gross 2006-02-03 12:04:21 UTC
I suppose SuSEconfig should export this setting here, I take the postfix-maintainer into CC here.
Comment 3 Ruediger Oertel 2006-02-06 17:14:37 UTC
reassigning to postfix maintainer
Comment 4 Peter Varkoly 2006-02-07 09:10:53 UTC
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?
Comment 5 Peter Varkoly 2006-02-14 12:11:27 UTC
Ladislav ???
Comment 6 Ladislav Slezák 2006-02-14 12:52:23 UTC
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.)
Comment 7 Peter Varkoly 2006-06-06 15:18:14 UTC
see the comment of ladislav