5.0.4 > 5.0.5

[LMStone]

Originally Posted by brian

Mark,

It would be helpful if you could file a bug on settings that were reset during upgrade, including the zmsetup.log. The zimbraFeatureBriefcase being reset sounds like a bug, I couldn't find anywhere that we set/reset the postfix settings and main.cf should be preserved across upgrades so please include zmsetup.log so we see if they were set during the upgrade.

For the postfix_header_checks, you'll just need to replace the colon after Content-Type: with something that will match in pcre like .* and the postmap will be much happier.

Hi Brian,

I'm on the road today and tomorrow but will look at this when I get back to the office on Friday.

Quick question re Postfix... Why are you doing a postmap on a pcre table? It's just a lookup table so no .db file needed, right? See Postfix manual - pcre_table(5) for example.

All the best,
Mark

[davidfsmith]

Got the same problem, my commerical cert didn't migrate from 5.0.2 to 5.0.5 support helped sort the problem, but now there is an issue with IE 7 and the cert....

Ah, just gone here to find the solution....
;-)

Will try in the morning

[Bill Brock]

Windows likes to have the CA that signed your certificates in the root store. Some times the individual certificate for the site can be put in the root store and sometimes not. But if you put the CA's (the issuer) certificate in the root store then any certificate that it has signed(issued) will be accepted without error.

I've never acquired a commercial cert for my Zimbra install but I'm sure that wherever you acquired your commercial cert should also provide you with a CA cert to install.

If Windows does not find the issuers cert in its root store it considers the chain broken.