Sending Email

[Brad]

Anyone know how to stop Outlook from displaying that "An application is
trying to send email on your behalf and wait 5 seconds" box? I have an
Access routine that sends out around 80 to 150 messages at the end of the
month. This dang security thing implemented in Outlook 2000 drives me
wonky.

Any help would be appreciated.

Thanks

Brad

 

[Cheryl Fischer]

Hello Brad,

Yes, the Outlook Security Prompt, while a good thing, has forced a lot of
re-worked code for automated emailings and driven a lot of us "wonky".
Outlook users operating outside of the Exchange environment cannot turn this
prompt off. There are a few options available, as outlined by Outlook MVP
Sue Mosher:

If you're the administrator in an Exchange Server environment, you can
reduce the impact of the security prompts with administrative tools. See
http://www.slipstick.com/outlook/esecup/admin.htm

If it's an application you wrote yourself, you can use one of these
approaches to redo the program:

-- Use Extended MAPI (see http://www.slipstick.com/dev/mapi.htm) and C++
or Delphi; this is the most secure method and the only one that Microsoft
recommendeds.

-- Use Redemption (http://www.dimastr.com/redemption/), a third-party
COM library that wraps around Extended MAPI but parallels the Outlook Object
Model

-- Use SendKeys to "click" the buttons on the security dialogs that your
application may trigger. See
http://www.slipstick.com/outlook/esecup.htm#autosec for a link to sample
code.

-- Program the free Express ClickYes
(http://www.express-soft.com/mailmate/clickyes.html) tool to start suspended
and turn it on only when your program needs to have the buttons clicked
automatically."

I have used the ClickYes utility successfully for myself and for a client,
using code provided by ClickYes which turns the utility on just before
sending the emails and turns it off when the process has completed. It
does not get rid of the prompt, but it uses code to click the 'Yes' button
for you.

hth,

 

[Brad]

Thanks Cheryl,

Because of company policies, I can not download and install unauthorized programs on the machine I am working on, but this scripting link (Send Keys) is intereseting. Thanks for the info.

Brad

 

[Guest]

I can see no argument for providing these controls on Exchange but not in Outlook. So the fair and acceptable solution from Micrsoft would be to provide MS Exchange at no cost to all users of our third party systems where the security is end user controllable. We have worked for many years using Microsoft products using their component object modelling and once again Microsoft pays scant regard for the needs of the community

Pete

 

[Brad]

hehe kinda reminds me of an Olde Saying regarding Microsoft Products,

That ain't a BUG... It's a Feature!!!

As for getting Exchange for nothing..... There are now commericals on TV
showing Pigs Flying....

Brad

I can see no argument for providing these controls on Exchange but not in

Outlook. So the fair and acceptable solution from Micrsoft would be to
provide MS Exchange at no cost to all users of our third party systems where
the security is end user controllable. We have worked for many years using
Microsoft products using their component object modelling and once again
Microsoft pays scant regard for the needs of the community.

 

[Brad]

One of the things that really tick me off about Microsoft applications and
operating systems, is that instead of providing upgrades to existing
software, Microsoft stops supporting older versions and sells what are
really bug fixes as new applications...

Organizations just can't keep up with the rate that the newer versions are
coming out. Dependent on the size of the organization, no one within the
organization will ever be 100% compatable with other colleagues. (I'm using
Win95, my computer is due to be changed out in June, your using WinNT due to
be switch out in Jan05, Fred's using Win98SE, George is on 2000 due to be
switched out in Jan06, Wilma has XP (she got her computer in Jan 04) and
Julie has Windows2003 (who got her's yesterday). We all use different
versions of Office. I have to keep everything compliant with earliest
version of Office that is in circulation at work (Office97) because the
company hasn't completely changed out its older computers. I'm using
Office2000 which isn't 100% compatable with the earlier version therefore I
also must run a copy of 97. The new Computers are being delivered with
OfficeXP (Doh, now I need to run 3 versions of Office or upgrade the older
computers (if they are compatable to run it) or downgrade the new
computers). By the time the Office2000 machines are changed out, their
replacements will probably shipped with a 2 Generation higher version of
Office. And around we go again...)

Another example, just as you get VB6 and C++ under your belt, become
comfortable with the programming environment and begin to produce usable
applications, MS punches out VB.NET, C# and the rest of the .NET products.
Support for older version will be gone in about a year (if it isn't gone
already). Everyone is now scrambling to become current with the new standard
and at a huge expense.

Oh well, I guess the money is better in Bill's pocket than in the
organization's shareholder's... (Cha Right!!!)

Hey, wasn't it Gates who said... 86Kb of memory.... Nobody will EVER use
86Kb of memory.

Thanks for listening to the bit**ing...

Brad

I can see no argument for providing these controls on Exchange but not in

Outlook. So the fair and acceptable solution from Micrsoft would be to
provide MS Exchange at no cost to all users of our third party systems where
the security is end user controllable. We have worked for many years using
Microsoft products using their component object modelling and once again
Microsoft pays scant regard for the needs of the community.

 

[Rick Brandt]

One of the things that really tick me off about Microsoft applications and
operating systems, is that instead of providing upgrades to existing
software, Microsoft stops supporting older versions and sells what are
really bug fixes as new applications...

Organizations just can't keep up with the rate that the newer versions are
coming out. [snip]

Just because a software company comes out with a new version every 'n' months
does not mean that you have to buy them or use them. That is the real problem
with many of these companies (and individuals). They have been conditioned to
believe that when newer is available, newer is what we should use, completely
skipping the step of considering whether what they are currently using is still
doing the job adequately or if the newer package is really offering anything
worthwhile.

"But they don't support the older versions" is the next line of reasoning. I
really don't know what this means. I have used MS "support" exactly one time in
my life so I can't really see what the problem would be if it suddenly wasn't
available (in that particular instance they couldn't help me anyway). If
support includes things like service releases and bug-fixes and such, the fact
is that by the time a piece of software is old enough for this to be cut off,
most issues of any real importance have already been addressed.

 

[Brad]

Hi Rick,

What you say is very true. Organizations really need to sit back and
observe before committing $$ and resourse to upgrades. However sometimes
change is driven by what a change-up computer is loaded with. Older
versions are no longer available, even if an organization wants to stagnate
with what is working. This is what I mean by no longer supported, Software
updates and fixes are no longer being produced for the older version as the
newer version is released.

But this is now getting way off topic. I suggest that if we want to
continue this thread we take it to another group....

Thanks for your response

Brad

One of the things that really tick me off about Microsoft applications and
operating systems, is that instead of providing upgrades to existing
software, Microsoft stops supporting older versions and sells what are
really bug fixes as new applications...

Organizations just can't keep up with the rate that the newer versions are
coming out. [snip]

Just because a software company comes out with a new version every 'n' months
does not mean that you have to buy them or use them. That is the real problem
with many of these companies (and individuals). They have been conditioned to
believe that when newer is available, newer is what we should use, completely
skipping the step of considering whether what they are currently using is still
doing the job adequately or if the newer package is really offering anything
worthwhile.

"But they don't support the older versions" is the next line of reasoning. I
really don't know what this means. I have used MS "support" exactly one time in
my life so I can't really see what the problem would be if it suddenly wasn't
available (in that particular instance they couldn't help me anyway). If
support includes things like service releases and bug-fixes and such, the fact
is that by the time a piece of software is old enough for this to be cut off,
most issues of any real importance have already been addressed.