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

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.

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.

It can be very useful to run a VBA macro when new mail is received in Outlook. A customer asked me to write something that would log an entry to a SQL database when an email produced contact form was received.

It’s easy to do but can take a bit of trial and error to get working just how you want it.

You need to add an event listener to the Inbox which will process incoming messages. A the following code to ThisOutlookSession:

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”

When you have multiple email aliases associated with your Exchange or Office 365 based email account, it can be useful to know which email address it was sent to. However Outlook does not show this information.

Use an Outlook rule to examine the message header and display an alert or perform some other action when an email to an alias is received.

The advantage of using a transport rule is that the rule is always executed, it does not depend on the Outlook client running. This is useful because mobile devices or other clients will not execute any rules.

There are a couple advantages of using Outlook the Outlook method:

Greater flexibility over what you want to do with the message.

No need for Office 365 administrator rights to set up.

As the transport rule method has already been documented, this post is about how to use an Outlook rule to determine which email alias an email was sent to.

Using an Outlook rule to determine which email alias an email has been sent to

Go to File and then “Manage Rules and Alerts” and then click on “New rule”.

Click on “Apply rule on messages I receive” from the “Start from a blank rule” section and click Next.

Choose “with specific words in the message header”.

In the “Step 2” section at the bottom of the page, click on the “specific words” link:

Type in the email address that you want to identify and click on “Add” and then click OK.
(Note: You can add multiple email addresses here to use this rule for multiple aliases.)

You will drop back to the main rule creation dialog box, click next.

On this page you have lots of options about what to do with the identified message, the options are quite self explanatory.

I am going to choose “display a specific alert in the New Item Alert window” as below:

This means that when I receive an email to the alias specified, Outlook will show an alert to inform me.

Finish creating the rule with any other options or exceptions that you require.

You should get an alert when messages are sent to the alias:

I hope this post was helpful, if you did, I would really appreciate it if you rated it 😀