Corvid Email Local Address Attribute
Also Known AsImplemented in LDAP as the mailLocalAddress attribute:
- Local Email Addresses
DescriptionThe mailLocalAddress attribute specifies a set of local email addresses associated with an email account, that is, a dataset the email server can use to map an address to a unique account. This is a multivalued attribute: Each account can have zero, one, or several mailLocalAddress values.
mailLocalAddress is not necessarily the final destination for email, since the latter is determined by the mailRoutingAddress attribute.
ExampleOur sample user, Harry Bovik, currently has several values for this attribute:
LimitsThe host component of the email address must be a local host, and the domain can be any one under control of SCS Facilities. You may not use a host or domain that is outside the CMU SCS domain.
The following email addresses are not appropriate for mailLocalAddress
These examples are inappropriate because they refer to domains outside SCS Facilities control. The mailLocalAddress attribute is only for email addresses directly associated with a local SCS account.
If you want to forward your email offsite or to another organization on campus, please see the documentation about mailRoutingAddress .
Any email address associated with your account is unique. No other user can request the same email address as one that is already associated with your account. Once an address successfully works for your account, it will continue to be associated with your account until that address is removed. We will not remove or give away an email address associated with your account without first discussing the action with you personally. No other user can be added to the system that will cause your choices to become ambiguous or fail to match properly.
If another user has an email address associated with his or her account that you feel should be associated with your account, we will not remove that address from their account nor we will add it to your account without first consulting with and getting the permission from the owner of that account to remove that address.
If, while doing your work for CMU, you have obtained a domain name, such as specialevent2006.org, that does not end with cmu.edu, please contact <email@example.com> about the special work involved in getting email to that domain working as expected.
The format of the email address is restricted by rfc2822. We strongly prefer email addresses of 80 characters or less.
To specify a preferred email address please see the information about the mail attribute. The value of the mail attribute should be one of the mailLocalAddress values if you prefer a local email address.
Recommended ValuesThere are three types of email addresses we can use for the mailLocalAddress attribute:
- Name-based with domain:
- UID-based with domain:
- UID-based without domain:
In the Name-based address form, we seed localEmailAddress with information from the name attribute. But the name and email address can change independently. Adding addresses of this type to cover vanity or pseudonyms is acceptable but not recommended.
We strongly recommend the firstname.lastname@example.org and email@example.com forms. Many applications and users assume that email to firstname.lastname@example.org and/or email@example.com is a reasonable way to contact an account owner. When the Corvid mail system receives email addressed to firstname.lastname@example.org, the mail system will remove all content between the "+" and the "@" before searching the directory service for mailbox matches. So, all of the following email addresses will find their way to Harry Bovik's mailbox.
The last type of email address found in the values of localMailAddress is the one that is just uid or uid+. These are required and assist in the delivery of email to your local mailbox, even if you have your email forwarded offsite.