This is scoped to be fixed in 8.1.2 which has an ETA of around April 15, 2013.  We also have a work around for this issue.  The work around is a extension manager that monitors the events for new arriving mail.  If the email meets some logic the extension manager will create a backup of the field needing to be modified, change the dot(s) (.) to the left of the @ sign to underscores (_), allow SMSDOM to then process the message.  The whitelist only works with the information to the right of the @ sign so the changes will help with this issue.

The work around should only be used if the whitelist feature must work now and using 64bit SMSDOM.  Otherwise, wait for the next build (8.1.2) which will fix this issue.  The workaround.zip file contains the dll and the ReadMe.doc file that explains how to install and use it.  There is also a movie file attached that demonstrates the work around.

Notice:  if there are Content Filtering rules working on the same field then it could affect those.  For example, if test.user@symantec.com gets changed to test_user@symantec.com it will no longer match a CF Rule looking for test.user@symantec.com.  So if there are rules like this you could just change the dots within the address to underlines while using the work around.