Re: default MTA

2013-05-28 Thread Redalert Commander
2013/5/28 Josselin Mouette :
> Le mardi 28 mai 2013 à 12:13 +0200, Adam Borowski a écrit :
>> Being able to send outgoing mail, and to handle local (such as SMTP rejects
>> or notifications from system daemons) seems plenty useful to me.
>
> Most clients (apart maybe from mailx) can use an external SMTP server to
> send email.
>
> And on desktop systems, nobody reads local email. We might want to think
> of a better notification system, but email is definitely not fit for
> that anymore.
>

I don't think that is true at all. Personally, I use it to get the
reports from smartd,
from btrfs scrub cron jobs, other cron jobs, the changelogs for updated packages
get mailed there, which I really like (happens only with certain packages).
It certainly makes my life easier.
I imagine a lot of people on a desktop use it, admittedly not everyone.
I do like the proposal to replace the current default MTA with a more
lightweight system for desktops,
but to remove it completely doesn't seem like a good idea to me.

Regards,
Steven


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camdu+mnh2p2j65aiy-3dvg3xuz1tl68w8+qgj3jop9prazg...@mail.gmail.com



Re: default MTA

2013-05-28 Thread Redalert Commander
2013/5/28 Simon McVittie :
[...]
>
> The participants in this thread are debian-devel subscribers: the sort
> of people who know that Debian is a Unix system, know what a Unix system
> is, and have some idea of what a "btrfs scrub cron job", or indeed an
> MTA, means. That's a pretty limiting audience for an operating system.
> The Universal Operating System should also be usable by people who don't
> meet those criteria, and I think Joss is right to speak up on their behalf.
>
> I'm quite prepared to believe that *our* Unix systems - and in
> particular, servers and development machines - need an MTA, but my
> parents' laptops really shouldn't need one. Ideally, we can have a
> sensible default that is suitable for both experts and non-experts; but
> if we can't, then the non-experts should probably have priority. After
> all, the sort of people who read debian-devel know how to switch away
> from a default MTA that isn't suitable for us, but my parents don't even
> know that they *have* an MTA.
>

I agree that a lot of (if not most) non-tech people probably don't use it, I do
see some benefits to this as opposed to desktop notifications. I
believe there was
a similar discussion going on about Ubuntu update notifications a few years ago,
when they started just popping up the update-manager window. My point here
being that those e-mails are more persistent than some notification
that can easily
get lost. Or perhaps there should be a more permanent system for such
notifications.
I'm not talking about the output of the btrfs scrub, but consider
important messages
on upgrades, such as were some things break compatibility with something and the
user needs to know that. For instance as the consequence of a security fix,
something no longer works (java applet? Instant messaging application?
that sort of
thing). You don't want a volatile message that they can't review after a reboot,
maybe they haven't even seen it if they ware away from the computer.
Also the e-mail doesn't get in the way of things, your work doesn't
get interrupted
by an e-mail, whereas desktop notifications may be more intrusive.

Perhaps there is a need for more permanent desktop notifications,
besides the current one-time notifications such as "USB storage drive has
been detected". Something that persists a reboot. I don't know, I'm
just brainstorming here.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camdu+mn_jqp6qb2yhfjqncu3t0sgzvlsbfy1ka-couytux6...@mail.gmail.com