[Index]
| Title | Description | Details | |||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| UseMapiRichTextFormat | The UseMapiRichTextFormat parameter specifies what to do with messages that are sent to the mail user or mail contact in MAPI rich text format, also known as Outlook Rich Text or Transport Neutral Encapsulation Format (TNEF). Valid values are: Always TNEF is used for all messages sent to the mail user or mail contact. Never TNEF is never used for any messages sent to the mail user or mail contact. TNEF messages are converted to plain text. UseDefaultSettings TNEF messages aren't specifically allowed or prevented for the mail user or mail contact. Whether TNEF messages are sent to the recipient depends on the remote domain TNEF settings (the default remote domain or a specific remote domain), or the Outlook Rich Text message settings specified by the sender in Outlook. The default value is UseDefaultSettings. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| RequireSenderAuthenticationEnabled | The RequireSenderAuthenticationEnabled parameter specifies whether to accept messages only from authenticated (internal) senders. Valid values are: $true Messages are accepted only from authenticated (internal) senders. Messages from unauthenticated (external) senders are rejected. $false Messages are accepted from authenticated (internal) and unauthenticated (external) senders. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| PSShowComputerName |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| AdministrativeUnits |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| LastExchangeChangedTime |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Initials | The Initials parameter specifies the user's middle initials. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| OriginatingServer |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| HiddenFromAddressListsEnabled | The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are: $true The recipient isn't visible in address lists. $false The recipient is visible in address lists. This is the default value. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| WindowsEmailAddress | The WindowsEmailAddress parameter specifies the Windows email address for this recipient. This is a common Active Directory attribute that's present in all environments, including environments without Exchange. Using the WindowsEmailAddress parameter on a recipient has one of the following results: In on-premises environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is set to the value True for the recipient), the WindowsEmailAddress parameter has no effect on the WindowsEmailAddress property or the primary email address value. In cloud environments or in on-premises environments where the recipient isn't subject to email address policies (the EmailAddressPolicyEnabled property is set to the value False for the recipient), the WindowsEmailAddress parameter updates the WindowsEmailAddress property and the primary email address to the same value. The WindowsEmailAddress property is visible for the recipient in Active Directory Users and Computers in the E-mail attribute. The attribute common name is E-mail-Addresses, and the Ldap-Display-Name is mail. If you modify this attribute in Active Directory, the recipient's primary email address is not updated to the same value. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| ModeratedBy | The ModeratedBy parameter specifies one or more moderators for this mail contact. A moderator approves messages sent to the mail contact before the messages are delivered. A moderator must be a mailbox, mail user, or mail contact in your organization. You can use any value that uniquely identifies the moderator. For example: Name Display name Alias Distinguished name (DN) Canonical DN Email address GUID To enter multiple values and overwrite any existing entries, use the following syntax: <value1>,<value2>.... If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "<value1>","<value2>".... To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="<value1>","<value2>"...; Remove="<value1>","<value2>"...}. You need to use this parameter to specify at least one moderator when you set the ModerationEnabled parameter to the value $true. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| RejectMessagesFrom | The RejectMessagesFrom parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected. Valid values for this parameter are individual senders in your organization (mailboxes, mail users, and mail contacts). You can use any value that uniquely identifies the sender. For example: Name Display name Alias Distinguished name (DN) Canonical DN Email address GUID You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: <sender1>,<senter2>.... If the values contain spaces or otherwise require quotation marks, use the following syntax: "<sender1>","<sender2>".... To add or remove senders without affecting other existing entries, use the following syntax: @{Add="<sender1>","<sender2>"...; Remove="<sender1>","<sender2>"...}. The senders you specify for this parameter are automatically copied to the RejectMessagesFromSendersOrMembers property. Therefore, you can't use the RejectMessagesFrom and RejectMessagesFromSendersOrMembers parameters in the same command. By default, this parameter is blank ($null), which allows this recipient to accept messages from all senders. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| WhenCreated |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Extensions |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| LegacyExchangeDN |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Organization | This parameter is reserved for internal Microsoft use. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| ExchangeVersion |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| ArbitrationMailbox | This parameter is available only in on-premises Exchange 2016. The ArbitrationMailbox parameter specifies the arbitration mailbox that's used to manage the moderation process for this recipient. You can use any value that uniquely identifies the arbitration mailbox. For example: Name Display name Alias Distinguished name (DN) Canonical DN <domain name>\<account name> Email address GUID LegacyExchangeDN SamAccountName User ID or user principal name (UPN) |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| MessageFormat | The MessageBodyFormat parameter specifies the message body format for messages sent to the mail contact or mail user. Valid values are: Text Html TextAndHtml This is the default value. The MessageFormat and MessageBodyFormat parameters are interdependent: MessageFormat is MimeMessageBodyFormat can be Text, Html, or TextAndHtml. MessageFormat is TextMessageBodyFormat can only be Text. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| AcceptMessagesOnlyFromDLMembers | The AcceptMessagesOnlyFromDLMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected. Valid values for this parameter are groups in your organization (distribution groups, mail-enabled security groups, and dynamic distribution groups). Specifying a group means all members of the group are allowed to send messages to this recipient. You can use any value that uniquely identifies the group. For example: Name Display name Alias Distinguished name (DN) Canonical DN Email address GUID You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: <group1>,<group2>.... If the values contain spaces or otherwise require quotation marks, use the following syntax: "<group1>","<group2>".... To add or remove groups without affecting other existing entries, use the following syntax: @{Add="<group1>","<group2>"...; Remove="<group1>","<group2>"...}. The groups you specify for this parameter are automatically copied to the AcceptMessagesOnlyFromSendersOrMembers property. Therefore, you can't use the AcceptMessagesOnlyFromDLMembers and AcceptMessagesOnlyFromSendersOrMembers parameters in the same command. By default, this parameter is blank ($null), which allows this recipient to accept messages from all groups. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| RejectMessagesFromSendersOrMembers | The RejectMessagesFromSendersOrMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected. Valid values for this parameter are individual senders and groups in your organization. Individual senders are mailboxes, mail users, and mail contacts. Groups are distribution groups, mail-enabled security groups, and dynamic distribution groups. Specifying a group means all members of the group aren't allowed to send messages to this recipient. To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: Name Display name Alias Distinguished name (DN) Canonical DN Email address GUID You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: <sender1>,<senter2>.... If the values contain spaces or otherwise require quotation marks, use the following syntax: "<sender1>","<sender2>".... To add or remove individual senders or groups without affecting other existing entries, use the RejectMessagesFrom and RejectMessagesFromDLMembers parameters. The individual senders and groups you specify for this parameter are automatically copied to the RejectMessagesFrom and RejectMessagesFromDLMembers properties, respectively. Therefore, you can't use the RejectMessagesFromSendersOrMembers parameter and the RejectMessagesFrom or RejectMessagesFromDLMembers parameters in the same command. By default, this parameter is blank ($null), which allows this recipient to accept messages from all senders. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| RunspaceId |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Guid |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| RecipientTypeDetails | The RecipientTypeDetails parameter specifies the type of recipients returned. Recipient types are divided into recipient types and subtypes. Each recipient type contains all common properties for all subtypes. For example, the type UserMailbox represents a user account in Active Directory that has an associated mailbox. Because there are several mailbox types, each mailbox type is identified by the RecipientTypeDetails parameter. For example, a conference room mailbox has RecipientTypeDetails set to ConferenceRoomMailbox, whereas a user mailbox has RecipientTypeDetails set to UserMailbox. You can select from the following values: ArbitrationMailbox ConferenceRoomMailbox Contact DiscoveryMailbox DynamicDistributionGroup EquipmentMailbox ExternalManagedContact ExternalManagedDistributionGroup LegacyMailbox LinkedMailbox MailboxPlan MailContact MailForestContact MailNonUniversalGroup MailUniversalDistributionGroup MailUniversalSecurityGroup MailUser PublicFolder RoleGroup RoomList RoomMailbox SharedMailbox SystemAttendantMailbox SystemMailbox User UserMailbox |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| MailTipTranslations | The MailTipTranslations parameter specifies additional languages for the custom MailTip text that's defined by the MailTip parameter. HTML tags are automatically added to the MailTip translation, additional HTML tags aren't supported, and the length of the MailTip translation can't exceed 175 displayed characters. To add or remove MailTip translations without affecting the default MailTip or other MailTip translations, use the following syntax: @{Add="<culture 1>:<localized text 1>","<culture 2>:<localized text 2>"...; Remove="<culture 3>:<localized text 3>","<culture 4>:<localized text 4>"...} <culture> is a valid ISO 639 two-letter culture code that's associated with the language. For example, suppose this recipient currently has the MailTip text: "This mailbox is not monitored." To add the Spanish translation, use the following value for this parameter: @{Add="ES:Esta caja no se supervisa."}. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| DisplayName | The DisplayName parameter specifies the display name of the mail contact. The display name is visible in the Exchange admin center and in address lists. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks ("). If you don't use the DisplayName parameter, the value of the Name parameter is used for the display name. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| OrganizationId |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| SimpleDisplayName | The SimpleDisplayName parameter is used to display an alternative description of the object when only a limited set of characters is permitted. Valid characters are: a - z A - Z 0 - 9 "<space>", """, "'", "(", ")", "+", ",", "-", ".", "/", ":", and "?". |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| ModerationEnabled | The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are: $true Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered. $false Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value. You use the ModeratedBy parameter to specify the moderators. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| MaxSendSize | This parameter is available only in on-premises Exchange 2016. The MaxSendSize parameter specifies the maximum size of a message that can be sent by the mail contact. When you enter a value, qualify the value with one of the following units: B (bytes) KB (kilobytes) MB (megabytes) GB (gigabytes) TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. A valid value is number up to 2 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited. The value unlimited indicates the maximum send size for the mail contact is controlled elsewhere (for example, organization, server, or connector limits). For any message size limit, you need to set a value that's larger than the actual size you want enforced. This accounts for the Base64 encoding of attachments and other binary data. Base64 encoding increases the size of the message by approximately 33%, so the value you specify should be approximately 33% larger than the actual message size you want enforced. For example, if you specify a maximum message size value of 64 MB, you can expect a realistic maximum message size of approximately 48 MB. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| HasSpokenName |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| HasPicture |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| AcceptMessagesOnlyFrom | The AcceptMessagesOnlyFrom parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected. Valid values for this parameter are individual senders in your organization (mailboxes, mail users, and mail contacts). You can use any value that uniquely identifies the sender. For example: Name Display name Alias Distinguished name (DN) Canonical DN Email address GUID You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: <sender1>,<senter2>.... If the values contain spaces or otherwise require quotation marks, use the following syntax: "<sender1>","<sender2>".... To add or remove senders without affecting other existing entries, use the following syntax: @{Add="<sender1>","<sender2>"...; Remove="<sender1>","<sender2>"...}. The senders you specify for this parameter are automatically copied to the AcceptMessagesOnlyFromSendersOrMembers property. Therefore, you can't use the AcceptMessagesOnlyFrom and AcceptMessagesOnlyFromSendersOrMembers parameters in the same command. By default, this parameter is blank ($null), which allows this recipient to accept messages from all senders. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| DistinguishedName |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| UserCertificate |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| PoliciesExcluded |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| BypassModerationFromSendersOrMembers | The BypassModerationFromSendersOrMembers parameter specifies who is allowed to send messages to this moderated recipient without approval from a moderator. Valid values for this parameter are individual senders and groups in your organization. Specifying a group means all members of the group are allowed to send messages to this recipient without approval from a moderator. To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: Name Display name Alias Distinguished name (DN) Canonical DN Email address GUID To enter multiple senders and overwrite any existing entries, use the following syntax: <sender1>,<sender2>.... If the values contain spaces or otherwise require quotation marks, use the following syntax: "<sender1>","<sender2>".... To add or remove one or more senders without affecting any existing entries, use the following syntax: @{Add="<sender1>","<sender2>"...; Remove="<sender3>","<sender4>"...}. This parameter is meaningful only when moderation is enabled for the recipient. By default, this parameter is blank ($null), which means messages from all senders other than the designated moderators are moderated. When a moderator sends a message to this recipient, the message is isn't moderated. In other words, you don't need to use this parameter to include the moderators. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| MaxReceiveSize | This parameter is available only in on-premises Exchange 2016. The MaxReceiveSize parameter specifies the maximum size of a message that can be sent to the mail contact. Messages larger than the maximum size are rejected. When you enter a value, qualify the value with one of the following units: B (bytes) KB (kilobytes) MB (megabytes) GB (gigabytes) TB (terabytes) Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte. A valid value is a number up to 2 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited. The value unlimited indicates the maximum receive size for the mail contact is controlled elsewhere (for example, organization, server, or connector limits). For any message size limit, you need to set a value that's larger than the actual size you want enforced. This accounts for the Base64 encoding of attachments and other binary data. Base64 encoding increases the size of the message by approximately 33%, so the value you specify should be approximately 33% larger than the actual message size you want enforced. For example, if you specify a maximum message size value of 64 MB, you can expect a realistic maximum message size of approximately 48 MB. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| AcceptMessagesOnlyFromSendersOrMembers | The AcceptMessagesOnlyFromSendersOrMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected. Valid values for this parameter are individual senders and groups in your organization. Individual senders are mailboxes, mail users, and mail contacts. Groups are distribution groups, mail-enabled security groups, and dynamic distribution groups. Specifying a group means all members of the group are allowed to send messages to this recipient. To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: Name Display name Alias Distinguished name (DN) Canonical DN Email address GUID You can enter multiple senders separated by commas. To overwrite any existing entries, use the following syntax: <sender1>,<senter2>.... If the values contain spaces or otherwise require quotation marks, use the following syntax: "<sender1>","<sender2>".... To add or remove individual senders or groups without affecting other existing entries, use the AcceptMessagesOnlyFrom and AcceptMessageOnlyFromDLMembers parameters. The individual senders and groups you specify for this parameter are automatically copied to the AcceptMessagesOnlyFrom and AcceptMessagesOnlyFromDLMembers properties, respectively. Therefore, you can't use the AcceptMessagesOnlyFromSendersOrMembers parameter and the AcceptMessagesOnlyFrom or AcceptMessagesOnlyFromDLMembers parameters in the same command. By default, this parameter is blank ($null), which allows this recipient to accept messages from all senders. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| DomainController | This parameter is available only in on-premises Exchange 2016. The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| UsePreferMessageFormat | The UsePreferMessageFormat specifies whether the message format settings configured for the mail user or mail contact override the global settings configured for the remote domain or configured by the message sender. Valid value are: $true Messages sent to the mail user or mail contact use the message format that's configured for the mail user or mail contact. $false Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This is the default value. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| IsValid |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| WhenChanged |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| ObjectState |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| ExternalEmailAddress * | The ExternalEmailAddress parameter specifies the target email address of the mail contact or mail user. By default, this value is used as the primary email address of the mail contact or mail user. In on-premises environments, you can use the PrimarySMTPAddress parameter to set the primary email address to a different value. However, we recommend this only in cross-forest environments. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| EmailAddressPolicyEnabled | This parameter is available only in on-premises Exchange 2016. The EmailAddressPolicyEnabled parameter specifies whether to apply email address policies to this recipient. Valid values are: $true All applicable email address policies are applied to this recipient. This is the default value. $false No email address policies are applied to this recipient. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| MaxRecipientPerMessage | This parameter is available only in on-premises Exchange 2016. The MaxRecipientPerMessage parameter specifies the maximum number of recipients allowed in messages sent by the mail contact. A valid value is an integer up to 2147483647 (Int32) or the value unlimited. The default value is unlimited. The value unlimited indicates the maximum number of recipients per message for the mail contact is controlled elsewhere (for example, organization, server, or connector limits). |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| FirstName | The FirstName parameter specifies the user's first name. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| LastName | The LastName parameter specifies the user's last name. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| EmailAddresses | The EmailAddresses parameter specifies all the email addresses (proxy addresses) for the recipient, including the primary SMTP address. In on-premises Exchange organizations, the primary SMTP address and other proxy addresses are typically set by email address policies. However, you can use this parameter to configure other proxy addresses for the recipient. For more information, see Email address policies in Exchange 2016. Valid syntax for this parameter is [<Type>]:<emailaddress1>,[<Type>]:<emailaddress2>.... The optional <Type> value specifies the type of email address. Some examples of valid values include: SMTP The primary SMTP address. You can use this value only once in a command. smtp Other SMTP email addresses. X400 X.400 addresses in on-premises Exchange. X500 X.500 addresses in on-premises Exchange. If you don't include a <Type> value for an email address, the value smtp is assumed. Note that Exchange doesn't validate the syntax of custom address types (including X.400 addresses). Therefore, you need to verify that any custom addresses are formatted correctly. To specify the primary SMTP email address, you can use any of the following methods: Use the <Type> value SMTP on the address. The first email address when you don't use any <Type> values, or when you use multiple <Type> values of smtp. If it's available, use the PrimarySmtpAddress parameter instead. You can't use the EmailAddresses parameter and the PrimarySmtpAddress parameter in the same command. To replace all existing proxy email addresses with the values you specify, use the following syntax: "[<Type>]:<emailaddress1>","[<Type>]:<emailaddress2>".... To add or remove specify proxy addresses without affecting other existing values, use the following syntax: @{Add="[<Type>]:<emailaddress1>","[<Type>]:<emailaddress2>"...; Remove="[<Type>]:<emailaddress2>","[<Type>]:<emailaddress2>"...}. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| PSComputerName |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| PrimarySmtpAddress | This parameter is available only in on-premises Exchange 2016. The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient. If it's available on this cmdlet, you can't use the EmailAddresses and PrimarySmtpAddress parameters in the same command. By default, the primary address is the same as the ExternalEmailAddress parameter value. If you use the PrimarySmtpAddress parameter to specify the primary email address, the command sets the EmailAddressPolicyEnabled property of the mail contact to False, which means the email addresses of the mail contact aren't automatically updated by email address policies. We recommend that you don't set the primary email address to a value other than the ExternalEmailAddress unless you're in a cross-forest scenario. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| MessageBodyFormat | The MessageBodyFormat parameter specifies the message body format for messages sent to the mail contact or mail user. Valid values are: Text Html TextAndHtml This is the default value. The MessageFormat and MessageBodyFormat parameters are interdependent: MessageFormat is MimeMessageBodyFormat can be Text, Html, or TextAndHtml. MessageFormat is TextMessageBodyFormat can only be Text. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Identity | The Identity parameter specifies the mail contact that you want to view. You can use any value that uniquely identifies the mail contact. For example: Name Display name Alias Distinguished name (DN) Canonical DN Email address GUID |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| CustomAttribute10 | The CustomAttribute1 to CustomAttribute15 parameters specify custom attributes. You can use these attributes to store additional information. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| CustomAttribute1 | The CustomAttribute1 to CustomAttribute15 parameters specify custom attributes. You can use these attributes to store additional information. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| CustomAttribute3 | The CustomAttribute1 to CustomAttribute15 parameters specify custom attributes. You can use these attributes to store additional information. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| CustomAttribute2 | The CustomAttribute1 to CustomAttribute15 parameters specify custom attributes. You can use these attributes to store additional information. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| CustomAttribute5 | The CustomAttribute1 to CustomAttribute15 parameters specify custom attributes. You can use these attributes to store additional information. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| CustomAttribute4 | The CustomAttribute1 to CustomAttribute15 parameters specify custom attributes. You can use these attributes to store additional information. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| CustomAttribute7 | The CustomAttribute1 to CustomAttribute15 parameters specify custom attributes. You can use these attributes to store additional information. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| CustomAttribute6 | The CustomAttribute1 to CustomAttribute15 parameters specify custom attributes. You can use these attributes to store additional information. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| CustomAttribute9 | The CustomAttribute1 to CustomAttribute15 parameters specify custom attributes. You can use these attributes to store additional information. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| CustomAttribute8 | The CustomAttribute1 to CustomAttribute15 parameters specify custom attributes. You can use these attributes to store additional information. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| ExternalDirectoryObjectId | This parameter is reserved for internal Microsoft use. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| GrantSendOnBehalfTo | The GrantSendOnBehalfTo parameter specifies who can send on behalf of this mail contact. Although messages sent on behalf of the mail contact clearly show the sender in the From field (<Sender> on behalf of <Mail contact>), replies to these messages are delivered to the mail contact, not the sender. The sender you specify for this parameter must a mailbox, mail user or mail-enabled security group (a mail-enabled security principal that can have permissions assigned). You can use any value that uniquely identifies the sender. For example: Name Display name Alias Distinguished name (DN) Canonical DN <domain name>\<account name> Email address GUID LegacyExchangeDN SamAccountName User ID or user principal name (UPN) To enter multiple values and overwrite any existing entries, use the following syntax: <value1>,<value2>.... If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "<value1>","<value2>".... To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="<value1>","<value2>"...; Remove="<value1>","<value2>"...}. By default, this parameter is blank, which means no one else has permission to send on behalf of this mail contact. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| UserSMimeCertificate |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| ObjectCategory |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| PoliciesIncluded |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| WhenChangedUTC |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| WhenCreatedUTC |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| RejectMessagesFromDLMembers | The RejectMessagesFromDLMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected. Valid values for this parameter are groups in your organization (distribution groups, mail-enabled security groups, and dynamic distribution groups). Specifying a group means all members of the group aren't allowed to send messages to this recipient. You can use any value that uniquely identifies the group. For example: Name Display name Alias Distinguished name (DN) Canonical DN Email address GUID You can enter multiple groups separated by commas. To overwrite any existing entries, use the following syntax: <group1>,<group2>.... If the values contain spaces or otherwise require quotation marks, use the following syntax: "<group1>","<group2>".... To add or remove groups without affecting other existing entries, use the following syntax: @{Add="<group1>","<group2>"...; Remove="<group1>","<group2>"...}. The groups you specify for this parameter are automatically copied to the RejectMessagesFromSendersOrMembers property. Therefore, you can't use the RejectMessagesFromDLMembers and RejectMessagesFromSendersOrMembers parameters in the same command. By default, this parameter is blank ($null), which allows this recipient to accept messages from all groups. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| IsDirSynced |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| UMDtmfMap | The UMDtmfMap parameter specifies the dual-tone multiple-frequency (DTMF) map values for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Typically, these DTMF values are automatically created and updated, but you can use this parameter to make changes manually. This parameter uses the following syntax: emailAddress:<integers> lastNameFirstName:<integers> firstNameLastName:<integers> To enter values that overwrite all existing entries, use the following syntax: emailAddress:<integers>,lastNameFirstName:<integers>,firstNameLastName:<integers>. If you use this syntax and you omit any of the DTMF map values, those values are removed from the recipient. For example, if you specify only emailAddress:<integers>, all existing lastNameFirstName and firstNameLastName values are removed. To add or remove values without affecting other existing entries, use the following syntax: @{Add="emailAddress:<integers>","lastNameFirstName:<integers>","firstNameLastName:<integers>"; Remove="emailAddress:<integers>","lastNameFirstName:<integers>","firstNameLastName:<integers>"}. If you use this syntax, you don't need to specify all of the DTMF map values, and you can specify multiple DTMF map values. For example, you can use @{Add="emailAddress:<integers1>","emailAddress:<intgers2>} to add two new values for emailAddress without affecting the existing lastNameFirstName and firstNameLastName values. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| AddressListMembership |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| ExtensionCustomAttribute3 | The ExtensionCustomAttribute1-5 parameters specify custom attributes that store additional information. You can specify multiple values for these parameters as a comma delimited list. Each ExtensionCustomAttribute parameter can hold up to 1,300 values. For more information about custom attributes, see Custom attributes. For more information about using multivalued properties, see Modifying multivalued properties. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| ExtensionCustomAttribute2 | The ExtensionCustomAttribute1-5 parameters specify custom attributes that store additional information. You can specify multiple values for these parameters as a comma delimited list. Each ExtensionCustomAttribute parameter can hold up to 1,300 values. For more information about custom attributes, see Custom attributes. For more information about using multivalued properties, see Modifying multivalued properties. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| ExtensionCustomAttribute1 | The ExtensionCustomAttribute1-5 parameters specify custom attributes that store additional information. You can specify multiple values for these parameters as a comma delimited list. Each ExtensionCustomAttribute parameter can hold up to 1,300 values. For more information about custom attributes, see Custom attributes. For more information about using multivalued properties, see Modifying multivalued properties. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| ExtensionCustomAttribute5 | The ExtensionCustomAttribute1-5 parameters specify custom attributes that store additional information. You can specify multiple values for these parameters as a comma delimited list. Each ExtensionCustomAttribute parameter can hold up to 1,300 values. For more information about custom attributes, see Custom attributes. For more information about using multivalued properties, see Modifying multivalued properties. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| ExtensionCustomAttribute4 | The ExtensionCustomAttribute1-5 parameters specify custom attributes that store additional information. You can specify multiple values for these parameters as a comma delimited list. Each ExtensionCustomAttribute parameter can hold up to 1,300 values. For more information about custom attributes, see Custom attributes. For more information about using multivalued properties, see Modifying multivalued properties. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Name * | The Name parameter specifies the unique name of the mail contact. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks ("). This value is also used for the DisplayName property if you don't use the DisplayName parameter. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| SendModerationNotifications | The SendModerationNotifications parameter specifies whether moderation status notification messages are sent to senders when they send a message to this moderated recipient. Valid values are: Always Moderation status notifications are sent to all internal and external senders. This is the default value. Internal Moderation status notifications are sent to all internal senders, but not to external senders. Never Moderation status notifications are disabled. Note that senders are always notified if their message is rejected by a moderator, regardless of the value of this parameter. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Alias | The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The value of Alias can contain letters, numbers and the characters !, #, $, %, &, ', *, +, -, /, =, ?, ^, _, `, {, |, } and ~. Periods (.) are allowed, but each period must be surrounded by other valid characters (for example, help.desk). Unicode characters from U+00A1 to U+00FF are also allowed. The maximum length of the Alias value is 64 characters. When you create a recipient without specifying an email address, the Alias value you specify is used to generate the primary email address (<alias>@<domain>). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (รถ) is changed to oe in the primary email address. If you don't use the Alias parameter when you create a recipient, the value of a different required parameter is used for the Alias property value: Recipients with user accounts (for example, user mailboxes, and mail users) The left side of the MicrosoftOnlineServicesID or UserPrincipalName parameter is used. For example, [email protected] results in the Alias property value helpdesk. Recipeints without user accounts (for example, room mailboxes, mail contacts, and distribution groups) The value of the Name parameter is used. Spaces are removed and unsupported characters are converted to question marks (?). If you modify the Alias value of an existing recipient, the primary email address is automatically updated only in on-premises environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is True for the recipient). The Alias parameter never generates or updates the primary email address of a mail contact or a mail user. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| MailTip | The MailTip parameter specifies the custom MailTip text for this recipient. The MailTip is shown to senders when they start drafting an email message to this recipient. If the value contains spaces, enclose the value in quotation marks ("). When you add a MailTip to a recipient, two things happen: HTML tags are automatically added to the text. For example, if you enter the text: "This mailbox is not monitored", the MailTip automatically becomes: <html><body>This mailbox is not monitored</body></html>. Additional HTML tags aren't supported, and the length of the MailTip can't exceed 175 displayed characters. The text is automatically added to the MailTipTranslations property of the recipient as the default value: default:<MailTip text>. If you modify the MailTip text, the default value is automatically updated in the MailTipTranslations property, and vice-versa. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| CustomAttribute11 | The CustomAttribute1 to CustomAttribute15 parameters specify custom attributes. You can use these attributes to store additional information. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| OverrideRecipientQuotas | This parameter is reserved for internal Microsoft use. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| CustomAttribute13 | The CustomAttribute1 to CustomAttribute15 parameters specify custom attributes. You can use these attributes to store additional information. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| CustomAttribute12 | The CustomAttribute1 to CustomAttribute15 parameters specify custom attributes. You can use these attributes to store additional information. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| CustomAttribute15 | The CustomAttribute1 to CustomAttribute15 parameters specify custom attributes. You can use these attributes to store additional information. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| CustomAttribute14 | The CustomAttribute1 to CustomAttribute15 parameters specify custom attributes. You can use these attributes to store additional information. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| RecipientType |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| ObjectClass |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| MacAttachmentFormat | The MacAttachmentFormat parameter specifies the Apple Macintosh operating system attachment format to use for messages sent to the mail contact or mail user. Valid values are: BinHex This is the default value. UuEncode AppleSingle AppleDouble The MacAttachmentFormat and MessageFormat parameters are interdependent: MessageFormat is TextMacAttachmentFormat can be BinHex or UuEncode. MessageFormat is MimeMacAttachmentFormat can be BinHex, AppleSingle, or AppleDouble. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Id |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| OrganizationalUnit | The OrganizationalUnit parameter specifies the location in Active Directory where the new contact is created. Valid input for this parameter is an organizational unit (OU) or domain that's visible using the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example: Name Canonical name Distinguished name (DN) GUID |
|
|||||||||||||||||||||||||||||||||||||||||||||||