Send email immediate when Outlook 2003 is closed?

[JJ]

Send email immediate when Outlook 2003 is closed?

I'm broadband so I'm always connected to the net but Outlook is
usually closed during the day except when I specifically want to
receive and reply to email. Of course I also send email when Outlook
is open, but sometimes I want to send email when Outlook is not
running, e.g.:

1) Sometimes I send and email from a shortcut on my desktop, e.g.
shortcut URL =
mailto:[email protected]

2) Some websites use a webform but others have a link, e.g. "Contact
Us" which will launch a new Outlook Compose email window just like the
shortcut #1 above.


3) Outlook doesn't do UseNet, and sometimes when I'm using my UseNet
newsreader I will want to reply by email instead of post a UseNet
reply. My newsreader, Forte Agent, is configured to use MAPI (Outlook)
to send an email message so it launches a new Outlook compose email
message, like #1 & #2 above.

The thing is outgoing Outlook email messages created in the three
examples above are not sent right away if Outlook is not running. They
go to the Outlook Outbox, and are not actually sent until I start up
Outlook.

Is there a way to configure Outlook to send these messages immediately
without actually starting up Outlook (even if it means starting
outlook in the background, but closing it back down upon successful
send, and not doing anything else like retrieving email messages etc.)

Obviously, even when Outlook is not running, it (or Windows) is
"listening" and in the above 3 cases it realizes I want to use Outlook
to compose an email message, so why can't it send the message?

Possibly related or not to my question what does the

"Schedule an automatic send/receive every x minutes" check box really
do, i.e.:


Tools / Options / Mail Setup / Send Receive / Send Receive Groups /

"Schedule an automatic send/receive every x minutes" check box


John "J.J." Jackson

 

[Russ Valentine [MVP-Outlook]]

Like most programs, Outlook only functions when it is running.
It can't function when it is closed.

 

[CMM]

Sorry Russ. But that is an argumentative, condenscending, and ridiculous
reply. Obviously, if he has an Outlook COMPOSE window open (triggered by a
MailTo: Url or whatever) Outlook *IS* "running." That it doesn't send the
message immediately when he hits Send (duh! uh, what could the user possibly
mean when he hits SEND?) is the question as an MVP that you should be
answering.

--
-C. Moya
www.cmoya.com

Like most programs, Outlook only functions when it is running.
It can't function when it is closed.
--
Russ Valentine
[MVP-Outlook]

Send email immediate when Outlook 2003 is closed?

I'm broadband so I'm always connected to the net but Outlook is
usually closed during the day except when I specifically want to
receive and reply to email. Of course I also send email when Outlook
is open, but sometimes I want to send email when Outlook is not
running, e.g.:

1) Sometimes I send and email from a shortcut on my desktop, e.g.
shortcut URL =
mailto:[email protected]

2) Some websites use a webform but others have a link, e.g. "Contact
Us" which will launch a new Outlook Compose email window just like the
shortcut #1 above.


3) Outlook doesn't do UseNet, and sometimes when I'm using my UseNet
newsreader I will want to reply by email instead of post a UseNet
reply. My newsreader, Forte Agent, is configured to use MAPI (Outlook)
to send an email message so it launches a new Outlook compose email
message, like #1 & #2 above.

The thing is outgoing Outlook email messages created in the three
examples above are not sent right away if Outlook is not running. They
go to the Outlook Outbox, and are not actually sent until I start up
Outlook.

Is there a way to configure Outlook to send these messages immediately
without actually starting up Outlook (even if it means starting
outlook in the background, but closing it back down upon successful
send, and not doing anything else like retrieving email messages etc.)

Obviously, even when Outlook is not running, it (or Windows) is
"listening" and in the above 3 cases it realizes I want to use Outlook
to compose an email message, so why can't it send the message?

Possibly related or not to my question what does the

"Schedule an automatic send/receive every x minutes" check box really
do, i.e.:


Tools / Options / Mail Setup / Send Receive / Send Receive Groups /

"Schedule an automatic send/receive every x minutes" check box


John "J.J." Jackson

 

[Russ Valentine [MVP-Outlook]]

I did answer the question.
Feel free to post a correction if you have one.
The new message window does not launch Outlook's transports.
Was there some part of my answer that you did not understand? Or are you
just beating up on me because you do not like the way Outlook was designed?
--
Russ Valentine
[MVP-Outlook]

Sorry Russ. But that is an argumentative, condenscending, and ridiculous
reply. Obviously, if he has an Outlook COMPOSE window open (triggered by a
MailTo: Url or whatever) Outlook *IS* "running." That it doesn't send the
message immediately when he hits Send (duh! uh, what could the user
possibly mean when he hits SEND?) is the question as an MVP that you
should be answering.

--
-C. Moya
www.cmoya.com

Like most programs, Outlook only functions when it is running.
It can't function when it is closed.
--
Russ Valentine
[MVP-Outlook]

Send email immediate when Outlook 2003 is closed?

I'm broadband so I'm always connected to the net but Outlook is
usually closed during the day except when I specifically want to
receive and reply to email. Of course I also send email when Outlook
is open, but sometimes I want to send email when Outlook is not
running, e.g.:

1) Sometimes I send and email from a shortcut on my desktop, e.g.
shortcut URL =
mailto:[email protected]

2) Some websites use a webform but others have a link, e.g. "Contact
Us" which will launch a new Outlook Compose email window just like the
shortcut #1 above.


3) Outlook doesn't do UseNet, and sometimes when I'm using my UseNet
newsreader I will want to reply by email instead of post a UseNet
reply. My newsreader, Forte Agent, is configured to use MAPI (Outlook)
to send an email message so it launches a new Outlook compose email
message, like #1 & #2 above.

The thing is outgoing Outlook email messages created in the three
examples above are not sent right away if Outlook is not running. They
go to the Outlook Outbox, and are not actually sent until I start up
Outlook.

Is there a way to configure Outlook to send these messages immediately
without actually starting up Outlook (even if it means starting
outlook in the background, but closing it back down upon successful
send, and not doing anything else like retrieving email messages etc.)

Obviously, even when Outlook is not running, it (or Windows) is
"listening" and in the above 3 cases it realizes I want to use Outlook
to compose an email message, so why can't it send the message?

Possibly related or not to my question what does the

"Schedule an automatic send/receive every x minutes" check box really
do, i.e.:


Tools / Options / Mail Setup / Send Receive / Send Receive Groups /

"Schedule an automatic send/receive every x minutes" check box


John "J.J." Jackson

 

[CMM]

I did answer the question.

Feel free to post a correction if you have one.

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

The new message window does not launch Outlook's transports.

But, it does launch "Outlook," which your "answer" implied it didn't. Easily
verifiable in Task Manager. AND, it also launches the "transports" (whatever
that is) as Workaround #1 above demonstrates. So, you're wrong on all
counts.

Was there some part of my answer that you did not understand?

The fact that that sort of answer came from an MVP.

Or are you just beating up on me because you do not like the way Outlook
was designed?

Designed? I wouldn't call Outlook's myriad of anomolies "by design."

--
-C. Moya
www.cmoya.com

I did answer the question.
Feel free to post a correction if you have one.
The new message window does not launch Outlook's transports.
Was there some part of my answer that you did not understand? Or are you
just beating up on me because you do not like the way Outlook was
designed?
--
Russ Valentine
[MVP-Outlook]

Sorry Russ. But that is an argumentative, condenscending, and ridiculous
reply. Obviously, if he has an Outlook COMPOSE window open (triggered by
a MailTo: Url or whatever) Outlook *IS* "running." That it doesn't send
the message immediately when he hits Send (duh! uh, what could the user
possibly mean when he hits SEND?) is the question as an MVP that you
should be answering.

--
-C. Moya
www.cmoya.com

Like most programs, Outlook only functions when it is running.
It can't function when it is closed.
--
Russ Valentine
[MVP-Outlook]
Send email immediate when Outlook 2003 is closed?

I'm broadband so I'm always connected to the net but Outlook is
usually closed during the day except when I specifically want to
receive and reply to email. Of course I also send email when Outlook
is open, but sometimes I want to send email when Outlook is not
running, e.g.:

1) Sometimes I send and email from a shortcut on my desktop, e.g.
shortcut URL =
mailto:[email protected]

2) Some websites use a webform but others have a link, e.g. "Contact
Us" which will launch a new Outlook Compose email window just like the
shortcut #1 above.


3) Outlook doesn't do UseNet, and sometimes when I'm using my UseNet
newsreader I will want to reply by email instead of post a UseNet
reply. My newsreader, Forte Agent, is configured to use MAPI (Outlook)
to send an email message so it launches a new Outlook compose email
message, like #1 & #2 above.

The thing is outgoing Outlook email messages created in the three
examples above are not sent right away if Outlook is not running. They
go to the Outlook Outbox, and are not actually sent until I start up
Outlook.

Is there a way to configure Outlook to send these messages immediately
without actually starting up Outlook (even if it means starting
outlook in the background, but closing it back down upon successful
send, and not doing anything else like retrieving email messages etc.)

Obviously, even when Outlook is not running, it (or Windows) is
"listening" and in the above 3 cases it realizes I want to use Outlook
to compose an email message, so why can't it send the message?

Possibly related or not to my question what does the

"Schedule an automatic send/receive every x minutes" check box really
do, i.e.:


Tools / Options / Mail Setup / Send Receive / Send Receive Groups /

"Schedule an automatic send/receive every x minutes" check box


John "J.J." Jackson

 

[Russ Valentine [MVP-Outlook]]

My answer is easier than your "workarounds."
Open Outlook. That's what you're doing, only with a lot more effort.
--
Russ Valentine
[MVP-Outlook]

I did answer the question.
Feel free to post a correction if you have one.

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

The new message window does not launch Outlook's transports.

But, it does launch "Outlook," which your "answer" implied it didn't.
Easily
verifiable in Task Manager. AND, it also launches the "transports"
(whatever that is) as Workaround #1 above demonstrates. So, you're wrong
on all counts.

Was there some part of my answer that you did not understand?

The fact that that sort of answer came from an MVP.

Or are you just beating up on me because you do not like the way Outlook
was designed?

Designed? I wouldn't call Outlook's myriad of anomolies "by design."

--
-C. Moya
www.cmoya.com

I did answer the question.
Feel free to post a correction if you have one.
The new message window does not launch Outlook's transports.
Was there some part of my answer that you did not understand? Or are you
just beating up on me because you do not like the way Outlook was
designed?
--
Russ Valentine
[MVP-Outlook]

Sorry Russ. But that is an argumentative, condenscending, and ridiculous
reply. Obviously, if he has an Outlook COMPOSE window open (triggered by
a MailTo: Url or whatever) Outlook *IS* "running." That it doesn't send
the message immediately when he hits Send (duh! uh, what could the user
possibly mean when he hits SEND?) is the question as an MVP that you
should be answering.

--
-C. Moya
www.cmoya.com
Like most programs, Outlook only functions when it is running.
It can't function when it is closed.
--
Russ Valentine
[MVP-Outlook]
Send email immediate when Outlook 2003 is closed?

I'm broadband so I'm always connected to the net but Outlook is
usually closed during the day except when I specifically want to
receive and reply to email. Of course I also send email when Outlook
is open, but sometimes I want to send email when Outlook is not
running, e.g.:

1) Sometimes I send and email from a shortcut on my desktop, e.g.
shortcut URL =
mailto:[email protected]

2) Some websites use a webform but others have a link, e.g. "Contact
Us" which will launch a new Outlook Compose email window just like the
shortcut #1 above.


3) Outlook doesn't do UseNet, and sometimes when I'm using my UseNet
newsreader I will want to reply by email instead of post a UseNet
reply. My newsreader, Forte Agent, is configured to use MAPI (Outlook)
to send an email message so it launches a new Outlook compose email
message, like #1 & #2 above.

The thing is outgoing Outlook email messages created in the three
examples above are not sent right away if Outlook is not running. They
go to the Outlook Outbox, and are not actually sent until I start up
Outlook.

Is there a way to configure Outlook to send these messages immediately
without actually starting up Outlook (even if it means starting
outlook in the background, but closing it back down upon successful
send, and not doing anything else like retrieving email messages etc.)

Obviously, even when Outlook is not running, it (or Windows) is
"listening" and in the above 3 cases it realizes I want to use Outlook
to compose an email message, so why can't it send the message?

Possibly related or not to my question what does the

"Schedule an automatic send/receive every x minutes" check box really
do, i.e.:


Tools / Options / Mail Setup / Send Receive / Send Receive Groups /

"Schedule an automatic send/receive every x minutes" check box


John "J.J." Jackson

 

[CMM]

CTRL+N is a lot more effort? If you say so.
"Deal with it" is always the easier answer.

P.S. And your original answer was still condenscending and unhelpful... and
wrong. With all due respect.
"The new message window does not launch Outlook's transports."
- Said with authority. But, wrong as I demonstrated.
"Like most programs, Outlook only functions when it is running. It can't
function when it is closed."
- Funny? Witty? Insulting? But also wrong as the compose mail window *does*
open "Outlook."



--
-C. Moya
www.cmoya.com

My answer is easier than your "workarounds."
Open Outlook. That's what you're doing, only with a lot more effort.
--
Russ Valentine
[MVP-Outlook]

I did answer the question.
Feel free to post a correction if you have one.

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

The new message window does not launch Outlook's transports.

But, it does launch "Outlook," which your "answer" implied it didn't.
Easily
verifiable in Task Manager. AND, it also launches the "transports"
(whatever that is) as Workaround #1 above demonstrates. So, you're wrong
on all counts.

Was there some part of my answer that you did not understand?

The fact that that sort of answer came from an MVP.

Or are you just beating up on me because you do not like the way Outlook
was designed?

Designed? I wouldn't call Outlook's myriad of anomolies "by design."

--
-C. Moya
www.cmoya.com

I did answer the question.
Feel free to post a correction if you have one.
The new message window does not launch Outlook's transports.
Was there some part of my answer that you did not understand? Or are you
just beating up on me because you do not like the way Outlook was
designed?
--
Russ Valentine
[MVP-Outlook]
Sorry Russ. But that is an argumentative, condenscending, and
ridiculous
reply. Obviously, if he has an Outlook COMPOSE window open (triggered
by
a MailTo: Url or whatever) Outlook *IS* "running." That it doesn't send
the message immediately when he hits Send (duh! uh, what could the user
possibly mean when he hits SEND?) is the question as an MVP that you
should be answering.

--
-C. Moya
www.cmoya.com
Like most programs, Outlook only functions when it is running.
It can't function when it is closed.
--
Russ Valentine
[MVP-Outlook]
Send email immediate when Outlook 2003 is closed?

I'm broadband so I'm always connected to the net but Outlook is
usually closed during the day except when I specifically want to
receive and reply to email. Of course I also send email when Outlook
is open, but sometimes I want to send email when Outlook is not
running, e.g.:

1) Sometimes I send and email from a shortcut on my desktop, e.g.
shortcut URL =
mailto:[email protected]

2) Some websites use a webform but others have a link, e.g. "Contact
Us" which will launch a new Outlook Compose email window just like
the
shortcut #1 above.


3) Outlook doesn't do UseNet, and sometimes when I'm using my UseNet
newsreader I will want to reply by email instead of post a UseNet
reply. My newsreader, Forte Agent, is configured to use MAPI
(Outlook)
to send an email message so it launches a new Outlook compose email
message, like #1 & #2 above.

The thing is outgoing Outlook email messages created in the three
examples above are not sent right away if Outlook is not running.
They
go to the Outlook Outbox, and are not actually sent until I start up
Outlook.

Is there a way to configure Outlook to send these messages
immediately
without actually starting up Outlook (even if it means starting
outlook in the background, but closing it back down upon successful
send, and not doing anything else like retrieving email messages
etc.)

Obviously, even when Outlook is not running, it (or Windows) is
"listening" and in the above 3 cases it realizes I want to use
Outlook
to compose an email message, so why can't it send the message?

Possibly related or not to my question what does the

"Schedule an automatic send/receive every x minutes" check box really
do, i.e.:


Tools / Options / Mail Setup / Send Receive / Send Receive Groups /

"Schedule an automatic send/receive every x minutes" check box


John "J.J." Jackson

 

[Russ Valentine [MVP-Outlook]]

You're the one who seems intent on being insulting.
The new message window does not launch Outlook and its mail transports. If
it did, it would send immediately when Outlook is configured that way.
Clearly it does not do that, nor can it be configured to behave that way.
Yes, you can purchase a utility that leaves Outlook running in the
background. Most users prefer just to open Outlook themselves.
--
Russ Valentine
[MVP-Outlook]

CTRL+N is a lot more effort? If you say so.
"Deal with it" is always the easier answer.

P.S. And your original answer was still condenscending and unhelpful...
and wrong. With all due respect.
"The new message window does not launch Outlook's transports."
- Said with authority. But, wrong as I demonstrated.
"Like most programs, Outlook only functions when it is running. It can't
function when it is closed."
- Funny? Witty? Insulting? But also wrong as the compose mail window
*does* open "Outlook."



--
-C. Moya
www.cmoya.com

My answer is easier than your "workarounds."
Open Outlook. That's what you're doing, only with a lot more effort.
--
Russ Valentine
[MVP-Outlook]

I did answer the question.
Feel free to post a correction if you have one.

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

The new message window does not launch Outlook's transports.

But, it does launch "Outlook," which your "answer" implied it didn't.
Easily
verifiable in Task Manager. AND, it also launches the "transports"
(whatever that is) as Workaround #1 above demonstrates. So, you're wrong
on all counts.

Was there some part of my answer that you did not understand?

The fact that that sort of answer came from an MVP.

Or are you just beating up on me because you do not like the way
Outlook
was designed?

Designed? I wouldn't call Outlook's myriad of anomolies "by design."

--
-C. Moya
www.cmoya.com
I did answer the question.
Feel free to post a correction if you have one.
The new message window does not launch Outlook's transports.
Was there some part of my answer that you did not understand? Or are
you
just beating up on me because you do not like the way Outlook was
designed?
--
Russ Valentine
[MVP-Outlook]
Sorry Russ. But that is an argumentative, condenscending, and
ridiculous
reply. Obviously, if he has an Outlook COMPOSE window open (triggered
by
a MailTo: Url or whatever) Outlook *IS* "running." That it doesn't
send
the message immediately when he hits Send (duh! uh, what could the
user
possibly mean when he hits SEND?) is the question as an MVP that you
should be answering.

--
-C. Moya
www.cmoya.com
Like most programs, Outlook only functions when it is running.
It can't function when it is closed.
--
Russ Valentine
[MVP-Outlook]
Send email immediate when Outlook 2003 is closed?

I'm broadband so I'm always connected to the net but Outlook is
usually closed during the day except when I specifically want to
receive and reply to email. Of course I also send email when Outlook
is open, but sometimes I want to send email when Outlook is not
running, e.g.:

1) Sometimes I send and email from a shortcut on my desktop, e.g.
shortcut URL =
mailto:[email protected]

2) Some websites use a webform but others have a link, e.g. "Contact
Us" which will launch a new Outlook Compose email window just like
the
shortcut #1 above.


3) Outlook doesn't do UseNet, and sometimes when I'm using my UseNet
newsreader I will want to reply by email instead of post a UseNet
reply. My newsreader, Forte Agent, is configured to use MAPI
(Outlook)
to send an email message so it launches a new Outlook compose email
message, like #1 & #2 above.

The thing is outgoing Outlook email messages created in the three
examples above are not sent right away if Outlook is not running.
They
go to the Outlook Outbox, and are not actually sent until I start up
Outlook.

Is there a way to configure Outlook to send these messages
immediately
without actually starting up Outlook (even if it means starting
outlook in the background, but closing it back down upon successful
send, and not doing anything else like retrieving email messages
etc.)

Obviously, even when Outlook is not running, it (or Windows) is
"listening" and in the above 3 cases it realizes I want to use
Outlook
to compose an email message, so why can't it send the message?

Possibly related or not to my question what does the

"Schedule an automatic send/receive every x minutes" check box
really
do, i.e.:


Tools / Options / Mail Setup / Send Receive / Send Receive Groups /

"Schedule an automatic send/receive every x minutes" check box


John "J.J." Jackson

 

[CMM]

You're the one who seems intent on being insulting.

The new message window does not launch Outlook and its mail transports. If
it did, it would send immediately when Outlook is configured that way.

If you have two New Message windows open and hit SEND on one, the message
*is* sent without Outlook being open. So apparently Outlook and its "mail
transports" are loaded somewhere invisibibly wouldn't you say?

That whatever function loads up these "on-demand" windows doesn't wait for
Outlook to send out the message when the last one closes is a design FLAW...
as keeping two of them open obviously demonstrates.

 

[Russ Valentine [MVP-Outlook]]

You can consider it a flaw if you want. Most people don't.
I am only telling you the way Outlook works. When Outlook is closed and a
user invokes a New Message Window programmatically with a Mailto link,
Outlook is launched with its mail transports disabled and closes as soon as
the message is completed. 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.
When a New Message Window is invoked while Outlook is running, then Outlook
will abide by the user's preferences for sending mail (either immediately or
on the next poll).
Most users leave Outlook running when they want to send or receive mail and
close it when they do not. Users who want their messages sent immediately
need to keep Outlook running.

 

[CMM]

I don't need you to tell me how Outlook works. I've been programming Outlook
since it was called Windows Inbox. And, yes, it is design flaw.

 

[Russ Valentine [MVP-Outlook]]

Wasn't that its name just before it became Exchange? Then everyone got
confused because they thought they would need Exchange Server. So next it
became Windows Messaging, which no one used because "Internet Mail and News"
made more sense (and was much easier than trying to use WM's full MAPI
protocols for SMTP/POP). So next they named it Outlook and changed Internet
Mail and News to Outlook Express. Now no one had any clue which to use, so
they gave up and used Netscape.
Sheer genius. I love history.

 

[CMM]

Ha ha. Yeah.
Though, if I remember correctly there's wasn't much confusion with the
"Exchange" part like you say. Exchange (the client) came out way before
Exchange Server. At that point NOBODY was using that program (except me
-) ).

Similar "confusion" happened with Windows 2000 and Windows ME.... is
happening right now with the gazillion versions of Visual Studio (it took me
two weeks to research the version I wanted... and even now I'm not sure I
made the right choice) and is about to happen again with gazillion versions
of Vista. Microsoft's Marketing department has gone insane.

--
-C. Moya
www.cmoya.com

Wasn't that its name just before it became Exchange? Then everyone got
confused because they thought they would need Exchange Server. So next it
became Windows Messaging, which no one used because "Internet Mail and
News" made more sense (and was much easier than trying to use WM's full
MAPI protocols for SMTP/POP). So next they named it Outlook and changed
Internet Mail and News to Outlook Express. Now no one had any clue which
to use, so they gave up and used Netscape.
Sheer genius. I love history.

 

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

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

Say I'm on a web site and mouse on "Contact US" which launches an
Outlook compose email message. Why wouldn't I want that sent right
away and why would I want to fire up Outlook to send it?

Right now I'm evaluating ACT! which ties to Outlook, but it seems that
when I send an email message in ACT! it is just going to my Outlook
OutBox if Outlook is not running.

ACT! is a machine hog as it is, so I sure don't want to have to keep
Outlook open all day.
John "J.J." Jackson

 

[directjj]

Thanks

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


But, it does launch "Outlook," which your "answer" implied it didn't. Easily
verifiable in Task Manager. AND, it also launches the "transports" (whatever
that is) as Workaround #1 above demonstrates. So, you're wrong on all
counts.


The fact that that sort of answer came from an MVP.


Designed? I wouldn't call Outlook's myriad of anomolies "by design."

John "J.J." Jackson

 

[Ben M. Schorr - MVP]

Hello directjj,

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]

I agree... and furthermore, this isn't "by design." If you have two compose
windows opened (for instance, you clicked two MailTo: links) and hit Send on
one of them, the message is Sent immediately (assuming you have the option
set to "Send Immediately" in Outlook)... at least that's my experience. You
still haven't "Loaded" Outlook, you haven't done anything magical, and it
still sends it. Russ Valentine (MVP) is off base. If this were truly by "by
design" you could have a gazillion New Mail windows and NONE of them would
Send Immediately.

 

[CMM]

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.

 

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

 

[CMM]

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.