As this issue is trending on our support Knowledgebase (in the Rocket Community
), I thought I would share it here with some extras.
If you would like more info on emails from CorVu Schedules please let me know.
Sending email notifications
from CorVu CorBusiness, especially from a Scheduled task is a powerful way to distribute business info to users, including those who may not have CorVu installed. The emails generated from a scheduler task can contain attachments of pdf, html, csv or other outputs generated from a CorVu query or report. You can also choose between plain text or HTML for the body message, which allows you to insert formatting and web-links to the files generated by your scheduler tasks. This way you can send users html links to the scheduler generated output instead of sending huge Excel files or PDFs to clog up their email systems and inboxes.
The popular issue at the moment is how to use MS Outlook in Office 365
to send your CorVu emails via a secured smtp. Enhanced security requirements often block the simple mail transfer protocol (smtp) to port 25 (default) or the pdf/Excel file attachments. So we have updated the email dll code to handle the common security levels. This has to be defined in the properties file called cvmapi32.ini located in the sending PC's Windows directory. Below is the full knowledge article, followed by some added info. I hope you find it useful.
---CorBusiness uses the cvmapi32.ini file that is located in the user Windows directory to configure and control communication between CorBusiness and the SMTP server.Office 365 requires the use of TLSv1 Channel Protocol, the SMTP channel of STARTTLS and using port 587 of the SMTP Server.Here is an example cvmapi32.ini file that is known to work with Office 365. Update the address and password fields with the appropriate email address and password:
Each section starts with [sectionname]. The comment lines are prefixed with a ;
; yes or no
;plain, starttls, smtps or ssl
;plain sslv2 sslv3 sslv23 tlsv1
..no changes required use existing settings...The address option above needs to be a valid user on the Office 365 server as it is used as the From address of the email. By default Office365 will reject any emails where the From address is not valid on the mail server. Passwords are case-sensitive as well.To verify that emails are going through, open any Query or Report in CorBusiness and select File -> Send and then fill in the appropriate fields in the Send Email dialog box. If you do not receive any errors messages, but the email does not arrive at the destination email address, first check the spam folder to see if it ended up there, otherwise have your mail administrator check the logs on the Office 365 instance to see if there are any error messages in the log files.If File -> Send is grayed out, then email is not configured correctly in CorBusiness. Please create a support case in the Rocket Community Portal to have support help investigate the problem.
More info.The mapi32.dll is used to send via SMTP rather than MAPI. This means it will work regardless of the email client installed on the laptop/PC/server, and it communicates directly with the email server. Use the latest version of the mapi32.dll - version 184.108.40.206, which is included in the cvupd32,exe upgrade for CorVu 5.40. Also if you are using the CorVu Scheduler Service to set the timings for your scheduler executions then the mapi32.dll file needs to be placed in the CORVU\SCHService folder.
(When running manually then corvu32.exe looks in the CORVU program folder for mapi32.dll)
The configuration can contain the following entries in the smtpchannel / channelprotocol fields;
The default for starttls (if no channel protocol is specified) is "tlsv1"The default for SMPTS/SSL(if no channel protocol is specified) is "sslv3"
|if smtpchannel is set to:
|| then channelprotocol can be set to
||none (plain text)
||tlsv1, tlsv1.1, tlsv1.2
||sslv1, sslv2, sslv3, sslv23
||sslv1, sslv2, sslv3, sslv23
If you do not need to use the added security then set both smtpchannel and channelprotocol to plain
, then you do not need to provide a password. However you may still need to ask your Email Administrator to allow your computer (ip address) to send lots of emails, especially if you are sending out batches which may look suspiciously like spam.