The guys from the Microsoft Exchange Team have worked on a new version of the Storage Requirements Calculator. This week version 16 is released of the Mailbox Server Role Storage Requirements Calculator. It’s a very useful tool when you need to determine what are the storage requirements for your mailbox server.
In Exchange 2003 we could prevend sending to a domain with delivery rectrictions. In Exchange 2007 we can do this by using transport rules _this can be created on the Hub Transport server. When we start the wizard and specify the name the next step is to define the _conditions, here we choose the following options:
Such as every software Exchange also has a versionnumber. Below a short overview of versionnumbers:
Maybe you discovered it yourself, maybe not. When you want to add values to the bypassedsenderdomains parameter via the set-contentfilterconfig you will lose all previous settings.
Normally creating a send connector is not really exited. The next step in the wizard is used for giving the domain for which the send connector needs to be used. But when you have a look at the bottom of the screen you will find the option scoped send connector, but what is the effect of enabling this option.
For troubleshooting mail delivery issues it can be usefull to have some logs, but where can you find them in Exchange 2007.
As you may no Exchange 2007 contains anti-spam agents. Besides this it’s possible for a user to create a safe list which a user can add senders from which he receives mail but he/she wants to ensure that they are not marked as spam. With multi-layer spam solutions this can cause issues. It can happen that a mail is not accepted by the Edge Transport server while the user wants to receive the mail.
This week I have been busy with a nice issue I found on the MsExchange forum. It started with an environment which had 2 Hub server where one could send mails to the internet but the otherone not. After asking somethings concerning Edge subscription I received the answer that the Edge subscription was renewed and the followign message was the result:
Most times it’s not a good idea to make everybody full administrator, but what can the different administrators do in Exchange 2007? In Exchange 2003 we had the Exchange Full Administrator, Exchange Administrator and theExchange View Only Administrator in Exchange 2007 we have the Exchange Organization Administrator, Exchange Server Administrator, Exchange Recipient Administrator and Exchange View-Only Administrator. Microsoft has published a really usefull Technet article on this which describes which administrator can do what and what he don’t can do .