Anyone have any advice for me? Journaling is not enough for my needs. I need to parse out the mail into 2 different archives.
Now, the way I see it, I can journal everything to a db and parse out the email with an LS agent that looks up the recipents and parses group members to assign the appropriate archive
or
I can set up a ton of rules based on every entry in the address book. Somehow I imagine that this would smash my router.
Putting one group on a different server would probably give me the solution I’m looking for but that’s not going to happen.
I’m leaning towards creating a central repository and then processing those emails with an LS agent based on my own rules db. Any advice on retrieving the to/from info? Parsing the groups?
Does anyone think a different approach based on my separate archive requirements would be more effective? Maybe DB2?
Subject: RE: Making journaling work for me - advice?
Your best solution will cost a bit of cash. Purchase either iLumin Mailbox Manager or EMC/Legato EmailXTender Archive Edition. I am not a salesperson for either solution so I will let you contact both vendors. They will both run you about $20.00/mailbox, not a cheap solution by any stretch; but both solutions will allow you to journal all messages and then form separate archive containers based on polices. The archiving polices can be assigned to groups pulled from your Domino Directory. This is the easiest, most efficient way to accomplish what you want. (Unless you consider splitting your two groups onto two different mail servers).
I’m sure this wasn’t the solution you were looking for but until Lotus Journalling allows you to use groups and the ability to send to separate databases, third party tools are your best bet.
Subject: RE: Making journaling work for me - advice?
I run Email Xtender and it does do policy based archiving although we don’t use it and just dump everything in to one store (and pray that backup solutions keep pace ). When we implemented, policy based archiving was a little clunky but that was a couple of years ago and I haven’t looked at it in later releases.
Your proposed solution sounds viable - use journaling to dump everything in to one store then use an LS agent to aggregate the mail out to other DBs, according to a set of rules. I’d put plenty of thought in to how I implemented the rules. You want them configurable - setup profile form(s) or parsing an XML document are two methods you could make work. You could add a Categories field to the documents as you process them and make use of this in your store DBs using a categorised view.
Once processed I’d set a flag field “Processed” to 1 and have a second agent running to clear out the processed documents periodically.
I can’t think of any reason why this wouldn’t work.
Subject: RE: Making journaling work for me - advice?
I can suggest iLumin(Assentor) or Ziplip for your purposes. These packages are intended for SEC and Sarbanes regulation compliance but will do what you want.
). When we implemented, policy based archiving was a little clunky but that was a couple of years ago and I haven’t looked at it in later releases.