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
 
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
 
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


>
 
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

> >
 
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
> > > > >
 
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
> > >> >> > >
 
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.
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
Z Hotmail account deleted from outlook and issue with account not exist Using Outlook 0
J 'Name on the security certificate is invalid or...' - Outlook on desktop talking to hotmail.com account Using Outlook.com accounts in Outlook 4
J Outlook, Word, Access crash unless run in Admin mode - time dependent it seems Using Outlook 10
T Why do Outlook Desktop 2021 tasks from my wife's email show up in my task pane? Using Outlook 2
B Delete Read Receipts in Your Outlook Outlook VBA and Custom Forms 0
M Outlook changes the "Modified" field when moving/copying a Contact. Using Outlook 0
macdotcom Outlook 365 Outlook folder export to PST archival tool - close, but need a nudge Outlook VBA and Custom Forms 2
M Outlook 2016 still feature updating Using Outlook 0
e_a_g_l_e_p_i Question about Outlook 2021 and Gmail Using Outlook 9
J Outlook VBA to send from Non-default Account & Data Files Outlook VBA and Custom Forms 3
P Limited Support for 3rd Party Mail in new Outlook? Using Outlook 1
O Any 3rd party tool that sync (mirror) from Outlook Calendar to Google Calendar? Using Outlook 5
T Outlook is categorizing emails incorrectly Using Outlook 1
R Legacy Outlook on Mac Email Cache Using Outlook 0
A Outlook can't remember outlook.com, Exchange password. Using Outlook 6
S Related messages show in main Outlook window vice new Advanced Find windows Using Outlook 1
H Force Outlook 2019 with GMail 2-Step to Require Login? Using Outlook 0
G Retaining Tabs in outlook body Using Outlook 2
V Setting up Outlook 2021 on new computer Using Outlook 2
G Add Map It button to Custom Contacts Form in Outlook Outlook VBA and Custom Forms 1
X Custom icon (not from Office 365) for a macro in Outlook Outlook VBA and Custom Forms 1
Victor_50 Problem - Google Workspace will stop "unsafe" access to Outlook end 2024 Using Outlook 3
C New pc, new outlook, is it possible to import auto-complete emailaddress Using Outlook 4
T Outlook 365 won't take new working password Using Outlook 0
S Create Outlook Task from Template and append Body with Email Body Outlook VBA and Custom Forms 4
P Can't add custom field to custom Outlook form, it always adds to the Folder instead Outlook VBA and Custom Forms 2
B Sync Outlook Public Folders to Contacts Using Outlook 2
D Delete Outlook emails from MS server Using Outlook 12
B Outlook tasks and PDF Using Outlook 4
D Outlook 2019 is no longer asking for password ... Using Outlook 5
Kika Melo How to mark as Junk any message not from Contacts (in Outlook.com) Using Outlook 3
L Outlook attachments from OneDrive as links Using Outlook 0
G Outlook 365 My iCloud Outlook doesn’t work after reinstalling Microsoft365 on Windows 10 PC – now I get error message on contacts and calendar Using Outlook 1
T How to Export & Import GMAIL Contacts into Outlook 2021 ? Using Outlook 4
M Synchronization and backup of Outlook from local to server. Using Outlook 12
T How to get an EVENT COLOR option in Outlook 2021 ? Using Outlook 0
K How can I delete an e-mail from Outlook Using Outlook 1
V Outlook Error The Attempted operation Failed. An Object Could Not be found Outlook VBA and Custom Forms 0

Similar threads

Back
Top