Rollup 5 released

Today rollup 5 for Exchange 2007 is released. This update contains fixes for:

Exchange Rollup 5 released soon

On the site of the Microsoft Exchange Team an article is published about rollup 5 which will be available within a few days. One of the fixes in the rollup will ensure that all services will start after the installation of a patch. There are some known cases that this will not happen after the installation of a rollup. The problem is caused by a check of a certificate which is used to sign the binaries. This check wil try to contact crl.microsoft.com but when the environment has limited or no internet access this can cause this issue.

ESE internals

It’s now a few weeks after TechEd, some sessions of TechEd are published on a special TechEd site. One of this sessions are ESE internals presented by Ross Smith IV, Senior Technology Architect from Microsoft. Ross goes in to the depth of ESE the database type used by Exchange.

Cannot start the Microsoft Exchange Transport service

As each version of a software package each package will need some tricks to solve issues. With Exchange 2007 this is also the case. It can happen that the Microsoft Exchange Transport service won’t start. When you have this issue you may see several events with the ID 5023. This was the case which I found on a forum. The cause of this issue appears to be an empty MsExchHomeRoutinggroup attribute.

Technet Edge

Exchange 2007 and Asterisk 1.6

Blat

If you would like to test the mail performance of your server then you could use jetstress to test your database. But when you would like to decide yourself what kind of e-mails you want to send to your mailserver then you should have a look at Blat. Blat is a command-line mailer which can be used in a batch file which send multiple mails to your mailserver. This program is not ment to be used for bothering other people with bulkmails. If you are interested in the tool then have a look at the site below.

Event ID 2050 on CAS Server

I have been very busy this week so I did not had many time to blog. Yesterday and today I visited a forum to have a look for interesting issues. One item I found was about Event ID 2050 on a CAS server. When looking at the details of the event you will see the following:

554 5.6.1 Body type not supported by Remote Host

Last week I found a message on the Technet forum which contained a question about how to disable 8 bit mime in Exchange 2007. So I started some research on mime types.

Prevent spoofing with IMSS

It’s time for a new tutorial but this time with another subject Trend Micro Interscan Messaging Security Suite, IMSS for short. IMSS is the antivirus/imss solution from Trend Micro which is available for Windows, Linux, Solaris and as appliance.</p>

With policies we can define our own rules, we will create a rule which will prevend spoofing. To do this we need to login to the admin console of IMSS. This can be done by selecting the option policy and then select the option policy list in the left menu.

Next we will choose the option new and choose the option other from the drop-down menu. Standard the option is selected that this rule needs to be applied to incoming mails.

First we define the sender/recipient en exclusions.

First the recipient, this can be done by clicking on the link recipient

As recipient we select all the users in the domain trendmicro.dyndns.org

When you are responsible for multiple domains you can fill in all domains here. When all domains are added you can click on the save button. The next step is choosing the sender, this can be done by clicking on the link sender. Here we fill in the same domains as defined in the recipient option. When ready we will click on save again when all domains are added.

The last option is to define the exceptions, this can be done when using a form on your website which uses an e-mail address which exists in your domain as the sender. In this case we choose the address info@trendmicro.dyndns.org

In this case we only allow from info@trendmicro.dyndns.org to info@trendmicro.dyndns.org but this can also be the complete domain.

When we have defined all three options it's time to define the scanning conditions. Here we only need to specify one thing. In this case we want to check every mail which is bigger then 1 Kb.

When we are statisfied with the settings we click on next to continue and specify the action.

Because we don't want the spoofing mails to arrive in the mailbox of users we select the option delete entire message. In case you want to first have a look what the result is you can choose the option quarantine to this will ensure that mail is placed in quarantine.

When the action is defined it's time for the last step, define the name and rulenumber. This last two fields can be defined with whatever you like. In our case we defined the name of the rule as anti-spoofing and placed it as the 8th rule.

Were finished now with creating the anti-spoofing rule. Keep in mind that this wil also block mails from sites which let you forward articles and use your e-mail address as sender, inform your users about this.