Exchange 2003 Recipient Policy error preventing Exchange 2007 migration (event id 8325)

Current Evironment:  Exchange 2003 SP2 running on Windows Server 2003 which is also a GC/DC (I know it's not recommended, which is why we are migrating).  I have installed Exchange 2007 w/SP1 'Typical Installation' (MB, HUB, CA).  When I attempt to move or create a user on the Exchange 2007 server I receive the following error:  
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:00
MS Test
Failed
Error:
The Exchange server address list service failed to respond. This could be because of an address list or email address policy configuration error.
Exchange Management Shell command attempted:
New-Mailbox -Name 'MS Test' -Alias 'mstest' -OrganizationalUnit 'internal.xxx.com/Users' -UserPrincipalName 'mstest@internal.xxx.com' -SamAccountName 'mstest' -FirstName 'MS' -Initials '' -LastName 'Test' -Password 'System.Security.SecureString' -ResetPasswordOnNextLogon $false -Database 'SERVERNAME\XXX Storage Group\XXX_Mail_DB'
**************************

And the following events appear in the App log of the 2007 server pointing to two recipient policies which are defined on the 2003 Server (one for each domain which assign a unique proxy address to each using an LDAP query):
The service can't work properly because Email Address Policy 'CN=XXX Recipient Policy,CN=Recipient Policies,CN=My Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=internal,DC=XXX,DC=com'  has an invalid filter rule (PurportedSearch). The error is 'Invalid token.'.  Use the Exchange Management Console to correct this problem.  New users, contacts, and groups won't be fully provisioned until this is fixed.
************************

Here is the value in the (Purported Search) field that the error above complains about:

(&((objectclass=*)(homemdb=CN=XXX Mailbox Store (SERVER03),CN=XXX Storage Group,CN=InformationStore,CN=SERVER03,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=My Organization,CN=Services,CN=Configuration,DC=internal,DC=XXX,DC=com)))
*********************

I believe the problem lies with the LDAP query used to create these policies that Exchange 2007 does not like.  But for the life of me I can't find one that Exchange 2007 is happy with.  I can't move forward with this migration until this problem is resolved.  Any help would be appreciated.  Thanks!