Trying to setup custom From email address on "Send Email" smart service on Appian 19.2 ,19.3.
Got a reference to link https://docs.appian.com/suite/help/17.1/Configuring_Custom_Email_Senders.html#Adding_a_Custom_From_Address which is on 17.1
the paths of files has been changes for newer versions.
Can you please help in steps to create and new paths
below steps taken with reference to 17.1
Navigate to C:\appian\deployment\web.war\WEB-INF\conf\process\email-address-config.xml
created a copy of it as email-address-config-custom.xml (should the file be left in same locaiton?)
what is the next step?
link regered to one other file in C:\appian\deployment\web.war\WEB-INF\resources\text\jsp\WEB-INF\conf\process\email-address-config_en_US.properties
what should be done here?
Discussion posts and replies are publicly visible
Note that the 17.1 Custom Email Senders documentation you linked to above, will also come out as "on behalf of". The reply is returned to the correct "From" setting however. We've been using this internally for years, in the process of converting to the new in-node configuration as Tejas linked to.
However there's a specific difference with the new functionality that's impossible to override. It boils down to the fact that the "sender" header or similar (i'll have to look again to remember if this is the correct one or not), is forced to use the environment-specific "admin email address" when sending using the new setup. The prior custom sender workaround which we've also been using for 5 years in production, allows emails to be sent as if they're actually coming from the user account passed in. In our system this caused immediate failures because at least one of the mail handlers along the line rejected the apparent mismatch. If you examine the headers for the new way compared to the old way, it'll become immediately obvious what the difference is - and no resolution has been provided for this (again, "because security" or something.)
Interesting, in our environment the header information as well as "on behalf of" is the same across both old and new configuration methods. Just ran a test and compared headers, they match..