Networknet.nl

I import my public SSL certificate to safely sync my mailbox with Samsung I600. I reinstalled my Exchange 2007 server couple times and moved mailboxes between my test servers; therefore I did not import my public SSL certificate.

Since the SSL import in IIS my Outlook 2007 clients are complaining with the Security warning below.

Information you exchange with this site cannot be viewed or changed by others. However, there is a problem with the site’s security certificate.

Each time I open outlook the message is displayed two times. Lucky me there was a post on MsExchange team blog and they forwarded me to here.

Copy the steps below and modify your new FQDN and server identity.

[PS] C:\>Set-WebServicesVirtualDirectory -Identity “Server\EWS (Default Web Site)” -InternalUrl https://mail.networknet.nl/ews/exchange.asmx

[PS] C:\>Set-OABVirtualDirectory -Identity “Server\oab (Default Web Site)” -InternalUrl https://mail.networknet.nl/oab

[PS] C:\>Set-UMVirtualDirectory -Identity “Server\unifiedmessaging (Default Web Site)” -InternalUrl https://mail.networknet.nl/unifiedmessaging/service.asmx

[PS] C:\>Set-ClientAccessServer -Identity Server -AutodiscoverServiceInternalUri https://mail.networknet.nl/autodiscover/autodiscover.xml

[PS] C:\>

Start the Exchange Management Shell and paste the commands.

Restart IIS by iisreset or recycle MSExchangeAutodiscoverAppPool application pool if the server is used in production.

No more warning in Outlook 2007 for my Exchange 2007 test environment.

My inbound email flow on the Exchange 2007 server didn’t work. I was able to send out my emails using the exchange server, but when receiving them the messages were bounced. During my last weeks migrations I configured second mx record at my hosting provider and all emails were caught there; because I also configured outlook to pull that mailbox it seemed that everything worked fine. After getting a strange message at LinkedIn and Gmail I started to troubleshoot and read the error messages.

At Gmail.com I’ve got the message below:

This is an automatically generated Delivery Status Notification

Delivery to the following recipient failed permanently:

    ivan1980@networknet.nl

Technical details of permanent failure:

PERM_FAILURE: SMTP Error (state 12): 530 5.7.1 Client was not authenticated

After reading this message I immediately went back to my Exchange 2007 Receive Connector and verified the authentication and saw that TLS was selected.

I unchecked the TLS settings and applied the Receive Connector configuration. Resend the email from Gmail to my primary account and the email failed again.

I went back again and this time to Network tab of the Receive Connector. I run the ipconfig and saw that the ip addresses did not match. Changed the binding ip address to one assigned to the server and my test from Gmail succeed this time. I can’t figure out why this setting was wrong; maybe I overlooked during the installation and configuration of the Hub Transport role and did not open the properties of my receiving domain.

I am happy my inbound email traffic is flowing into the Exchange store and filling up with SPAM.

The screencapture below shows the installation time of my first Exchange Server 2007 ever. Exchange 2007 requires a 64bit Windows Server operating system and this was my opportunity to test the Windows Server 2008 RC0 Hypervisor on my new Intel Q6600 serverbox. 

Oeps 90 minutes in total ;(.  Finally I could test a Exchange Server 2007 installation myself. I reinstalled the Q6600 serverbox HDD with VistaX64 and I will start using the VMWare Workstation 6.0 with X64 bit support for guest operating systems. At this moment RC0 is very slow for me.