mailmaster blog

Do you get a “550 Client host rejected: [not accepting mail from this ip]” when you send mail today?

It’s a Mxtreme issue when you have Reputation Authority enabled.

Two solutions are available to fix this:

Solution 1:
a. Remove a DNS entry’s for borderware.com in DNS servers Boderware uses.(You find them under Configuration -> Network or Interfaces).
b. Empty DNS cache in Mxtreme/XCS under Status & Utility -> Flush DNS Cache.

Solution 2:
If above doesn’t work you can disable the Reputation Authority:
Version 7.1.x
Intercept – connection control
-Clear all checkboxes under BSN
-Clear Reject on DNSBL under DNSBL Reject Intercept – Anti-spam
-Clear DNS Block list
-Clear URL Block list

Version 8.x/9.x
Security – ReputationAuthority
-Clear all checkboxes on that page
Security – Connection control
-Clear Reject on DNSBL
Security – anti-spam
-Clear DNS Block list
-Clear URL Block list

I know this was not at all related to Exchange but I had this problem first hand today…

Update: I think someone at Borderware forgot to register… A whois on borderware.com gave me the following result:

Update 2: Try do the following as well:

Go to Activity – Threat Prevention Status and press “Reset Threat Prevention History”

I have seen a couple of reports of problems after installing KB973917 on Exchange (more often Exchange on SBS-serves).

The problem a user get is repeated login prompts.

A solution for Exchange is to apply Exchange 2007 SP1 Rollup 9. If it’s a SBS server you need to go to the Management Console, Updates and approve Rollup 9 for deployment.

Here’s a link to a friend of mine who has put more effort into this then me

As you probably heard there was a problem installing Exchange 2007 SP2 in a domain with only Windows Server 2008 R2 domain controllers. This issue is now solved. Microsoft has released updated xml files that will fix the problem.

Download the new files and copy it to the default location, where the present files are. Recommendation is to move the present xml files to a different directory or to rename them before copying the new files. More info & download files here

If you get the following error during installation of Exchange 2007 sp2:

Error:

An error occurred.  The error code was 3221685950.  The message was The remote procedure call failed

verify that you use the same account as you used for setup of Exchange.

I have seen some issues with installing SP2 with other accounts (yes, the second account was also Exchange Org admin)

Please be aware of a problem in Exchange Best Practice Analyzer, EXBPA.

If you get the following error:
“The value for the Extensible Storage Engine (ESE) transaction log file size has changed on server XXXXXX. This configuration is not supported. Current log file size is 5120 KB. Default log file size is 1024 KB”

Don’t worry, it’s a “bug” in the check EXBPA does and you could just download a new version of the EXBPA-file and itäs solved.