...

• Required arguments include the to argument to specify the recipient of mail.
• Any other arguments are optional, provided that a job resource is used that specifies connection details to your mail server, see below. Otherwise individual settings such as the SMTP host, SMTP port etc. can be specified from arguments.
• Select the check box provided with each argument if you want this argument to be added to the arguments of the mail job MailJob template.

When hitting the "Submit" button the wizard adds the required arguments to your the job which should look like this:

...

• from individual variables as configured using the job wizard,
• by using job resources JS7 - Job Resources.

Use of Job Resources for Mail Settings

...

• The variable names specified are selected to match those used with the JITL MailJob template.
• Note the use of variable names that start with mail.smtp.
  • These variable names correspond to Java properties available with the JavaMail API. Any of the JavaMail properties can be specified.
  • You will find a full list of the available mail.smtp. properties from https://javaee.github.io/javamail/docs/api/com/sun/mail/smtp/package-summary.html
  • Required properties include (but are not limited to):
    • mail.smtp.host
    • mail.smtp.port
  • When using a secure SSL connection consider that:
    • for use of TLS the mail.smtp.starttls.enable argument has to be used with the value true, for use with SSL the mail.smtp.ssl.enable argument has to be used with the value true.
    • different ports might be in use: for unencrypted connections port 25 is frequently used, for TLS connections port 465 or 587 is frequently used, for SSL connections port 587 is frequently used.
    • optionally use the mail.smtp.ssl.protocols argument with a value such as TLSv1.2 or TLSv1.1,TLSv1.2 to specify one or more protocol versions that limit handshake with the mail server to the protocol versions specified. Depending on the Java version in use and possible modifications of the java.security file a number of protocols could be enabled that might not match the mail server's capabilities. Typically SSL handshaking starts from the highest protocol version accepted by both parties. However, it is not guaranteed that protocol negotiation will work perfectly. In such a situation it is recommended that the protocol version is specified using this argument.

...