All the Image attachments are first saved. These are referenced only from within HTML attachments and will be incorporated during HTML conversion to TIF, so no $fax_filename command is required for them.
The list of attachments to be added as a $fax_filename (so far containing only rich text bodies) is then extended with the remaining attachments. For each attachment:
•attachments extracted from TNEF are included
•attachments identified as inline attachments in the message are included
•attachments with extension GCT. GTT or CVR among these attachments are marked as cover sheet attachments
•if sender option 23 (save unverified) is set, attachments which are contain S/MIME public keys but not as part of a signed message are converted to .CER, saved, and then excluded from the list to be faxed.
•attachments marked as excluded embedded MIME messages or Microsoft protected message attachments are excluded from the list to be faxed.
•the attachment file is saved. Failure to save initiates a GWSAVERROR notification but does not cause the SMTP message processing to be stopped
•the first attachment marked as a cover sheet is identified as a cover sheet to be used as such provided that sender option 2 (no cover sheet) is not set. Other attachments marked as a cover sheet will in included as $fax_filename entries
•variables are added to the FS file to identify the attachment names
A count of the saved attachment files is added to the FS file as SMTP_ATTACH_COUNT
The SMTP priority value is used to assign a TOSEND queue for the FS file, and then overridden by the value from $fax_tosend saved from the sender template, if present.
If sender option 2 (no cover sheet) is not set, and no cover sheet is present in the attachments then the configured default cover sheet is assigned as the cover sheet to be used.
The number of FS files to be written is determined from the number of recipients and special recipients, and the pathname for the FS file is determined from the chosen TOSEND queue.
If the FS file is for a special recipient it is prepared as follows:
•any sender notification options are cleared
•the saved memo text for special recipients, if present, overrides any other memo text saved from the message.
•the recipient template is reloaded. It there is no recipient template or it fails to load, error (15), and notification GWLOADERROR is initiated.
•The $email_decrypt_keyfile and $authenticate commands are removed, if present.
•If present, $var_def SMTP_PASSWORD is removed.
•If recipient option 5 (requires valid sender) is set, this causes a check for a valid sender; the variable SMTP_OPTIONS is always then removed. Lack of a valid sender causes error (18).
•If there is no $worker_box command, error (17); otherwise the need to create a worker box FS is recorded
•If a $fax_tosend command is present it is removed, but its value is used to update the path which will be used for the FS file.
•The recipient template (as modified) then replaces the sender template as the basis of the FS file.
The count of processed recipients is then incremented, because an FS file will now be assembled:
•A comment is added to identify the Gateway version
•If there is a sender template, commands $fax_origin, $fax_user, $fax_sender, $fax_status1 and $fax_status2 are the active template; otherwise a default values are used..
•If we are creating a $worker_box FS file, this command is added, along with a $fax_cover command if a fax cover has been found in the message. Otherwise the following commands are added:
▪$fax_filename commands for each attachment
▪a $fax_receiver command using the first found of the Subject header (after data has been removed from it), the first recipient e-mail alias, or the recipient e-mail address.
▪a $fax_phone command (replacing any in the template) using the recipient fax phone number.
▪a $fax_cover command if a fax cover has been found in the message.
•if a message body is present and has not been saved as an attachment, its contents are written into MEMOx variables, and a count of these $var_def commands is added as SMTP_MEMO_COUNT.
•The SMTP_ variables describing the message are then written to the FS file as $var_def commands.
•If sender options 3 (save message headers) is set, the headers from the SMTP message are written as SMTP_HEADERn variables.
•if this is not a special recipient and sender notification options are enabled, A NOTIFY_SENDER variable is written to the FS file with a value to indicate the SMTP_NOTIFY_OPTIONS settings, and a command $fax_post-process notify_smtp infoboxend is written to the FS file.
•The remaining commands from the active template file are added to the FS file.
•Finally, the FS file is written. A write error causes error (3).
If there are multiple FS files to write, no further files are written after an error. If no FS files were written, error (3) results.
