Senza impazzire con il codice, ho visto personalmente che funziona anche il questo metodo, riassunto alla fine di questo articolo.
Normally this comes from deleting a rule BEFORE disabling it, but who
knows. I used to have to hunt these down with NotesPeek, if I remember
correctly. I would find out how many "phantom" rules were still in the
mailbox, create n+1 new rules, then disable all the new rules, then delete
all the rules. That would take out the "phantoms", along with the new
rules.
INOLTRE:
Mail rules are stored in two places - in the Rule document, and in the
Calendar Profile document (enabled rules only). The server\'s ROUTER task is
what processes rules, and rather than reading the Rules documents, it reads
the rules from the Calendar Profile document prior to delivering a message
(there is some caching too).
As you\'ve discovered, a user can delete a Rule document. The problem is
with R5 clients, and maybe some Notes 6 clients, deleting a Rule document
without first enabling it leaves the Rule in the Calendar Profile document.
And once the Rule document is gone, there is no easy way to get it out of
the Calendar Profile. Sometimes you can create enough new rules, enable
them,and disable them - but I\'ve had minimal success with that.
If you open the database with NotesPeek and look at the Calendar Profile
document, you\'ll see at least two fields - $FilterFormulaCount and one or
more $FilterFormula_x fields (one for each enabled rule). While the content
of the $FilterFormula_x field is not totally readable, If you are familiar
with Formula language, you\'ll be able to figure out which rule is in the
Calendar Profile that doesn\'t have a corresponding Rule document.
The only real reliable way is to write an agent to manipulate the Calendar
Profile document by deleting the $FilterFormula_x field, and setting the
$FilterFormulaCount to the right value. I think that number is supoosed to
be the total number of Rules documents, whether they are enabled or not. If
there are no Rules documents, you can delete the $FilerFormulaCount field.
When I deal with this problem, I find it best to disable all rules, and
delete all of the $FilterFormula_x fields. Then go back and re-enable the
rules you want.
In definitiva per risolvere il problema si deve andare con Notes Peek nel db interessato, aprire la cartella "profiles" cercare il documento "calendar Profile" e controllare la presenza della regola incriminata e leggere il numero contenuto del campo $FilerFormulaCount. Creare N+1 regole, attivarle, disabilitarle e cancellarle. A questo punto anche la regola incriminata "dovrebbe" essere eliminata.
MR
|