<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>How to Set Up Automatic Replies on Emails from Process Model</title><link>https://community.appian.com/discussions/f/general/18272/how-to-set-up-automatic-replies-on-emails-from-process-model</link><description>We use process models to send a number of emails to our users. The emails come from addresses like processXXXXX@appiancloud.com. When a user replies to those emails, the email goes into a black hole. We would like to set up an automatic reply back to</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: How to Set Up Automatic Replies on Emails from Process Model</title><link>https://community.appian.com/thread/71917?ContentTypeID=1</link><pubDate>Wed, 05 Feb 2020 17:18:11 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:717e83a8-6200-4f30-b1ee-cbc551e807d5</guid><dc:creator>Mike Schmitt</dc:creator><description>&lt;p&gt;One option might be to work with Cloud support and set up a &amp;quot;custom sender&amp;quot; - that was the only way of having the sender&amp;#39;s name and email address appear different, until the relatively recent changeover of the Send Email node to allow the new customizations in the &amp;quot;sender&amp;quot; info.&amp;nbsp; The reason the old &amp;quot;custom sender&amp;quot; functionality works seems to be centered around how Appian sets the headers in the outbound email -- in the new, out-of-box functionality (as best i can remember), the environment&amp;#39;s &amp;quot;admin&amp;quot; email is always listed as the &amp;quot;sender&amp;quot; parameter, which at least in my case was why it was being flagged as spam by some recipients.&amp;nbsp; Our old-style custom sender setup never had this issue, as its headers are more consistent with how actual emails work.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I&amp;#39;d previously asked Appian Support to look into this, but they declined to change this behavior for some odd security reason - if i remember correctly, it&amp;#39;s something focused on not wanting Appian to be able to effectively &amp;quot;spoof&amp;quot; emails from other individuals.&amp;nbsp; So it&amp;#39;s a bit of a catch-22 at this point.&amp;nbsp; In the one project I attempted to use the new functionality in, I just ended up having to roll back to the old style since too many of their customers were reporting emails not coming through or getting flagged as spam.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>