Every night I find a spurious file created in / This file is called /dead.letter, and begins as below: I'm working on a freshly installed (and hardly tweaked) Mageia 2 Beta system. I suspect this is fairly minor, but surely this isn't the place to leave such a file, and shouldn't the installer have prompted for the info it needs? ------ Date: Sat, 10 Mar 2012 04:02:03 +0000 To: rjn Subject: [msec] *** Security Check on chocolate.ruo3.org, Mar 10 04:02:02 *** User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit *** Security Check, Mar 10 04:02:02 *** *** Check type: daily *** *** Check executed from: /etc/cron.daily/msec *** Report summary: Test started: Mar 10 04:02:02 Test finished: Mar 10 04:02:03 Total of open network ports: 27 Total of configured firewall rules: 118 Total local users: 34 .... Total local group: 55
Source RPM: (none) => msec
dmorgan, can you (as the listed maintainer) have a look at this please? If you accept this bug report, please set the status to assigned.
Assignee: bugsquad => dmorganec
IIRC this is a repeat of an old Mandriva bug that was fixed. It had something to do with msec producing messages that had embedded UTF-8 characters, and were deemed by the mail application involved to be unsatisfactory.
CC: (none) => ftg
I'm fairly sure that this isn't the problem. I just tried forcing conversion to ascii and comparing: iconv /dead.letter -o test.txt -f utf8 -t ascii diff /dead.letter test.txt ; echo $? resulting in 0. i.e. the file is already 7-bit clean. I wonder whether it's actually caused by having no mail server application installed? Have just installed postfix; will see if this helps.
>I wonder whether it's actually caused by having no mail server application That could certainly do it. There was another thread in the mageia-dev ML some time ago about problems caused by msec sending mail on systems without an MTA installed, and under what circumstances we should be installing one anyway (and which one) whether the user checked the "Mail" group or not.
In the meantime, might I suggest that leaving the file in /var/log and calling it something like msec_report would be better?
I think you'd better read the thread, which was extensive and discussed many proposals. Msec already writes its reports to the filesystem. The problem occurred when users would fill in a mail recipient on the Sumary Security screen of the Install, but had not chosen to install an MTA, basically telling msec to mail the reports, but giving it no way to do so. A lot of the discussion centered on the undesirablility of installing an MTA that would require configuration in order to be usable.
That makes some sense. In the meantime, a perfect fix for this bug isn't nearly as important as documenting/crossreferencing it where the user can see it. I suspect the simplest thing to do would be to add an explanation on that summary screen of the installer: something like: Who should get emailed by msec's reports [______] (You need to install an MTA, but haven't selected one; it's OK to leave this blank)
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
I suspect this is still true, but I'd have to re-run the installer to make sure. Can I suggest that my comment #7 would be a simple fix?
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
[michael@localhost ~]$ chocolate-doom Chocolate Doom 1.7.0 Z_Init: Init zone memory allocation daemon. zone memory: 0xb5bf0008, 1000000 allocated for zone DEH_Init: Init Dehacked support. Game mode indeterminate. No IWAD file was found. Try specifying one with the '-iwad' command line parameter.
CC: (none) => michaelfm21
Keywords: NEEDINFO => (none)Hardware: x86_64 => All
[michael@localhost ~]$ uname -a Linux localhost 3.3.8-desktop-2.mga2 #1 SMP Mon Jul 30 21:42:09 UTC 2012 i686 i686 i386 GNU/Linux [michael@localhost ~]$ cat /etc/issue Mageia release 2 (Official) for i586 Kernel 3.3.8-desktop-2.mga2 on a 4-processor i686 / \l
Assignee: dmorganec => bugsquad
(In reply to Richard Neill from comment #7) > That makes some sense. > > In the meantime, a perfect fix for this bug isn't nearly as important as > documenting/crossreferencing it where the user can see it. > > I suspect the simplest thing to do would be to add an explanation on that > summary screen of the installer: something like: > > Who should get emailed by msec's reports [______] > > (You need to install an MTA, but haven't selected one; it's OK > to leave this blank) In order to make things simpler to follow, since it isn't a bug I suggest to open a new enhancement request with your proposal, and will close this bug report as OLD.
Status: NEW => RESOLVEDResolution: (none) => OLD