Send email immediate when Outlook 2003 is closed?

[Russ Valentine [MVP-Outlook]]

Not sure how or why I would ever have two compose windows open, nor how that
is relevant since no none else would either.
Interesting observation, nonetheless.
--
Russ Valentine
[MVP-Outlook]

We're hardly calling it a feature. We are, however, saying that this
behavior is by design and explaining the historical reasons why this
design was implemented.

I'm just trying to understand.... Your explanations have been that *when a
Compose Window is started, but Outlook itself is not started, that
messages will stay in the Outbox when sent.* OK.... I can see rationales
for that. But, how come when you have TWO compose windows open and hit
Send on one of them, the message is indeed Sent?

No, either your "by design" explanation is actually a bug, or the
"two-compose-windows" behavior is a bug. Knowing what I know about Outlook
loading as an ActiveX Server, and how it disposes of itself when it goes
out of scope of COM calls, I'd say the former is THE BUG (not by design).

--
-C. Moya
www.cmoya.com

We're hardly calling it a feature. We are, however, saying that this
behavior is by design and explaining the historical reasons why this
design was implemented.
Personally, I think this behavior should have been changed long ago to
reflect modern connectivity realities. The list of things I think should
have been changed long ago in Outlook is so long it would bring this news
server to its knees. But what I think is irrelevant. We must deal with
what is. We have no influence over what should be.
You seem to keep beating up on the wrong people.
This particular issue is simple. Leaving Outlook running is what most
people do anyway. And that was Microsoft's assumption.
--
Russ Valentine
[MVP-Outlook]

The examples in your answer examples are moot (or should be) if the user
has set "Send Messages Immediately" in Outlook Options. Nor does the
answer explain why the message is sent immediately when you have two
compose windows open. There's a big lapse of logic here.

You guys are trying to say that this is some "feature" or by design.
That just doesn't make sense. If that were true, having two compose
windows open should have no bearing on whether the message is sent or
not.... Outlook still IS NOT "open." But, it does send the message
immediately on *one* of the compose windows.


--
-C. Moya
www.cmoya.com

Hello directjj,


The assumption is that if the user has deliberately closed his
or her email program, that user does not want to send mail
at that time. The message is stored until the next time the
user wants to send mail.
I can't agree with that. That assumption would make sense back when
everyone had a dialup connection, and was paying by the minute for
connect time. Don't want to dial up to send one email message.

These days, many HOME users including myself not to mention BUSINESS
users have a broadband connection so they are online any time their
computer is running.

And many home users (and even a dwindling number of business users)
still have dial-up.

Making Microsoft Office is like ordering pizza for 400 million people.
They can't please everybody all the time.

Why would I NOT want the message to be sent right away?

Maybe you're a mobile user logged into a wireless connection that isn't
on your ISP's network and so the ISP is going to bounce the message if
you try to send it now. So you'd rather wait for it to send until you
reconnect to your ISP's home network. That's one possible reason.

Maybe you're trying to leave for the day and the message to be sent is
huge. You don't want to wait for it to spool before you can shut your
machine down so you'd just assume let it stay in the Outbox for now and
send when you have more time.

Maybe you're one of those many still on dial-up. There are lots of
reasons.

The solution is fairly simple -- open Outlook.


-Ben-
Ben M. Schorr, MVP
Roland Schorr & Tower
http://www.rolandschorr.com
Microsoft OneNote FAQ: http://www.factplace.com/onenote.html

 

[CMM]

Not sure how or why I would ever have two compose windows open, nor how
that is relevant since no none else would either.

How: click a mailto: link in one place, and another somewhere else or even
the same one.
Why: Lots of reasons. Reporting two bugs. Answering two related questions or
even unrelated ones. Or simply just because you feel like it. It is a
windowing and multitasking OS after all.

Interesting observation, nonetheless.

I wouldn't say the observation is interesting. The behavior in question
is... considering you guys claim "Outlook is not open" and its "mail
transports are not loaded."

--
-C. Moya
www.cmoya.com

Not sure how or why I would ever have two compose windows open, nor how
that is relevant since no none else would either.
Interesting observation, nonetheless.
--
Russ Valentine
[MVP-Outlook]

We're hardly calling it a feature. We are, however, saying that this
behavior is by design and explaining the historical reasons why this
design was implemented.

I'm just trying to understand.... Your explanations have been that *when
a Compose Window is started, but Outlook itself is not started, that
messages will stay in the Outbox when sent.* OK.... I can see rationales
for that. But, how come when you have TWO compose windows open and hit
Send on one of them, the message is indeed Sent?

No, either your "by design" explanation is actually a bug, or the
"two-compose-windows" behavior is a bug. Knowing what I know about
Outlook loading as an ActiveX Server, and how it disposes of itself when
it goes out of scope of COM calls, I'd say the former is THE BUG (not by
design).

--
-C. Moya
www.cmoya.com

We're hardly calling it a feature. We are, however, saying that this
behavior is by design and explaining the historical reasons why this
design was implemented.
Personally, I think this behavior should have been changed long ago to
reflect modern connectivity realities. The list of things I think should
have been changed long ago in Outlook is so long it would bring this
news server to its knees. But what I think is irrelevant. We must deal
with what is. We have no influence over what should be.
You seem to keep beating up on the wrong people.
This particular issue is simple. Leaving Outlook running is what most
people do anyway. And that was Microsoft's assumption.
--
Russ Valentine
[MVP-Outlook]
The examples in your answer examples are moot (or should be) if the
user has set "Send Messages Immediately" in Outlook Options. Nor does
the answer explain why the message is sent immediately when you have
two compose windows open. There's a big lapse of logic here.

You guys are trying to say that this is some "feature" or by design.
That just doesn't make sense. If that were true, having two compose
windows open should have no bearing on whether the message is sent or
not.... Outlook still IS NOT "open." But, it does send the message
immediately on *one* of the compose windows.


--
-C. Moya
www.cmoya.com

Hello directjj,


The assumption is that if the user has deliberately closed his
or her email program, that user does not want to send mail
at that time. The message is stored until the next time the
user wants to send mail.
I can't agree with that. That assumption would make sense back when
everyone had a dialup connection, and was paying by the minute for
connect time. Don't want to dial up to send one email message.

These days, many HOME users including myself not to mention BUSINESS
users have a broadband connection so they are online any time their
computer is running.

And many home users (and even a dwindling number of business users)
still have dial-up.

Making Microsoft Office is like ordering pizza for 400 million people.
They can't please everybody all the time.

Why would I NOT want the message to be sent right away?

Maybe you're a mobile user logged into a wireless connection that
isn't on your ISP's network and so the ISP is going to bounce the
message if you try to send it now. So you'd rather wait for it to
send until you reconnect to your ISP's home network. That's one
possible reason.

Maybe you're trying to leave for the day and the message to be sent is
huge. You don't want to wait for it to spool before you can shut your
machine down so you'd just assume let it stay in the Outbox for now
and send when you have more time.

Maybe you're one of those many still on dial-up. There are lots of
reasons.

The solution is fairly simple -- open Outlook.


-Ben-
Ben M. Schorr, MVP
Roland Schorr & Tower
http://www.rolandschorr.com
Microsoft OneNote FAQ: http://www.factplace.com/onenote.html

 

[Russ Valentine [MVP-Outlook]]

OK you win.
I'm not an Outlook developer.
I've never claimed to be one.
Again, you are beating up on the wrong people.
But thanks. It's been fun.
--
Russ Valentine
[MVP-Outlook]

Not sure how or why I would ever have two compose windows open, nor how
that is relevant since no none else would either.

How: click a mailto: link in one place, and another somewhere else or even
the same one.
Why: Lots of reasons. Reporting two bugs. Answering two related questions
or even unrelated ones. Or simply just because you feel like it. It is a
windowing and multitasking OS after all.

Interesting observation, nonetheless.

I wouldn't say the observation is interesting. The behavior in question
is... considering you guys claim "Outlook is not open" and its "mail
transports are not loaded."

--
-C. Moya
www.cmoya.com

Not sure how or why I would ever have two compose windows open, nor how
that is relevant since no none else would either.
Interesting observation, nonetheless.
--
Russ Valentine
[MVP-Outlook]

We're hardly calling it a feature. We are, however, saying that this
behavior is by design and explaining the historical reasons why this
design was implemented.

I'm just trying to understand.... Your explanations have been that *when
a Compose Window is started, but Outlook itself is not started, that
messages will stay in the Outbox when sent.* OK.... I can see rationales
for that. But, how come when you have TWO compose windows open and hit
Send on one of them, the message is indeed Sent?

No, either your "by design" explanation is actually a bug, or the
"two-compose-windows" behavior is a bug. Knowing what I know about
Outlook loading as an ActiveX Server, and how it disposes of itself when
it goes out of scope of COM calls, I'd say the former is THE BUG (not by
design).

--
-C. Moya
www.cmoya.com
We're hardly calling it a feature. We are, however, saying that this
behavior is by design and explaining the historical reasons why this
design was implemented.
Personally, I think this behavior should have been changed long ago to
reflect modern connectivity realities. The list of things I think
should have been changed long ago in Outlook is so long it would bring
this news server to its knees. But what I think is irrelevant. We must
deal with what is. We have no influence over what should be.
You seem to keep beating up on the wrong people.
This particular issue is simple. Leaving Outlook running is what most
people do anyway. And that was Microsoft's assumption.
--
Russ Valentine
[MVP-Outlook]
The examples in your answer examples are moot (or should be) if the
user has set "Send Messages Immediately" in Outlook Options. Nor does
the answer explain why the message is sent immediately when you have
two compose windows open. There's a big lapse of logic here.

You guys are trying to say that this is some "feature" or by design.
That just doesn't make sense. If that were true, having two compose
windows open should have no bearing on whether the message is sent or
not.... Outlook still IS NOT "open." But, it does send the message
immediately on *one* of the compose windows.


--
-C. Moya
www.cmoya.com

Hello directjj,


The assumption is that if the user has deliberately closed his
or her email program, that user does not want to send mail
at that time. The message is stored until the next time the
user wants to send mail.
I can't agree with that. That assumption would make sense back when
everyone had a dialup connection, and was paying by the minute for
connect time. Don't want to dial up to send one email message.

These days, many HOME users including myself not to mention BUSINESS
users have a broadband connection so they are online any time their
computer is running.

And many home users (and even a dwindling number of business users)
still have dial-up.

Making Microsoft Office is like ordering pizza for 400 million
people. They can't please everybody all the time.

Why would I NOT want the message to be sent right away?

Maybe you're a mobile user logged into a wireless connection that
isn't on your ISP's network and so the ISP is going to bounce the
message if you try to send it now. So you'd rather wait for it to
send until you reconnect to your ISP's home network. That's one
possible reason.

Maybe you're trying to leave for the day and the message to be sent
is huge. You don't want to wait for it to spool before you can shut
your machine down so you'd just assume let it stay in the Outbox for
now and send when you have more time.

Maybe you're one of those many still on dial-up. There are lots of
reasons.

The solution is fairly simple -- open Outlook.


-Ben-
Ben M. Schorr, MVP
Roland Schorr & Tower
http://www.rolandschorr.com
Microsoft OneNote FAQ: http://www.factplace.com/onenote.html

 

[CMM]

Not trying to beat up. Just trying to correct false information.

 

[Russ Valentine [MVP-Outlook]]

To everyone's great benefit, I'm sure.
The fact remains: For the original poster to do what he wants, he must keep
Outlook running.

 

[CMM]

The fact remains: For the original poster to do what he wants, he must

keep Outlook running.

Or hit CTRL+N in the compose window.

 

[Russ Valentine [MVP-Outlook]]

Right. So it looks like rather than launching with transports disabled,
Outlook is simply launched with polling disabled.
With CTRL+N, does Outlook remain open after the send?

 

[CMM]

Right. So it looks like rather than launching with transports disabled,

Outlook is simply launched with polling disabled.
With CTRL+N, does Outlook remain open after the send?

Polling isn't disabled either. If you have 10 compose windows open and hit
send on all of them, 9 of them get sent.... 1 does not (come on that can't
be by-design.... if it is, then it's bad-design and bad coding). What
happens is that when the very last compose window closes Outlook (running
hidden in the bckgrnd) abruptly terminates without giving its spooler thread
a chance to send out the message.

--
-C. Moya
www.cmoya.com

Right. So it looks like rather than launching with transports disabled,
Outlook is simply launched with polling disabled.
With CTRL+N, does Outlook remain open after the send?

 

[Brian Tillman]

I'm just trying to understand.... Your explanations have been that
*when a Compose Window is started, but Outlook itself is not started,
that messages will stay in the Outbox when sent.* OK.... I can see
rationales for that. But, how come when you have TWO compose windows
open and hit Send on one of them, the message is indeed Sent?

I'd say because with the second compose window open, the Outlook engine
remains running and so the sending can be performed. If you were to close
the second window fast enough after clicking Send on the first, I suspect
you'd get the same behavior as you would were you to not have opened the
second compose in the first place.

No, either your "by design" explanation is actually a bug, or the
"two-compose-windows" behavior is a bug. Knowing what I know about
Outlook loading as an ActiveX Server, and how it disposes of itself
when it goes out of scope of COM calls, I'd say the former is THE BUG
(not by design).

It's reasonable to think that if other SMTP clients can do it (Outlook
Express, for example), then so could Outlook. I can't believe it would be a
huge design change. Nonetheless, it's what we have to live with until it
changes, if ever.

 

[Russ Valentine [MVP-Outlook]]

But polling _is_ disabled when you open Outlook only with a mail to link.
That is by design, not bad coding. The intention is to create and save the
message, close Outlook automatically, and only send the message when the
user intentionally opens Outlook. That's one of many holdover features from
the dial up days.
All CTRL+N does is intentionally launch Outlook with polling enabled, the
same as launching Outlook any other way. My guess is that the user must then
intentionally close Outlook again.
I won't argue that this is an outdated feature that could be updated. But I
don't see how it qualifies as a bug or bad coding.
This is hardly even an issue any more now that the days of dial up are over
since most users just keep Outlook running. If they don't, Microsoft assumes
they prefer leave Outlook closed until they are ready to send messages.
--
Russ Valentine
[MVP-Outlook]

Right. So it looks like rather than launching with transports disabled,
Outlook is simply launched with polling disabled.
With CTRL+N, does Outlook remain open after the send?

Polling isn't disabled either. If you have 10 compose windows open and hit
send on all of them, 9 of them get sent.... 1 does not (come on that can't
be by-design.... if it is, then it's bad-design and bad coding). What
happens is that when the very last compose window closes Outlook (running
hidden in the bckgrnd) abruptly terminates without giving its spooler
thread a chance to send out the message.

--
-C. Moya
www.cmoya.com

Right. So it looks like rather than launching with transports disabled,
Outlook is simply launched with polling disabled.
With CTRL+N, does Outlook remain open after the send?
--
Russ Valentine
[MVP-Outlook]

The fact remains: For the original poster to do what he wants, he must
keep Outlook running.

Or hit CTRL+N in the compose window.

 

[CMM]

But polling _is_ disabled when you open Outlook only with a mail to link.

That is by design, not bad coding.

Polling disabled... No it's not. Hit another mailto: link creating another
compose window so that you now have two. mailto: isn't the culprit. See
Brian Tillman's message later in this thread. He understands what's going
on.

<snip> That's one of many holdover features from the dial up days. All
CTRL+N does is intentionally launch Outlook with polling enabled, the
same as launching Outlook any other way.

Nope. Wrong. It's not just CTRL+N as I already stated above.

My guess is that the user must then intentionally close Outlook again.

Not so. Wrong again.

--
-C. Moya
www.cmoya.com

But polling _is_ disabled when you open Outlook only with a mail to link.
That is by design, not bad coding. The intention is to create and save the
message, close Outlook automatically, and only send the message when the
user intentionally opens Outlook. That's one of many holdover features
from the dial up days.
All CTRL+N does is intentionally launch Outlook with polling enabled, the
same as launching Outlook any other way. My guess is that the user must
then intentionally close Outlook again.
I won't argue that this is an outdated feature that could be updated. But
I don't see how it qualifies as a bug or bad coding.
This is hardly even an issue any more now that the days of dial up are
over since most users just keep Outlook running. If they don't, Microsoft
assumes they prefer leave Outlook closed until they are ready to send
messages.
--
Russ Valentine
[MVP-Outlook]

Right. So it looks like rather than launching with transports disabled,
Outlook is simply launched with polling disabled.
With CTRL+N, does Outlook remain open after the send?

Polling isn't disabled either. If you have 10 compose windows open and
hit send on all of them, 9 of them get sent.... 1 does not (come on that
can't be by-design.... if it is, then it's bad-design and bad coding).
What happens is that when the very last compose window closes Outlook
(running hidden in the bckgrnd) abruptly terminates without giving its
spooler thread a chance to send out the message.

--
-C. Moya
www.cmoya.com

Right. So it looks like rather than launching with transports disabled,
Outlook is simply launched with polling disabled.
With CTRL+N, does Outlook remain open after the send?
--
Russ Valentine
[MVP-Outlook]
The fact remains: For the original poster to do what he wants, he must
keep Outlook running.

Or hit CTRL+N in the compose window.

 

[Russ Valentine [MVP-Outlook]]

Thanks for nothing
So what is your explanation for why the first mailto link fails to send
(other than "bad coding")?
I do agree with Brian (which is what I said all along). This is the behavior
that is by design and that we have to live with until that design changes.
Informing users of that reality seems a bit more useful than bashing the
developers and insulting those who must explain what that reality is.
--
Russ Valentine
[MVP-Outlook]

But polling _is_ disabled when you open Outlook only with a mail to link.
That is by design, not bad coding.

Polling disabled... No it's not. Hit another mailto: link creating another
compose window so that you now have two. mailto: isn't the culprit. See
Brian Tillman's message later in this thread. He understands what's going
on.

<snip> That's one of many holdover features from the dial up days. All
CTRL+N does is intentionally launch Outlook with polling enabled, the
same as launching Outlook any other way.

Nope. Wrong. It's not just CTRL+N as I already stated above.

My guess is that the user must then intentionally close Outlook again.

Not so. Wrong again.

--
-C. Moya
www.cmoya.com

But polling _is_ disabled when you open Outlook only with a mail to link.
That is by design, not bad coding. The intention is to create and save
the message, close Outlook automatically, and only send the message when
the user intentionally opens Outlook. That's one of many holdover
features from the dial up days.
All CTRL+N does is intentionally launch Outlook with polling enabled, the
same as launching Outlook any other way. My guess is that the user must
then intentionally close Outlook again.
I won't argue that this is an outdated feature that could be updated. But
I don't see how it qualifies as a bug or bad coding.
This is hardly even an issue any more now that the days of dial up are
over since most users just keep Outlook running. If they don't, Microsoft
assumes they prefer leave Outlook closed until they are ready to send
messages.
--
Russ Valentine
[MVP-Outlook]

Right. So it looks like rather than launching with transports disabled,
Outlook is simply launched with polling disabled.
With CTRL+N, does Outlook remain open after the send?

Polling isn't disabled either. If you have 10 compose windows open and
hit send on all of them, 9 of them get sent.... 1 does not (come on that
can't be by-design.... if it is, then it's bad-design and bad coding).
What happens is that when the very last compose window closes Outlook
(running hidden in the bckgrnd) abruptly terminates without giving its
spooler thread a chance to send out the message.

--
-C. Moya
www.cmoya.com
Right. So it looks like rather than launching with transports disabled,
Outlook is simply launched with polling disabled.
With CTRL+N, does Outlook remain open after the send?
--
Russ Valentine
[MVP-Outlook]
The fact remains: For the original poster to do what he wants, he
must keep Outlook running.

Or hit CTRL+N in the compose window.

 

[CMM]

Thanks for nothing > So what is your explanation for why the first
mailto link fails to send (other than "bad coding")?
I do agree with Brian (which is what I said all along). This is the
behavior that is by design and that we have to live with until that design
changes.
Informing users of that reality seems a bit more useful than bashing the
developers and insulting those who must explain what that reality is.

I already offered an explanation... and so did Brian. Outlook terminates
when the last window closes without allowing its spooler thread to do its
work. It's not the first mailto: that fails to send... it's the very last
one you click send on. I think we have a fundamental misunderstanding here.

And, I don't think Brian said this was "By Design." As a developer "by
design" means done on purpose on for a reason (rather than a side-effect of
coding logic... no matter how longstanding and unaddressed). There is no
possible logical reason for a scenerio where you have might have FIVE
compose windows and only FOUR actually send a message when the user hits
Send on them.

I understand your contentions about mailto:.... and they seem to make sense.
But the logic does not play out in real usage.

 

[Russ Valentine [MVP-Outlook]]

But most users terminate this window by clicking on Send...at which point
Outlook closes without sending.
The explanation I've been given is that a New Message window launched from a
mailto link while Outlook is closed is designed to do exactly that: create
and save a message, but not send that message until the user expressly opens
Outlook.
Isn't that exactly what happens? That behavior is intentional. The method by
which it occurs may be sloppy and easily overridden, but that is the way
Outlook was intended to function.
I suspect we can both agree that it is the words "logic" and "Outlook"
rarely belong in the same sentence.

 

[CMM]

I supposse you may be right... and I see your point.
Though I'd add that developers can provide any technobabble explanation for
a bug thus turning it into "yeah we meant to do that" feature. I know I've
done it. ;-)

In any case, even if what you say is true, there is STILL a bug here. The
bug being that additional open mailto: windows should *not* send the message
(using your reasoning).

So, I remain dubious. I posit that you've been hoodwinked. To quote an old
rap song... Don't believe the hype.


--
-C. Moya
www.cmoya.com

But most users terminate this window by clicking on Send...at which point
Outlook closes without sending.
The explanation I've been given is that a New Message window launched from
a mailto link while Outlook is closed is designed to do exactly that:
create and save a message, but not send that message until the user
expressly opens Outlook.
Isn't that exactly what happens? That behavior is intentional. The method
by which it occurs may be sloppy and easily overridden, but that is the
way Outlook was intended to function.
I suspect we can both agree that it is the words "logic" and "Outlook"
rarely belong in the same sentence.

 

[CMM]

I'd say because with the second compose window open, the Outlook engine
remains running and so the sending can be performed. If you were to close
the second window fast enough after clicking Send on the first, I suspect
you'd get the same behavior as you would were you to not have opened the
second compose in the first place.

Quite right.

It's reasonable to think that if other SMTP clients can do it (Outlook
Express, for example), then so could Outlook. I can't believe it would be
a huge design change. Nonetheless, it's what we have to live with until
it changes, if ever.

I agree.
And would stress "If ever." We're more likely to see the Preview Pane docked
on top and called a "new feature" and hyped as such. The "Reading Pane" in
2003 (although I like it!) was just way too funny too me to see all the
marketing hype.... like it was some programming breakthrough. I just had to
laugh.

 

[Russ Valentine [MVP-Outlook]]

Hoodwinked? I doubt that. You've read these groups. You will not find a more
severe critic of Outlook than I. Most Outlook developers develop nausea at
the mention of my name. The fact that Microsoft retains this crusty
curmudgeon cardiologist on its MVP roster is a tribute to the integrity of
both Microsoft and its MVP program.

I've met most of the Outlook developers over the last 10 years. They are a
very talented and very dedicated lot. They are keenly aware of the
sacrifices they must make to create a product that will fit the needs of
Exchange, POP/SMTP, IMAP, HTTP, and Fax users (you can now scratch the
latter). Ben said it best. Make a pizza that will please 400 million people.
Once you do, post your recipe.

 

[Diane Poremsky [MVP]]

Note that #1 doesn't work for all versions and account type, so it's
definitely "YMMV" and it's not foolproof. I would never trust it for an
important message that needed to be sent ASAP.

#2 means outlook is running hidden - might as well just open it and be done
with it.

1) Workaround for this retarded bug: Start another Compose window before
hitting send by hitting CTRL+N. This will keep Outlook open long enough to
send the message... works for me in Ol2003.

(And you're the MVP?).

2) Use a tool to keep Outlook open in the background
(http://www.cflashsoft.com/ see Outlook Sidebar or Outlook Loader.... both
free utilities).

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/





(posted using Entourage)

 

[Diane Poremsky [MVP]]

Depending on how you open the first window, you may not be able to get a
second one until the first is closed. Hint: File, Send menus.

How: click a mailto: link in one place, and another somewhere else or even
the same one.
Why: Lots of reasons. Reporting two bugs. Answering two related questions or
even unrelated ones. Or simply just because you feel like it. It is a
windowing and multitasking OS after all.


I wouldn't say the observation is interesting. The behavior in question
is... considering you guys claim "Outlook is not open" and its "mail
transports are not loaded."

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/





(posted using Entourage)

 

[Diane Poremsky [MVP]]

Other clients don't support ExMAPI. When outlook no longer uses exmapi, then
it might change, but until then, you can try the second window trick but if
it doesn't work, it doesn't work.

It's reasonable to think that if other SMTP clients can do it (Outlook
Express, for example), then so could Outlook. I can't believe it would be a
huge design change. Nonetheless, it's what we have to live with until it
changes, if ever.

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/





(posted using Entourage)