KB-1887 Appian 18.4 custom email sender functionality "Return-Path" and "Sender" fields differ from the old custom email sender functionality

Jordan Horwat — Thu, 14 Mar 2019 19:57:56 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 3/14/2019 7:57:56 PM

Symptoms

When testing the new feature to Configure Custom Email Senders Inline, emails may not be received by certain mail servers. Upon further inspection, it is seen that the Sender and the Return-Path headers are not the same as the From header (which is the value configured in the Sender Email field configured in the Send Email Smart Service node).

For example, the Send Email Smart Service node is configured as follows:

However, instead of seeing "help@example.com" in the Sender header and the Return-Path header (as the pre-18.4 custom email senders would display), these headers display a different value such as "admin@siteurl.appianurl.com" as seen below:

Return-Path: <admin@siteurl.appianurl.com>
From: IT Service Desk <help@example.com>
Sender: <admin@siteurl.appianurl.com>

This may result in emails failing to deliver to certain servers if these servers only accept mail from the domain "*@example.com" and block mail from other domains such as "*@siteurl.appianurl.com" or "*@siteurl.appiancloud.com".

Cause

This is the intended design for the Appian 18.4 Configure Custom Email Senders Inline feature. Since the feature introduced the ability for any designer to select any sender email and sender display name, it became important to make it explicitly clear that the email is being sent by the system on behalf of an email address, rather than from the email address directly.

Therefore, the feature will set the Sender header and the Return-Path header to the #site value specified in the conf.mailhandler.ntf_sndr_addr property in custom.properties. In Appian Cloud, the default value for this property is of the form "admin@subdomain.appiancloud.com".

Action

Appian Self-managed

Change the conf.mailhandler.ntf_sndr_addr property in custom.properties to an email address with the desired domain. In this case, setting the value to admin@example.com will suffice.

Appian Cloud

Create an Appian Support case to request to change the notification sender email address property to an email address with the desired domain (rather than *@subdomain.appiancloud.com). In this case, requesting to set the value to admin@example.com will suffice.

Affected Versions

This article applies to Appian 18.4 and later.

Last Reviewed: March 2019

Tags: email, custom email senders, infrastructure

KB-1887 Appian 18.4 custom email sender functionality "Return-Path" and "Sender" fields differ from the old custom email sender functionality

Jordan Horwat — Thu, 14 Mar 2019 15:57:56 GMT

Revision 6 posted to Appian Knowledge Base by Jordan Horwat on 3/14/2019 3:57:56 PM

Symptoms

For example, the Send Email Smart Service node is configured as follows:

Return-Path: <admin@siteurl.appianurl.com>
From: IT Service Desk <help@example.com>
Sender: <admin@siteurl.appianurl.com>

Cause

Action

Appian On-Premise

Change the conf.mailhandler.ntf_sndr_addr property in custom.properties to an email address with the desired domain. In this case, setting the value to admin@example.com will suffice.

Appian Cloud

Affected Versions

This article applies to Appian 18.4 and later.

Last Reviewed: March 2019

Tags: email, custom email senders, infrastructure

DRAFT KB-XXXX 18.4 custom email sender functionality "Return-Path" and "Sender" fields differ from the old custom email sender functionality

Jordan Horwat — Wed, 13 Mar 2019 11:42:56 GMT

Revision 5 posted to Appian Knowledge Base by Jordan Horwat on 3/13/2019 11:42:56 AM

Symptoms

For example, the Send Email Smart Service node is configured as follows:

Return-Path: <admin@siteurl.appianurl.com>
From: IT Service Desk <help@example.com>
Sender: <admin@siteurl.appianurl.com>

Cause

Action

Appian On-Premise

Change the conf.mailhandler.ntf_sndr_addr property in custom.properties to an email address with the desired domain. In this case, setting the value to admin@example.com will suffice.

Appian Cloud

Affected Versions

This article applies to Appian 18.4 and later.

Last Reviewed: March 2019

Tags: email, custom email senders, infrastructure

DRAFT KB-XXXX 18.4 custom email sender functionality "Return-Path" and "Sender" fields differ from the old custom email sender functionality

Jordan Horwat — Fri, 08 Mar 2019 16:18:55 GMT

Revision 4 posted to Appian Knowledge Base by Jordan Horwat on 3/8/2019 4:18:55 PM

Symptoms

For example, the Send Email Smart Service node is configured as follows:

Return-Path: <admin@siteurl.appianurl.com>
From: IT Service Desk <help@example.com>
Sender: <admin@siteurl.appianurl.com>

Cause

Therefore, the feature will set the Sender header and the Return-Path header to the #site value specified in the conf.mailhandler.ntf_sndr_addr property in custom.properties. In Appian Cloud, the default value for this property is of the form "admin@subdomain.appiancloud.com".

Action

Appian On-Premise

Change the conf.mailhandler.ntf_sndr_addr property in custom.properties to an email address with the desired domain. In this case, setting the value to admin@example.com will suffice.

Appian Cloud

Affected Versions

This article applies to Appian 18.4 and later.

Last Reviewed: March 2019

Tags: email, custom email senders, infrastructure

DRAFT KB-XXXX 18.4 custom email sender functionality "Return-Path" and "Sender" fields differ from the old custom email sender functionality

Jordan Horwat — Fri, 08 Mar 2019 16:17:10 GMT

Revision 3 posted to Appian Knowledge Base by Jordan Horwat on 3/8/2019 4:17:10 PM

Symptoms

For example, the Send Email Smart Service node is configured as follows:

Return-Path: <admin@siteurl.appianurl.com>
From: IT Service Desk <help@example.com>
Sender: <admin@siteurl.appianurl.com>

Cause

Action

Appian On-Premise

Change the conf.mailhandler.ntf_sndr_addr property in custom.properties to an email address with the desired domain. In this case, setting the value to admin@example.com will suffice.

Appian Cloud

Create an Appian Support case to request to change the notification sender email address property to an email address with the desired domain (rather than the *@appiancloud.com domain). In this case, requesting to set the value to admin@example.com will suffice.

Affected Versions

This article applies to Appian 18.4 and later.

Last Reviewed: March 2019

Tags: email, custom email senders, infrastructure

DRAFT KB-XXXX 18.4 custom email sender functionality "Return-Path" and "Sender" fields differ from the old custom email sender functionality

Jordan Horwat — Wed, 06 Mar 2019 17:21:17 GMT

Revision 2 posted to Appian Knowledge Base by Jordan Horwat on 3/6/2019 5:21:17 PM

Symptoms

When testing the new feature to Configure Custom Email Senders Inline, emails may not be received by certain mail servers. Upon further inspection, it is seen that the Sender header and the Return-Path header do are not the same as the Sender Email address field configured in the Send Email Smart Service node.

For example, the Send Email Smart Service node is configured as follows:

However, instead of seeing "help@example.com" in the Sender header and the Return-Path header, these headers display a different value such as "admin@siteurl.appianurl.com" as seen below:

Return-Path: <admin@siteurl.appianurl.com>
From: IT Service Desk <help@example.com>
Sender: <admin@siteurl.appianurl.com>

Cause

The Appian 18.4 Configure Custom Email Senders Inline feature was designed this way. As the feature introduced the ability for any designer to select any sender email and sender display name, it was important to make it explicitly clear that the email is being sent by the system on behalf of an email, rather than from the email directly. Therefore, the feature will set the Sender header and the Return-Path header to the #site value specified in custom.properties (typically admin@siteurl.appianurl.com). This is the intended behavior of the 18.4 custom email sender, and designers cannot circumvent this.

Action

Appian On-Premise

Set the conf.mailhandler.ntf_sndr_addr= property in custom.properties to an email address with the desired domain. In this case, setting the value to admin@example.com will suffice.

Appian Cloud

Create an Appian Support case to request to change the notification sender email address property to an email address with the desired domain. In this case, requesting to set the value to admin@example.com will suffice.

Affected Versions

This article applies to Appian 18.4 and later.

Last Reviewed: March 2019

Tags: email, custom email senders, infrastructure

DRAFT KB-XXXX 18.4 custom email sender functionality "Return-Path" and "Sender" fields differ from the old custom email sender functionality

Jordan Horwat — Tue, 05 Mar 2019 23:02:32 GMT

Revision 1 posted to Appian Knowledge Base by Jordan Horwat on 3/5/2019 11:02:32 PM

Symptoms

When testing the new feature to Configure Custom Email Senders Inline, emails may not be received by certain mail servers. Upon further inspection, it is noticeable that the Sender header and the Return-Path header do are not the same as the Sender Email address field configured in the Send Email Smart Service node.

For example, the Send Email Smart Service node is configured as follows:

However, instead of seeing "help@example.com" in the Sender header and the Return-Path header, these headers display a different value such as "admin@sitename.appian.com" as seen below:

Return-Path: <admin@sitename.appian.com>

From: IT Service Desk <help@example.com>
Sender: <admin@sitename.appian.com>

To: <recipient@example.com>

Cause

The Appian 18.4 Configure Custom Email Senders Inline feature was designed this way. As the feature introduced the ability for any designer to select any sender email and sender display name, it was important to make it explicitly clear that the email is being sent by the system on behalf of an email, rather than from the email directly. Therefore, the feature will set the Sender header and the Return-Path header to the #site value specified in custom.properties (typically admin@sitename.appian.com). This is the intended behavior of the 18.4 custom email sender, and designers cannot circumvent this.

Action

Affected Versions

This article applies to Appian 18.4 and later.

Last Reviewed: March 2019

Tags: email, custom email senders, infrastructure