Disable warning in Outlook "a program trying to send email on your behalf"

Discussion:

(too old to reply)

d***@tallerworks.com

2008-11-16 19:30:56 UTC

Hello,

I have an application which sends out emails via Outlook, (I'm using
Outlook 2007, Exchange 2003). I am getting warnings that an
application is trying to send email on my behalf. As an additional
nicety, Outlook delays the ability to "allow" by 5 seconds. I am
trying to send out dozens of bills, and this is crippling me. After
much hunting online, I have discovered many articles that say that the
"programmatic" preferences in Outlook whereby you can opt to never be
warned is not effective if you are using Exchange. They say that you
need to configure this preference in Exchange, but I'm unable to
locate anywhere to set this preference.

Help! How can I get rid of this warning permanently?
Thanks.

Andy David {MVP}

2008-11-16 20:09:39 UTC

Permalink

Post by d***@tallerworks.com
Hello,
I have an application which sends out emails via Outlook, (I'm using
Outlook 2007, Exchange 2003). I am getting warnings that an
application is trying to send email on my behalf. As an additional
nicety, Outlook delays the ability to "allow" by 5 seconds. I am
trying to send out dozens of bills, and this is crippling me. After
much hunting online, I have discovered many articles that say that the
"programmatic" preferences in Outlook whereby you can opt to never be
warned is not effective if you are using Exchange. They say that you
need to configure this preference in Exchange, but I'm unable to
locate anywhere to set this preference.
Help! How can I get rid of this warning permanently?
Thanks.

3rd party software like ClickYes:
http://www.contextmagic.com/express-clickyes/

Atreju

2008-11-16 20:25:16 UTC

Permalink

On Sun, 16 Nov 2008 15:09:39 -0500, Andy David {MVP}

Post by Andy David {MVP}
http://www.contextmagic.com/express-clickyes/

Firstly, I can script my own "answer yes" I have many such scripts -
the problem with that is that the dialog box disables the "allow"
button for 5 seconds.

However, the repeated delays crash my billing application so this is
not a feasible measure.

I'm looking for a solution not a work-around.

Thanks.

Andy David {MVP}

2008-11-16 21:03:14 UTC

Permalink

On Sun, 16 Nov 2008 15:25:16 -0500, Atreju

Post by Atreju
On Sun, 16 Nov 2008 15:09:39 -0500, Andy David {MVP}

Post by Andy David {MVP}
http://www.contextmagic.com/express-clickyes/

Firstly, I can script my own "answer yes" I have many such scripts -
the problem with that is that the dialog box disables the "allow"
button for 5 seconds.
However, the repeated delays crash my billing application so this is
not a feasible measure.
I'm looking for a solution not a work-around.

Dont use Outlook to send it then. There are plenty of better ways to
send messages from applications using SMTP rather than trying to hook
into Outlook.

That's been a part of Outlook for years, but if there is a way around
it, I would ask in an Outlook newsgroup.

s***@gmail.com

2014-04-28 07:28:51 UTC

Permalink

Huge Thanks 48 hours to find this solution.
I wanted to send by mail merge 1500 emails and the annoying message was a very major obstacle.

Thanks Andy

Post by Andy David {MVP}

http://www.contextmagic.com/express-clickyes/

Martin Blackstone [MVP]

2008-11-16 20:11:39 UTC

Permalink

You're not going to find the fix in Exchange.
It was coded into Outlook to specifically address issues with virus'.
Check out an app called ClickYes.
http://www.contextmagic.com/express-clickyes/

Atreju

2008-11-16 20:26:52 UTC

Permalink

On Sun, 16 Nov 2008 12:11:39 -0800, "Martin Blackstone [MVP]"

Post by Martin Blackstone [MVP]
You're not going to find the fix in Exchange.
It was coded into Outlook to specifically address issues with virus'.
Check out an app called ClickYes.
http://www.contextmagic.com/express-clickyes/

Same as other poster - clickyes is a scripted response. I don't want
a response, I want to eliminate the error. Are you telling me that
Outlook no longer has the ability to support MAPI access to send
emails at all, no matter if I decide it is a trusted application?
That's insane. There must be a way to allow the application to send
email.

Post by Martin Blackstone [MVP]

Martin Blackstone [MVP]

2008-11-16 23:54:37 UTC

Permalink

Post by Atreju
On Sun, 16 Nov 2008 12:11:39 -0800, "Martin Blackstone [MVP]"

Like I said, its not an Exchange function.

If you want to press it, post in the Outlook groups.

Jamestechman

2008-11-17 01:48:53 UTC

Permalink

Not sure what custom app you are using but if it's a script based app
you can use Outlook redemption which is an extension of the Outlook
object model. I've used this sucessfully for office macros to send out
emails\attachemnts to bypass the security warning.

Outlook Redemption v. 4.6
http://www.dimastr.com/redemption/

James Chong (MVP)
MCITP | EMA; MCSE | M+, S+,
Security+, Project+, ITIL
msexchangetips.blogspot.com

Alexander Zammit [MVP]

2008-11-17 10:56:17 UTC

Permalink

MS made available a solution for this a long time ago.

Basically there are two ways to eliminate these warning dialogs. The old way
was to use the Outlook Security Administrative Package. Details here:
http://www.exchangeinbox.com/article.aspx?i=57

As from Outlook 2007 you should be able to disable these warnings through
Group Policy.

I personally did this a couple of times. It works but I remember it took me
quite some playing around. With Outlook 2007 I still used the old Admin Pack
simply because I know better how to do it the old way.
--
Alexander Zammit
WinDeveloper Software
IMF Tune - Enable the Exchange 2003 IMF/Exchange 2007 Content Filter to
unleash its full power.
http://www.windeveloper.com/imftune/

Jamestechman

2008-11-17 15:41:20 UTC

Permalink

Neat tool!!

James Chong (MVP)
MCITP | EMA; MCSE | M+, S+,
Security+, Project+, ITIL
msexchangetips.blogspot.com

Post by Alexander Zammit [MVP]
MS made available a solution for this a long time ago.
Basically there are two ways to eliminate these warning dialogs. The old way
was to use the Outlook Security Administrative Package. Details here:http://www.exchangeinbox.com/article.aspx?i=57
As from Outlook 2007 you should be able to disable these warnings through
Group Policy.
I personally did this a couple of times. It works but I remember it took me
quite some playing around. With Outlook 2007 I still used the old Admin Pack
simply because I know better how to do it the old way.
--
Alexander Zammit
WinDeveloper Software
IMF Tune - Enable the Exchange 2003 IMF/Exchange 2007 Content Filter to
unleash its full power.http://www.windeveloper.com/imftune/

- Show quoted text -

Andy David {MVP}

2008-11-17 15:57:47 UTC

Permalink

On Mon, 17 Nov 2008 11:56:17 +0100, "Alexander Zammit [MVP]"

Post by Alexander Zammit [MVP]
MS made available a solution for this a long time ago.
Basically there are two ways to eliminate these warning dialogs. The old way
http://www.exchangeinbox.com/article.aspx?i=57
As from Outlook 2007 you should be able to disable these warnings through
Group Policy.
I personally did this a couple of times. It works but I remember it took me
quite some playing around. With Outlook 2007 I still used the old Admin Pack
simply because I know better how to do it the old way.

One could argue that you dont want to disable that warning, but that's
another thread!

Alexander Zammit [MVP]

2008-11-17 16:39:56 UTC

Permalink

True. Although the tool does allow to select the users for whom to disable
the warnings. So really one could create an account just for the process
that will need sending emails and keep the warning for everyone else.
--
Alexander Zammit
WinDeveloper Software
IMF Tune - Enable the Exchange 2003 IMF/Exchange 2007 Content Filter to
unleash its full power.
http://www.windeveloper.com/imftune/

Post by Andy David {MVP}
On Mon, 17 Nov 2008 11:56:17 +0100, "Alexander Zammit [MVP]"

One could argue that you dont want to disable that warning, but that's
another thread!