<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>What's the difference between Archive Sink and Journaling?</title><link>http://blogs.technet.com/exchange/archive/2004/07/06/174188.aspx</link><description>I have been asked this question several times. The short answer is that Archive Sink allows capturing emails that go through a specific SMTP virtual server. Journaling will capture every email that is sent and/or received by users that are hosted in a</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: What's the difference between Archive Sink and Journaling?</title><link>http://blogs.technet.com/exchange/archive/2004/07/06/174188.aspx#175154</link><pubDate>Wed, 07 Jul 2004 11:41:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:175154</guid><dc:creator>David R. Hibbeln</dc:creator><description>Compliance requirements - The issue is much larger then just Sarbanes-Oxley and HIPPA. &lt;br&gt;&lt;br&gt;The need of companies to be able to produce copies of e-mail when discovery happens in civil ligitgation is going to be more common place faster then most people think. &lt;br&gt;&lt;br&gt;Several changes in the procedures followed in various jurisdictions have all ready happened and this trend will acclerate. &lt;br&gt;&lt;br&gt;It is there responsiblity of the producing party (the one served with the discovery &lt;br&gt;motion) to supply the e-mails.  This effects ANY business that has an e-mail server.&lt;br&gt;&lt;br&gt;There is a need for the ablity to be able to index, search and produce all the e-mails sent with in an organization based on the terms of the discovery order issued by the judge. &lt;br&gt;&lt;br&gt;This is NOT just a big company issue, it is all company with e-mail. &lt;br&gt;&lt;br&gt;Hopefully the Exchange Team is having some discussion with the computer forensic's / electronic discovery community about these issues.&lt;br&gt;&lt;br&gt;drh at hibbeln dot net</description></item><item><title>re: What's the difference between Archive Sink and Journaling?</title><link>http://blogs.technet.com/exchange/archive/2004/07/06/174188.aspx#180799</link><pubDate>Mon, 12 Jul 2004 16:34:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:180799</guid><dc:creator>Nick Wade</dc:creator><description>Great article Max, thank you. As David points out there are larger compliance considerations and we thank you for also pointing out your archiving partners who can assist in this space. Sidbar; there is an email forensics team internal to Microsoft somewhere and this group's opinion would be interesting.&lt;br&gt;&lt;br&gt;Onto a question I have - ArchiveSink is particular to Exchange Servers in that it relies on Event Sink stuff from Exchange. Is there a way (and I haven't done any R&amp;amp;D, this just popped up at the right time) where an IIS SMTP Server can be made to drop a copy of all messages passing through to a disk queue for &amp;quot;archiving&amp;quot;? EML format would be suitable. Or perhaps another way of doing essentially what ArchiveSink does, but without Exchange involved? I'm thinking of SMTP gateway boxes where IIS alone is being used.&lt;br&gt;&lt;br&gt;Cheers</description></item><item><title>re: What's the difference between Archive Sink and Journaling?</title><link>http://blogs.technet.com/exchange/archive/2004/07/06/174188.aspx#180801</link><pubDate>Mon, 12 Jul 2004 16:43:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:180801</guid><dc:creator>Nick Wade</dc:creator><description>Errr - okay, now I feel like a fool for posting that question, the first bit of google-fishing (bring on the new MSN Search!!) I did brought up an older blog (&lt;a target="_new" href="http://blogs.msdn.com/exchange/archive/2004/02/19/76432.aspx"&gt;http://blogs.msdn.com/exchange/archive/2004/02/19/76432.aspx&lt;/a&gt;) from the Exchange team - which answers my question in a basic fashion at this point - but it does rely on the SMTP box being the endpoint for that email traffic. I'm also interested in mail passing through, rather than being at the end of it's travel... hence ArchiveSink-like functionality would be cool...I'm thinking the sink sample provided in the blog post I just referenced could be modded to do similar things?&lt;br&gt;&lt;br&gt;Cheers</description></item><item><title>re: What's the difference between Archive Sink and Journaling?</title><link>http://blogs.technet.com/exchange/archive/2004/07/06/174188.aspx#185815</link><pubDate>Sat, 17 Jul 2004 01:04:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:185815</guid><dc:creator>David Barnes</dc:creator><description>This is good and very close, but I find outbound messages are not logged? have I missed something.. &lt;br&gt;I find the messages 'pre SMTP format' in \Mapi-Gateway Messages, but this does not show what the server actually sent to the destination.&lt;br&gt;&lt;br&gt;Personal view, but I find Exchange 5.5's protocol logging and archival better and far easier to trace and diagnose what came in/went out. Yes I know there could be inprovements, like logging the IP address and noting the message archive file in the protocol log and perhaps even having a copy of the protocol session data at the top and bottom of each message archive file.&lt;br&gt;&lt;br&gt;The IIS protocol log is a mess (again personal view).. can we go back to one logfile per session. and can we have the ability to FULLY log everything INCLUDING the message in the protocol log, so things are consistent and very easy to diagnose.&lt;br&gt;Oh and while I'm asking can we see exposure of the DNS MX lookup, that was performed to find the destination server, in the protocol log.&lt;br&gt;&lt;br&gt;The sinks are a very good idea and provide the ability to do lots of good stuff (like global footers etc) but for diagnostics and LEGAL purposes we do need to be able to see an exact log of what the server actually sent and recieved. with sinks you can't be certain that another sink existed after/before the archive one that modified the message..&lt;br&gt;My thoughts as a techie is that an archive journal would not stand up in court as I would not be able to prove/disprove the existance of any other sinks.&lt;br&gt;In the UK we don't worry so much about Sarbanes-Oxley and HIPPA. What we do wory about is e-mail is a legal comunication method and a copy of the message send must be just that a copy of what was sent/recieved over the wire. I've put exchange 2003 in for some firms of solicitors here and we still have to feed everything through an Exchange 5.5 server as the logging and journal is accepted PROOF, but I'm told that everyones still arguing about 2000+ [This could be totally wrong by now though].</description></item></channel></rss>