|
|
|
| Author |
Message |
Cappy
Joined: 05 Aug 2007 Posts: 2
|
Posted: Mon Jul 02, 2007 5:26 pm Post subject: Long shot - email monitoring program written by MS question |
|
|
We have an application written by MS that is called Email Monitoring.
It takes emails from a source mailbox, and depending on (text?) in the
message, sorts them out to different public folders.
Within the program, a parameter is set by picking the source mailbox
out of the GAL. The "name" of the source mailbox is written to the
registry as a string of letters and numbers, about 60 characters
long. So that variable is stored in the registry.
A bit later in the program, the program has this line:
Archived from group: microsoft>public>exchange>applications |
|
| Back to top |
|
 |
Cappy
Joined: 05 Aug 2007 Posts: 2
|
Posted: Mon Jul 02, 2007 5:39 pm Post subject: Re: Long shot - email monitoring program written by MS quest |
|
|
On Jul 2, 4:26 pm, Cappy wrote:
> We have an application written by MS that is called Email Monitoring.
> It takes emails from a source mailbox, and depending on (text?) in the
> message, sorts them out to different public folders.
>
> Within the program, a parameter is set by picking the source mailbox
> out of the GAL. The "name" of the source mailbox is written to the
> registry as a string of letters and numbers, about 60 characters
> long. So that variable is stored in the registry.
>
> A bit later in the program, the program has this line:
(Let me finish typing... sheesh I dislike Google
strongly...)
Set AEUnattended =
gMapiSess.GetAddressEntry(sourceMailboxVariableNameHeldInRegistry)
The error that pops up is "Program is trying to access email addresses
you have stored in Outlook." Do you want to allow this? Set time for
up to 10 minutes to allow this.
Once that time is set and the Yes button is clicked, for *each and
every message* in this source mailbox, the following prompt is
displayed:
"A program is trying to send on your behalf. Do you want to allow
this?"
The user clicks Yes on this prompt for about 500 messages/day.
We are using a security form set up in the Public Folders. In our lab
environment, which pretty much mimics our production environment, we
have set every single option under Programmatic Settings to
automatically approve. The source mailbox and the user are listed in
the members of the form. The user has about every single right on the
source mailbox he could need. But I'm missing something.
In the source mailbox settings in AD, the user has full rights on the
Exchange Advanced/Mailbox rights tab. He has full rights in the
Security tab. He has "send on behalf of" rights set on the Exchange
General tab. He has Owner rights set on most of the folders within
the mailbox.
Now, bear in mind I am not a programmer. grin This user keeps
referring to .send and .receive which means nothing to me.
So I know this is a long shot...... but if anyone has any idea of
what/where needs changing, please let me know...
Thanks,
Cappy |
|
| Back to top |
|
 |
Tom Libby
Joined: 05 Aug 2007 Posts: 1
|
Posted: Fri Jul 06, 2007 9:46 pm Post subject: Re: Long shot - email monitoring program written by MS quest |
|
|
Try this. http://www.mapilab.com/outlook/security/
"Cappy" wrote in message @q75g2000hsh.googlegroups.com...
> On Jul 2, 4:26 pm, Cappy wrote:
>> We have an application written by MS that is called Email Monitoring.
>> It takes emails from a source mailbox, and depending on (text?) in the
>> message, sorts them out to different public folders.
>>
>> Within the program, a parameter is set by picking the source mailbox
>> out of the GAL. The "name" of the source mailbox is written to the
>> registry as a string of letters and numbers, about 60 characters
>> long. So that variable is stored in the registry.
>>
>> A bit later in the program, the program has this line:
>
> (Let me finish typing... sheesh I dislike Google
> strongly...)
>
> Set AEUnattended =
> gMapiSess.GetAddressEntry(sourceMailboxVariableNameHeldInRegistry)
>
>
> The error that pops up is "Program is trying to access email addresses
> you have stored in Outlook." Do you want to allow this? Set time for
> up to 10 minutes to allow this.
>
> Once that time is set and the Yes button is clicked, for *each and
> every message* in this source mailbox, the following prompt is
> displayed:
>
> "A program is trying to send on your behalf. Do you want to allow
> this?"
>
> The user clicks Yes on this prompt for about 500 messages/day.
>
>
> We are using a security form set up in the Public Folders. In our lab
> environment, which pretty much mimics our production environment, we
> have set every single option under Programmatic Settings to
> automatically approve. The source mailbox and the user are listed in
> the members of the form. The user has about every single right on the
> source mailbox he could need. But I'm missing something.
>
> In the source mailbox settings in AD, the user has full rights on the
> Exchange Advanced/Mailbox rights tab. He has full rights in the
> Security tab. He has "send on behalf of" rights set on the Exchange
> General tab. He has Owner rights set on most of the folders within
> the mailbox.
>
> Now, bear in mind I am not a programmer. grin This user keeps
> referring to .send and .receive which means nothing to me.
>
> So I know this is a long shot...... but if anyone has any idea of
> what/where needs changing, please let me know...
>
> Thanks,
> Cappy
> |
|
| Back to top |
|
 |
James Vickers
Joined: 05 Aug 2007 Posts: 1
|
Posted: Tue Jul 10, 2007 5:04 am Post subject: Re: Long shot - email monitoring program written by MS quest |
|
|
I had similar problems when writing a VSTO add-in for Outlook. I ended up
using a free utility called REDEMPTION which can be used with VStudio, and
has a similar outlook model to the original.
The beauty is, there are no security warnings.
Forgive me if I am wrong, but I believe the security warning can be
supressed in Outlook versions 2003 and above in the mail client settings.
Unfortunately we have Outlook 2000, so I had to use REDEMPTION!
James
"Cappy" wrote:
> On Jul 2, 4:26 pm, Cappy wrote:
> > We have an application written by MS that is called Email Monitoring.
> > It takes emails from a source mailbox, and depending on (text?) in the
> > message, sorts them out to different public folders.
> >
> > Within the program, a parameter is set by picking the source mailbox
> > out of the GAL. The "name" of the source mailbox is written to the
> > registry as a string of letters and numbers, about 60 characters
> > long. So that variable is stored in the registry.
> >
> > A bit later in the program, the program has this line:
>
> (Let me finish typing... sheesh I dislike Google
> strongly...)
>
> Set AEUnattended =
> gMapiSess.GetAddressEntry(sourceMailboxVariableNameHeldInRegistry)
>
>
> The error that pops up is "Program is trying to access email addresses
> you have stored in Outlook." Do you want to allow this? Set time for
> up to 10 minutes to allow this.
>
> Once that time is set and the Yes button is clicked, for *each and
> every message* in this source mailbox, the following prompt is
> displayed:
>
> "A program is trying to send on your behalf. Do you want to allow
> this?"
>
> The user clicks Yes on this prompt for about 500 messages/day.
>
>
> We are using a security form set up in the Public Folders. In our lab
> environment, which pretty much mimics our production environment, we
> have set every single option under Programmatic Settings to
> automatically approve. The source mailbox and the user are listed in
> the members of the form. The user has about every single right on the
> source mailbox he could need. But I'm missing something.
>
> In the source mailbox settings in AD, the user has full rights on the
> Exchange Advanced/Mailbox rights tab. He has full rights in the
> Security tab. He has "send on behalf of" rights set on the Exchange
> General tab. He has Owner rights set on most of the folders within
> the mailbox.
>
> Now, bear in mind I am not a programmer. grin This user keeps
> referring to .send and .receive which means nothing to me.
>
> So I know this is a long shot...... but if anyone has any idea of
> what/where needs changing, please let me know...
>
> Thanks,
> Cappy
>
>
|
|
| Back to top |
|
 |
|
|