Click on the red underlined text to get to the source
...
This is a proposal for additional header fields to be added to email
messages sent by email distribution lists. The content of each new
...
... additional header fields to be added to email
messages sent by email distribution lists. The content of each new
field is typically a URL - usually mailto ...
... by mail client applications to provide simplified and consistent user
access to email distribution list functions. This could take the form
of menu items, push buttons, or other user interface elements ...
... mailto protocols should be considered in
light of those users who do not have access to the specified
mechanism (those who only have email - with no web access).
...
... Command syntaxes requiring variable fields to be set by the client
(such as including the user's email address within a command) are not
supported by this implementation. However, systems using such
syntaxes SHOULD still take advantage of the List-Help field to
...
... header fields which will provide the
command syntax description for the 'core' and key secondary
functions of most email distribution lists. The fields implemented
on a given list SHOULD be included on all messages distributed by
the list (including command responses to individual users), and on
...
... fields being inserted or headers being forged, but these are problems
inherent in Internet email, not specific to the protocol described in
this document. Further, the implications are relatively harmless.
...
...
A standard command language, supported by all email list services,
would go a long way to reducing the problems of list access that
...
... to provide specialized feedback (such as presenting a dialog or
alert), instead of the actual command email message, asking for
command confirmation from the user. The feedback should identify the
message destination ...
... USA
EMail: josh@skyweyr.com
Grant Neufeld
...
... Canada
EMail: grant@acm.org
Web: http://www.nisto.com/
...