Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
CRM 2011 e-mail router / Impersonation / Send As -- I need some help I don't know what else to read RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    CRM 2011 on-premise deployment. IFD and ADFS.  CRM 2011 email router Version 5. RU 5.   Using Exchange 2007 SP2/W2K8 SP2.

    I must say with all the reading I have done, I am thoroughly confused and I hope someone can jump in and save me from drowning.

    At first the CRM implementation team wanted to use, email router: incoming profile: protocol Exch web services with Other specified: Access Cred: forward mailbox (Exch server Full Admin Account. Outgoing profile: SMTP using E2K7 Hub Transport with Other Specified: Access Cred: CRM Service Account (domain Admin). Then push an Outlook server-based rule to the CRM users.

    Now the CRM implementation team still wants to use the email router but they are looking for different user setups which are within the email access configuration properties of the CRM user account.

    So they want me to test different email router scenarios using the different email access configurations:  CRM for Outlook; Incoming:email router and Outgoing:email router and of course Incoming: fwd mailbox Outgoing: email router-then push a rule.

    With the Scenario: using the email router for both incoming and outgoing, I receive a Send As error for incoming but outgoing is fine. I researched and I believe for this setup I have to apply MS exch impersonation but I am not sure if SendAs will work.   

    I have two questions:

    (1) When would you use MS Exch Impersonation over SendAS persmission when you are using the email router with an E2K7 SP2 backend?

    (2) Signed workflow is setup with the owner as the CRM service account but they want a different account to stamp the FROM.  Will MS Exch Impersonation work over SendAS because I cannot get SendAS to work.  Suggestion on this one please?

    Many thanks

    Tuesday, February 14, 2012 9:23 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Here is the way that I would suggest setting up the Organization.

    1. For Out-Going e-mail set it up to use the Email Router, users can enter their creds and the router will use those creds to login to the Exchange Web Services and initiate the send.  Use this method because that way for out-going email generated via workflow the user's Outlook Client does not have be on and connected.  Also, since user's supply the uid/pwd in CRM you don't have to worry about impersonation because it logs in directly to the web service.

    2. For Incoming e-mail, I would scratch the forward mailbox.  It puts too much overhead on the system.  I would either use the Outlook Client to process incoming e-mail or the Mail Router again for that as well.  In either case, the creds are already provided so you don't have to worry as much as long as the incoming provider setup has the proper rights to the mailboxes.

    The workflow can be owned by any user, the key requirement is the From address in terms of sending.  If a workflow fails to send due to Send As issue, there is a Send As setting within each user's options that will allow email to be sent on their behalf, including the mail router.

    Jeremy

    Jeremy Winchell
    Avtex
    Visit the Avtex Blog

    • Marked as answer by -ee Wednesday, February 15, 2012 1:40 AM
    Tuesday, February 14, 2012 11:42 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Here is the way that I would suggest setting up the Organization.

    1. For Out-Going e-mail set it up to use the Email Router, users can enter their creds and the router will use those creds to login to the Exchange Web Services and initiate the send.  Use this method because that way for out-going email generated via workflow the user's Outlook Client does not have be on and connected.  Also, since user's supply the uid/pwd in CRM you don't have to worry about impersonation because it logs in directly to the web service.

    2. For Incoming e-mail, I would scratch the forward mailbox.  It puts too much overhead on the system.  I would either use the Outlook Client to process incoming e-mail or the Mail Router again for that as well.  In either case, the creds are already provided so you don't have to worry as much as long as the incoming provider setup has the proper rights to the mailboxes.

    The workflow can be owned by any user, the key requirement is the From address in terms of sending.  If a workflow fails to send due to Send As issue, there is a Send As setting within each user's options that will allow email to be sent on their behalf, including the mail router.

    Jeremy

    Jeremy Winchell
    Avtex
    Visit the Avtex Blog

    • Marked as answer by -ee Wednesday, February 15, 2012 1:40 AM
    Tuesday, February 14, 2012 11:42 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    many many and one more many thanks
    Wednesday, February 15, 2012 1:40 AM