public folder replication broken


Posted Jul 16, 2010, 4:11 pm
Hi All,

QS Disclaimer has been working well for about 1 year now. I just built an additional exchange 2003 sp2 back end server. I've discovered QS Disclaimer is preventing the public folder replication emails that get sent between servers from being delivered. If i turn off the disclaimer server, the emails get delivered.

I tried using disclaimer groups to exempt users - i added the email server accounts to the "Disclaimer exempt users" AD group. No luck. Looking in email tracking, the emails have from: addresses that are slightly different than the servers names.

How would one go about adding a specific from: address that can be exempted from disclaimers, without using the AD groups feature?

Does anyone have any other suggestions?


Posted Jul 17, 2010, 10:10 am
This does sound like an issue that occured with an older version of QS Disclaimer and an Exchange/Windows update. So if you are not using 2.6.18, I recommend upgrading to the latest version first.

Posted Jul 19, 2010, 12:53 pm

Thanks for the reply - uprading to 2.6.18 was one of my troubleshooting steps. Problem remained.

When the disclaimer service is running, email tracking shows that the messages get delivered to the destination server. However the event chain stops at "SMTP: Message submitted to categorizer". The destination server does not show the messages as being stuck in the queue.

After stopping the dislaimer service and re-syncing the public folders, email tracking shows a completed delivery process. The last event in the chain is:

"SMTP store driver: message delivered locally
to store to"

The public folder content then syncs up. (server and domain names have been replaced with generics in above message)

There are various types of public folder replication emails. The subjects i have seen are:

Hierarchy backfill response
Folder content backfill response
Status Request

The senders i have seen in email tracking are:

Each type of replication email has been observed to fail when the disclaimer service is running.

Message tracking failures and successes seem to be the same whether going from server1-server2 or server2-server1.

Before i discovered problems with public folder replication, all other email functions seemed to be working fine with the disclaimer service running on both servers.

The above senders are not active directory users because i cannot add them to my Disclaimer exempt users AD group. And i don't want to try making users by those names - i'm sure that would really mess up something.


Posted Jul 19, 2010, 4:13 pm
Are you using internal disclaimers? If so, does switching the delivery type temporarily to external only allow replication?

Another option is to update the engine to allow the use of an exempt users list rather than the AD group. If you would like to do this, please e-mail support so that we can send you the details.

Posted Jul 19, 2010, 5:30 pm
When i turn off internal disclaimers then replication works.

I will email support.


Posted Jul 20, 2010, 7:54 pm

Updating the engine to allow the use of an exempt users list did the trick.