Try the following code:

public void sendEMailThroughOUTLOOK()
{
Outlook.Application oApp = null;
SecurityManager m_ObjSM = null;
Outlook._MailItem oMsg = null;
Outlook.Recipients oRecips = null;
Outlook.Recipient oRecip = null;
try
{
oApp = new Outlook.Application();
m_ObjSM = new SecurityManager();
m_ObjSM.ConnectTo(oApp);
m_ObjSM.DisableOOMWarnings = true;

oMsg = (Outlook._MailItem)oApp.CreateItem(Outlook.OlItemType.olMailItem);
oMsg.HTMLBody = “Hello, This is a test mail !!!”;
oMsg.Subject = “BMW Test”;
oRecips = (Outlook.Recipients)oMsg.Recipients;
oRecip = (Outlook.Recipient)oRecips.Add(“xxxxx@xxxxx-xx.com”);
oRecip.Resolve();
oMsg.Send();
}
catch (Exception ex)
{
System.Windows.Forms.MessageBox.Show(ex.Message);
}
finally
{
if (oMsg != null) Marshal.ReleaseComObject(oMsg); oMsg = null;
if (oRecip != null) Marshal.ReleaseComObject(oRecip); oRecip = null;
if (oRecips != null) Marshal.ReleaseComObject(oRecips); oRecips = null;
if (oApp != null)
{
if (m_ObjSM != null)
{
m_ObjSM.DisableOOMWarnings = false;
m_ObjSM.Disconnect(oApp);
}
Marshal.ReleaseComObject(oApp); oApp = null;
}
}
}

Please pay attention to the template code we provide at http://www.add-in-express.com/outlook-security/:

Dim SecurityManager As New AddinExpress.Outlook.SecurityManager
SecurityManager.DisableOOMWarnings = True
Try
‘ … any action with protected objects …
Finally
‘ In any case please remember to turn on
‘ Outlook Security after your code,
‘ since now it is very easy to switch it off! :-)
SecurityManager.DisableOOMWarnings = False
End Try

A) You need to use the only Disable*Warnings property: the one corresponding to the way you access Outlook. since you do this via the Outlook object model, you need to use DisableOOMWarnings only; all other properties should be removed.

B) You should allow the warnings in the finally clause.

In addition to the general case, your code could leave OUTLOOK.EXE hanging in the Task Manager window. I’d suggest that you use oApp.Quit.

public void sendEMailThroughOUTLOOK()
{
Outlook.Application oApp=null;
SecurityManager m_ObjSM=null;
try
{

try
{
oApp = new Outlook.Application();
m_ObjSM = new SecurityManager();
m_ObjSM.ConnectTo(oApp);
m_ObjSM.DisableCDOWarnings = true;
m_ObjSM.DisableOOMWarnings = true;
m_ObjSM.DisableSMAPIWarnings = true;
}
catch (Exception ex1)
{
System.Windows.Forms.MessageBox.Show(ex1.Message);
}
Outlook.NameSpace oNS = oApp.GetNamespace(“mapi”);
Outlook.MailItem oMsg = (Outlook.MailItem)oApp.CreateItem(Outlook.OlItemType.olMailItem);
oMsg.HTMLBody = “Hello, This is a test mail !!!”;
oMsg.Subject = “BMW Test”;
Outlook.Recipients oRecips = (Outlook.Recipients)oMsg.Recipients;
Outlook.Recipient oRecip = (Outlook.Recipient)oRecips.Add(“xxxxx@xxxxx-xx.com”);
oRecip.Resolve();
oMsg.Send();

oRecip = null;
oRecips = null;
oMsg = null;
oApp = null;
}
catch (Exception ex)
{
System.Windows.Forms.MessageBox.Show(ex.Message);
}
}

Please suggest if i am missing anything.

You can send me your code for review: please find the support email address in {Security Manager installation folder}\readme.txt. The business logic and sencitive info can be removed; I’ll need to look at ALL Outlook-related code, however.

Ususally, that line produces an exception if the Security Manager isn’t registered on the target PC. Please find more info about deploying Outlook Security Manager at Outlook Security Manager 2010 deployment: Summary.

If you develop an add-in than you will not see security warnings in Outlook 2007 provided that you have an antivirus software installed.

However, there are other scenarios in which you’ll need to use Security Manager. Say, an Exchange administrator can use some settings that cause your code to produce warnings when accessing Outlook.Namespace.CurrentUser. You can find if this is your case by looking at the About window of your Outlook; it displays either “Security Mode: Default” or “Security Mode: Administrator controlled”.

You can send me extra details about the issue to the support e-mail address (see readme.txt or use any contact form on the web site).