The following example describes how to schedule febooti Command line mail tool so that a report can be generated from within another application and sent to the appropriate destination. The reporting application in this context can be defined as any application that accepts some inputs, processes them and generates some form of output. This can be anything from a simple batch file to a corporate application.
The application creating report in this example is assumed to accept command-line parameters and will generate a report in a known directory. The information contained in this report can be of any form, possibly some data gathered and generated from a database.
This information used in combination with the scheduling commands of febooti Command line mail tool for Windows allows a convenient creating of batch file in order to achieve this task.
The primary focus of this example is to generate a generic solution that can be used across a variety of applications in conjunction with febooti Command line email tool.
Solution:
@echo off
rem Launch report-application.exe with 4 parameters... report-application.exe input.txt output.txt file1.txt file2.txt
The following points describe the process of sending email with reports:
1: The first line executes the report application. It is assumed that the application takes an input file as the first parameter and processes and produces the report by sending the results to three separate files as stated in the solution.
2: The second line makes a call to email tool to send command line mail.
3: The -SERVER parameter indicates SMTP server address.
4: The -FROM, -TO and -SUBJECT parameters are self-explanatory and standard arguments when calling Command line email tool for Windows to send DOS prompt mail.
5: The -ATTACH argument takes a filename as a parameter and attaches the specified file to the email that is to be sent. Sometimes it is worth attaching text documents rather than pasting the content in the email body, because different email clients may use different character encoding schemes. This may result in the client email program not interpreting the character set correctly and displaying different results. Each file that is to be attached will have to have a separate -ATTACH parameter appended. It is worth noting that long filenames and filenames with spaces must be enclosed in double quotes for the command to work correctly.
