polletfa
asked on
How to send emails programmatically using MAPI calls without user confirmation
Hi everybody,
I'm working on a software which needs to send emails. I plan to use MAPI calls to do this (precisely, I want to use the PowerBuilder mailSession object which is based on MAPI).
This however requires the user to confirm that the program is allowed to send the email, each time that a MAPI call is done.
Is it possible to disable this? I found some software to do that (ClickYes and Outlook Security Manager) but I would prefer a solution which does not require buying an extra software.
I didn't found much information by myself and I don't know much about MAPI yet.
Some information about the "context":
1) The software will be running as a service, in the background -- so without any user. This is why I really need to shut off these security settings.
2) The email client is Outlook, the server is Exchange. Other email protocol could be used in the future, but this is no strong requirement at the time
3) The users have strong security requirements. It would then be much better if the security warnings could be disabled for this software only but still appear in case another software tries to send an email.
Thanks a lot!
Best Regards,
Fabien Pollet
I'm working on a software which needs to send emails. I plan to use MAPI calls to do this (precisely, I want to use the PowerBuilder mailSession object which is based on MAPI).
This however requires the user to confirm that the program is allowed to send the email, each time that a MAPI call is done.
Is it possible to disable this? I found some software to do that (ClickYes and Outlook Security Manager) but I would prefer a solution which does not require buying an extra software.
I didn't found much information by myself and I don't know much about MAPI yet.
Some information about the "context":
1) The software will be running as a service, in the background -- so without any user. This is why I really need to shut off these security settings.
2) The email client is Outlook, the server is Exchange. Other email protocol could be used in the future, but this is no strong requirement at the time
3) The users have strong security requirements. It would then be much better if the security warnings could be disabled for this software only but still appear in case another software tries to send an email.
Thanks a lot!
Best Regards,
Fabien Pollet
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Ok, thanks to you both.
I don't quite understand why Microsoft didn't provide a way to configure those settings. I guess I'll have to work with that anyway.
I don't quite understand why Microsoft didn't provide a way to configure those settings. I guess I'll have to work with that anyway.
ASKER
In case someone is intereste, here's a workaround:
http://www.everythingaccess.com/tutorials.asp?ID=Outlook-Send-E-mail-Without-Security-Warning
It's not very simple but it works (with Outlook 2003 and later only)
1) Create an Outlook macro to send a mail
2) Change the security level for macros (or somehow configure Outlook so that it trusts the macro)
3) Call the macro using OLE automation (the link gives an example with Access VBA, but I tried it with PowerBuilder)
http://www.everythingaccess.com/tutorials.asp?ID=Outlook-Send-E-mail-Without-Security-Warning
It's not very simple but it works (with Outlook 2003 and later only)
1) Create an Outlook macro to send a mail
2) Change the security level for macros (or somehow configure Outlook so that it trusts the macro)
3) Call the macro using OLE automation (the link gives an example with Access VBA, but I tried it with PowerBuilder)
ASKER
I would prefer to stay on MAPI because the software will eventually be deployed within several different companies and it will be better if the customers may use whatever email protocol they want.
I keep that in mind anyway as a backup solution.
Thanks.