Outlook 2007 Will Not Send Mail From C# Application

Status
Not open for further replies.
D

Dale Franks

I have a C# Windows Forms application that I am developing. I am running

into a problem sending mail via Outlook 2007. The application is being

developed in VS2008. I work in a DoD (Navy) environment, where I have no

control over the security settings for Outlook. The code is very simple:

Outlook.Application oApp = new Outlook.Application();

Outlook._NameSpace oNameSpace = oApp.GetNamespace("MAPI");

Outlook.MAPIFolder oOutboxFolder =

oNameSpace.GetDefaultFolder(Outlook.OlDefaultFolders.olFolderOutbox);

oNameSpace.Logon(null, null, false, false);

Outlook._MailItem oMailItem =

(Outlook._MailItem)oApp.CreateItem(Outlook.OlItemType.olMailItem);

oMailItem.To = "edwin.franks@navy.mil";

oMailItem.Subject = cboSubject.Text;

oMailItem.Body = txtMessage.Text;

oMailItem.Send();

In the application I am developing, the email DOES get sent through Outlook

2003, after the user approves the mail on the security dialog box. In 2007,

however, the Send() function results in the error:

Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT))

In the Outlook 2007 Trust Center, the Programmatic Access security setting

is set to "Warn me about suspicious activity when my antivirus software is

inactive or out of date (recommended)", which, although I cannot change it in

the Outlook interface, seems to me to be the appropriate level of security.

I really don't care if the security dialog box appears or not. It does

appear in Outlook 2003, and the user can approve the message. That's fine.

What I don't understand is why Office 2007 refuses to either send the email,

or provide a security dialog box for the user to approve it. I can save the

email. I can move it into the Outbox, or anywhere else. I can display the

email, and have the user manually click the send button. But I can't

actually send the email.

Since the rest of the organization is scheduled to upgrade to Office 2007 in

the near future, this is a matter of some pressing interest for me.

Any suggestions?
 
What does Tools | Trust Center tell you about the status of your anti-virus

application?

Have you tried adding a Namespace.Logon statement? That may be necessary if

Outlook isn't already running.

I've also seen people report good results from displaying the message before

adding recipients and sending.

Sue Mosher

"Dale Franks" <Dale Franks> wrote in message

news:967D84CD-1BDD-4E03-9B03-17A0D8D3BA59@microsoft.com...
> I have a C# Windows Forms application that I am developing. I am running
> into a problem sending mail via Outlook 2007. The application is being
> developed in VS2008. I work in a DoD (Navy) environment, where I have no
> control over the security settings for Outlook. The code is very simple:

> Outlook.Application oApp = new Outlook.Application();
> Outlook._NameSpace oNameSpace = oApp.GetNamespace("MAPI");
> Outlook.MAPIFolder oOutboxFolder =
> oNameSpace.GetDefaultFolder(Outlook.OlDefaultFolders.olFolderOutbox);
> oNameSpace.Logon(null, null, false, false);
> Outlook._MailItem oMailItem =
> (Outlook._MailItem)oApp.CreateItem(Outlook.OlItemType.olMailItem);
> oMailItem.To = "edwin.franks@navy.mil";
> oMailItem.Subject = cboSubject.Text;
> oMailItem.Body = txtMessage.Text;
> oMailItem.Send();

> In the application I am developing, the email DOES get sent through
> Outlook
> 2003, after the user approves the mail on the security dialog box. In
> 2007,
> however, the Send() function results in the error:

> Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT))

> In the Outlook 2007 Trust Center, the Programmatic Access security setting
> is set to "Warn me about suspicious activity when my antivirus software is
> inactive or out of date (recommended)", which, although I cannot change it
> in
> the Outlook interface, seems to me to be the appropriate level of
> security.

> I really don't care if the security dialog box appears or not. It does
> appear in Outlook 2003, and the user can approve the message. That's
> fine.

> What I don't understand is why Office 2007 refuses to either send the
> email,
> or provide a security dialog box for the user to approve it. I can save
> the
> email. I can move it into the Outbox, or anywhere else. I can display
> the
> email, and have the user manually click the send button. But I can't
> actually send the email.

> Since the rest of the organization is scheduled to upgrade to Office 2007
> in
> the near future, this is a matter of some pressing interest for me.

> Any suggestions?
 
My anti-virus software is up to date, according to the trust center. I did

add the line to display the message prior to adding the recipient addresses

and body text. It did display, and was correctly contstructed. The Send()

function still resulkted in the same error. I can do everything imaginable

to the message...except send it.

Although after the message displays, I can hit the send button on the

displayed message form, which sends the message promptly. It just won't send

programmatically.

The code already has the Namespace.Logon() command incorporated.

"Sue Mosher [MVP]" wrote:


> What does Tools | Trust Center tell you about the status of your anti-virus
> application?

> Have you tried adding a Namespace.Logon statement? That may be necessary if
> Outlook isn't already running.

> I've also seen people report good results from displaying the message before
> adding recipients and sending.

> > Sue Mosher
> > >

> "Dale Franks" <Dale Franks> wrote in message
> news:967D84CD-1BDD-4E03-9B03-17A0D8D3BA59@microsoft.com...
> >I have a C# Windows Forms application that I am developing. I am running
> > into a problem sending mail via Outlook 2007. The application is being
> > developed in VS2008. I work in a DoD (Navy) environment, where I have no
> > control over the security settings for Outlook. The code is very simple:
> > Outlook.Application oApp = new Outlook.Application();
> > Outlook._NameSpace oNameSpace = oApp.GetNamespace("MAPI");
> > Outlook.MAPIFolder oOutboxFolder =
> > oNameSpace.GetDefaultFolder(Outlook.OlDefaultFolders.olFolderOutbox);
> > oNameSpace.Logon(null, null, false, false);
> > Outlook._MailItem oMailItem =
> > (Outlook._MailItem)oApp.CreateItem(Outlook.OlItemType.olMailItem);
> > oMailItem.To = "edwin.franks@navy.mil";
> > oMailItem.Subject = cboSubject.Text;
> > oMailItem.Body = txtMessage.Text;
> > oMailItem.Send();
> > In the application I am developing, the email DOES get sent through
> > Outlook
> > 2003, after the user approves the mail on the security dialog box. In
> > 2007,
> > however, the Send() function results in the error:
> > Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT))
> > In the Outlook 2007 Trust Center, the Programmatic Access security setting
> > is set to "Warn me about suspicious activity when my antivirus software is
> > inactive or out of date (recommended)", which, although I cannot change it
> > in
> > the Outlook interface, seems to me to be the appropriate level of
> > security.
> > I really don't care if the security dialog box appears or not. It does
> > appear in Outlook 2003, and the user can approve the message. That's
> > fine.
> > What I don't understand is why Office 2007 refuses to either send the
> > email,
> > or provide a security dialog box for the user to approve it. I can save
> > the
> > email. I can move it into the Outbox, or anywhere else. I can display
> > the
> > email, and have the user manually click the send button. But I can't
> > actually send the email.
> > Since the rest of the organization is scheduled to upgrade to Office 2007
> > in
> > the near future, this is a matter of some pressing interest for me.
> > Any suggestions?


> .
>
 
Namespace.Logon should be invoked before any statements that use the

instantiated Namespace object. Also, if Outlook isn't already running, you

may need to prompt the user to choose a mail profile.

The only other thing I can think to try is calling Recipients.ResolveAll

before sending.

BTW, is there a particular reason why you're using Outlook and not

System.Net.Mail?

Sue Mosher

"Dale Franks" <DaleFranks> wrote in message

news:144C99AC-68E5-47C3-A666-BD349F61281B@microsoft.com...
> My anti-virus software is up to date, according to the trust center. I
> did
> add the line to display the message prior to adding the recipient
> addresses
> and body text. It did display, and was correctly contstructed. The
> Send()
> function still resulkted in the same error. I can do everything
> imaginable
> to the message...except send it.

> Although after the message displays, I can hit the send button on the
> displayed message form, which sends the message promptly. It just won't
> send
> programmatically.

> The code already has the Namespace.Logon() command incorporated.

> "Sue Mosher [MVP]" wrote:
>
> > What does Tools | Trust Center tell you about the status of your
> > anti-virus
> > application?
>

>> Have you tried adding a Namespace.Logon statement? That may be necessary
> > if
> > Outlook isn't already running.
>

>> I've also seen people report good results from displaying the message
> > before
> > adding recipients and sending.
>

>> "Dale Franks" <Dale Franks> wrote in message
> > news:967D84CD-1BDD-4E03-9B03-17A0D8D3BA59@microsoft.com...
> > >I have a C# Windows Forms application that I am developing. I am
> > >running
> > > into a problem sending mail via Outlook 2007. The application is being
> > > developed in VS2008. I work in a DoD (Navy) environment, where I have
> > > no
> > > control over the security settings for Outlook. The code is very
> > > simple:
> >> > Outlook.Application oApp = new Outlook.Application();
> > > Outlook._NameSpace oNameSpace =
> > > oApp.GetNamespace("MAPI");
> > > Outlook.MAPIFolder oOutboxFolder =
> > > oNameSpace.GetDefaultFolder(Outlook.OlDefaultFolders.olFolderOutbox);
> > > oNameSpace.Logon(null, null, false, false);
> > > Outlook._MailItem oMailItem =
> > > (Outlook._MailItem)oApp.CreateItem(Outlook.OlItemType.olMailItem);
> > > oMailItem.To = "edwin.franks@navy.mil";
> > > oMailItem.Subject = cboSubject.Text;
> > > oMailItem.Body = txtMessage.Text;
> > > oMailItem.Send();
> >> > In the application I am developing, the email DOES get sent through
> > > Outlook
> > > 2003, after the user approves the mail on the security dialog box. In
> > > 2007,
> > > however, the Send() function results in the error:
> >> > Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT))
> >> > In the Outlook 2007 Trust Center, the Programmatic Access security
> > > setting
> > > is set to "Warn me about suspicious activity when my antivirus software
> > > is
> > > inactive or out of date (recommended)", which, although I cannot change
> > > it
> > > in
> > > the Outlook interface, seems to me to be the appropriate level of
> > > security.
> >> > I really don't care if the security dialog box appears or not. It does
> > > appear in Outlook 2003, and the user can approve the message. That's
> > > fine.
> >> > What I don't understand is why Office 2007 refuses to either send the
> > > email,
> > > or provide a security dialog box for the user to approve it. I can save
> > > the
> > > email. I can move it into the Outbox, or anywhere else. I can display
> > > the
> > > email, and have the user manually click the send button. But I can't
> > > actually send the email.
> >> > Since the rest of the organization is scheduled to upgrade to Office
> > > 2007
> > > in
> > > the near future, this is a matter of some pressing interest for me.
 
> BTW, is there a particular reason why you're using Outlook and not
> System.Net.Mail?


Yeah. As I mentioned, I'm working in the US Navy NMCI environment. I'm not

allowed to touch an SMTP server. And, even if I could, the SMTP ports are

blocked anyway.

"Sue Mosher [MVP]" wrote:


> Namespace.Logon should be invoked before any statements that use the
> instantiated Namespace object. Also, if Outlook isn't already running, you
> may need to prompt the user to choose a mail profile.

> The only other thing I can think to try is calling Recipients.ResolveAll
> before sending.

> BTW, is there a particular reason why you're using Outlook and not
> System.Net.Mail?
> > Sue Mosher
> > >

> "Dale Franks" <DaleFranks> wrote in message
> news:144C99AC-68E5-47C3-A666-BD349F61281B@microsoft.com...
> > My anti-virus software is up to date, according to the trust center. I
> > did
> > add the line to display the message prior to adding the recipient
> > addresses
> > and body text. It did display, and was correctly contstructed. The
> > Send()
> > function still resulkted in the same error. I can do everything
> > imaginable
> > to the message...except send it.
> > Although after the message displays, I can hit the send button on the
> > displayed message form, which sends the message promptly. It just won't
> > send
> > programmatically.
> > The code already has the Namespace.Logon() command incorporated.
> > "Sue Mosher [MVP]" wrote:
> >
> >> What does Tools | Trust Center tell you about the status of your
> >> anti-virus
> >> application?
> >
> >> Have you tried adding a Namespace.Logon statement? That may be necessary
> >> if
> >> Outlook isn't already running.
> >
> >> I've also seen people report good results from displaying the message
> >> before
> >> adding recipients and sending.
> >
> >> "Dale Franks" <Dale Franks> wrote in message
> >> news:967D84CD-1BDD-4E03-9B03-17A0D8D3BA59@microsoft.com...
> >> >I have a C# Windows Forms application that I am developing. I am
> >> >running
> >> > into a problem sending mail via Outlook 2007. The application is being
> >> > developed in VS2008. I work in a DoD (Navy) environment, where I have
> >> > no
> >> > control over the security settings for Outlook. The code is very
> >> > simple:
> >> >> > Outlook.Application oApp = new Outlook.Application();
> >> > Outlook._NameSpace oNameSpace =
> >> > oApp.GetNamespace("MAPI");
> >> > Outlook.MAPIFolder oOutboxFolder =
> >> > oNameSpace.GetDefaultFolder(Outlook.OlDefaultFolders.olFolderOutbox);
> >> > oNameSpace.Logon(null, null, false, false);
> >> > Outlook._MailItem oMailItem =
> >> > (Outlook._MailItem)oApp.CreateItem(Outlook.OlItemType.olMailItem);
> >> > oMailItem.To = "edwin.franks@navy.mil";
> >> > oMailItem.Subject = cboSubject.Text;
> >> > oMailItem.Body = txtMessage.Text;
> >> > oMailItem.Send();
> >> >> > In the application I am developing, the email DOES get sent through
> >> > Outlook
> >> > 2003, after the user approves the mail on the security dialog box. In
> >> > 2007,
> >> > however, the Send() function results in the error:
> >> >> > Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT))
> >> >> > In the Outlook 2007 Trust Center, the Programmatic Access security
> >> > setting
> >> > is set to "Warn me about suspicious activity when my antivirus software
> >> > is
> >> > inactive or out of date (recommended)", which, although I cannot change
> >> > it
> >> > in
> >> > the Outlook interface, seems to me to be the appropriate level of
> >> > security.
> >> >> > I really don't care if the security dialog box appears or not. It does
> >> > appear in Outlook 2003, and the user can approve the message. That's
> >> > fine.
> >> >> > What I don't understand is why Office 2007 refuses to either send the
> >> > email,
> >> > or provide a security dialog box for the user to approve it. I can save
> >> > the
> >> > email. I can move it into the Outbox, or anywhere else. I can display
> >> > the
> >> > email, and have the user manually click the send button. But I can't
> >> > actually send the email.
> >> >> > Since the rest of the organization is scheduled to upgrade to Office
> >> > 2007
> >> > in
> >> > the near future, this is a matter of some pressing interest for me.


> .
>
 
Dale,

I have the same problem. If have resolved please suggest your solution that

fixed your problem.

My problem:

When I send the Email programmatically (C#) through Outlook 2007, it throws

Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT))

error and did not send the mail.

As when OUTLOOK 2007 process is started in the background, the same

application sends successfully the email.

The same application sends the email on another machine where OutLook 2003

is installed, without the outlook 2003 process started in the background.

I appreciate your solution.

Thanks,

SAM

"Dale Franks" wrote:


> I have a C# Windows Forms application that I am developing. I am running
> into a problem sending mail via Outlook 2007. The application is being
> developed in VS2008. I work in a DoD (Navy) environment, where I have no
> control over the security settings for Outlook. The code is very simple:

> Outlook.Application oApp = new Outlook.Application();
> Outlook._NameSpace oNameSpace = oApp.GetNamespace("MAPI");
> Outlook.MAPIFolder oOutboxFolder =
> oNameSpace.GetDefaultFolder(Outlook.OlDefaultFolders.olFolderOutbox);
> oNameSpace.Logon(null, null, false, false);
> Outlook._MailItem oMailItem =
> (Outlook._MailItem)oApp.CreateItem(Outlook.OlItemType.olMailItem);
> oMailItem.To = "edwin.franks@navy.mil";
> oMailItem.Subject = cboSubject.Text;
> oMailItem.Body = txtMessage.Text;
> oMailItem.Send();

> In the application I am developing, the email DOES get sent through Outlook
> 2003, after the user approves the mail on the security dialog box. In 2007,
> however, the Send() function results in the error:

> Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT))

> In the Outlook 2007 Trust Center, the Programmatic Access security setting
> is set to "Warn me about suspicious activity when my antivirus software is
> inactive or out of date (recommended)", which, although I cannot change it in
> the Outlook interface, seems to me to be the appropriate level of security.

> I really don't care if the security dialog box appears or not. It does
> appear in Outlook 2003, and the user can approve the message. That's fine.

> What I don't understand is why Office 2007 refuses to either send the email,
> or provide a security dialog box for the user to approve it. I can save the
> email. I can move it into the Outbox, or anywhere else. I can display the
> email, and have the user manually click the send button. But I can't
> actually send the email.

> Since the rest of the organization is scheduled to upgrade to Office 2007 in
> the near future, this is a matter of some pressing interest for me.

> Any suggestions?
 
Dale

I found a soultion for my problem.

For Outlook 2007, the code needs Outlook.Inpector object.

Outlook.Application oApp = null;

Outlook.MailItem oMsg = null;

Outlook.Inspector oAddSig = null;

oApp = new Outlook.Application();

oMsg = (Outlook.MailItem)oApp.CreateItem(Outlook.OlItemType.olMailItem);

oAddSig = oMsg.GetInspector;

After adding Inspector object the code sends email through Outlook 2007.

That is the solution to my problem.

With Outlook 2003, the code does not need this Inspector object. Without the

Inspector object, the Outlook 2003 sends email.

THX

SAM

"SAM" wrote:


> Dale,

> I have the same problem. If have resolved please suggest your solution that
> fixed your problem.

> My problem:
> When I send the Email programmatically (C#) through Outlook 2007, it throws
> Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT))
> error and did not send the mail.

> As when OUTLOOK 2007 process is started in the background, the same
> application sends successfully the email.

> The same application sends the email on another machine where OutLook 2003
> is installed, without the outlook 2003 process started in the background.

> I appreciate your solution.

> Thanks,
> SAM

> "Dale Franks" wrote:
>
> > I have a C# Windows Forms application that I am developing. I am running
> > into a problem sending mail via Outlook 2007. The application is being
> > developed in VS2008. I work in a DoD (Navy) environment, where I have no
> > control over the security settings for Outlook. The code is very simple:
> > Outlook.Application oApp = new Outlook.Application();
> > Outlook._NameSpace oNameSpace = oApp.GetNamespace("MAPI");
> > Outlook.MAPIFolder oOutboxFolder =
> > oNameSpace.GetDefaultFolder(Outlook.OlDefaultFolders.olFolderOutbox);
> > oNameSpace.Logon(null, null, false, false);
> > Outlook._MailItem oMailItem =
> > (Outlook._MailItem)oApp.CreateItem(Outlook.OlItemType.olMailItem);
> > oMailItem.To = "edwin.franks@navy.mil";
> > oMailItem.Subject = cboSubject.Text;
> > oMailItem.Body = txtMessage.Text;
> > oMailItem.Send();
> > In the application I am developing, the email DOES get sent through Outlook
> > 2003, after the user approves the mail on the security dialog box. In 2007,
> > however, the Send() function results in the error:
> > Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT))
> > In the Outlook 2007 Trust Center, the Programmatic Access security setting
> > is set to "Warn me about suspicious activity when my antivirus software is
> > inactive or out of date (recommended)", which, although I cannot change it in
> > the Outlook interface, seems to me to be the appropriate level of security.
> > I really don't care if the security dialog box appears or not. It does
> > appear in Outlook 2003, and the user can approve the message. That's fine.
> > What I don't understand is why Office 2007 refuses to either send the email,
> > or provide a security dialog box for the user to approve it. I can save the
> > email. I can move it into the Outbox, or anywhere else. I can display the
> > email, and have the user manually click the send button. But I can't
> > actually send the email.
> > Since the rest of the organization is scheduled to upgrade to Office 2007 in
> > the near future, this is a matter of some pressing interest for me.
> > Any suggestions?
 
Sam,

I have a similar problem with my VB5 program using MAPI trying to send Email

thru Outlook 2000. I have an unanswered post below but wondered if you could

help.

I have a VB5 pgm that uses MAPI to send emails to customers. Everything

works fine when "Outlook Express" is installed on my XP computer. When I

replaced Outlook Express with "Outlook 2002", it appears that my pgm sends

emails out just fine, but when I click Outlook I get an error message "System

Administrator: None of your e-mail accounts could send to this recipient."

What is wrong and how can I fix this?

Dennis Rose

"SAM" wrote:


> Dale

> I found a soultion for my problem.

> For Outlook 2007, the code needs Outlook.Inpector object.

> Outlook.Application oApp = null;
> Outlook.MailItem oMsg = null;
> Outlook.Inspector oAddSig = null;

> oApp = new Outlook.Application();
> oMsg = (Outlook.MailItem)oApp.CreateItem(Outlook.OlItemType.olMailItem);
> oAddSig = oMsg.GetInspector;

> After adding Inspector object the code sends email through Outlook 2007.
> That is the solution to my problem.

> With Outlook 2003, the code does not need this Inspector object. Without the
> Inspector object, the Outlook 2003 sends email.

> THX
> SAM

> "SAM" wrote:
>
> > Dale,
> > I have the same problem. If have resolved please suggest your solution that
> > fixed your problem.
> > My problem:
> > When I send the Email programmatically (C#) through Outlook 2007, it throws
> > Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT))
> > error and did not send the mail.
> > As when OUTLOOK 2007 process is started in the background, the same
> > application sends successfully the email.
> > The same application sends the email on another machine where OutLook 2003
> > is installed, without the outlook 2003 process started in the background.
> > I appreciate your solution.
> > Thanks,
> > SAM
> > "Dale Franks" wrote:
> >
> > > I have a C# Windows Forms application that I am developing. I am running
> > > into a problem sending mail via Outlook 2007. The application is being
> > > developed in VS2008. I work in a DoD (Navy) environment, where I have no
> > > control over the security settings for Outlook. The code is very simple:
> > > > Outlook.Application oApp = new Outlook.Application();
> > > Outlook._NameSpace oNameSpace = oApp.GetNamespace("MAPI");
> > > Outlook.MAPIFolder oOutboxFolder =
> > > oNameSpace.GetDefaultFolder(Outlook.OlDefaultFolders.olFolderOutbox);
> > > oNameSpace.Logon(null, null, false, false);
> > > Outlook._MailItem oMailItem =
> > > (Outlook._MailItem)oApp.CreateItem(Outlook.OlItemType.olMailItem);
> > > oMailItem.To = "edwin.franks@navy.mil";
> > > oMailItem.Subject = cboSubject.Text;
> > > oMailItem.Body = txtMessage.Text;
> > > oMailItem.Send();
> > > > In the application I am developing, the email DOES get sent through Outlook
> > > 2003, after the user approves the mail on the security dialog box. In 2007,
> > > however, the Send() function results in the error:
> > > > Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT))
> > > > In the Outlook 2007 Trust Center, the Programmatic Access security setting
> > > is set to "Warn me about suspicious activity when my antivirus software is
> > > inactive or out of date (recommended)", which, although I cannot change it in
> > > the Outlook interface, seems to me to be the appropriate level of security.
> > > > I really don't care if the security dialog box appears or not. It does
> > > appear in Outlook 2003, and the user can approve the message. That's fine.
> > > > What I don't understand is why Office 2007 refuses to either send the email,
> > > or provide a security dialog box for the user to approve it. I can save the
> > > email. I can move it into the Outbox, or anywhere else. I can display the
> > > email, and have the user manually click the send button. But I can't
> > > actually send the email.
> > > > Since the rest of the organization is scheduled to upgrade to Office 2007 in
> > > the near future, this is a matter of some pressing interest for me.
> > > > Any suggestions?
 
Status
Not open for further replies.
Similar threads
Thread starter Title Forum Replies Date
L Outlook 2007 Separate the Send/Receive functions Using Outlook 2
P Outlook 2007 not sending/receiving until restart (send/receive stuck at __%) Using Outlook 27
W OUTLOOK 2007 FREEZES. WILL NOT SEND NOR RECEIVE Using Outlook 1
S Send email from excel based on a condition (outlook 2007) Outlook VBA and Custom Forms 1
E Microsoft Office Outlook 2007 Send Error Using Outlook 11
S Can't send messages using Outlook 2007 from a business email Using Outlook 3
J Outlook 2007 Error sharing Calendar: Error while preparing to send sharing message Using Outlook.com accounts in Outlook 2
J New Outlook 2007 form - try to send and get error Operation Failed Outlook VBA and Custom Forms 11
S unable to send email from my second address (outlook 2007) Using Outlook 2
B Outlook 2007 - How to set the "send from diff email" as default? Using Outlook 5
M Outlook 2007 cant send email with vista Home Premium Using Outlook 8
J Outlook 2007 Failure to Send Message<=Sending reported Error 0x80040201 Using Outlook 1
P Send/Receive error in Outlook 2007 Using Outlook 2
S Outlook 2007 will not send emails Using Outlook 0
S Connector Forces Outlook 2007 To Hang On Send/Receive Using Outlook.com accounts in Outlook 3
I Send Secure Email Through Microsoft Outlook 2007 and 2010 (32 bit) Using Outlook 0
I Send Secure Email Through Microsoft Outlook 2007 and 2010 (32 bit) Using Outlook 0
N Outlook 2007 - Set account to send only with .prf file Using Outlook 1
S Outlook 2007 Running on Windows 7 hangs on send Using Outlook 7
M Unable to send email to gmail - using Outlook 2007 Using Outlook 3
A Send a letter from Microsoft Outlook 2007 Business Contacts BCM (Business Contact Manager) 1
G Outlook 2007 Meeting Item Send Button Outlook VBA and Custom Forms 10
D Outlook 2007: "the Operation Failed" on Send to Multiple addresses Using Outlook 6
C Not able to send emails with Outlook 2007 using Vista BCM (Business Contact Manager) 1
J How to hide/disable send button in Outlook 2007 Outlook VBA and Custom Forms 1
J How to hide/disable send button in Outlook 2007 Outlook VBA and Custom Forms 2
J How to hide/disable send button in Outlook 2007 Outlook VBA and Custom Forms 1
J Outlook 2007 crashed when pushing send on a displayed mailitem Outlook VBA and Custom Forms 1
D Outlook 2007 Recovering E-Mails Using Outlook 0
W Transfer Outlook 2016 autocomplete file to Outlook 2007 Using Outlook 1
C Outlook 2007 Removing then adding account restores junk email processing Using Outlook 0
S Outlook 2007 crash linked to gdiplus.dll Using Outlook 0
S Outlook 2007 - Automatic purge fail Using Outlook 0
J outlook 2007 doesn't let me choose which .pst to search Using Outlook 2
D Outlook 2007 vs. Outlook 2010 -- ToDo Bar Using Outlook 0
D Outlook 2007 on 365 Using Outlook.com accounts in Outlook 2
S Macro for other actions - Outlook 2007 Outlook VBA and Custom Forms 23
S Verwendung von Outlook 2007 Using Outlook 0
A Arthur needs help with 2007 Outlook e-mail Using Outlook.com accounts in Outlook 3
M PST import from Outlook 2007 to 2010 - Address Book contacts all in 1 group Using Outlook 4
S outlook 2007 calendar search Using Outlook 6
B Migrate Outlook 2007 to Office 365 Using Outlook 3
X I have met my waterloo trying to resolve embedded graphics problem with outlook 2007 and now 2016 Using Outlook 1
R Outlook 2007 only loads some appointments Using Outlook 0
C Move Outlook 2007 to new PC with Outlook 365 Using Outlook 3
J Outlook 2007 Hide Messages Option not Available Using Outlook 2
S Outlook 2007 Calendar instant search problem. Windows 7 Using Outlook 4
S Outlook 2007 Calendar instant search problem. Windows 7 Using Outlook 0
B Server errors Outlook 2007 Using Outlook 1
S Reboot of frozen windows7 results in changed outlook 2007 settings Using Outlook 1

Similar threads

Back
Top