On Mon, 29 Jul 2002, Wichert Akkerman <[EMAIL PROTECTED]> wrote:
> > mail-reader: honestly, I fail to see a reason why this is sane.
> > "less /var/mail/moshez" is as good a mail reader as any.
> > what on earth would prompt someone to suggest a mail-reader
> > is truly beyond me.
>
> Mail notification programs what start a MUA when you click on them
> for example.
However, let me tell you what *currently* suggests mail-reader: MTAs.
Why? Damned if I know. As mail reader stands now, it is next to useless.
What you suggest is nice, but would require a different definition of
mail-reader (that is "something which reads /var/mail/<something>").
In this case, pms (which is mine) and nmh (which is someone else's) should
stop Provide:ing m-r.
> The name mail-reader suggests it doesn't. Perhapt it would be useful
> to introduce mail-user-agent, which is both a common name, unlike
> mail-reader, and has a proper definition:
>
> mail user agent
>
> <messaging> (MUA) The program that allows the user to compose
> and read {electronic mail} messages. The MUA provides the
> interface between the user and the {Message Transfer Agent}.
> Outgoing mail is eventually handed over to an MTA for delivery
> while the incoming messages are picked up from where the MTA
> left it (although MUA's running on single-user machines may
> pick up mail using {POP}).
Yep, I think that'd be useful. Again, I give "urlview" as an example of
something which would like a common interface. Also, browsers which are
capable of launching external programs for mailto: urls could use that
interface.
So far, all examples I can think of mandate an interface as a well-defined
path to a binary, with either Conflicts: or update-alternatives to negotiate
between multiple potential providers.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
