15 ott 2011

Exchange Management Console Troubleshooter

The EMTshooter runs on the local (target) Exchange server and attempts to identify potential problems with management tools connection to it.

The troubleshooter runs in 2 stages. First, it will look at the IIS Default Web Site, the PowerShell vdir, and other critical areas, to identify known causes of connection problems. If it identifies a problem with one of the pre-checks it will make a recommendation for resolving the problem. If the pre-checks pass, the troubleshooter will go ahead and try to connect to the server in the exact same way that the management tools would. If that connection attempt still results in a WinRM-style error, the troubleshooter will attempt to compare that error to a list of stored strings that we have taken from the related support cases that we have seen. If a match is found, the troubleshooter will display the known causes of that error in the CMD window.

For more informaiton on this download see: http://blogs.technet.com/b/exchange/archive/2010/12/07/3411644.aspx

13 ott 2011

Exchange 2010: IP Block List Providers and the variables

In Exchange 2003 we could set custom error message with below variables:


%0: IP address of the sending mail server
%1: Rule name of the connection filter
%2: The RBL provider

BUT in Exchange 2007 or Exchange 2010 the variables above are not longer available.

To set custom rejection response we can use below variables.


{0}: IP address of the sending mail server
{1}: Rule name of the connection filter
{2}: The RBL provider

I.e.: Message refused: your IP {0} is listed by {2} (see http://multirbl.valli.org/lookup/{0}.html for details).

image

Naturally we can use the EMS:

Add-IPBlockListProvider -Name:Spamhaus -LookupDomain:zen.spamhaus.org -AnyMatch $True –RejectionResponse “Message refused: your IP {0} is listed by {2} (see http://multirbl.valli.org/lookup/{0}.html for details).”

image

Ref: http://technet.microsoft.com/en-us/library/bb124369(EXCHG.140).aspx