Compartir a través de

Configure email for incoming messages

  • Artículo

 

Applies To: Dynamics CRM 2013

If you want incoming email messages to be delivered directly to a queue, specify the following information in the queue:

  • An email address by using the Queue.EmailAddress attribute. It must be a valid email address where emails that are sent to the queue are directed.

  • An incoming email delivery method by using the Queue.IncomingEmailDeliveryMethod attribute. You can specify email to be sent and received with the Microsoft Dynamics CRM Email Router or forwarded from another email address. If you specify the email router, you have an option to include the user’s email server credentials to give the user access to the server for retrieving emails.

  • An outgoing email delivery method, such as email router, by using the Queue.OutgoingEmailDeliveryMethod attribute.

  • An incoming email filtering method by using the Queue.IncomingEmailFilteringMethod attribute. You can specify to convert all incoming email messages to email activities or only email messages that relate to existing Microsoft Dynamics CRM records.

Important

The primary email address of the queue must be approved to ensure that the incoming and outgoing email messages are not blocked. The Queue.EmailRouterAccessApproval attribute contains the status of the primary email address of the queue. The status must be set to 1 (Approved). You can update the queue record to change the attribute value to 1 (Approved), if it is not already in the approved state. To update the attribute value, you must have the prvApproveRejectEmailAddress privilege. You also must set the Organization.RequireApprovalForQueueEmail attribute to 1 (True). If not set to 1 (True), the value provided in the Queue.EmailRouterAccessApproval attribute is ignored.

Beginning with the Microsoft Dynamics CRM 2013 and CRM Online Fall ‘13 releases, it’s no longer possible to configure Email Router credentials by setting the Queue.AllowEmailCredentials attribute to true followed by specifying the user name and password in Queue.EmailUserName and Queue.EmailPassword. These attributes have been deprecated and made read-only. The same restriction applies to the UserSettings.EmailPassword and UserSettings.EmailUserName attributes. However, these attributes can be set in the Email Router configuration. More information: Configure the Email Router.

See Also

Queue entities
Sample: Configure Email for a Queue (Early Bound)
Queue entity privileges
Privileges not associated with an entity
Queue entity messages and methods