There are plenty of reasons for wanting to look at a message header, to see where a mail has come from or from which email address it was sent for example. Different versions of Outlook have different methods of letting you read the email header.
Solution
Display Message Headers with Outlook 2013
1. Open the mail in question and select ‘file’.
2. Info > Properties.
3. Your message headers are displayed.
Display Message Headers with Outlook 2010
1. Open the mail in question and select ‘file’.
2. Info > Properties.
3. Your message headers are displayed.
Display Message Headers with Outlook 2007
1. Option 1: Open the mail in question, and select the expand icon next to ‘Options’.
2. Option 2: From the inbox right click the relevant message and select ‘Message Options’.
3. Your message headers are displayed.
Display Message Headers with Outlook 2003
1. Option 1: Open the mail in question > View > Options.
2. Option 2: From the inbox right click the relevant message and select ‘Options’.
3. Your message headers are displayed.
Related Articles, References, Credits, or External Links
Outlook will show you this error if you attempt to grant rights to a “distribution group” on an object for example, a public folder, or for calendar permissions.
You would think that converting the “Universal Distribution Group” to a “Universal Security Group” would solve this problem, but it does not.
Note: You may also see the following error, “an error occurred. Exception: Cannot use {Group_Name} as a security principal, Parameter name: secuirtyPrincipal.
Solution
1. First (I’m assuming) you ARE trying to add a security group that you have converted using the Active Directory Users and computers snap in like so, you will see I’ve got a Universal Distribution Group called “TestGroup”
2. To convert to a Universal Security Group simply change the group type and apply. (Note you will need to refresh the view in Exchange System Manager, before it reflects the correct group type as below).
3. But you will see, even though the type of group is correct you still see this error. (The more eagle eyed among you will see there’s a small error icon on the group type).
Why this has happened.
This has been a known problem since Exchange 2007. Essentially there’s an active directory attribute called “msExchRecipientDisplayType” that does not get changed properly when you convert the group using the GUI interface.
How to Fix it
Exchange 2007
Run the following Powershell command in the Exchange Management Shell;
I’ve seen this happen on both Outlook 2010 and Outlook 2013. You can open additional Exchange mailboxes from your accounts ‘Advanced’ section, but these mailboxes were not listed there.
Solution
Above, you can see that the offending mailbox here is called Training&Holidays.
1. On a DC, (or your Exchange server) > Windows Key + R > dsa.msc {Enter} > When Active Directory Users and Computers loads > View > Advanced Features.
2. Locate the user that has the offending mailbox > Properties > Attribute Editor > Locate the msExchDelegateListLink value > Edit > Remove the affected user(s) > OK > Apply.
3. Let the users restart Outlook. (Note: It may take a few minutes after Outlook is restarted for the mailbox to disappear).
Remove All Mailbox Mappings for All Users
WARNING: Use with caution, some users may be using this feature to automatically connect to mailboxes.
Use the following PowerShell;
[box]foreach ($u in $(Get-User)) { Write-Host “Clearing the msExchDelegateListLink for $($u.distinguishedname)”; $ad = [adsi]”LDAP://$($u.originatingserver)/$($u.distinguishedname)”; $ad.msExchDelegateListLink.Clear(); $ad.SetInfo(); }[/box]
Related Articles, References, Credits, or External Links
Seen on Outlook 2007 and Outlook 2010 talking to Exchange 2007 (Note this fixes Outlook 2007 but NOT 2010.) When opening the “Out Of Office Assistant.”
Your Out of Office Settings cannot be displayed, because the Server is currently unavailable. Try Again Later
Other Symtoms
1. You see hash marks in the Scheduling Assistant.
2. You see “Object reference not set to an instance of an object.” error when running the Poweshell cmdlet Test-OutlookWebServices.
3. The OOF Log shows “Response error code: 00000000” and “HTTP status code: 0”.
Solution
This is caused by a .NET error.
To Fix it install this HOTFIX (Afterwards neither Exchange or Outlook needs restarting.)
To Workaround.
Option 1
Use the out of office assistant with Outlook Web Access.
Option 2 (On a client by Client basis)
Note: This will only work if you have Schedule+ Free/Busy Public folders, you will only have this if you ticked “Yes” at the “Do you have computers running Outlook 2003..” option when Exchange was installed.
1. On the affected Outlook machine, Click Start > Run > regedit > {enter}
2 Navigate to, HKEY_CURRENT_USERSoftwareMicrosoftOffice12.0OutlookOptionsCalendar
3. Right click in the right hand window > New DWORD
I upgraded a clients firewall and CSC software a couple of weeks ago, and ever since “some” users saw the following errors,
Error 0x800CCC0F
Task ‘{email address} – Sending’ reports error (0x800CCC0F): #The connection to the server was interrupted. If the problem continues, contact your server administrator or Internet service provider (ISP).’
Eventually it would time out altogether with the following error,
All I could discern from Googling the error, was that the AV (In this case the Trend Micro InterScan for Cisco CSC SSM), in the Cisco CSC Module) was probably the culprit.
I tried stopping the POP3 Service on the CSC that did NOT fix the error.
I confirmed that the CSC module was the root cause of the problem, by disabling the entire module with the following command on the Cisco ASA firewall;
[box]hw-module module 1 shutdown[/box]
Warning: If you do this, your CSC settings must be set to “csc fail-open” or web and email traffic will stop! Once you have confirmed this IS the problem you can re-enable the module with the following command.
[box]hw-module module 1 reset[/box]
I tried from my office and it worked fine, I could not replicate the error, I tried from various servers and Citrix box’s from other clients who kindly let me test from their network. Still I could not replicate the error! I went home and that was the first time I could see the same error their users were seeing. Sadly this led me on a wild goose chase, (I use Outlook 2007 at home and Outlook 2010 everywhere else so I (wrongly) assumed that was the problem).
Breakthrough!
As I could now replicate the error, I could at least do some testing, I attempted a send/receive and looked at the CSC Logging.
Note: To view CSC Logging, connect to the ASDM > Monitoring > Logging > Trend Micro Content Security > Continue > Enter the password > OK > View.
Every time it failed, I saw my public IP being logged with a RejectWithErrorCide-550 and RBL-Fail,QIL-NA. At last something I could work with.
This error indicates a problem with the Email Reputation system, I logged into the CSC web management console > and located this.
Then I disabled the ‘SMTP Anti-spam (Email Reputation)’, and everything started to work.
Conclusion
I understand the need for this system, but the nature of POP3 email clients, dictates they can connect in from anywhere, usually from a home ISP account on a DHCP address. I know from experience that major ISP’sIP ranges get put in RBL block lists (I checked by popping my IP in here, and sure enough it was blocked).
If you are going to use POP3 then you need to leave this system disabled, but to be honest, if you have Exchange, simply swap over to Outlook Anywhere and stop using POP3.
Related Articles, References, Credits, or External Links
Special thanks to Jenny Ames for her patience while I fought with this over a number of days.
