Hi, I believe generally all emails are stored in a .PST file on Exchange Server. Is there a way where emails are stored on Harddisk as Individual Message(both incomming/outgoing) in either .EML or .MSG format? - Jiya

Email messages are not stored individually on the Exchange server, all emails are stored in a central database: *.EDB. This database is specific to Exchange and can only be read by an Exchange server of the same version or special third party tools. *.PST files are for local archival storage on a per-mailbox level usually on local storage on a personal pc. PST files are a personal database that allows a single file to hold multiple email messages. *.EML or .MSG files are if you want to save off individual messages to a different location. What are you trying to accomplish in the long run?Tim Harrington - Catapult Systems - http://HowDoUC.blogspot.com

I did this once for inbound email to a single domain by making it a relay domain, creating a send connector for that domain that used an unreachable smarthost, and using a scheduled task and a powershell script to periodically suspend the queue, export all the messages to .eml files, and then clear and restart the queue. It worked for the application I was using it for, but it might not scale very well. [string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

On Sun, 26 Dec 2010 06:52:47 +0000, mjolinor wrote: >I did this once for inbound email to a single domain by making it a relay domain, creating a send connector for that domain that used an unreachable smarthost, You could have just had the smart host put the messages into the local "drop" directory. The IIS SMTP server writed them as .eml files. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

You could have just had the smart host put the messages into the local "drop" directory. The IIS SMTP server writed them as .eml files. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP Would that require setting up a smarthost to receive them? The unreachable smarthost configuration was just to "dead-end" the queue so the messages would accumulate there.[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

On Sun, 26 Dec 2010 21:40:27 +0000, mjolinor wrote: > You could have just had the smart host put the messages into the local "drop" directory. The IIS SMTP server writed them as .eml files. --- Rich Matheisen MCSE+I, Exchange MVP >--- Rich Matheisen MCSE+I, Exchange MVPWould that require setting up a smarthost to receive them? The unreachable smarthost configuration was just to "dead-end" the queue so the messages would accumulate there. Yes, it would. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi Tim, The entire purpose is to "Search emails". Earlier we tried "EWS" Exchange WebService. But its so slow that is unacceptable to client. Earlier client had a custom program that used to download emails and write it into a SQLServer database and had written another custom program to display email messages from sqlserver database. The problem is that these email history is difficult to migrate into new system. We suggested EWS as a good solution (Keeping emails where they are suppose to be in their native format ) but now it has fallen back to us, because EWS is very slow in searching emails compared to their existing SQLServer database searching. Also out of 10 attempts EWS Times out almost 6 times. Now what we are thinking is to do two things. 1. When an inbound/outbound emails arrive we would capture To,CC,Subject, Inbound/outbound, From fields and store it in database. 2. We also want to store path of Email in database. There is the reason i am looking if Emails can be stored as individual items on harddisk, then i can pull the .EML file and show the content to user, while the search will be taken care by SQLServer. So how do we go about doing this..............also anyone, with any alternative thoughts, I would love to hear them. Regards Jiya.

You might be able to set up journaling to an exernal SMTP recipient, then set up a send connector to that namespace and use Rich's suggestion of setting up a smarthost to receive the journal files and pull the .eml files out of the drop directory.[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "