Steven JW Kennedy

My Blog

Posts Tagged ‘Exchange 2010’

Using the Exchange Simple Display Name

Posted by Steven Kennedy on February 23, 2011


A couple of years ago I found that it was possible in an Exchange Server 2003 environment to change the display name that external users see on your email, to the Simple Display Name rather than the Display Name that appears in the GAL. Unfortunately this ‘feature’ went away in Exchange 2007, at least initially, it cam e back in a Service Pack update. SP 1 RU4 or later I believe but you should check to make sure.

When I was working on my home setup, which uses Exchange 2010, I came across the Simple Display Name field again and it occurred to me to check to see if Exchange 2010 supported this capability. I did an Internet search and low and behold I found the steps required to turn this capability on, only they didn’t work!

Not only did the steps not work but as I dug in to it I found the Microsoft documentation indicated it should work. My problem, it seems, is that while the Microsoft documentation said that the Set-RemoteDomain command supported the –UseSimpleDisplayName parameter my setup didn’t. Issuing a Get-Help Set-RemoteDomain didn’t show the UseSimpleDisplayName parameter. What’s going on? Then the light bulb went off. I checked my version of Exchange against the latest and yes mine was Exchange Server 2010 while the latest available was Exchange Server 2010 SP1.

Unfortunately I didn’t take any screen shots of the PowerShell error that I got when I tried to implement the Set-RemoteDomain command but if you do a simple check to find out what Exchange build you have you can then determine if the command will work.

You can issue a Get-ExchangeServer –Identity <server> | FL command to identify the build. You can see the build number under AdminDisplayVersion, as shown in the screen shot below. Microsoft have a list of Exchange Server versions and associated build numbers. These can be viewed at; Build numbers and release dates for Exchange Server. For Exchange Server 2010 the build was 14.00.0639.021. For Exchange Server 2010 SP1 the build was 14.01.0218.015 which show up under AdminDisplayVersion as 14.0 (Build 639.21) and 14.1 (Build 218.15) respectively.

Identify_Exchange_Server_Version - Annotated

You could also use the Get_Help Set-RemoteDomain command and see if the help shows the UseSimpleDisplayName parameter or not. The screen shot below shows the result of the Get-Help Set-RemoteDomain command for Exchange 2010 SP1.

Get-Help_Set-RemoteDomain - Annotated

Once I’d determined that I didn’t have Exchange 2010 SP1 I went and downloaded it went through the update process. Once I completed the update I was able to use the Set-RemoteDomain command with the –UseSimpleDisplayName parameter.

Reminder! To enable the use of Simple Display names for external email you have to be running Exchange 2010 SP1 or better

The command to enable Simple Display Names for external email domains is;

Get-RemoteDomain | Set-RemoteDomain –UseSimpleDisplayName $true

The Get-RemoteDomain pipes all remote domains to the Set-RemoteDomain command so that all outbound messages will use the Simple Display name. You could explicitly define which external domains will see the Simple Display name and which will see the Display Name. It’s probably a lot easier to implement and manage if you just go ahead and apply the change to all external emails.

Set-RemoteDomain_-UseSimpeDisplayName_command

To test that it’s working I updated the properties on my mail box to define a Simple Display name of; Kennedy, Steven. My Display Name being set to Kennedy, Steven (SJWK). As you can see from the following screen shots it works fine. The first screen shot is of the email as seen by an Internal recipient. As indicated by the red arrows the internal user see the Display Name. In this case with a (SJWK) appended to the display name.

Internal_email_sample - Annotated

The second screen shot shows the same email but as seen by an external recipient, my Gmail account. In this case it’s had a disclaimer notice prepended to it but as indicated the Internal users show up with their Simple Display name showing.

External_email_sample - Annotated

 

Some things to note.

Adding a Simple Display name on my home system was pretty easy. I only have a few accounts and it was pretty easy to update. In a business however you’ll need a process, or preferably an automated way, to generate the Simple Display name. You’ll also need some sort of governance model around it. You probably don’t want users pestering IT to set either or both of the display names to what they want.

You should also be aware that if an internal user Forwards or Reply’s to an email (Reply or Reply All) then the message body will show the internal Display Names. The point being that you cannot depend on the use of the Simple Display name to ‘hide’ whatever you’re using for an Display Name. However, external recipients will only see various address fields of the email; From, To, CC, Bcc etc..

Some possible scenarios for using this capability would be to have a Display name that included an indicator to the users office or perhaps country as in; Kennedy, Steven (Los Angeles), or Kennedy, Steven (USA) with perhaps the Simple Display name being set to the company name; Kennedy, Steven (Acme)

Posted in Exchange 2010 | Tagged: | 3 Comments »

Must remember to set outbound SMTP port

Posted by Steven Kennedy on January 25, 2011


Part of my home network includes an an Exchange 2010 server, that I use to look at the features & functions of Exchange. However, when trying to send email from home it’s a bit hit or miss as to whether it’s received at the other end. This is largely due to the other email systems not liking the IP address from which my email is sent, it’s a Verizon TCP/IP address. Seems a lot of the address Verizon uses for home are on various Black Lists.

So, I signed up for DynDNS’s Send mail capability, called Sendlabs SMTP. This allows be to send email via DynDNS. The recipients email system therefore sees the source as DynDNS so as long as DynDNS isn’t Black Listed I’m okay.

As there is also the possibility that my Internet provider, Verizon FIOS, could decide to block outbound traffic on port 25 I setup Sendlabs SMTP to use an alternate port.

The thing to remember is to set the outbound SMTP connector in Exchange to that alternate port, which I didn’t remember to do.

I’d an issue with my outbound email and as part of the fix I had to re-do my Edge Synchronization which entailed re-creating both the Inbound and outbound connectors. Note! because I’m using Edge Synchronization all of the configuration for the send and receive connectors is done on the Hub Transport server, NOT the Edge Transport server.

DynDNS have the steps for configuring the outbound connector using both the Exchange Management Console (EMC) and the Exchange Management shell. As my send connector already existed, it’s created automatically when using Edge Subscription, I only had to update the send connector to point to DynDNS’s mail hop URL and provide the appropriate credentials.

With the EdgeSync connector Properties page open select the Network tab. Select the radio button Route mail through the following smart hosts: and then click on Add

EdgeSync Connector Properties

Click on the radio button Full qualified domain name (FQDN) and type in the name of the smart host, in this case the DynDNS smart host, outbound.mailhop.org. Click on OK

Add smart host

You’ll be taken back to Network tab, as shown above. Now click on the Change button. In the subsequent dialog box select Basic Authentication AND Basic Authentication over TLS (not shown in picture). Then enter your DynDNS user name and password. Click on OK to complete the configuration.

Smart host authentication settings

Having done that I still needed to update the SMTP port, but I couldn’t find anywhere to do that using the console. Instead I had to use the Exchange Management Shell and issue the command;

set-sendconnector “connector name” – Port <alternate port number>

after which you need to either wait for or force an update of the Edge Synchronization. You can do so using;

Start-edgesynchronization

So in my particular case the two commands were;

set-sendconnector “EdgeSync – Default-First-Site-Name to Internet”  -Port 2525

Start-edgesynchronization

Posted in Exchange 2010 | Tagged: , | Leave a Comment »

MailTips: Custom, use of HTML

Posted by Steven Kennedy on December 30, 2010


With Custom MailTips you can use HTML codes, well the <A href=> code, as part of the MailTip. However, I’ve only been able to see the HTML work when using Outlook Web Access (OWA). As you can see from the two screen shots below OWA displays the correct HTML but the Outlook client doesn’t.

This would seem to be a fairly useless MailTip capability as the OWA version of the MailTip would behave differently than the Outlook version. Seems that the only time when this capability would be of any real use would be in an environment where only OWA is used, or where you know that the Custom MailTip will only apply to OWA users.

In the example below I used the HTML code; ‘Please visit the Help Desk site  <A href = http://help-desk-support.companyname.com>&#160; to log a support call.</A>’

You could have also used similar HTML to send an email instead, as in; ‘Please contact me via email <A href=  "Mailto: john.doe@companyname.com"> at john.doe@companyname.com.</A>

In this later case instead of opening the targeted help desk web site an email will be opened with the email address pre-populated.

Custom MailTip with HTML - OWA client 

Custom MailTip with HTML - Outlook client

Posted in Exchange 2010, Outlook 2010 | Tagged: , , , | Leave a Comment »

MailTips: Restricted Recipient

Posted by Steven Kennedy on December 29, 2010


Scenario

The Restricted Recipient MailTip is displayed if the sender adds a recipient for which delivery restrictions are configured prohibiting this sender from sending messages.

The MailTip indicates the recipient to which the sender isn’t allowed to send messages and gives the sender the option to remove the recipient from the message. It also clearly informs the sender that the message won’t be delivered if sent.

If the restricted recipient is an external recipient, or if it’s a distribution group that contains external recipients, this information is also provided to the sender. However, the following MailTips, if applicable, are suppressed:

  • Automatic Replies
  • Mailbox Full
  • Custom MailTip
  • Moderated Recipient
  • Oversize Message

The screen shot below shows the actual MailTip wording that you’ll see, for an Internal recipient.

Restricted Recipient

The screen shot below shows the same wording for the MailTip in the case of a restricted External Recipient. In this case the External Recipient MailTip is also turned on so you get both the Restricted Recipient MailTip and the External Recipient MailTip.

Restricted Recipient - External - redacted

Posted in Exchange 2010, Outlook 2010 | Tagged: , , | 1 Comment »

MailTips: Reply-All on BCC

Posted by Steven Kennedy on December 29, 2010


This MailTip is only supported in Microsoft Office Outlook Web App. It does not show up when using Outlook.

The Reply-All on Bcc MailTip is displayed if the sender receives a Bcc copy of a message and selects Reply to All.

When a user selects Reply to All to such a message, the fact that the user received a Bcc of that message is revealed to the rest of the audience to which the message was sent. In almost all cases, this is an undesirable situation, and this MailTip informs the user of this condition.

The screen shot below shows the wording you’ll see for this MailTip.

Reply All - Bcc - Redacted

 

clip_image00111_thumbNote:

This MailTip is only supported in Microsoft Office Outlook Web App.

Posted in Exchange 2010, Outlook 2010 | Tagged: , , | Leave a Comment »