[Bug 865132] New: Postfix main.cnf had mailbox_command stripped
https://bugzilla.novell.com/show_bug.cgi?id=865132 https://bugzilla.novell.com/show_bug.cgi?id=865132#c0 Summary: Postfix main.cnf had mailbox_command stripped Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: andrew@acooke.org QAContact: qa-bugs@suse.de Found By: --- Blocker: --- Created an attachment (id=579559) --> (http://bugzilla.novell.com/attachment.cgi?id=579559) 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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=865132
https://bugzilla.novell.com/show_bug.cgi?id=865132#c1
--- Comment #1 from andrew cooke
https://bugzilla.novell.com/show_bug.cgi?id=865132
https://bugzilla.novell.com/show_bug.cgi?id=865132#c
andrew cooke
https://bugzilla.novell.com/show_bug.cgi?id=865132
https://bugzilla.novell.com/show_bug.cgi?id=865132#c
Xiyuan Liu
https://bugzilla.novell.com/show_bug.cgi?id=865132
https://bugzilla.novell.com/show_bug.cgi?id=865132#c2
--- Comment #2 from andrew cooke
http://bugzilla.novell.com/show_bug.cgi?id=865132
SMASH SMASH
http://bugzilla.novell.com/show_bug.cgi?id=865132
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=865132
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=865132
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=865132
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=865132
http://bugzilla.novell.com/show_bug.cgi?id=865132#c10
--- Comment #10 from Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=865132
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=865132
http://bugzilla.novell.com/show_bug.cgi?id=865132#c11
--- Comment #11 from Swamp Workflow Management
participants (1)
-
bugzilla_noreply＠novell.com