Add

   Syntax: add alias-name alias-value [attributes[,...]]

   With the add command an alias and its expansion value can be
   added to the database currently opened. If the alias expansion
   value contains any spaces, commas, or upper case characters
   which should not be converted to lower case, then the expansion
   value must be enclosed in double quotes. Any double quotes in
   the expansion value must be "doubled" (i.e., entered as two
   consecutive double quotes). Examples of these two cases are:

db> add STAFF "BOB@EXAMPLE.COM,SUE@EXAMPLE.COM,TOM@EXAMPLE.COM"
db> add JOHN-FAX """/FN=x8645/AT=Jo Doe/""@text-fax.EXAMPLE.com"
db> add LDAP-ALL <"""ldap:///dc=example,dc=edu?mail?sub?(cn=*)"""

   The first add command establishes the alias

      STAFF - >  BOB@EXAMPLE.COM,SUE@EXAMPLE.COM,TOM@EXAMPLE.COM

   This alias required quoting since it included commas. The second
   add command establishes the alias


      JOHN-FAX - >  "/FN=x8645/AT=John Doe/"@text-fax.example.com

   and was enclosed in double quotes because of the space in it, and
   the need to not convert John Doe's name to "john doe". Also,
   the double quotes present in the alias expansion value were
   doubled; that is, each double quote, ", was specified as two
   double quotes, "".

   The third add command establishes the alias


      LDAP-ALL - >  <"ldap:///dc=example,dc=edu?mail?sub?(cn=*)"

   Which means that PMDF will expand the alias into a mailing list
   by performing an LDAP query using the LDAP URL specified.

   As another example, consider entering the alias JD with the
   simple expansion value JD573@VAXC.EXAMPLE.COM:

   db> add JD JD573@VAXC.EXAMPLE.COM
   [Entry added to database]
   db> show JD
   Key         Value
   ----------  -----------------------------
   jd          jd573@vaxc.example.com
   [1 entry shown]
   db>

   Note that the alias name along with its translation value was
   converted to lower case. DB will always translate the name of
   an alias to lower case; PMDF does not do case sensitive alias
   matching. To prevent the alias translation value from being
   converted to lower case, enclose it in double quotes; e.g.,

   db> modify JD "JD573@VAXC.EXAMPLE.COM"
   [1 entry modified]
   db> show JD
   Key         Value
   ----------  -----------------------------
   jd          JD573@VAXC.EXAMPLE.COM
   [1 entry shown]
   db>

   The optional attributes parameter of the add command can be one
   or more comma separated keywords selected from the list:
 

mail-address

   Treat this alias as a mail address; i.e., set the mail address
   attribute flag for this alias. Default when in either normal or
   FAX mode. Not set when an "override on" command has been issued.
 

non-mail-address

   Do not treat this alias as a mail address; i.e., clear the mail
   address attribute flag for this alias.
 

fax-address

   Treat this alias as a FAX address; i.e., set the FAX address
   attribute flag for this alias. Default when in FAX mode. Not set
   when an "override on" command has been issued.
 

non-fax-address

   Do not treat this alias as a FAX address; i.e., clear the FAX
   address attribute flag for this alias.
 

public

   Mark this alias as being publicly accessible. Other users can
   reference this alias by sending mail to an address of the form
   USER+ALIAS@LOCAL-HOST. When this alias is used in outgoing mail
   and is not expanded into component addresses, it will appear
   in the message in the form USER+ALIAS@LOCAL-HOST. Public is the
   opposite of the private attribute described below.
 

private

   Mark this alias as being private. Other users will not be able
   to use this alias. If this alias appears in outgoing mail (and
   is not expanded into its component addresses) it will appear as
   an unexpanded RFC 822 group address: ALIAS: ;. Private is the
   opposite of the public attribute described above.
 

expand

   This attribute forces the expansion of the alias into its
   component addresses. All of the component addresses will be
   listed in the message header as the alias expands.
 

no-expand

   This attribute inhibits the expansion of the alias into its
   component addresses. The alias itself will appear in the header
   in some form; see the description of the public and private
   attributes above for details on the forms the alias can take.
 

pass-receipts

   This attribute enables the passage of requests for delivery and
   read receipts through to all recipients as the alias is expanded.
   Note that allowing the passage of such a request to a large
   distribution list can result in a lot of return mail.
 

block-receipts

   This attribute disables the passage of requests for delivery
   and read receipts through to all recipients as the alias is
   expanded. Requests for such receipts are honored at the time
   the alias expands; in effect the alias is treated as the message
   destination.

   When an alias is entered with the add command at the "db>"
   prompt, the alias will automatically be given the mail address
   attribute unless an "override on" command has been previously
   issued or the non-mail-address keyword is specified with the add
   command.