Skip to main content
  • EN

Hello to the community,

I successfully set up an fme flow automation with a final action to send out an smtp email via our email server. The connection to this email server with the “SMTP Account” is valid and successfully tested and mails were sent. But the “SMTP Account” is not setup to receive emails at all.

When i try to change the parameter “Email From” in the “email send” action to a different mail address than the used “SMTP Account”, our mail server denies to send out the email as a different user.
This is for security reasons.

But i want the email recipients to be able to just reply to an incoming email without changing the mail address. Further I don’t want to place a hint in every mail that it is not possible to simply reply to this mail without changing the address.

Is there another way to change the smtp header parameter “replyto” for the email send action in fme flow?

Thank you very much for any help and hints

best regards

Jürgen

 

 

There are no advanced or hidden parameters documented for customizing email headers like "Reply-To" in the email send action. The "Email From" field is intended to match the authenticated SMTP account, and most mail servers will reject emails if you try to set a different "From" address for security reasons.

 

If you require a custom "Reply-To" header, a common workaround is to use the Emailer transformer within an FME workspace (FME Form), which does support setting a "Reply-To" address. You can then run this workspace from your automation instead of using the built-in email action.

Hello j.botterill,

thank you very much for your post and advice. This really helped me to find the needed solution with a reply_to header in the Emailer-Transformer. I already had tried the Emailer-Transformer, but got error messages when running it in a flow automation process.
Yesterday I first updated my flow server and form installation both to the latest version 2025.1.0.1. Today I added the Emailer-Transformer to my workspace and configured it. When publishing the workspace to the flow server today, the Emailer-Transformer was uploaded to the server too, what probably did not happen before, since my flow server was a 2024 version and my form version was a 2025 version already. Guess this was the main cause why the automation did not work before with the E-Mailer Transformer. Thanks again for this great support in short time.

 

Yeah you need to have sames Form and Flow version. Without this compatibility, you can expect the unexpected

Community Stats

31,758
Posts
120,642
Replies
39,383
Members

Latest FME

Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.