Emails not sending on FME Flow Hosted

Considerations

When using the Emailer transformer or the Email action in Automations, emails may be sent successfully from on-premises FME Form or FME Flow but fail when running on FME Flow Hosted. This typically results in a 503 SMTPDataError, such as:

SMTPDataError: Could not complete request. Message: (503, b'5.5.2 Need rcpt command...

This issue can affect both workspaces using the Emailer transformer and Automations email actions or subscribers.
 

Why This Happens

The 503 error usually means that FME Flow Hosted cannot authenticate with your email server.

• On-premises FME works because its IP address is known to the email server, allowing authentication via SMTP Relay.
• FME Flow Hosted has a different, unknown IP, so the SMTP server rejects the email request.

How to Resolve It

1. Assign a Static IP to Your FME Flow Hosted Instance
   • If your FME Flow Hosted instance does not already have a static IP, assign one.
2. Register the Static IP with Your IT Department
   • Provide your new static IP to your IT team or whoever manages the email server.
   • They must add the IP to the SMTP Relay to allow authentication
3. Troubleshoot Further If Issues Persist
   • If emails still fail, pass the error details on to your IT team. They may need to adjust additional settings or delist the FME Flow Hosted IP
   • To get more detailed logs, attempt to send an email and check:
     • Resources > Logs > core > current > subscribers > email.log