Skip to main content
Question

Best Practices for Preventing FME Server Executing Workspace Based On An Email Reply All


Forum|alt.badge.img+1

I want to execute a workspace in FME Server by an email that is Bcc'd to FME Server. However, I am worried that a Reply All from both internally or externally may trigger the workspace to be executed again. Any thoughts or suggestions on best practices to prevent this from occurring? Thank you in advance.

4 replies

david_r
Celebrity
  • October 17, 2018

Are you sure this will be a problem? If FME Server is Bcc'd, then that email address won't be visible to the other receivers, and thus not included in any replies, forwards, etc.


Forum|alt.badge.img+1
david_r wrote:

Are you sure this will be a problem? If FME Server is Bcc'd, then that email address won't be visible to the other receivers, and thus not included in any replies, forwards, etc.

Valid point. I will have to thoroughly test.

 

 


Forum|alt.badge.img+1
david_r wrote:

Are you sure this will be a problem? If FME Server is Bcc'd, then that email address won't be visible to the other receivers, and thus not included in any replies, forwards, etc.

I do not believe it used to be that way (don't know how far back Bcc's were still included) this was the concern of my management. However, you are right. As of now, by default (at least in Outlook as tested) Bcc'd recipients are not included on replies, reply all, forwards, etc.

 

 


david_r
Celebrity
  • October 17, 2018
dane_stephenson wrote:
I do not believe it used to be that way (don't know how far back Bcc's were still included) this was the concern of my management. However, you are right. As of now, by default (at least in Outlook as tested) Bcc'd recipients are not included on replies, reply all, forwards, etc.

 

 

For what it's worth, it's worked that way as long as I've been online, which is about since 1992 :-)

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings