The archive sink plus a bit of FSO and CDO coding could give you that.
 
joe has probably already written a utility so that you wouldn't have to do any coding. :-)  j/k
 

The Archive Sink provides the capability of storing all messages to a flat file. It is an event sink that archives each email message handled by a specified SMTP Virtual Server to a flat file (more specifically, an EML file). This file contains the complete text of a message; including headers, body, MIME separators, etc. It is relatively simple to process each individual file as appropriate (such as storing it into a SQL database, for example) and then deleting the file.

As with Message Journaling/Archiving, the Archive Sink does not, by default, include BCC recipients or process various system messages. Options are available to enable inclusion of those messages.

If you choose to use the Archive Sink, disk usage of the files can grow at a quick pace; since SIS (Single Instance Storage) does not apply to the generated EML files.

For information about acquiring, installing, and using the Archive Sink, please see Microsoft KB 871110 (How to install and use the Archive Sink utility in Exchange Server 2003). For more information about event sinks, see the Microsoft Exchange Server 2003 Software Development Kit (SDK), available at http://microsoft.com/exchange/downloads.



From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tom Kern
Sent: Wednesday, September 07, 2005 8:58 PM
To: activedirectory
Subject: [ActiveDir] event sinks(OT)

My company is tied in to a specific archive solution. they want to outsource the whole archive thing.
this solution uses mapi and needs a dedicated journal mailbox server.
however due to my AD issues, i can't install a new exchange server.(no root domain. no SA or EA access. writtien about ad infinitum in older posts..)
 
so, i want to specifiy a contact with the smtp addy of the archive company smarthost as an archive mbox and route that out a dedicated smtp connector.
however, i know the archive contact will rewrite, at least,the envelop header of the email and thus put us out of compliance.
 
my question is, is there an event sink i could write that would somehow keep the original header and strip the envelop rewrite? make it look just like a copy of the orginial email like a true archive mbox would.
i know a previous company called Assentor did this somehow but i'm not sure how.
 
any help in this would be great.
 
thanks!!

Reply via email to