Tachytelic.net

Office 365

Mail (microsoft outlook 2016) application not found 5/5 (1)

by 4 Comments

When migrating a customer to Office 365 I had a problem opening the mail control panel applet. It simply showed the error message “Application not found”:

Error message when trying to run the mail applet from Microsoft Outlook 2016 "Application not found"

This seemed to be occurring on 64-Bit machines where we had installed 32-Bit Office 2016 from the Office 365 portal.

I found two workarounds for this:

Workaround One: Run the mail applet directly from the command line

  1. Press Windows Key + R to bring up the run dialog
  2. Paste the following:
    C:\Program Files (x86)\Microsoft Office\root\Office16\MLCFG32.CPL 

Workaround Two: Run the mail applet from Outlook 2016

If you in Outlook you can run the control panel mail applet from within Outlook by going to File and clicking on account settings, at the bottom of the account settings drop down you should see a “Manage Profiles” button, which will take you into the mail applet.
Manage mail profiles from within Outlook 2016

I would like to find a proper solution for why this is happening, so if anyone comes across a solution, I’d appreciate it if you share your solution.

Exclude messages from Clutter in Office 365 using a transport rule

by Leave a Comment

This post shows you create a transport rule to exclude messages from clutter and provides the code for you to do it automatically. Clutter is a handy feature of Office 365, but sometimes you need to see emails even if they don’t really require any attention.

Example: Exclude message from clutter based on the email subject using a transport rule.

New-TransportRule -Name "Tachytelic Test Rule" -SubjectContainsWords "Sample Subject to bypass clutter" -SetHeaderName "X-MS-Exchange-Organization-BypassClutter" -SetHeaderValue "true"

The rule is created using the “New-TransportRule” cmdlet as per the above.

Fill the form below to have the PowerShell code to create a transport rule to exclude your important messages:

PowerShell code to exclude messages from Clutter

 

The above example should result in the following in the Office 365 Admin Centre:

Screenshot showing Office 365 Transport Rule to exclude messages from clutter

You can check if the rule worked by sending an email from an external account to your Office 365 tenant and checking the properties of the message when it has arrived:

Screenshot showing message properties from a message that has bypassed clutter
Look for X-MS-Exchange-Organization-BypassClutter: true in the message header to confirm your rule is working.

If you found this post helpful, please rate it 😀

Setting the primary email address for Office 365 users with PowerShell

by 1 Comment

It’s easy to Set the Primary Email Address on Office 365 with PowerShell using the Set-Mailbox cmdlet. The primary address is defined using “SMTP” in uppercase in the email address. For example:

Set-Mailbox -Identity "test.user" -EmailAddresses SMTP:[email protected],smtp:[email protected]

Note: The Set-Mailbox cmdlet will remove all existing aliases, so include them with the command.

Enter the details of the mailbox to be changed in the form below, and PowerShell code will be generated. It includes the required PowerShell to connect to Office 365.

Set the Primary Email Address on Office 365 using Powershell

 

Screenshot showing how to Set the Primary Email Address on Office 365 with Powershell
Example of the Powershell Code changing the Primary SMTP Address

Set the Primary Email Address on Office 365 when the user is being managed by the local active directory

The steps above will work if the user that you are changing is cloud managed. If your accounts are synchronised from your local active directory, then they will be out of the write scope of Office 365. If that is the case please follow the instructions on this page:

https://www.tachytelic.net/2018/08/office-365-how-to-change-primary-email-address/

Office 365: 550 5.7.1 RESOLVER.RST.AuthRequired when emailing a mail enabled public folder

by Leave a Comment

A recent change in Exchange online seems to have caused a problem with mail enabled public folders receiving messages from people outside of the organisation. It has never been necessary with Office 365/Exchange Online to give create permissions to the anonymous or default users , you could instead set the mail flow settings of the public folder to allow anonymous access.

You may see the following bounce message when sending to a mail enabled public folder:

Delivery has failed to these recipients or groups:

Your message wasn’t delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept email from certain senders, or another restriction may be preventing delivery. For more tips to resolve this issue see DSN code 5.7.1 in Exchange Online. If the problem continues contact your help desk.

5.7.1 RESOLVER.RST.AuthRequired; authentication required [Stage: CreateMessage]>’

Of course it is possible and easy to set permissions for the public folder from Outlook to solve this problem, but doing this does not seem to be working for everyone. Some people are reporting success with it, but others not.

Setting the public folder permissions with PowerShell fixes the problem, but I cannot understand why there is a difference.

Setting Offiec 365 Public Folder Permissions with Powershell

In order to fix this problem you have to grant create permissions to anonymous and the default user. The Powershell cmdlet to do this is Add-PublicFolderClientPermission.

After connecting to Office 365 Remote Powershell as described here, you can run the following commands:

Add-PublicFolderClientPermission -identity "\test public folder" -User Anonymous -AccessRights CreateItems
Add-PublicFolderClientPermission -identity "\test public folder" -User Default -AccessRights CreateItems

Once you have added the permission it’s probably best to give it a quick check with:

Get-PublicFolderClientPermission -identity "\test public folder"

Hope this helps.

Office 365: Outlook crashes when sending an email when ESET NOD32 Antivirus is installed

by Leave a Comment

Just a quick post, had a incident today with a user where Outlook 2013 crashed every time they attempted to send an email.

It turned out that this was caused by the ESET NOD32 installation on the machine. Disabling the email integration in NOD32 immediately fixes the problem.

To disable the email integration right click on the NOD32 icon in the notification area to bring up the options screen. Open out the “Web and email” section and then “Email client integration” and then untick the option “Integrate into Microsoft Outlook”

Eset NOD32 options to stop Outlook crashes when sending an email

 

A quick and easy fix to a pain in the arse problem. 😀