I am looking for a C API way to test whether a Domino database is a journal or not.
The best I’ve got so far is to check for notes with $JournalResponsibility>0, but:
it requires to traverse All Documents view
it might not be 100% accurate, if notes with this property appear in regular mailbox.
Ideally, this check should operate on open databases and cover rollover journals as well.
Subject: What makes Journaled Note a Journaled Note?
Dear all,
Looks like there is no reliable way to distinguish Journal mailbox from a ‘regular-user’ mailbox at database level.
I’ll follow the track of checking notes for ‘journal-specific’ fields values, like $JournalResponsibility>0.
Is it a reliable method? Which statement is more accurate:
All Journal mailbox notes have $JournalResponsibility>0
No ‘regular-user’ mailbox can have notes with $JournalResponsibility>0
Also, from my application point of view, it is harmless to take a Journal for ‘regular-user’ mailbox, while treating ‘regular-user’ mailbox as a Journal can lead to data loss.
Any help is well appreciated.
Subject: What makes Journal a Journal?
Just a guess, but the TemplateName property of the database should be a giveaway…
For instance, databases created with the “standard” Journal Template under R6 will have “Std6Journal” in the TemplateName property of the NotesDatabase object.
Gary
Subject: RE: What makes Journal a Journal?
TemplateName property of the database…It may work, but customers are allowed to change the template and/or its name.
I was thinking of contacting the database’s server and comparing DB name with server’s journal, but this is also far from perfect:
different paths (as strings) can point to same database
how can I tell if a database name is a rollover journal?
what if journaled messages go to main-in database?
Subject: RE: What makes Journal a Journal?
<<< > TemplateName property of the database… It may work, but customers are allowed to change the template and/or its name. >>>
Is that on the server? That’s a scary thought.
Subject: RE: What makes Journal a Journal?
I should read: “… but our customers’ administrators …” For me, there are mere customers 
Still scared?
Subject: RE: What makes Journal a Journal?
Well, I’ll be scared when Monday morning rolls around as it seems there is something new every week! some good, some bad. It’s the bad stuff i don’t like.
I follow you with the customers, I didn’t think that was the case but I had to make a comment.
Sorry I’m a little rusty on the admin side so I don’t have an answer off hand, I hope it works out for you.
Subject: RE: What makes Journal a Journal?
Oh – you are talking about Mail Journaling???
Subject: RE: What makes Journal a Journal?
I don’t think you can.
You can look at the documents, and see if they look like journaled messages. E.g., they have certain fields in them. But mail.box database have documents with similar fields. And customers can make databases containing documents with the same fields.
What’s the real requirement here?
Subject: RE: What makes Journal a Journal?
Thanks, Rich, Gary, I would stuck to checking messages for $JournalResponsibility.
The application receives from third-party feeder server/mailbox and ID/password, crawls the mailbox All Documents view and modifies some messages, based on a arbitrary criteria. I have no control over the third-party format – even if the feeder ‘knows’ database X is a journal, it cannot pass this info to me.
Journals are to be treated differently. That’s why database-level check is preferable to note-level check.