004 4:46 AM
To: [EMAIL PROTECTED]
Subject: Re: [Declude.JunkMail]
Determining a BCC Recipient
Let's please try to keep the personal stuff off of
this list for the good of everyone. Even though I might find it a tad bit
amusing at times when it is directed at me, I don't think that othe
Let's please try to keep the personal stuff off of this list for the
good of everyone. Even though I might find it a tad bit amusing at
times when it is directed at me, I don't think that others appreciate
seeing it here, and I generally don't. I hesitated even to draft this
reply except that
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".
Not to debate the applicability of the technology, but you shouldn't
proceed under the assumption that government regulators are out there
giving I
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 :) Manual
review is necessary to verify, and chances are you would need to
manually review every E-mail going to and from specific employees
across a range of dat
Please don't parse my words so carefully. Each company is different
and therefore so are their needs. Many that archive will never need to
go through the data, primarily because many companies aren't so
enormous that they have the legal liability nor the volume that would
necessitate a preemp
;Matt" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, October 27, 2004 3:53 PM
Subject: Re: [Declude.JunkMail] Determining a BCC Recipient
That's funny that you should ask. I just coded that one up in
VBScript this last weekend. I even managed to decode base6
Davidson" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, October 27, 2004 4:29 PM
> Subject: Re: [Declude.JunkMail] Determining a BCC Recipient
>
>
> > Essentially the good folks at Enron and WorldComm brought us the
> > Sarbanes-Oxley Act o
D]>
Sent: Wednesday, October 27, 2004 4:29 PM
Subject: Re: [Declude.JunkMail] Determining a BCC Recipient
> Essentially the good folks at Enron and WorldComm brought us the
> Sarbanes-Oxley Act or SOX for short. Public companies have to keep a
record
> of all communications, the details of
Mabry Internet/X Controls has a very good "Mime" processing
controls for easy reading of uue files.
- Original Message -
From: "Matt" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, October 27, 2004 3:53 PM
Subject: Re: [Declude.JunkMail] Dete
large attachments to deal with.
Rick Davidson
National Systems Manager
North American Title Group
-
- Original Message -
From: "Matt" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, October 27, 2004 3:53 PM
Subject: Re: [Declude.JunkMail] Determining a
t; <[EMAIL PROTECTED]>
To: "Rick Davidson" <[EMAIL PROTECTED]>
Sent: Wednesday, October 27, 2004 3:21 PM
Subject: Re: [Declude.JunkMail] Determining a BCC Recipient
Rick,
I am looking at creating our own email archiving solution using sql
This, as Matt notes, could be monstro
idson
National Systems Manager
North American Title Group
-
- Original Message - From: "Matt" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, October 27, 2004 2:58 PM
Subject: Re: [Declude.JunkMail] Determining a BCC Recipient
That's going to be one
remove attachments
would you? :-)
Rick Davidson
National Systems Manager
North American Title Group
-
- Original Message -
From: "Matt" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, October 27, 2004 2:58 PM
Subject: Re: [Declude.JunkMail] Deter
Rick,
> I am looking at creating our own email archiving solution using sql
This, as Matt notes, could be monstrous. It certainly is not
best-practice to store this many CLOBs (or BLOBs, if you're decoding
MIME) in a generic DB. That's why the only RDBMS message stores worth
their s
am to parse and insert it into the SQL database.
Rick Davidson
National Systems Manager
North American Title Group
-
- Original Message - From: "Matt" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, October 26, 2004 5:15 PM
Subject: Re: [Declude.JunkMail] De
IL PROTECTED]>
Sent: Tuesday, October 26, 2004 5:15 PM
Subject: Re: [Declude.JunkMail] Determining a BCC Recipient
Rick,
This information is in the Q* file. If you use the COPYFILE action, it
will keep both the D* and the Q* file. The only issue is that the Declude
headers are lost an
Rick,
This information is in the Q* file. If you use the COPYFILE action, it
will keep both the D* and the Q* file. The only issue is that the
Declude headers are lost and each message is kept separately and not
viewable without a special application like spamreview. IMO, this is
appropriate
17 matches
Mail list logo
