Send email immediate when Outlook 2003 is closed?

[Diane Poremsky [MVP]]

Well, it only works if send immediately is enabled... So it's really not a
bug, just the way it works. The second message keeps outlook running without
a UI long enough for the transport to make the connection (if send
immediately is enabled) and send the message. You can do the same by opening
a note form or even by cradling a PDA and starting a sync. Leave it open
long enough and outlook will also download new mail, if you have it so
configured.

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.

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

 

[CMM]

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.

Point taken. I agree.

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

I might be an idiot. I keep dozens of windows open (developer here), VS
IDE's, bunch of notepad, IE's windows, bla bla bla) and I find that I close
Outlook all the time accidentally when I really mean for it to stay on ALL
THE TIME. It is probably the only "standard" (meaning non-tray... though
2003 fakes it) app that I keep open 100% of the time. The Hide When Minimize
option in Outlook 2003 doesn't alleviate the problem much.

I realize the problem is with *me* and my usage patterns and not Outlook.
Still, it's annoying.

 

[CMM]

Well, it only works if send immediately is enabled... So it's really not a

bug, just the way it works. The second message keeps outlook running
without
a UI long enough for the transport to make the connection (if send
immediately is enabled) and send the message.

Well, the "first" form (really the *last*... to be closed that is) should
keep Outlook open long enough to make the connection when the user hits
Send.... *or* NONE of the forms should send the message when you hit Send if
Outlook isn't "loaded."

It's User Interface 101. I can't see how this shouldn't be considered a
"bug." My boss would chew my a* off I developed something like this.

P.S.
(this whole discussion is premised on the assumption that the Send
Immediately option is set)

 

[Diane Poremsky [MVP]]

My son is an idiot too... So are many others but you can prevent it from
closing: http://www.outlook-tips.net/archives/2004/20040907.htm

I might be an idiot. I keep dozens of windows open (developer here), VS
IDE's, bunch of notepad, IE's windows, bla bla bla) and I find that I close
Outlook all the time accidentally when I really mean for it to stay on ALL
THE TIME. It is probably the only "standard" (meaning non-tray... though
2003 fakes it) app that I keep open 100% of the time. The Hide When Minimize
option in Outlook 2003 doesn't alleviate the problem much.

I realize the problem is with *me* and my usage patterns and not Outlook.
Still, it's annoying.

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

Exmapi needs more time to connect than simple mapi (OE) and once the message
hook is closed, so is outlook. Making the exe hang around when nothing was
open would just add to the problems we have with it not closing properly
when another program is accessing it's data.

Well, the "first" form (really the *last*... to be closed that is) should
keep Outlook open long enough to make the connection when the user hits
Send.... *or* NONE of the forms should send the message when you hit Send if
Outlook isn't "loaded."

It's User Interface 101. I can't see how this shouldn't be considered a
"bug." My boss would chew my a* off I developed something like this.

P.S.
(this whole discussion is premised on the assumption that the Send
Immediately option is set)

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

 

[CMM]

hook is closed, so is outlook.

I think we can appreciate the reasons for this behavior *technically*, but
definately not *functionaly* so as to call it "by design" and not a bug. I
can't think of a single Use Case scenerio that would allow for Four out of
Five messages being sent when the user hits the Send button on the messages.
Can you?

Either all should be sent (the user's intention if he has "Send Immediately"
option set) or NONE should be sent (because Outlook is technically "not
loaded" as Russ Valentine contends). As it is, right now, Outlook's behavior
cannot be deemed "by design." It is anomalous.

P.S.
And besides, IMO, whatever RunDll.exe call or "Outlook /c ipm.note"
subroutine is responsible for mailto: and new message functionality could
very well keep Outlook loaded long enough in the Send Button code-behind if
it was coded to do so.... ExMAPI notwithstanding.

--
-C. Moya
www.cmoya.com

Exmapi needs more time to connect than simple mapi (OE) and once the
message
hook is closed, so is outlook. Making the exe hang around when nothing was
open would just add to the problems we have with it not closing properly
when another program is accessing it's data.

Well, the "first" form (really the *last*... to be closed that is) should
keep Outlook open long enough to make the connection when the user hits
Send.... *or* NONE of the forms should send the message when you hit Send
if
Outlook isn't "loaded."

It's User Interface 101. I can't see how this shouldn't be considered a
"bug." My boss would chew my a* off I developed something like this.

P.S.
(this whole discussion is premised on the assumption that the Send
Immediately option is set)

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

 

[Brian Tillman]

And, I don't think Brian said this was "By Design."

Only because I've never spoken with the people who designed it. I simply
don't know.

 

[Ben M. Schorr - MVP]

Aloha Brian,

I have. I don't know if I would describe it as "by design" exactly, but
certainly not sending when OL is closed is the expected behavior by them.
In fact they were surprised to find that it sometimes will send immediately
from a second window -- that's the anomaly.

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

That is what I was told as well. They intended for Outlook not to send
immediately if it was closed when the new message window was invoked.
It could have been behavior they stumbled upon because Exmapi couldn't
finish loading before they programmatically closed the window. We'd have no
way of knowing that. If so, it was behavior they left in place
intentionally.

 

[Ben M. Schorr - MVP]

Aloha Russ Valentine [MVP-Outlook],

Yes, that's pretty much exactly what I was told by the devs regarding this.

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