Bug 865132

Summary: Postfix main.cnf had mailbox_command stripped
Product: [openSUSE] openSUSE 13.1 Reporter: andrew cooke <andrew>
Component: OtherAssignee: Michal Filka <mfilka>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: chcao, forgotten_0SfHqLcqFR, jreidinger, varkoly, wagner-thomas
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 13.1   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: output from save_y2logs
the main.cf from /etc/postfix

Description andrew cooke 2014-02-21 15:43:48 UTC
Created attachment 579559 [details]
output from save_y2logs

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0

I was confusedly messing around with Yast network config (adding and then removing a bridge) when local mail delivery suddenly broke.  Instead of mail messages being delivered to a local maildir via procmail, they were being delivered to the system mailbox.

Looking at /etc/postfix, I saw that main.cnf had a modified date of today.  When I diffed it with a daily backup, the mailbox_command parameter had been cleared.  originally I had

  mailbox_command = /usr/bin/procmail

but that had been changed to

  mailbox_command =

Note - for some strange reason, this entry appeared TWICE in main.cnf.  Both entries were consistent, in either case.  So it would be more correct to say that originally I had it defined twice as procmail, and afterwards, it was cleared twice.

Grepping for "postfix" in y2log, I see

  y2log:2014-02-21 11:26:04 <1> block(7737) [Ruby] network/runtime.rb:48 Updating sendmail and/or postfix configuration.

which had the right date (and about the right time; by this point I had edited main.cnf and changed the timestamps, so I cannot check exactly).

That message seems to be associated with changes made when I deleted the bridge in Yast (but decide yourself; I will include the logs).

It seems that the "update" to postfix accidentally wiped important data.  This is not good.

Reproducible: Didn't try

Steps to Reproduce:
1. Sorry, but I don't want to mess around with this system more than necessary.
2.
3.
Comment 1 andrew cooke 2014-02-21 19:28:49 UTC
Created attachment 579597 [details]
the main.cf from /etc/postfix
Comment 2 andrew cooke 2014-02-24 02:08:44 UTC
[Sorry; I mistyped the file name almost everywhere above - it was main.cf]
Comment 3 Peter Varkoly 2015-09-23 15:39:01 UTC
*** Bug 852604 has been marked as a duplicate of this bug. ***
Comment 4 Michal Filka 2015-10-01 12:17:36 UTC
ok. There are three reports for the same bug already. 

@Peter:
Should I drop call to config.postfix from yast2-network completely?
Comment 5 Peter Varkoly 2015-10-11 08:36:35 UTC
(In reply to Michal Filka from comment #4)
> ok. There are three reports for the same bug already. 
> 
> @Peter:
> Should I drop call to config.postfix from yast2-network completely?

Yes please do it so.
Comment 7 Michal Filka 2016-06-23 08:24:45 UTC
Should be fixed in 3.1.158
Comment 8 Michal Filka 2016-06-23 08:25:14 UTC
(In reply to Michal Filka from comment #7)
> Should be fixed in 3.1.158

Should be fixed in yast2-network 3.1.158
Comment 10 Swamp Workflow Management 2016-07-18 13:09:25 UTC
SUSE-RU-2016:1817-1: An update that has four recommended fixes can now be installed.

Category: recommended (moderate)
Bug References: 852604,865132,970320,971175
CVE References: 
Sources used:
SUSE Linux Enterprise Software Development Kit 12-SP1 (src):    yast2-network-3.1.140.5-17.2
SUSE Linux Enterprise Server 12-SP1 (src):    yast2-network-3.1.140.5-17.2
SUSE Linux Enterprise Desktop 12-SP1 (src):    yast2-network-3.1.140.5-17.2
Comment 11 Swamp Workflow Management 2016-07-23 15:09:50 UTC
openSUSE-RU-2016:1857-1: An update that has four recommended fixes can now be installed.

Category: recommended (moderate)
Bug References: 852604,865132,970320,971175
CVE References: 
Sources used:
openSUSE Leap 42.1 (src):    yast2-network-3.1.140.5-9.1