{"id":6867,"date":"2016-08-22T16:29:58","date_gmt":"2016-08-22T21:29:58","guid":{"rendered":"http:\/\/www.highclouder.ninja\/?p=6867"},"modified":"2024-05-21T14:49:54","modified_gmt":"2024-05-21T14:49:54","slug":"convenient-way-handle-multiple-email-addresses-receive-send","status":"publish","type":"post","link":"https:\/\/www.highclouder.com\/?p=6867","title":{"rendered":"Most Convenient Way to Handle Multiple eMail Addresses: “Receive As” \/ “Send As”"},"content":{"rendered":"

During many Exchange<\/strong> projects (On-Premises<\/em> or in the Cloud<\/em>) we see a lot of situations when organisations create an additional mailbox (secondary mailbox) for some users. Everybody, who works with Exchange environments, knows that a mailbox could have multiple email addresses associated with it. The question is always, why not just define an additional email as an alias to the mailbox? Of course, this scenario could work in some use cases. You\u00a0probably think, it’s OK…<\/p>\n

However, when someone sends an email to the address that defined as an alias, the recipient is not going to easily see to what email address the email was sent (in more details down in this blog post<\/em>). Also, when we only use aliases, all emails that we send are always seen as if they were sent from the primary email<\/strong> address associated with the mailbox.<\/p>\n

We all know that\u00a0 pictures explain better than 1000 words, so let’s take a look. Because of this, let’s see how to do this On-Premises<\/strong> and in the Cloud<\/strong> (Office 365<\/em>).<\/p>\n

The “Challenge”<\/h2>\n

The following image illustrates that I have multiple email addresses associated with my mailbox:<\/p>\n

\"Multiple<\/a><\/p>\n

When someone sends me an email to one of my addresses, let’s say to InterruptYourVacation@iRangers.com <\/strong>\ud83d\ude42 , of course it will arrive at my main mailbox.<\/p>\n

\"Email<\/a><\/p>\n

 <\/p>\n

As \u00a0you can see, the email arrived. And\u2026 do you see the first issue?! At least it bothers me! \ud83d\ude42 \u2026 If I look on the line “To:<\/strong>“, I see that this email was sent to Misha Hanin<\/strong>. When I double-click at the name I see the following screen:<\/p>\n

\"Contact<\/a><\/p>\n

 <\/p>\n

Yes, it’s not clear to what address the email was sent! Of course, I can go and check “Internet headers<\/em>” and I will see something like this:<\/p>\n

 <\/p>\n

\"Internet<\/a><\/p>\n

 <\/p>\n

I don’t know about you, but for me going and checking headers for all emails, every time when I need to know to what address it was sent to is too much :)!<\/p>\n

And, this is only the first part of the problem! \u00a0In addition to this, we also have a “challenge” to use “Send As<\/strong>” functionality!<\/p>\n

Let’s try to “Send As<\/strong>” InterruptYourVacation@iRangers.com<\/em><\/strong>. So, logically, many of us will try to do something like this:<\/p>\n

 <\/p>\n

\"5\"<\/a><\/p>\n

 <\/p>\n

or<\/p>\n

 <\/p>\n

\"Send<\/a><\/p>\n

 <\/p>\n

Now, let’s see how I will see this email when I check my @highclouder.ninja<\/strong> mailbox:<\/p>\n

 <\/p>\n

\"Send<\/a><\/p>\n

 <\/p>\n

Seems like, ALL my attempts to send emails as\u00a0 InterruptYourVacation@iRangers.com<\/strong> were ignored and as a result, this email looks like it was sent from misha.hanin@irangers.com<\/strong> (this is the primary email address of my corporate mailbox<\/em>)!<\/p>\n

Therefore, exactly at this moment, many companies decide to create an additional mailbox (in my case it should be InterruptYourVacation@iRangers.com<\/em>) and configure “Send As<\/em><\/strong>” permissions.<\/p>\n

It’s nothing wrong with this approach, however, as a result of this decision, now you have to manage multiple mailboxes (I even not touching the licensing topic yet!<\/em>).<\/p>\n

HOW EXPERTS WORK WITH MULTIPLE EMAIL ADDRESSES<\/h2>\n

So, when our clients deal with this “Receive As<\/strong> \/ Send As<\/strong>” problem, we, at iRangers, do the following:<\/p>\n

    \n
  1. Create a new Distribution Group<\/strong>. As a Primary Email address for this group we define an address that we want to use as “Receive As<\/strong> \/ Send As<\/strong>“<\/li>\n
  2. We add required users to this new Distribution Group. So, in My case, I added myself (misha.hanin@irangers.com<\/em>) to this group. Now, all emails that will arrive to address InterruptYourVacation@iRangers.com<\/em> will be forwarded to misha.hanin@irangers.com<\/em><\/li>\n
  3. Assign “Send As<\/strong>” permissions. By doing this, misha.hanin@irangers.com<\/em> will be able to Send As: InterruptYourVacation@iRangers.com<\/em><\/li>\n<\/ol>\n

    I hope you know how to do all this by using GUI, therefore let’s see one of the ways how to do this in PowerShell (first of all,\u00a0If you are in the Hybrid Mode, you will need to do all steps, from On-Premises<\/strong> and Office 365<\/strong>\u00a0sections<\/em>):<\/p>\n

    On-Premises:<\/h3>\n
    $SendAsRecipient = \"InterruptYourVacation@irangers.com\"\n$ForwardToRecipient = \"Misha.Hanin@irangers.com\"\n\n$ContactsOU = \"OU=Contacts,OU=Users,OU=Winnipeg,OU=Canada,OU=iRangers,DC=prv,DC=irangers,DC=com\"\n\nNew-DistributionGroup -Name $SendAsRecipient -Members $ForwardToRecipient -Alias $SendAsRecipient.Split('@')[0] -PrimarySmtpAddress $SendAsRecipient -OrganizationalUnit $ContactsOU\nSet-DistributionGroup $SendAsRecipient -RequireSenderAuthenticationEnabled $False\n\nAdd-ADPermission -Identity $SendAsRecipient -User $ForwardToRecipient -AccessRights \"ExtendedRight\" -ExtendedRights \"Send-As\"\n<\/pre>\n
    Also, we can try to allow the Group itself to Sen-As (Sometimes this doesn’t work. So, please consider this command just as<\/em> a reference<\/em>):<\/p>\n
    Add-ADPermission -Identity $SendAsRecipient -User \"NT AUTHORITY\\SELF\" -AccessRights \"ExtendedRight\" -ExtendedRights \"Send-As\"\n<\/pre>\n
    For a validation<\/em>:<\/p>\n
    (Get-ADPermission -Identity $SendAsRecipient -User $ForwardToRecipient).ExtendedRights<\/pre>\n
    Office 365:<\/h3>\n
    Before moving forward, be sure that Azure Active Directory Connector<\/strong> (AADC<\/strong>) has already synchronized all data. Of course, you can force the sync by executing the following command from the AADC server:<\/p>\n
    Enter-pssession IR-SYNC01<\/pre>\n
    (iR-Sync01 is our AADC server. And…., Yes, I am lazy\u2026 I am connecting to my AADC server with remote PowerShell… <\/em> )<\/p>\n
    & \"C:\\Program Files\\Microsoft Azure AD Sync\\Bin\\DirectorySyncClientCmd.exe\"<\/pre>\n
    Now, when all objects get synced to the cloud, let’s connect to Office 365<\/strong> and execute there a few commands. Here is how we connect to the Office 365:<\/p>\n
    $strUserName = \"yourAdminAccountAtO365@YourOrgName.onmicrosoft.com\"\n$strConnectionURL = \"https:\/\/outlook.office365.com\/powershell-liveid\"\n$objCredential = Get-Credential -Credential $strUserName\n\n$objPSSession = New-PSSession -ConfigurationName \"Microsoft.Exchange\" -ConnectionUri $strConnectionURL -Authentication \"Basic\" -Credential $objCredential -AllowRedirection\nImport-PSSession -Session $objPSSession\n<\/pre>\n
    OK, now as a result of the previous steps, we are inside O365 PowerShell<\/strong> session. Let’s run this commands:<\/p>\n
    $SendAsRecipient = \"InterruptYourVacation@irangers.com\"\n$ForwardToRecipient = \"Misha.Hanin@irangers.com\"\n\nGet-RecipientPermission -Identity $SendAsRecipient\nAdd-RecipientPermission -Identity $SendAsRecipient -Trustee $ForwardToRecipient -AccessRights \"SendAs\" -Confirm:$False\n<\/pre>\n
    In addition, for a validation purposes<\/em>:<\/p>\n
    Get-RecipientPermission $SendAsRecipient | Where { ($_.IsInherited -eq $False) -and -not ($_.Trustee -like \"NT AUTHORITY\\SELF\") } | Select Trustee,AccessControlType,AccessRights\n<\/pre>\n
    In Conclusion<\/h2>\n
    Now, after all those steps, let’s repeat Receive As<\/strong> and Send As<\/strong> exercise \u00a0:). First of all, I will send an email to InterruptYourVacation@iRangers.com<\/strong><\/p>\n
    And… Voila! As a result of all our hard work \ud83d\ude42 \u00a0email was automatically forwarded to my primary mailbox: misha.hanin@irangers.com<\/em> and \u2026in the “To<\/strong>” field I see that this email was sent to InterruptYourVacation@iRangers.com<\/em>:<\/p>\n
     <\/p>\n
    \"Recieve<\/a><\/p>\n
     <\/p>\n
    We are almost at the end :). So, I think this is a time for the last test. Now let’s Send as<\/strong>: InterruptYourVacation@iRangers.com<\/em><\/p>\n
     <\/p>\n
    \"Send<\/a><\/p>\n
     <\/p>\n
    Yes, here is the result we were looking for!<\/p>\n
     <\/p>\n
    \"Send<\/a><\/p>\n
     <\/p>\n
    Finally, I hope you find this blog post informative.<\/p>\n
    Don’t hesitate to contact me via contact form<\/a> or be in touch through iRangers.com<\/a><\/p>\n
    Cheers,
    \nMisha<\/p>\n
    P.S.
    \nSpecial thanks to     Alexander Stankevich<\/a> and Dima Razbornov<\/a> (iRangers’ Sr. Solutions Architects<\/em>), who were actively involved in crafting this blog post!<\/p>\n","protected":false},"excerpt":{"rendered":"
    During many Exchange projects (On-Premises or in the Cloud) we see a lot of situations when organisations create an additional mailbox (secondary mailbox) for some users. Everybody, who works with Exchange environments, knows that a mailbox could have multiple email addresses associated with it. The question is always, why not just define an additional email […]<\/p>\n","protected":false},"author":1,"featured_media":6905,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-6867","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.highclouder.com\/index.php?rest_route=\/wp\/v2\/posts\/6867","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.highclouder.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.highclouder.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.highclouder.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.highclouder.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=6867"}],"version-history":[{"count":1,"href":"https:\/\/www.highclouder.com\/index.php?rest_route=\/wp\/v2\/posts\/6867\/revisions"}],"predecessor-version":[{"id":7246,"href":"https:\/\/www.highclouder.com\/index.php?rest_route=\/wp\/v2\/posts\/6867\/revisions\/7246"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.highclouder.com\/index.php?rest_route=\/wp\/v2\/media\/6905"}],"wp:attachment":[{"href":"https:\/\/www.highclouder.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=6867"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.highclouder.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=6867"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.highclouder.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=6867"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}