*Repost Begins (the original post)*
We have run into a strange issue after applying Rollup 7 last night to one of our SBS 2008 servers.
In this case, there are customized recipient policies to hand out return addresses based on the Custom Attribute 1 field’s entry. There are multiple e-mail domains on this particular SBS box.
Somehow, last night’s update has choked the return e-mail address stamp that comes on any e-mail sent by those with that custom attribute set!
The reply to address looks like this:
When we do a message tracking trace on for the user, the results show the Return Path as it should be UserN@TheirDomain.com, yet the above is on any e-mail they send out.
We have not yet applied Exchange 2007 Rollup 7 for SP1 to any of our other SBS 2008 boxes yet. It seems that default SBS 2008 installations should take the update with no issues as there has been very little feedback indicating otherwise.
More to come on the problem …
*Repost Ends*
It turns out that Rollup 7 will choke on Hidden Mailboxes.
Hide from Exchange address lists
The knowledgebase article: Microsoft KB969690: Unresolved sender for delivery status notifications after applying update rollup 7 for Exchange Server 2007 Service Pack 1.
The Knowledgebase article on the update itself: Description of Update Rollup 7 for Exchange Server 2007 Service Pack 1. Nothing here indicates that hidden mailboxes will cause things to choke up!
Now that we know what caused the problem, it is important to know that Exchange 2007 SP1 Rollup 7 should not be applied in cases where there are hidden mailboxes!
The only option we have now is to uninstall RU7, reinstall RU6, and we will be able to keep those addresses hidden. Thanks to Chris Puckett of Microsoft (Live Search) for pointing us in the right direction!
The problem will be fixed with Exchange 2007 Service Pack 2 according to the KB969690 article.
Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book
*All Mac on SBS posts will not be written on a Mac until we replace our now missing iMac! (previous blog post)
No comments:
Post a Comment