Save Messages (called tickets by the compagny) to a SQL Server Database .
I have to save email détails in our database using C# . I found that writing a macro in outlook or writing outlook plugins could do that for me , but with that approach we must do this for every Outlook contact .
So after searching I found that the best approach is to do that within the exchange server to watch over a specific mailbox for incoming emails .
How can I do that please ? I'm quite new to the field . Could please provide me some solution with implementations .
So after searching I found that the best approach is to do that within the exchange server to watch over a specific mailbox for incoming emails .
How can I do that please ? I'm quite new to the field . Could please provide me some solution with implementations .
Who is Participating?
You can try an existing Outlook Add-on that does this www.geniusconnect.com
Link the Outlook Folder(s) to your table and check "Auto Save" option. This will save sent items automatically to DB.
Link the Outlook Folder(s) to your table and check "Auto Save" option. This will save sent items automatically to DB.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
-
Course of the Month8 days, 17 hours left to enrollMonitoring and Operating a Private Cloud with System Center 2012 R2 273 lessons
Event Sinks allow you to register custom code on the Exchange server that will execute at specific points in message processing (when a message is received or sent, as one example):
https://support.microsoft.com/en-us/kb/317680 (Example of a sink when mail is sent)
https://support.microsoft.com/en-us/kb/324021 (Example of a sink when mail is received)
On newer versions of Exchange, this is accomplished via "Transport Rules" and "Mail Flows":
https://technet.microsoft.com/en-us/library/jj919238(v=exchg.150).aspx
Though a bit less flexible, they appear to be significantly easier to implement as they're native functionality (rather than custom code), though they appear to allow for custom code execution as well rather than just the pre-defined options. I've never used them before, but they appear to cover what you're looking for.