2.4.5 Cautionary notes on the mail system linkage function

This subsection gives some cautionary notes on the mail system linkage function.

Cautionary notes on using the mail system linkage function on a UNIX host

• A mail file where mail is stored when an error occurs is created for each package activated by the service. The mail file is usually created in /var/opt/jp1ajs2/sys/infoagt/tmp/mail/errmail.

• During email reception monitoring, emails that meet the monitoring conditions of multiple email reception monitoring jobs are stored in the email storage file specified in the environment settings file. The emails are stored if saving emails is specified for at least one of the email reception monitoring jobs.

• JP1/AJS3 does not automatically delete the passing information storage file, mail storage file, mismatching mail storage file, received-mail list file, or error mail file created by the email reception monitoring job. Delete these files manually once they have become unnecessary, because they reduce the amount of available disk space.

• Email reception monitoring is executed after an email reception monitoring job starts. No emails are monitored until at least one email reception monitoring job starts.

• Although the mail system linkage function monitors mail files at the specified interval, if the mail file contains multiple emails, it picks up the emails one by one. It takes about one second to handle each email.

• Linefeed codes in the body of received email are treated as follows:

  If a character string matches a character string specified as a monitoring condition but is split by a linefeed code, the condition is judged as not satisfied.

  Example:

  Expected string: ABC

  String in the body of received email: A<linefeed>BC

  If a linefeed code appears before or after a character string that matches a character string specified as a monitoring condition, the condition is judged as satisfied:

  Example

  Expected string: ABC

  String in the body of received email: ABC<linefeed>

• If you specify multi-byte characters (Japanese) or single-byte katakana characters in the subject line or message text in the definition of an email sending job, characters will be unreadable and the email will not be sent successfully. Therefore, do not specify multi-byte characters (Japanese) or single-byte katakana characters in the subject line or message text. Note, however, that if you specify a message text file containing the text of an email converted to JIS encoding, the file can be sent successfully.

• The sendmail function might use a program that restricts the operation of mail delivery functions that are set up later than the sendmail function. That program might prevent the JP1/AJS3 mail delivery function from running normally. In such a case, see the documentation for the program that restricts mail delivery functions and set up the program so that the JP1/AJS3 mail delivery function can run normally. For details about the mail delivery function, see 2.4.3 Setting up the mail delivery function.

  Example:

  Emails cannot be delivered because the jpomailrecv command, which is a part of the mail delivery function, cannot be started from a sendmail alias because of the smrsh limitation on sendmail.

  <Action to be taken>

  Create a symbolic link to the jpomailrecv command.

  Example of creating a symbolic link with the ln command:

  ln -s /opt/jp1ajs2/bin/jpomailrecv /etc/smrsh/jpomailrecv

  Note that the location for creating the symbolic link might vary according to the system environment. Note also that the smrsh limitation described above is only an example. For details about the sendmail limitations, see the sendmail Help and other sendmail documentation.

  For details about the ln command, see the documentation for the OS.

  For details about aliases, see the SMTP mail system documentation.

  For details about the jpomailrecv command, see jpomailrecv (UNIX only) in 2. Commands Used during Setup in the manual JP1/Automatic Job Management System 3 Command Reference.

• Attached files cannot be specified for an email sending job.

  To run an email sending job on a UNIX host, you must specify UNIX for Platform in the definition of the email sending job. When UNIX is specified for Platform, you will not be able to specify any attached files for the email sending job.

  If PC (Windows) is specified for Platform in the definition of the email sending job, you can specify attached files for the email sending job. However, if the email sending job with attached files specified is run on a UNIX host, the job ends abnormally because the specified platform type is invalid.

To Page Top