On Tue, 1 Jul 2008 14:23:21 +0100, "Oliver Moazzezi [MVP]" wrote: >> Thanks for the reply. >> >> I have seen your points. Can you tell me the mechanism for reading the log >> files directly. >> >> Now i don't know the format of transaction log file. Is there any >> mechnism >> for reading those logs? > >Hi there, > >You need to give up on the idea of reading the Transaction Logs. Implement >Journaling and then read any messages from an alternate Journaling Exchange >Server. > >Oliver > Not to mention that the logs arent "Joe Smith sent a message to Bob" Its more like , "At offset 3bf543......"
If you really wanted zero impact, then an archiving appliance that sits in the middle is about the only thing I can think of. If the appliance were a Windows box, you'll still implement an event sink of sorts that copied off the RFC822 message and then manipulated it till your heart's content as it transited the SMTP queue. For items locally delivered to the store still in MAPI format (Exchange 2000/2003), you'd have to route them through the appliance (border server) to force content conversion. #*&$ Still not zero footprint, is it? "Andy David {MVP}" wrote in message news:i8ck645vbsbvpu4h4m06gvvij307vlouji@4ax.com... > On Tue, 1 Jul 2008 14:23:21 +0100, "Oliver Moazzezi [MVP]" > wrote: > >>> Thanks for the reply. >>> >>> I have seen your points. Can you tell me the mechanism for reading the >>> log >>> files directly. >>> >>> Now i don't know the format of transaction log file. Is there any >>> mechnism >>> for reading those logs? >> >>Hi there, >> >>You need to give up on the idea of reading the Transaction Logs. Implement >>Journaling and then read any messages from an alternate Journaling >>Exchange >>Server. >> >>Oliver >> > > Not to mention that the logs arent "Joe Smith sent a message to Bob" > Its more like , "At offset 3bf543......" > > > > > >
