diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-October/008984.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-October/008984.html | 165 |
1 files changed, 165 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-October/008984.html b/zarb-ml/mageia-dev/2011-October/008984.html new file mode 100644 index 000000000..7b3978994 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-October/008984.html @@ -0,0 +1,165 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] [RFC] msec (nail) can't send reports to local users accounts - require an MTA? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BRFC%5D%20msec%20%28nail%29%20can%27t%20send%20reports%0A%20to%09local%09users%20accounts%20-%20require%20an%20MTA%3F&In-Reply-To=%3C4E9EEE66.9010608%40arcor.de%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="008973.html"> + <LINK REL="Next" HREF="008986.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] [RFC] msec (nail) can't send reports to local users accounts - require an MTA?</H1> + <B>Florian Hubold</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BRFC%5D%20msec%20%28nail%29%20can%27t%20send%20reports%0A%20to%09local%09users%20accounts%20-%20require%20an%20MTA%3F&In-Reply-To=%3C4E9EEE66.9010608%40arcor.de%3E" + TITLE="[Mageia-dev] [RFC] msec (nail) can't send reports to local users accounts - require an MTA?">doktor5000 at arcor.de + </A><BR> + <I>Wed Oct 19 17:36:06 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="008973.html">[Mageia-dev] [RFC] msec (nail) can't send reports to local users accounts - require an MTA? +</A></li> + <LI>Next message: <A HREF="008986.html">[Mageia-dev] [RFC] msec (nail) can't send reports to local users accounts - require an MTA? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#8984">[ date ]</a> + <a href="thread.html#8984">[ thread ]</a> + <a href="subject.html#8984">[ subject ]</a> + <a href="author.html#8984">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Am 19.10.2011 11:01, schrieb nicolas vigier: +><i> On Wed, 19 Oct 2011, andre999 wrote: +</I>><i> +</I>>><i> nicolas vigier a écrit : +</I>>>><i> On Tue, 18 Oct 2011, andre999 wrote: +</I>>>><i> +</I>>>>><i> Balcaen John a écrit : +</I>>>>><i> +</I>>>>>><i> Le lundi 17 octobre 2011 16:39:14 nicolas vigier a écrit : +</I>>>>>><i> [...] +</I>>>>>><i> +</I>>>>>><i> +</I>>>>>>><i> I think that : +</I>>>>>>><i> - changing the default configuration in an update is wrong. If it's +</I>>>>>>><i> better that msec do not send emails by default, I think this change +</I>>>>>>><i> should be done in cauldron only, maybe with some note about this change +</I>>>>>>><i> in the release notes for Mageia 2. +</I>>>>>>><i> +</I>>>>>>><i> +</I>>>>>><i> Agree. +</I>>>>>><i> +</I>>>>><i> A question : wouldn't changing the default in _both_ cauldron and an update +</I>>>>><i> to mga1 be acceptable ? +</I>>>>><i> +</I>>>><i> I think stable updates should not change defaults. +</I>>>><i> +</I>>>><i> +</I>>>>><i> Since I really think that sending messages silently to dead.letter, +</I>>>>><i> gradually filling up the disk is a bug. (When I first discovered the +</I>>>>><i> problem on my system a few years ago, dead.letter used about 1G of disk +</I>>>>><i> space in my root partition.) +</I>>>>><i> That is what happens with the default setting, if an MTA is not installed. +</I>>>>><i> At the default settings with an MTA installed, the root mailbox gradually +</I>>>>><i> fills up the disk, if it is not emptied. And a less informed user is +</I>>>>><i> unlikely to realise this. +</I>>>>><i> +</I>>>>><i> So it seems to me that as a minimum, the default should be changed to _not_ +</I>>>>><i> send alert emails. Since the status is visible on the main msec screen, +</I>>>>><i> informed users should have no problem appropriately adjusting the setting. +</I>>>>><i> +</I>>>>><i> To deal with the potential problem of users who use the email alert feature +</I>>>>><i> having it deactivated by the update, we only need a warning in the update, +</I>>>>><i> as often occurs for other packages. +</I>>>>><i> +</I>>>><i> Updates should not require manual changes. And not everybody read the +</I>>>><i> update logs from urpmi. People can expect important changes when upgrading +</I>>>><i> to a new version of the distribution, and that's why there is release +</I>>>><i> notes to explain the important changes, but not for stable updates. +</I>>>><i> +</I>>><i> Personally I am much more likely to notice the update log message from +</I>>><i> urpmi than everything in the release notes. I make a point of reading the +</I>>><i> former, which necessarily affect an application that I have installed. +</I>>><i> Most of the release notes comments are either painfully obvious, or affect +</I>>><i> something that I don't have installed or don't care about, so I tend to +</I>>><i> miss many details until I run into a problem. +</I>>><i> In this particular case, the problem would be not getting msec +</I>>><i> notifications. +</I>><i> People should not expect an update to change something that has been the +</I>><i> default for years. This kind of change should be done for a new release +</I>><i> of the distribution, not in updates. If you don't read the release +</I>><i> notes when doing upgrade changing important things, but always read +</I>><i> urpmi logs of updates that are supposed to have minimal changes, then +</I>><i> you're doing something wrong, but I hope not everybody does that. +</I>><i> +</I>>><i> Although I realise that in general it would be better to avoid significant +</I>>><i> changes in updates, in this case I think that most users would be better +</I>>><i> served by this change being introduced in an update, rather than in a +</I>>><i> release. +</I>><i> So you want to break something for some user, to improve it for some +</I>><i> others ? +</I>><i> +</I>><i> This has been the default for years. I don't see any reason to urgently +</I>><i> change this with an update. +</I>><i> +</I>>>>><i> Something like "If you use the msec alert emails, please verify that the +</I>>>>><i> alerts are still active." Note that if the user has ever explicitly set +</I>>>>><i> alerts, they would be still active. +</I>>>>><i> +</I>>><i> I was mistaken. But editing /etc/security/msec/security.conf to add the +</I>>><i> line "MAIL_WARN=yes" will protect from a default of "MAIL_WARN=no". +</I>>><i> (Tested.) +</I>>><i> +</I>>>>><i> This potential problem would exist even if the next update for the user is +</I>>>>><i> mga2. +</I>>>>><i> However, if the update is on mga2 (from changes in cauldron), wouldn't the +</I>>>>><i> change in defaults be less visible ? +</I>>>>><i> +</I>>><i> [...] +</I>>>>><i> According to documentation, dma is only active if no other MTA is installed. +</I>>>>><i> (I don't know if the priority is what causes this.) +</I>>>>><i> So at worst dma would be a (very small) harmless extra install, at best it +</I>>>>><i> would ensure the ability for local delivery. +</I>>>>><i> +</I>>>><i> Then dma could be installed by default on mageia 2, this would fix the +</I>>>><i> problem for all programs using the sendmail command, not only msec, +</I>>>><i> without adding a require on dma. +</I>>>><i> +</I>>><i> That would work, as long as it is a "require" of Mageia 2. +</I>><i> Not a require, but installed by default. And msec should have a require +</I>><i> on sendmail-command. +</I>><i> +</I>><i> +</I>So to make this clear for Mageia 1 we keep msec as it currently is, not changing +anything and for Cauldron should i already add Requires: sendmail-command? + + +BTW: Would have been nice if you would have dropped your opinion earlier in the +thread, that would have saved much email noise and you would have prevented +quite some investigative work which got in there IMHO ... +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="008973.html">[Mageia-dev] [RFC] msec (nail) can't send reports to local users accounts - require an MTA? +</A></li> + <LI>Next message: <A HREF="008986.html">[Mageia-dev] [RFC] msec (nail) can't send reports to local users accounts - require an MTA? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#8984">[ date ]</a> + <a href="thread.html#8984">[ thread ]</a> + <a href="subject.html#8984">[ subject ]</a> + <a href="author.html#8984">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |