Installation (reinstallation) did not open firewall ports

[Steevo]

I migrated a failing windows 2000 server to a windows 2003 server.
I took the HDD out of the old server, put it in the new server as a second drive.

I copied the mailenable directory tree over to the new server HDD and ran the same version 5.1 installer over it.
It seemed to work ok, except for when i moved the mail back to that server in DNS I cannot check mail.

I turned off the windows firewall in network connections and I could. Ah ha! As I suspected.

I seem to remember the ME installer taking care of this, and mediag did not detect the problem at all.

I read some forum posts and one of your guys told someone to run MEInstaller.exe in the bin directory Remove Strict Server Security Policy and then to Apply Strict Server Security policy.
I tried that but I don't have an entry to Remove, only to apply. So that seems odd. Why would that entry be missing?

So I opened up tcp ports 25, 110 and 587 manually and it works.
However I don't know if that results in the server being properly locked down.

Why didn't the installer open the ports as required, and why didn't the diagnostics complain?

Do I need to do anything else? This seems like an installer bug.

[Steevo]

Anyone here? I got no response to this report.