With R7, Lotus introduced the possibility of adding message disclaimers in the Mail Policy (yay!) so we wanted to use this to deal with disclaimers.
In the organisation there are several OUs, of which some want to implement a disclaimer that are specific to the OU.
In theory this seems really simple: using organisational policies and mail settings documents we can set the disclaimer for the different OUs. In practice however, we can’t get it to work: when the router is restarted, it seems to pick one disclaimer at random (e.g.: most recently edited mail settings document) and applies that to ALL mails, regardless of OU of the sender. We’re not sure that really all mails get a disclaimer (some may not get one), but we can’t differentiate between them.
Since we still have R5 clients active on the network, we’ve deselected the “Clients can add Disclaimer” option in the policy – just for sake of uniformity and simplicity in testing.
At this point, we don’t know if message disclaimers using organisational policies are just not functioning or there is something we’re doing wrong.
Therefore I’d like to know if any of you succeeded in making this work, and how you did it… We have tried this in to different environments, but simply cannot get it to work as advertised.
Subject: RE: R7 Message Disclaimers via Organisational Policy – Anybody got them to work properly?
I believe this is a bug with the “mail settings” that was added in Lotus Notes 7.0
I’ve been running policies as described in this thread for over 3 years and they work “as expected” and as documented. Now when I add the new mail setting with a disclaimer to one OU policy, all 18 OU’s are affected and use that mail setting.
Oddly enough, when looking at the hierarchy of the policies using Policy Viewer, and when doing a Policy synopsis, there is no reference to the mail settings in the particular OU. So everything appears to look normal.
I am now running 7.02 FP1 HF68.
IBM support suggested that I remove the parent ou in my policy structure. I refused to do this as it seems to make no sense and would be a band-aide at best as a solution.
Subject: RESOLVED - R7 Message Disclaimers via Organisational Policy – Anybody got them to work properly?
After sending a link of this thread to IBM support, they were able to identify this as a bug, with a couple of resolutions.1. use explicit poilies (not an option for me).
add a notes.ini setting on the Domino server “policy_disable_cache=1” (without the quotes) and restart server.
Although I could not find any inormation on SPR KRED6WXKP8, I applied it with good faith and I am pleased with the results. Option 2 worked great for me. There seems to be a problem with the Policy cache because when using policy_disable_cache=1 the problem goes away.
Subject: RE: R7 Message Disclaimers via Organisational Policy – Anybody got them to work properly?
Ronny,
There is a long list of steps for setting up mail disclaimers, so I’m going to try to keep this short.
Consider you have a company called “ACME”, with the organizational units “RED”, “ORANGE” and “GREEN”, each of which have a couple of users.
For sake of simplicity, there’s only one server called SERVER/ACME that contains both the mail files and which acts as SMTP gateway.
Create an organisational policy for */ACME in the names and address book.
For that policy, create a Mail Settings Policy document, and include a disclaimer text “Disclaimer for */ACME”. Set the option for client processing of the policy to Disabled.
Assign the mail settings document in the organisational policy created in step 1.
Now repeat steps 1 to 3 for the OUs */RED/ACME, */ORANGE/ACME, */GREEN/ACME.
Open the configuration document for SERVER/ACME, and enable support for Message Disclaimers (Tab: router/smtp, subtab message disclaimers).
Re-load the router configuration (or restart the server if you like) and start sending out mails from users within the different OUs. In our case, the message disclaimer for messages sent by all users are identical.
Touch one or more mail policy settings document (just open and save, don’t save anything), reload router config and send yet some more mails. Check the disclaimers – in our case these were different.
As far as I can see it is not working as it is supposed to be unless there is somehting I’m missing in the documentation.