Outlook 2000 Message stuck in Outbox

Status
Not open for further replies.
J

John Erickson

Hi,

I'm developing an Add-in which works fine for Outlook 2003 and 2007. I'm

trying to get it to also work for Outlook 2000, but I have one problem. I am

autogenerating a message to be sent for some of the messages that I receive.

In Outlook 2003 & 2007, this generated message gets sent fine, but in Outlook

2000 it gets stuck in the Outbox and Outlook won't send the message. If I

double click the message in Outlook's Outbox and then click send, it sends

the message fine and the message gets deleted as I planned. FWIW I'm doing

all the message creation work in MAPI in a seperate thread that my add-in

sends messages to and not in the Outlook object model to avoid the

restrictions that generate possible virus warning messages. After I build the

message and set all it's properties I am calling IMessage::SubmitMessage(0)

and that seems to be all it takes for 2003 & 2007. I've looked at the message

that gets stuck in the Outbox using MFCMapi to inspect the message properties

and everything looks fine to me. I'm at a loss to explain why it's not being

sent. Have you heard of this before? Is there some property I'm not setting

or a call I'm not making that OL2000 requires?

John
 
D

Dmitry Streblechenko

Is Outlook 2000 installed in the IMO mode (which breaks Extended MAPI) or

C/W?

Dmitry Streblechenko (MVP)

-

"John Erickson" <JohnErickson> wrote in message

news:07E3F58F-04EF-4651-9E98-7636DF53A0C1@microsoft.com...
> Hi,

> I'm developing an Add-in which works fine for Outlook 2003 and 2007. I'm
> trying to get it to also work for Outlook 2000, but I have one problem. I
> am
> autogenerating a message to be sent for some of the messages that I
> receive.
> In Outlook 2003 & 2007, this generated message gets sent fine, but in
> Outlook
> 2000 it gets stuck in the Outbox and Outlook won't send the message. If I
> double click the message in Outlook's Outbox and then click send, it sends
> the message fine and the message gets deleted as I planned. FWIW I'm doing
> all the message creation work in MAPI in a seperate thread that my add-in
> sends messages to and not in the Outlook object model to avoid the
> restrictions that generate possible virus warning messages. After I build
> the
> message and set all it's properties I am calling
> IMessage::SubmitMessage(0)
> and that seems to be all it takes for 2003 & 2007. I've looked at the
> message
> that gets stuck in the Outbox using MFCMapi to inspect the message
> properties
> and everything looks fine to me. I'm at a loss to explain why it's not
> being
> sent. Have you heard of this before? Is there some property I'm not
> setting
> or a call I'm not making that OL2000 requires?

> John
 
J

John Erickson

It's IMO, but I know that all of the MAPI calls I'm making work well (with

the exception of this SubmitMessage call), so I don't think it's broken. Even

the SubmitMessage call succeeds with S_OK. It just doesn't send the message.

When you say it breaks Extended MAPI, what exactly do you mean?

"Dmitry Streblechenko" wrote:


> Is Outlook 2000 installed in the IMO mode (which breaks Extended MAPI) or
> C/W?

> > Dmitry Streblechenko (MVP)
>

>

>

> -
> "John Erickson" <JohnErickson> wrote in message
> news:07E3F58F-04EF-4651-9E98-7636DF53A0C1@microsoft.com...
> > Hi,
> > I'm developing an Add-in which works fine for Outlook 2003 and 2007. I'm
> > trying to get it to also work for Outlook 2000, but I have one problem. I
> > am
> > autogenerating a message to be sent for some of the messages that I
> > receive.
> > In Outlook 2003 & 2007, this generated message gets sent fine, but in
> > Outlook
> > 2000 it gets stuck in the Outbox and Outlook won't send the message. If I
> > double click the message in Outlook's Outbox and then click send, it sends
> > the message fine and the message gets deleted as I planned. FWIW I'm doing
> > all the message creation work in MAPI in a seperate thread that my add-in
> > sends messages to and not in the Outlook object model to avoid the
> > restrictions that generate possible virus warning messages. After I build
> > the
> > message and set all it's properties I am calling
> > IMessage::SubmitMessage(0)
> > and that seems to be all it takes for 2003 & 2007. I've looked at the
> > message
> > that gets stuck in the Outbox using MFCMapi to inspect the message
> > properties
> > and everything looks fine to me. I'm at a loss to explain why it's not
> > being
> > sent. Have you heard of this before? Is there some property I'm not
> > setting
> > or a call I'm not making that OL2000 requires?
> > John

>
 
J

John Erickson

I did a futher study of the differences in the properties of the message that

is stuck in the Outbox vs the message after double clicking it and hitting

send. (Fortunately it doesn't send right away and I could close Outlook 2000

and use MFCMapi to look at the properties.) The one after hitting send has

the following differences:

PR_CLIENT_SUBMIT_TIME exists,

PR_MESSAGE_DELIVERY_TIME exists,

PR_MESSAGE_FLAGS has an added bit (MSGFLAG_SUBMIT),

PR_MESSAGE_SIZE increased by 69,

PR_SENTMAIL_ENTRYID exists,

PR_SUBMIT_FLAGS exists,

PR_ACCESS looses the MAPI_ACCESS_MODIFY bit

PR_ACCESS_LEVEL changes from 1 to 0,

PR_LAST_MODIFICATION_TIME changes

named properties 0x8552, 0x8554, and 0x8583 are added.

It looks suspiciously like the SubmitMessage call is only saving the message

and not actually submitting it to be sent. Is there an additional call I need

to make for Outlook 2000?

John

"John Erickson" wrote:


> It's IMO, but I know that all of the MAPI calls I'm making work well (with
> the exception of this SubmitMessage call), so I don't think it's broken. Even
> the SubmitMessage call succeeds with S_OK. It just doesn't send the message.
> When you say it breaks Extended MAPI, what exactly do you mean?

> "Dmitry Streblechenko" wrote:
>
> > Is Outlook 2000 installed in the IMO mode (which breaks Extended MAPI) or
> > C/W?
> > > > Dmitry Streblechenko (MVP)
> >

> >

> >

> > -
> > "John Erickson" <JohnErickson> wrote in message
> > news:07E3F58F-04EF-4651-9E98-7636DF53A0C1@microsoft.com...
> > > Hi,
> > > > I'm developing an Add-in which works fine for Outlook 2003 and 2007. I'm
> > > trying to get it to also work for Outlook 2000, but I have one problem. I
> > > am
> > > autogenerating a message to be sent for some of the messages that I
> > > receive.
> > > In Outlook 2003 & 2007, this generated message gets sent fine, but in
> > > Outlook
> > > 2000 it gets stuck in the Outbox and Outlook won't send the message. If I
> > > double click the message in Outlook's Outbox and then click send, it sends
> > > the message fine and the message gets deleted as I planned. FWIW I'm doing
> > > all the message creation work in MAPI in a seperate thread that my add-in
> > > sends messages to and not in the Outlook object model to avoid the
> > > restrictions that generate possible virus warning messages. After I build
> > > the
> > > message and set all it's properties I am calling
> > > IMessage::SubmitMessage(0)
> > > and that seems to be all it takes for 2003 & 2007. I've looked at the
> > > message
> > > that gets stuck in the Outbox using MFCMapi to inspect the message
> > > properties
> > > and everything looks fine to me. I'm at a loss to explain why it's not
> > > being
> > > sent. Have you heard of this before? Is there some property I'm not
> > > setting
> > > or a call I'm not making that OL2000 requires?
> > > > John
> >
 
J

John Erickson

I reconfigured it to be C/W instead of IMO and I am seeing the exact same

behavior. Another thing I have noticed now is that once I have Done 1 or more

SubmitMessage calls, Outlook will not terminate. Instead it hangs and I have

to Stop debugging to get it to shutdown all the way. After discovering this I

reviewed all my COM object references during the SubmitMessage process and I

don't see anyplace where I am not releasing a reference when I should be.

It's like Outlook itself is hung up in the SubmitMessage process even though

it returned S_OK to me. I just tried adding the FORCE_SUBMIT option to the

SubmitMessage call and that solved part of my problem. The message now gets

sent. However, I still have the termination problem if I have done 1 or more

SubmitMessage calls.

John

"John Erickson" wrote:


> I did a futher study of the differences in the properties of the message that
> is stuck in the Outbox vs the message after double clicking it and hitting
> send. (Fortunately it doesn't send right away and I could close Outlook 2000
> and use MFCMapi to look at the properties.) The one after hitting send has
> the following differences:

> PR_CLIENT_SUBMIT_TIME exists,
> PR_MESSAGE_DELIVERY_TIME exists,
> PR_MESSAGE_FLAGS has an added bit (MSGFLAG_SUBMIT),
> PR_MESSAGE_SIZE increased by 69,
> PR_SENTMAIL_ENTRYID exists,
> PR_SUBMIT_FLAGS exists,
> PR_ACCESS looses the MAPI_ACCESS_MODIFY bit
> PR_ACCESS_LEVEL changes from 1 to 0,
> PR_LAST_MODIFICATION_TIME changes
> named properties 0x8552, 0x8554, and 0x8583 are added.

> It looks suspiciously like the SubmitMessage call is only saving the message
> and not actually submitting it to be sent. Is there an additional call I need
> to make for Outlook 2000?

> John

> "John Erickson" wrote:
>
> > It's IMO, but I know that all of the MAPI calls I'm making work well (with
> > the exception of this SubmitMessage call), so I don't think it's broken. Even
> > the SubmitMessage call succeeds with S_OK. It just doesn't send the message.
> > When you say it breaks Extended MAPI, what exactly do you mean?
> > "Dmitry Streblechenko" wrote:
> >
> > > Is Outlook 2000 installed in the IMO mode (which breaks Extended MAPI) or
> > > C/W?
> > > > > > > Dmitry Streblechenko (MVP)
> > >

> > >

> > >

> > > -
> > > "John Erickson" <JohnErickson> wrote in message
> > > news:07E3F58F-04EF-4651-9E98-7636DF53A0C1@microsoft.com...
> > > > Hi,
> > > > > > I'm developing an Add-in which works fine for Outlook 2003 and 2007. I'm
> > > > trying to get it to also work for Outlook 2000, but I have one problem. I
> > > > am
> > > > autogenerating a message to be sent for some of the messages that I
> > > > receive.
> > > > In Outlook 2003 & 2007, this generated message gets sent fine, but in
> > > > Outlook
> > > > 2000 it gets stuck in the Outbox and Outlook won't send the message. If I
> > > > double click the message in Outlook's Outbox and then click send, it sends
> > > > the message fine and the message gets deleted as I planned. FWIW I'm doing
> > > > all the message creation work in MAPI in a seperate thread that my add-in
> > > > sends messages to and not in the Outlook object model to avoid the
> > > > restrictions that generate possible virus warning messages. After I build
> > > > the
> > > > message and set all it's properties I am calling
> > > > IMessage::SubmitMessage(0)
> > > > and that seems to be all it takes for 2003 & 2007. I've looked at the
> > > > message
> > > > that gets stuck in the Outbox using MFCMapi to inspect the message
> > > > properties
> > > > and everything looks fine to me. I'm at a loss to explain why it's not
> > > > being
> > > > sent. Have you heard of this before? Is there some property I'm not
> > > > setting
> > > > or a call I'm not making that OL2000 requires?
> > > > > > John
> > > > >
 
D

Dmitry Streblechenko

After calling SubmitMessage, you must immediatley release all references to

that message - it now belongs to the spooler.

Calling SubmitMessage (or any other method) after you have alreday called

SubmitMessage is a bad idea.

Are you sure all the recipients are resolved?

Dmitry Streblechenko (MVP)

-

"John Erickson" <JohnErickson> wrote in message

news:B99A888A-69F0-4876-BF3E-8366D7116D08@microsoft.com...
> I reconfigured it to be C/W instead of IMO and I am seeing the exact same
> behavior. Another thing I have noticed now is that once I have Done 1 or
> more
> SubmitMessage calls, Outlook will not terminate. Instead it hangs and I
> have
> to Stop debugging to get it to shutdown all the way. After discovering
> this I
> reviewed all my COM object references during the SubmitMessage process and
> I
> don't see anyplace where I am not releasing a reference when I should be.
> It's like Outlook itself is hung up in the SubmitMessage process even
> though
> it returned S_OK to me. I just tried adding the FORCE_SUBMIT option to the
> SubmitMessage call and that solved part of my problem. The message now
> gets
> sent. However, I still have the termination problem if I have done 1 or
> more
> SubmitMessage calls.

> John

> "John Erickson" wrote:
>
> > I did a futher study of the differences in the properties of the message
> > that
> > is stuck in the Outbox vs the message after double clicking it and
> > hitting
> > send. (Fortunately it doesn't send right away and I could close Outlook
> > 2000
> > and use MFCMapi to look at the properties.) The one after hitting send
> > has
> > the following differences:
>

>> PR_CLIENT_SUBMIT_TIME exists,
> > PR_MESSAGE_DELIVERY_TIME exists,
> > PR_MESSAGE_FLAGS has an added bit (MSGFLAG_SUBMIT),
> > PR_MESSAGE_SIZE increased by 69,
> > PR_SENTMAIL_ENTRYID exists,
> > PR_SUBMIT_FLAGS exists,
> > PR_ACCESS looses the MAPI_ACCESS_MODIFY bit
> > PR_ACCESS_LEVEL changes from 1 to 0,
> > PR_LAST_MODIFICATION_TIME changes
> > named properties 0x8552, 0x8554, and 0x8583 are added.
>

>> It looks suspiciously like the SubmitMessage call is only saving the
> > message
> > and not actually submitting it to be sent. Is there an additional call I
> > need
> > to make for Outlook 2000?
>

>> John
>

>> "John Erickson" wrote:
> >
> > > It's IMO, but I know that all of the MAPI calls I'm making work well
> > > (with
> > > the exception of this SubmitMessage call), so I don't think it's
> > > broken. Even
> > > the SubmitMessage call succeeds with S_OK. It just doesn't send the
> > > message.
> > > When you say it breaks Extended MAPI, what exactly do you mean?
> >> > "Dmitry Streblechenko" wrote:
> >> > > Is Outlook 2000 installed in the IMO mode (which breaks Extended
> > > > MAPI) or
> > > > C/W?
> > >> > > > > > > Dmitry Streblechenko (MVP)
> > > >

> > > >

> > > >

> > > > -
> > > > "John Erickson" <JohnErickson> wrote in
> > > > message
> > > > news:07E3F58F-04EF-4651-9E98-7636DF53A0C1@microsoft.com...
> > > > > Hi,
> > > >> > > > I'm developing an Add-in which works fine for Outlook 2003 and
> > > > > 2007. I'm
> > > > > trying to get it to also work for Outlook 2000, but I have one
> > > > > problem. I
> > > > > am
> > > > > autogenerating a message to be sent for some of the messages that I
> > > > > receive.
> > > > > In Outlook 2003 & 2007, this generated message gets sent fine, but
> > > > > in
> > > > > Outlook
> > > > > 2000 it gets stuck in the Outbox and Outlook won't send the
> > > > > message. If I
> > > > > double click the message in Outlook's Outbox and then click send,
> > > > > it sends
> > > > > the message fine and the message gets deleted as I planned. FWIW
> > > > > I'm doing
> > > > > all the message creation work in MAPI in a seperate thread that my
> > > > > add-in
> > > > > sends messages to and not in the Outlook object model to avoid the
> > > > > restrictions that generate possible virus warning messages. After I
> > > > > build
> > > > > the
> > > > > message and set all it's properties I am calling
> > > > > IMessage::SubmitMessage(0)
> > > > > and that seems to be all it takes for 2003 & 2007. I've looked at
> > > > > the
> > > > > message
> > > > > that gets stuck in the Outbox using MFCMapi to inspect the message
> > > > > properties
> > > > > and everything looks fine to me. I'm at a loss to explain why it's
> > > > > not
> > > > > being
> > > > > sent. Have you heard of this before? Is there some property I'm not
> > > > > setting
> > > > > or a call I'm not making that OL2000 requires?
> > > >> > > > John
> > >> >> > >
 
J

John Erickson

In the course of converting all my MAPI code to Ansi instead of Unicode the

termination problem went away. I retested on OL2007 and Ansi seems to work

fine there too, so I guess I'll stick with Ansi. I was setting it up to

attempt Unicode calls first and if the calls failed with CdoE_BAD_CHARWIDTH

or CdoE_NOT_FOUND, then I would attempt the call with Ansi. Now I've reversed

that and I attempt Ansi first and things seem to work much better for OL2000.

Thanks for the tips.

John

"Dmitry Streblechenko" wrote:


> After calling SubmitMessage, you must immediatley release all references to
> that message - it now belongs to the spooler.
> Calling SubmitMessage (or any other method) after you have alreday called
> SubmitMessage is a bad idea.
> Are you sure all the recipients are resolved?

> > Dmitry Streblechenko (MVP)
>

>

>

> -
> "John Erickson" <JohnErickson> wrote in message
> news:B99A888A-69F0-4876-BF3E-8366D7116D08@microsoft.com...
> >I reconfigured it to be C/W instead of IMO and I am seeing the exact same
> > behavior. Another thing I have noticed now is that once I have Done 1 or
> > more
> > SubmitMessage calls, Outlook will not terminate. Instead it hangs and I
> > have
> > to Stop debugging to get it to shutdown all the way. After discovering
> > this I
> > reviewed all my COM object references during the SubmitMessage process and
> > I
> > don't see anyplace where I am not releasing a reference when I should be.
> > It's like Outlook itself is hung up in the SubmitMessage process even
> > though
> > it returned S_OK to me. I just tried adding the FORCE_SUBMIT option to the
> > SubmitMessage call and that solved part of my problem. The message now
> > gets
> > sent. However, I still have the termination problem if I have done 1 or
> > more
> > SubmitMessage calls.
> > John
> > "John Erickson" wrote:
> >
> >> I did a futher study of the differences in the properties of the message
> >> that
> >> is stuck in the Outbox vs the message after double clicking it and
> >> hitting
> >> send. (Fortunately it doesn't send right away and I could close Outlook
> >> 2000
> >> and use MFCMapi to look at the properties.) The one after hitting send
> >> has
> >> the following differences:
> >
> >> PR_CLIENT_SUBMIT_TIME exists,
> >> PR_MESSAGE_DELIVERY_TIME exists,
> >> PR_MESSAGE_FLAGS has an added bit (MSGFLAG_SUBMIT),
> >> PR_MESSAGE_SIZE increased by 69,
> >> PR_SENTMAIL_ENTRYID exists,
> >> PR_SUBMIT_FLAGS exists,
> >> PR_ACCESS looses the MAPI_ACCESS_MODIFY bit
> >> PR_ACCESS_LEVEL changes from 1 to 0,
> >> PR_LAST_MODIFICATION_TIME changes
> >> named properties 0x8552, 0x8554, and 0x8583 are added.
> >
> >> It looks suspiciously like the SubmitMessage call is only saving the
> >> message
> >> and not actually submitting it to be sent. Is there an additional call I
> >> need
> >> to make for Outlook 2000?
> >
> >> John
> >
> >> "John Erickson" wrote:
> >
> >> > It's IMO, but I know that all of the MAPI calls I'm making work well
> >> > (with
> >> > the exception of this SubmitMessage call), so I don't think it's
> >> > broken. Even
> >> > the SubmitMessage call succeeds with S_OK. It just doesn't send the
> >> > message.
> >> > When you say it breaks Extended MAPI, what exactly do you mean?
> >> >> > "Dmitry Streblechenko" wrote:
> >> >> > > Is Outlook 2000 installed in the IMO mode (which breaks Extended
> >> > > MAPI) or
> >> > > C/W?
> >> > >> > > > >> > > Dmitry Streblechenko (MVP)
> >> > >

> >> > >

> >> > >

> >> > > -
> >> > > "John Erickson" <JohnErickson> wrote in
> >> > > message
> >> > > news:07E3F58F-04EF-4651-9E98-7636DF53A0C1@microsoft.com...
> >> > > > Hi,
> >> > > >> > > > I'm developing an Add-in which works fine for Outlook 2003 and
> >> > > > 2007. I'm
> >> > > > trying to get it to also work for Outlook 2000, but I have one
> >> > > > problem. I
> >> > > > am
> >> > > > autogenerating a message to be sent for some of the messages that I
> >> > > > receive.
> >> > > > In Outlook 2003 & 2007, this generated message gets sent fine, but
> >> > > > in
> >> > > > Outlook
> >> > > > 2000 it gets stuck in the Outbox and Outlook won't send the
> >> > > > message. If I
> >> > > > double click the message in Outlook's Outbox and then click send,
> >> > > > it sends
> >> > > > the message fine and the message gets deleted as I planned. FWIW
> >> > > > I'm doing
> >> > > > all the message creation work in MAPI in a seperate thread that my
> >> > > > add-in
> >> > > > sends messages to and not in the Outlook object model to avoid the
> >> > > > restrictions that generate possible virus warning messages. After I
> >> > > > build
> >> > > > the
> >> > > > message and set all it's properties I am calling
> >> > > > IMessage::SubmitMessage(0)
> >> > > > and that seems to be all it takes for 2003 & 2007. I've looked at
> >> > > > the
> >> > > > message
> >> > > > that gets stuck in the Outbox using MFCMapi to inspect the message
> >> > > > properties
> >> > > > and everything looks fine to me. I'm at a loss to explain why it's
> >> > > > not
> >> > > > being
> >> > > > sent. Have you heard of this before? Is there some property I'm not
> >> > > > setting
> >> > > > or a call I'm not making that OL2000 requires?
> >> > > >> > > > John
> >> > >> > >> > >

>
 
Status
Not open for further replies.
< To use Marshal.ReleaseComObject or not to use | Pointing to the different folder >
Similar threads
Thread starter Title Forum Replies Date
M which Outlook recommended to buy for moving Outlook 2000 versions Contact Data Using Outlook 2
B Outlook 2000 Rule to Move txt msg Not Working if size >24KB Using Outlook 3
D Outlook 2000 slow Using Outlook 2
T How can I eradicate Outlook 2000+ Using Outlook 6
T passwords in outlook 2000(in XP Virtual PC mode) under Windows 7 Professional Using Outlook 6
P Printing problems with MS Outlook 2000 Using Outlook 1
B Restoring Outlook 2000 messages Using Outlook 4
B strange change in Outlook 2000 forms Outlook VBA and Custom Forms 1
J Outlook 2000 "My Shortcuts" question Outlook VBA and Custom Forms 2
S Choosing different reply template in Outlook 2000 Outlook VBA and Custom Forms 1
R IConverterSession::MAPIToMIMEStm error in outlook 2000 Outlook VBA and Custom Forms 3
R IConverterSession::MIMEToMAPI error in outlook 2000 Outlook VBA and Custom Forms 1
M Outlook Macro to save as Email with a file name format : Date_Timestamp_Sender initial_Email subject Outlook VBA and Custom Forms 0
G LinkedIn tab missing in Outlook 365 (but working in OWA) Using Outlook 0
J Outlook forgets "not junk" marking Using Outlook 0
KurtLass Opening Graphics Attachments in Outlook 2021 Using Outlook 0
P now on office 365 but getting error messages about missing Outlook 2013 cache folders Using Outlook 2
B Outlook config download Outlook VBA and Custom Forms 1
M Short term workaround for when Outlook searching stopped functioning Using Outlook 0
D Outlook 2016 Creating an outlook Macro to select and approve Outlook VBA and Custom Forms 0
L Fetch, edit and forward an email with VBA outlook Outlook VBA and Custom Forms 2
BartH VBA no longer working in Outlook Outlook VBA and Custom Forms 1
L Synch Outlook 365 calendar with iPhone Using Outlook 0
W Can vba(for outlook) do these 2 things or not? Outlook VBA and Custom Forms 2
S Outlook 2016 and Acrobat PDFMaker Office COM Addin Using Outlook 0
M "Attachment Detacher for Outlook" add in, does it update the server copy of the email? Using Outlook 1
M Outlook 365 Rename Outlook Priority Using Outlook 3
R Outlook 2019 accesses POP3 but says its offline (because of IMAP servers?) Using Outlook 0
R Outlook Working off line Using Outlook 0
D Outlook 365 Custom forms field limit? Outlook VBA and Custom Forms 4
W Outlook 2016 MSI - Possible to make work with O365 modern Auth & Win7? Using Outlook 4
T Outlook roaming signatures Using Outlook 4
S Adding a recipient's column to Sent folder in Outlook 2010 Outlook VBA and Custom Forms 1
J Outlook search bar in Office 2021 Professional Using Outlook 1
J PSA: How to create custom keyboard shortcut for "Paste Unformatted Text" in Outlook on Windows Outlook VBA and Custom Forms 1
C How to fix outlook continuing to prompt fo an Exchange password Using Outlook 0
C Outlook doesn't feel reliable, anymore Using Outlook 5
J Outlook 2016 Trying to get Outlook 2016 to work with Office 365 Using Outlook 0
C Outlook 365 Copy/Save Emails in Folder Outside Outlook to Show Date Sender Recipient Subject in Header Using Outlook 0
U Outlook not responding when trying to print Emails Using Outlook 5
O How to sync (one way) contacts between two Outlook (exchange) accounts? Using Outlook 0
S Sync Outlook (2021) tasks with Microsoft To Do Using Outlook 1
L Duplicate calendar entries in Outlook 365 Using Outlook 4
V Outlook 2021 Can anyone explain why my Outlook views keep changing?! Using Outlook 2
AlphonseG Outlook 365 Outlook Crashes on setting SaveSentMessageFolder Outlook VBA and Custom Forms 5
S Outlook 2021 How to customize colors Outlook 2021 & Office 2021 on PC Using Outlook 2
D Outlook 2007 Recovering E-Mails Using Outlook 0
G Stop Outlook 365 adding meetings to calendar Using Outlook 2
HarvMan Using Emojis in Outlook 365 Using Outlook 3
T Outlook 2019 Not Using Auto Compete After Deletion of 365 Using Outlook 1

Similar threads

Top