Email - SMTP

The Email - SMTP trigger allows you to configure email addresses to receive messages from SMTP email clients, and send the email data toFME Flowas JSON.

The Email - SMTP trigger has two output ports. The success port (✔) can send a message if the trigger receives successfully. The failure port (x) can send a message if the trigger fails to receive.

To use the Email - SMTP trigger, you must first make sure yourFME Flowis properly configured to receive email. For more information seeConfiguring FME Flow to Receive Email.

Note  "> NoteThe Email - SMTP trigger is not supported in afault tolerantinstallation ofFME Flow. Consider using theEmail - IMAPtrigger instead.

Parameters

Note  "> NoteSee alsoWorking with Parameters in Automations Workflows.
Tip  "> TipTo test that your parameters work as expected, clickValidate.
  1. Email User Name:
    • To emailFME Flowdirectly, enter the user account name to receive the email on theFME Flowhost system. For example, if theFME Flowhost name is services.internal, and the email address is user@services.internal, enteruser.
    • To email a separate server that relays the email toFME Flow,输入电子邮件地址的用户名on the email server. For example, if the email address is user@company.com, enteruser.
      • Note  "> NoteA rule must be configured on the email server that relays emails for the specifiedEmail User Nameon toFME Flow. The rule must specify theFME Flowmachine name and SMTP port. To determine the port, seeConfiguring FME Flow to Receive Email.
    2. Note  "> NoteEmail addresses are case-insensitive.
  2. Download Attachments To: (Optional) Specify a location to download any attachments.
    • Select aResourcesfolder (...).
    • Enter your own location. Directory paths must use forward slashes (/) or escaped backslashes (\\).

      • If not specified, any attachments are saved to the following default temporary folder:

      $(FME_SHAREDRESOURCE_SYSTEM)/temp/emailattachments/<date>-<automation_name>-<email_subject>-<automation_id>\<filename>.

      If specified, the following subfolder is created in the specified location:

      <specifiedLocation>/<date>-<automation_name>-<email_subject>-<automation_id>/<filename>

      If<specifiedLocation>is invalid, attachments are saved to the default temporary folder.

      If<automation_name>,<email_subject>, or<filename>contains invalid characters, these characters are stripped. Invalid characters are\/:*?\"<>|&='+%#. Whitespace characters are converted to_.

Output Attributes

See Also

Attribute Description
time Event time
source Event type
error.type

(Failure port only) Error type:

  • InvalidMessage: An error occurred while configuring this component, such as missing or malformed values.
  • DeadLetter: An error occured while connecting to an external resource. Examples may include connection issues, invalid credentials, or generic external resource exceptions.
error.message (Failure port only) Error message
email.subject (Success port only) Email subject
email.body (Success port only) Email body
email.attachment

(Success port only) Email attachment

Note  "> NoteIf the email contains multiple attachments, this attribute accesses only the first attachment. To access multiple attachments, use email.attachments instead.
email.attachments (Success port only) Path to directory containing all email attachments
email.sent (Success port only) Time sent
email.received (Success port only) Time received
email.from (Success port only) Sent from address
email.to (Success port only) Sent to address
email.contentType (Success port only) Email body content type

Email - SMTP Trigger Log Files

Resources\logs\core\current|old\publishers\

fmepublishers.log

  • Shows some additional communication between SMTP Relay andFME Flow.

email.log

  • Shows Email Received - SMTP trigger and configuring email accounts