Re[2]: [Declude.JunkMail] Determining a BCC Recipient

2004-10-29 Thread Sanford Whiteman
you shouldn't proceed under the assumption that government regulators are out there giving IT staff lists of words to be used in full-text search of E-mail archives. That is not the law, and it is not how subpoenas are issued. First: I clearly noted that legal (or

Re[2]: [Declude.JunkMail] Determining a BCC Recipient

2004-10-28 Thread Sanford Whiteman
Each company is different and therefore so are their needs. Okay, but _Rick's_ needs are SOX compliance. I don't have any interest in discussing general archiving methods; to each his/her own in that effort. Many that archive will never need to go through the data, primarily because many

Re[2]: [Declude.JunkMail] Determining a BCC Recipient

2004-10-28 Thread Sanford Whiteman
Show me a search of a full text index that can positively give you 100% of the hits on a given topic and I'll let you have this one :) The regulators will typically give you a list of search terms to be used in a full-text search. Their specifications are what guide the accuracy of

Re[2]: [Declude.JunkMail] Determining a BCC Recipient

2004-10-28 Thread Pete McNeil
On Thursday, October 28, 2004, 10:44:32 PM, Matt wrote: M Patrick Childers wrote: Hi Pete, I think your gut is right. I'm pretty sure that I have 2 clients that would be quite interested in SOXsniffer. g M Not to debate the applicability of the technology, but you shouldn't M proceed under

Re[2]: [Declude.JunkMail] Determining a BCC Recipient

2004-10-27 Thread Sanford Whiteman
I will look into those, the boss wants me to do this on the cheap, the sql idea was first so we could at least say we were archiving the email. If you just want archiving for independent audit and to show good faith, concatenate the Q and D into an envelope-preserving MBOX for

RE: Re[2]: [Declude.JunkMail] Determining a BCC Recipient

2004-10-27 Thread Mark E. Smith
... Not sure if that helps but that's what we did for archiving/searching. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sanford Whiteman Sent: Wednesday, October 27, 2004 4:47 PM To: Rick Davidson Subject: Re[2]: [Declude.JunkMail] Determining

Re[2]: [Declude.JunkMail] Determining a BCC Recipient

2004-10-27 Thread Sanford Whiteman
If it were me I would just use the CATCHALLMAILS feature of Declude and COPY them to an archival e-mail address and then just burn the inbox of that address to disk once a month. For low-volume and unregulated businesses, perhaps, but this will not accomplish compliance, since: - it

Re: Re[2]: [Declude.JunkMail] Determining a BCC Recipient

2004-10-27 Thread Dan Geiser
- From: Sanford Whiteman [EMAIL PROTECTED] To: Dan Geiser [EMAIL PROTECTED] Sent: Wednesday, October 27, 2004 5:33 PM Subject: Re[2]: [Declude.JunkMail] Determining a BCC Recipient If it were me I would just use the CATCHALLMAILS feature of Declude and COPY them to an archival e-mail address

Re: Re[2]: [Declude.JunkMail] Determining a BCC Recipient

2004-10-27 Thread Rick Davidson
- From: Sanford Whiteman [EMAIL PROTECTED] To: Rick Davidson [EMAIL PROTECTED] Sent: Wednesday, October 27, 2004 4:46 PM Subject: Re[2]: [Declude.JunkMail] Determining a BCC Recipient I will look into those, the boss wants me to do this on the cheap, the sql idea was first so we could at least

Re[2]: [Declude.JunkMail] Determining a BCC Recipient

2004-10-27 Thread Sanford Whiteman
I strongly recommend that you just simply keep these in their Q* and D* formats and zip up the directories every night and write them to a CD or something every so often. Like I keep trying to say, this isn't an every so often or best-effort regulation. It's strict and for-real. .