F20 - Unintended consequences of no default MTA - How best to fix

[Chris Murphy]

On Jan 3, 2014, at 6:41 PM, "Lars E. Pettersson" <lars at homer.se> wrote:

> On 01/04/2014 02:40 AM, Suvayu Ali wrote:
>> What I fail to follow is, why break the existing mechanism *before* we
>> have these other future notification mechanisms ready?
> 
> *Exactly*

Please, SNMP has been around since 1988. Gnome has had a notification system for several years at least, probably longer. If I did 10 minutes of research there are probably 1/2 dozen other notification systems out there, a few of which are reasonably mature.

So how long do you want for your ancient email only sending program to modernize? They haven't picked an alternative by choice. And it is their choice to not do so. It is inappropriate for Fedora to sit on its laurels waiting for every program to modernize before it makes changes the benefit most users. And it's inappropriate for Fedora to dictate these programs use some other method of notification than email.

So *exactly* what are you two even talking about? Precisely how does waiting and doing NOTHING encourage program devs to change their notification methods? OH right, it doesn't do anything except enhance the stagnation and legitimize the non-working notification by email paradigm.

Guess what? Presumably the programs that you use that only notify by email, do not modernize because their user base doesn't care for any other kind of notification system. In which case you will have to install an MTA to get your important messages. I don't see what's so difficult to understand.

Chris Murphy