Emails stay in Outbox forever once addin is loaded

  • Thread starter Jason
  • Start date Views 1,466
Status
Not open for further replies.
J

Jason

The problem only occurs when user click the Outbox folder, then send an

Email. No problem if the folder is not selected.

The problem happens on Outlook 2007 and 2003. Not every computer will have

the problem.

The problem is caused by the interception of explorer.SelectionChange, whose

sole purpose is to catches the EntryIDs of the appointments selected for

deletion.

In Outlook 2007, the problem can be avoided by replacing

explorer.SelectionChange with BeforeItemMove event.

What is the feasible solution for 2003?
 
T

Tom

Hi Jason,

You are not alone. I have seen this issue multiple times with Outlook 2003.

I believe this is an Outlook problem of some sort. I think it is a race

condition and has something to do with the view table.

In fact with some of our add-ins that are message intensive I have disabled

(low level hook) from selecting the outbox during message processing.

Tom -

"Jason" <a@a.com> wrote in message

news:uPxrh24tJHA.2376@TK2MSFTNGP04.phx.gbl...
> The problem only occurs when user click the Outbox folder, then send an
> Email. No problem if the folder is not selected.

> The problem happens on Outlook 2007 and 2003. Not every computer will have
> the problem.

> The problem is caused by the interception of explorer.SelectionChange,
> whose sole purpose is to catches the EntryIDs of the appointments selected
> for deletion.

> In Outlook 2007, the problem can be avoided by replacing
> explorer.SelectionChange with BeforeItemMove event.

> What is the feasible solution for 2003?

>
 
J

Jason

Thanks Tom. I agre that could be the last resort. Right now we just leave

the option open. Our customers pay for the service. Internal users are much

easier to deal with.

"Tom" <tom@gigasoftdevelopment.com> wrote in message

news:eJPH9vFuJHA.4648@TK2MSFTNGP06.phx.gbl...
> Hi Jason,

> You are not alone. I have seen this issue multiple times with Outlook
> 2003. I believe this is an Outlook problem of some sort. I think it is a
> race condition and has something to do with the view table.

> In fact with some of our add-ins that are message intensive I have
> disabled (low level hook) from selecting the outbox during message
> processing.

> Tom -

> "Jason" <a@a.com> wrote in message
> news:uPxrh24tJHA.2376@TK2MSFTNGP04.phx.gbl...
> > The problem only occurs when user click the Outbox folder, then send an
> > Email. No problem if the folder is not selected.
>

>> The problem happens on Outlook 2007 and 2003. Not every computer will
> > have the problem.
>

>> The problem is caused by the interception of explorer.SelectionChange,
> > whose sole purpose is to catches the EntryIDs of the appointments
> > selected for deletion.
>

>> In Outlook 2007, the problem can be avoided by replacing
> > explorer.SelectionChange with BeforeItemMove event.
>

>> What is the feasible solution for 2003?
>

>>


>
 
J

Jason

The problem of Email won't go out appears in one VM for Outlook 2007. No

problem in dev machine since we replaced the ActiveExplorer.SelectionChange

with BeforeItemMove event. Now the suspect is

Application.Inspectors.NewInspector event. What we really need is the

calendar item open event (or better, the Read event to handle in place

input). Is there any way to catch the calendar item Open/Read event without

intercepting the NewInspector event? Please advise how to.

"Jason" <a@a.com> wrote in message

news:uPxrh24tJHA.2376@TK2MSFTNGP04.phx.gbl...
> The problem only occurs when user click the Outbox folder, then send an
> Email. No problem if the folder is not selected.

> The problem happens on Outlook 2007 and 2003. Not every computer will have
> the problem.

> The problem is caused by the interception of explorer.SelectionChange,
> whose sole purpose is to catches the EntryIDs of the appointments selected
> for deletion.

> In Outlook 2007, the problem can be avoided by replacing
> explorer.SelectionChange with BeforeItemMove event.

> What is the feasible solution for 2003?

>
 
Status
Not open for further replies.
Top