/usr/share/doc/cyrus-imspd/option.registry is in cyrus-imspd 1.8-3.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 | IMSP option registry
--------------------
by Chris Newman
Last update 02/16/00
In order to prevent conflicts in option naming, the namespace for IMSP
options needs to be controlled by a central registry. Two types of
registrations may be made:
1) Registration of an option prefix. Each client should register a
prefix. The client implementor or team then has complete control over
option names beginning with that prefix.
2) Registration of common options. If a specific option is deemed
useful for multiple clients, it can be registered in one of the shared
option hierarchies. A precise description of the option's function
must be sent with the registration. The registration authority
reserves the right to reject a registration, require that the
registered option be in use by multiple clients, or open the
proposal up for discussion.
NOTE: The IMAP integration features of the IMSP server have been
removed as of version 1.6a1 of the IMSP server. Therefore, many of
these options are deprecated.
Periodic updates of the registration list will be sent to the IMAP
discussion list.
Current procedure: Send the request in email to
imsp-options@andrew.cmu.edu
--------------------------------------
Common registered option prefixes:
Prefix Controller Description
------ ---------- -----------
common. registry Options useful to multiple clients.
desc. registry Text descriptions of other options.
imap. registry Options that affect or describe IMAP
server configuration.
imsp. registry Options that affect or describe IMSP
server configuration.
x. none Unrestricted option space for testing.
Client specific registered option prefixes:
Prefix Controller Product
------ ---------- -------
cyrus. Carnegie Mellon University X-Cyrus
ecsmail. ESYS Corp Simeon (formerly ECSmail)
eudora. Qualcomm Incorporated Eudora
mailstrom. Adam Treister Mailstrom
ML. Mike Macgirvin ML
pine. University of Washington Pine
simeon. ESYS Corp. Simeon
cyrusoft.mulberry. Cyrusoft International, Inc. Mulberry
--------------------------------------
Registered options:
common.date
The value of this option is the current date and time at the IMSP
server in the proper format for an RFC822 date header as updated
by RFC1123. This should be used in place of a client's internal
clock if there is reason to suspect the internal clock may not be
accurate.
common.delivery.hosts
The value of this option is a list of SMTP hosts for mail
submission. A client should try all hosts in the order specified
before announcing failure to the user.
common.domain
The value of this option is the RFC822 mail domain of the current
IMSP server. There is no requirement that a host with the
specified name exists, since a DNS MX record would be sufficient.
common.from
The value of this option is the RFC822 from address that should be
used for mail submitted by the current user. All clients should
use this option in order to leave administrative control of
whether and how users may adjust their from address to the IMSP
server implementation and configuration.
common.sent.mailbox
The value of this option is the name of a mailbox where copies of
all outgoing mail should be stored.
desc.<option-name>
A textual description of the option <option-name> that may be
desplayed to users to describe that option.
imap.charset
[proposal currently being discussed]
imsp.imap.servers [ Deprecated as of version 1.6a1 ]
The value of this option is a list of host-descriptors for the
IMAP servers managed by this IMSP server. A host-descriptor is a
hostname which may be followed by a "/" and an implementation
dependent string (used to identify the IMAP implementation as
necessary).
|