URL
Click on the red underlined text to get to the source
... messages sent by email distribution lists. The content of each new
field is typically a URL - usually mailto [RFC2368] - which locates
...
... mail headers as described in [RFC822]. Additionally,
the URL content is further restricted to the set of URL safe
characters [RFC1738 ...
... RFC822]. Additionally,
the URL content is further restricted to the set of URL safe
characters [RFC1738].
...
... The contents of the list header fields mostly consist of angle-
bracket ('<', '>') enclosed URLs, with internal whitespace being
ignored. MTAs MUST NOT insert whitespace within the brackets, but
...
...
A list of multiple, alternate, URLs MAY be specified by a comma-
separated list of angle-bracket enclosed URLs. The URLs ...
... A list of multiple, alternate, URLs MAY be specified by a comma-
separated list of angle-bracket enclosed URLs. The URLs have order of
preference from left to right. The client ...
... URLs MAY be specified by a comma-
separated list of angle-bracket enclosed URLs. The URLs have order of
preference from left to right. The client application should use the
...
... clients who do not have access to non-mail protocols. The client
should only use one of the available URLs for a command, using
another only if the first one used failed.
...
...
The use of URLs allows for the use of the syntax with existing URL
supporting applications. As the standard for URLs ...
...
The use of URLs allows for the use of the syntax with existing URL
supporting applications. As the standard for URLs is extended, the
...
... URLs allows for the use of the syntax with existing URL
supporting applications. As the standard for URLs is extended, the
list header fields will gain the benefit of those extensions.
...
... list header fields will gain the benefit of those extensions.
Additionally, the use of URLs provides access to multiple transport
protocols (such as ftp and http) although it is expected that the
"mailto ...
... '<', the field SHOULD be ignored.
2) Any characters following an angle bracket enclosed URL SHOULD be
ignored, unless a comma is the first non-whitespace/comment
character after the closing angle bracket.
...
...
3) If a sub-item (comma-separated item) within the field is not an
angle-bracket enclosed URL, the remainder of the field (the
current, and all subsequent, sub-items) SHOULD be ignored.
...
... manager to include only this field, since by definition it SHOULD
direct the user to complete instructions for all other commands.
Typically, the URL specified would request the help file, perhaps
incorporating an HTML form for list commands, for the list, and
...
... The List-Owner field identifies the path to contact a human
administrator for the list. The URL MAY contain the address of a
administrator ...
...
All security considerations for the use of URLs [RFC1738] apply
equally to this protocol. Mail client ...
... client applications should not support
list header field URLs which could compromise the security of the
user's system. This includes the "file://" URL ...
... URLs which could compromise the security of the
user's system. This includes the "file://" URL type which could
potentially be used to trigger the execution of a local application
on some user systems.
...
... meta-syntax in order
to describe the list commands (as opposed to the use of the widely
deployed URL syntax which was chosen for this implementation). Every
additional layer of complexity and newness reduces the likelihood of
...
... layer of complexity and newness reduces the likelihood of
actual implementation because it will require additional work to
support. Also, by using the existing URL syntax, we can profit from
the end users' knowledge of that syntax and ability to use it even if
their client ...
... A.2. URLs vs. parameter lists ...
...
URLs are already an established syntax which is flexible, well-
defined, and in wide spread use. As its definition matures and
expands, the abilities of the list fields will grow as well, without
...
... defined, and in wide spread use. As its definition matures and
expands, the abilities of the list fields will grow as well, without
requiring modification of this proposal. URLs are well prepared to
handle future protocols and developments, and can easily describe the
different existing access protocols such as mailto ...
... Many clients already have functionality for recognizing, parsing, and
evaluating URLs, either internally or by passing the request to a
helper application. This makes implementation easier and more
realistic. As an example, this existing support for URL ...
... URLs, either internally or by passing the request to a
helper application. This makes implementation easier and more
realistic. As an example, this existing support for URL parsing
allowed us to add prototype list header functionality to existing
...
... We can support most existing list manager command syntaxes without a
standard command language. By using URLs, we allow alternate access
methods a standard command language ...
...
Multilingual support is up to the URL standard. If URLs support it,
then the List- header fields ...
...
Multilingual support is up to the URL standard. If URLs support it,
then the List- header fields support it. This is another advantage of
...
... then the List- header fields support it. This is another advantage of
using URLs as the building blocks for the list header fields.
...
... every existing list manager. However, it would immeasurably increase
the complexity of the entire proposal, and possibly involve
redefining the URL standard, or force us to use something more
complicated (and hence more difficult to implement) than URLs to
...
... redefining the URL standard, or force us to use something more
complicated (and hence more difficult to implement) than URLs to
describe the command syntax.
...
... On others, the users will often see the header fields of messages and
would be able to recognize the function of the URLs contained within.
...
...
For 'mailto' URL based commands, mail client applications may choose
to provide specialized feedback (such as presenting a dialog or
...
... Berners-Lee, T., Masinter, L., and M. McCahill, "Uniform Resource Locators (URL)" RFC 1738(-> 4266prop | 4248prop), December 1994. ...
... Hoffman, P., Masinter, L., and J. Zawinski, "The mailto URL scheme", RFC 2368prop, July 1998. ...
... Header" Mail list. list-header@list.nisto.com <URL:http://www.nisto.com/listspec/mail/> <URL:http://www.nisto.com/listspec/ ...
... header@list.nisto.com <URL:http://www.nisto.com/listspec/mail/> <URL:http://www.nisto.com/listspec/> ...
... "ListMom-Talk" Mail list. listmom-talk@skyweyr.com <URL:http://cgi.skyweyr.com/ListMom.Home> ...