MAPILab Outlook Advanced Security question

[Paul D.Smith]

Outlook 2000 and MAPILab...

I have this all working and I no longer get the irritating security prompt
but I have a question that I haven't yet answered.

I got my program (lets call it FRED) to send by running FRED and when the
Outlook security prompts and Advanced Security prompts came up, simply
saying "yes" and allowing it to work. Now "FRED" sends happily without any
nasty popups.

But here's the kicker - the "exe/module/dll" which was sending was not FRED,
rather it looked to me like some sort of common library. So rather than
having setup "Only FRED can send", I suspect I've set-up "Anyone using this
library can send".

Have I missed a trick here? Could I somehow have found the top level
exe/module/dll (FRED) and enabled that so that anyone else trying to send
would be blocked?

Thanks for your help or suggestions, even if just a reference to the bit of
the instructions that I missed!

Paul DS.

 

[Paul D.Smith]

Christian,

I don't want to appear rude, but perhaps you should take a closer look at
what is on offer at the link you provided. There is only the possibility of
"leaving a suggestion", which is not what I require. I have read the FAQs
and they don't address my question.

Since this is a group for Outlook users, and I suspect I'm not the only
MAPILab user on this NG, it is possible that others have hit the same
problem and already solved it, thus my post.

Regards,
Paul DS.

 

[Brian Tillman]

But here's the kicker - the "exe/module/dll" which was sending was
not FRED, rather it looked to me like some sort of common library.
So rather than having setup "Only FRED can send", I suspect I've
set-up "Anyone using this library can send".

Easily tested by creating a second instance of FRED, call it GEORGE and see
if it prompts or not, or so it seems to me.

 

[Diane Poremsky [MVP]]

right click on the module and see what installed it - only apps using that
module can send and it's unlikely a virus would use the module. Many
installations place them in the common folder but are the only one using it.
Also note that provided you practice other safety measures, the chances of
something using that to send is slim and probably worth it the slightly
lower security model.

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Coauthor, OneNote 2003 for Windows (Visual QuickStart Guide)
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/



Subscribe to Exchange Messaging Outlook newsletter:
(e-mail address removed)

 

[Paul D.Smith]

Easily tested by creating a second instance of FRED, call it GEORGE and see
if it prompts or not, or so it seems to me.

Good idea - too simple for me to think of ;-) I'll give it a try.

Paul DS.

 

[Paul D.Smith]

....snip...

Sorted. I don't know why but the first time I sent e-mail from my program
(call is FRED), it was undetected by MAPILab which was only able to identify
the calling (common) DLL. This led me to at least temporarily open a
possible security hole via this common DLL.

Last night I deleted the existing MAPILab action and re-ran FRED. This time
MAPILab explicitly identified "FRED" as the sender and I was able to enable
FRED and instead of the common library.

Maybe I should have rebooted or something after installing MAPILab, who
knows. But what I needed is certainly possible.

BTW, there is some help installed as part of the program which I've read but
as yet not fully understood. This may indicate how I should have proceeded
initially which may help others.

Paul DS.