KB-1757 Receive message event fails when using a routing alias with recipient name in 'Bcc' field

Parmida Borhani — Wed, 24 Oct 2018 23:54:52 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 10/24/2018 11:54:52 PM

Symptoms

The Receive Message Event fails when all the following conditions are met:

Destination process model is specified with the routing alias field conf.mailhandler.alias.<recipientName>=<routing> in custom.properties.
A destination key/value pair such as [DestinationPMUUID=<ProcessModelUUID>] is not being used when sending emails.
The recipient name is specified in the 'Bcc' field of an email.

The following error also appears in mail-listener.log:

[Appian EmailHandlerBean - 64] ERROR com.appiancorp.process.emailpoller.EmailHandlerBean - Error receiving message in EmailHandlerBean MDB
javax.mail.MessagingException: Message could not be sent;
 nested exception is:
 com.appiancorp.messaging.ProcessRouteMissingException: APNX-1-8001-001: No Process Routing Information Provided: Needs one of DestinationEventPersistentID, DestinationProcessID, DestinationPMID, DestinationPMUUID

Cause

This is unsupported behavior in Appian.

Workaround

The Receive Message Event still functions properly if used in the following ways:

Specify recipient name in the 'To' email field instead of 'Bcc'
Specify recipient name in the 'Cc' email field instead of 'Bcc'
Specify [DestinationPMUUID=<ProcessModelUUID>] in the subject line or body of the email when recipient name is in the 'Bcc' email field.

See the Routing Email Messages section of the Mail Server Setup guide for more details on using a destination key/value pair for email routing.

Affected Versions

This article applies to Appian 17.4 and later.

Last Reviewed: October 2018

Tags: email, infrastructure

DRAFT-XXXX Receive message event fails when using a routing alias with recipient name in 'Bcc' field

Parmida Borhani — Wed, 24 Oct 2018 19:51:09 GMT

Revision 10 posted to Appian Knowledge Base by Parmida Borhani on 10/24/2018 7:51:09 PM

Symptoms

The Receive Message Event fails when all the following conditions are met:

Destination process model is specified with the routing alias field conf.mailhandler.alias.<recipientName>=<routing> in custom.properties.
A destination key/value pair such as [DestinationPMUUID=<ProcessModelUUID>] is not being used when sending emails.
The recipient name is specified in the 'Bcc' field of an email.

The following error also appears in mail-listener.log:

[Appian EmailHandlerBean - 64] ERROR com.appiancorp.process.emailpoller.EmailHandlerBean - Error receiving message in EmailHandlerBean MDB
javax.mail.MessagingException: Message could not be sent;
 nested exception is:
 com.appiancorp.messaging.ProcessRouteMissingException: APNX-1-8001-001: No Process Routing Information Provided: Needs one of DestinationEventPersistentID, DestinationProcessID, DestinationPMID, DestinationPMUUID

Cause

This is unsupported behavior in Appian.

Workaround

The Receive Message Event still functions properly if used in the following ways:

Specify recipient name in the 'To' email field instead of 'Bcc'
Specify recipient name in the 'Cc' email field instead of 'Bcc'
Specify [DestinationPMUUID=<ProcessModelUUID>] in the subject line or body of the email when recipient name is in the 'Bcc' email field.

See the Routing Email Messages section of the Mail Server Setup guide for more details on using a destination key/value pair for email routing.

Affected Versions

This article applies to Appian 17.4 and later.

Last Reviewed: October 2018

Tags: email, infrastructure

DRAFT-XXXX Appian receive email fails when using a routing alias with recipient name in 'Bcc' field

Zach Puderbach — Wed, 24 Oct 2018 10:22:54 GMT

Revision 9 posted to Appian Knowledge Base by Zach Puderbach on 10/24/2018 10:22:54 AM

Symptoms

Appian Receive Message fails when all the following conditions are met:

Destination process model is specified with the routing alias field conf.mailhandler.alias.<recipientName>=<routing> in custom.properties.
A destination key/value pair such as [DestinationPMUUID=<ProcessModelUUID>] is not being used when sending emails.
The recipient name is specified in the 'Bcc' field of an email.

The following error also appears in mail-listener.log:

[Appian EmailHandlerBean - 64] ERROR com.appiancorp.process.emailpoller.EmailHandlerBean - Error receiving message in EmailHandlerBean MDB
javax.mail.MessagingException: Message could not be sent;
 nested exception is:
 com.appiancorp.messaging.ProcessRouteMissingException: APNX-1-8001-001: No Process Routing Information Provided: Needs one of DestinationEventPersistentID, DestinationProcessID, DestinationPMID, DestinationPMUUID

Cause

This is unsupported behavior in Appian.

Workaround

Appian Receive Message still functions properly if used in the following ways:

Specify recipient name in the 'To' email field instead of 'Bcc'
Specify recipient name in the 'Cc' email field instead of 'Bcc'
Specify [DestinationPMUUID=<ProcessModelUUID>] in the subject line or body of the email when recipient name is in the 'Bcc' email field.

See the Routing Email Messages section of the Mail Server Setup guide for more details on using a destination key/value pair for email routing.

Affected Versions

This article applies to Appian 17.4 and later.

Last Reviewed: October 2018

Tags: email, infrastructure

DRAFT-XXXX Appian receive email fails when using a routing alias with recipient name in 'Bcc' field

Zach Puderbach — Wed, 24 Oct 2018 10:20:10 GMT

Revision 8 posted to Appian Knowledge Base by Zach Puderbach on 10/24/2018 10:20:10 AM

Symptoms

Appian Receive Message fails when all the following conditions are met:

Destination process model is specified with the routing alias field conf.mailhandler.alias.<recipientName>=<routing> in custom.properties.
A destination key/value pair such as [DestinationPMUUID=<ProcessModelUUID>] is not being used when sending emails.
The recipient name is specified in the 'Bcc' field of an email.

The following error also appears in mail-listener.log:

[Appian EmailHandlerBean - 64] ERROR com.appiancorp.process.emailpoller.EmailHandlerBean - Error receiving message in EmailHandlerBean MDB
javax.mail.MessagingException: Message could not be sent;
 nested exception is:
 com.appiancorp.messaging.ProcessRouteMissingException: APNX-1-8001-001: No Process Routing Information Provided: Needs one of DestinationEventPersistentID, DestinationProcessID, DestinationPMID, DestinationPMUUID

Cause

This is unsupported behavior in Appian.

Workaround

Appian Receive Message still functions properly if used in the following ways:

Specify recipient name in the 'To' email field instead of 'Bcc'
Specify recipient name in the 'Cc' email field instead of 'Bcc'
Specify [DestinationPMUUID=<ProcessModelUUID>] in the subject line or body of the email when recipient name is in the 'Bcc' email field.

See the Routing Email Messages section of the Mail Server Setup guide for more details on using a destination key/value pair for email routing.

Affected Versions

This article applies to Appian 17.4 and later

Last Reviewed: October 2018

Tags: email, infrastructure

DRAFT-XXXX Appian receive email fails when using a routing alias with recipient name in 'Bcc' field

Zach Puderbach — Fri, 19 Oct 2018 16:05:44 GMT

Revision 7 posted to Appian Knowledge Base by Zach Puderbach on 10/19/2018 4:05:44 PM

Symptoms

Appian receive email fails when all the following conditions are met:

Destination process model is specified with the routing alias field conf.mailhandler.alias.<recipientName>=<routing> in custom.properties.
A destination key/value pair such as [DestinationPMUUID=<ProcessModelUUID>] is not being used when sending emails.
The recipient name is specified in the 'Bcc' field of an email.

The following error also appears in mail-listener.log:

[Appian EmailHandlerBean - 64] ERROR com.appiancorp.process.emailpoller.EmailHandlerBean - Error receiving message in EmailHandlerBean MDB
javax.mail.MessagingException: Message could not be sent;
 nested exception is:
 com.appiancorp.messaging.ProcessRouteMissingException: APNX-1-8001-001: No Process Routing Information Provided: Needs one of DestinationEventPersistentID, DestinationProcessID, DestinationPMID, DestinationPMUUID

Cause

This issue has been reported to the Appian Product Team.

Workaround

Appian receive email still functions properly if used in the following ways:

Specify recipient name in the 'To' email field instead of 'Bcc'
Specify recipient name in the 'Cc' email field instead of 'Bcc'
Specify [DestinationPMUUID=<ProcessModelUUID>] in the subject line or body of the email when recipient name is in the 'Bcc' email field.

See the Routing Email Messages section of the Mail Server Setup guide for more details on using a destination key/value pair for email routing.

Affected Versions

This article applies to Appian 17.4 and later

Last Reviewed: October 2018

Tags: email, infrastructure

DRAFT-XXXX Appian receive email fails when using a routing alias with recipient name in 'Bcc' field

Zach Puderbach — Fri, 19 Oct 2018 15:59:30 GMT

Revision 6 posted to Appian Knowledge Base by Zach Puderbach on 10/19/2018 3:59:30 PM

Symptoms

Appian receive email fails when all the following conditions are met:

Destination process model is specified with the routing alias field conf.mailhandler.alias.<recipientName>=<routing> in custom.properties.
A destination key/value pair such as [DestinationPMUUID=<ProcessModelUUID>] is not being used when sending emails.
The recipient name is specified in the 'Bcc' field of an email.

The following error also appears in mail-listener.log:

[Appian EmailHandlerBean - 64] INFO com.appiancorp.process.emailpoller.EmailHandlerBean - EmailHandlerBean received email message. (email subject)
[Appian EmailHandlerBean - 64] ERROR com.appiancorp.process.emailpoller.EmailHandlerBean - Error receiving message in EmailHandlerBean MDB
javax.mail.MessagingException: Message could not be sent;
 nested exception is:
 com.appiancorp.messaging.ProcessRouteMissingException: APNX-1-8001-001: No Process Routing Information Provided: Needs one of DestinationEventPersistentID, DestinationProcessID, DestinationPMID, DestinationPMUUID

Cause

This issue has been reported to the Appian Product Team.

Workaround

Appian receive email still functions properly if used in the following ways:

Specify recipient name in the 'To' email field instead of 'Bcc'
Specify recipient name in the 'Cc' email field instead of 'Bcc'
Specify [DestinationPMUUID=<ProcessModelUUID>] in the subject line or body of the email when recipient name is in the 'Bcc' email field.

See the Routing Email Messages section of the Mail Server Setup guide for more details on using a destination key/value pair for email routing.

Affected Versions

This article applies to Appian 17.4 and later

Last Reviewed: October 2018

Tags: email, infrastructure

DRAFT-XXXX Appian receive email fails when using a routing alias with recipient name in 'Bcc' field

Zach Puderbach — Wed, 17 Oct 2018 17:41:30 GMT

Revision 5 posted to Appian Knowledge Base by Zach Puderbach on 10/17/2018 5:41:30 PM

Symptoms

Appian receive email fails when used in the following way:

Destination process model is specified with the routing alias field conf.mailhandler.alias.<recipientName>=<routing> in custom.properties.
A destination key/value pair such as [DestinationPMUUID=<ProcessModelUUID>] is not being used when sending emails.
The recipient name is specified in the 'Bcc' field of an email.

The following error also appears in mail-listener.log:

[Appian EmailHandlerBean - 64] INFO com.appiancorp.process.emailpoller.EmailHandlerBean - EmailHandlerBean received email message. (email subject)
[Appian EmailHandlerBean - 64] ERROR com.appiancorp.process.emailpoller.EmailHandlerBean - Error receiving message in EmailHandlerBean MDB
javax.mail.MessagingException: Message could not be sent;
 nested exception is:
 com.appiancorp.messaging.ProcessRouteMissingException: APNX-1-8001-001: No Process Routing Information Provided: Needs one of DestinationEventPersistentID, DestinationProcessID, DestinationPMID, DestinationPMUUID

Cause

This issue has been reported to the Appian Product Team.

Workaround

Appian receive email still functions properly if used in the following ways:

Specify recipient name in the 'To' email field instead of 'Bcc'
Specify recipient name in the 'Cc' email field instead of 'Bcc'
Specify [DestinationPMUUID=<ProcessModelUUID>] in the subject line or body of the email when recipient name is in the 'Bcc' email field.

See the Routing Email Messages section of the Mail Server Setup guide for more details on using a destination key/value pair for email routing.

Affected Versions

This article applies to Appian 17.4 and later

Last Reviewed: October 2018

Tags: email, infrastructure

DRAFT-XXXX Appian receive email fails when using a routing alias with recipient name in BCC field

Zach Puderbach — Wed, 17 Oct 2018 17:26:04 GMT

Revision 1 posted to Appian Knowledge Base by Zach Puderbach on 10/17/2018 5:26:04 PM

Symptoms

Appian receive email fails when used in the following way:

Destination process model is specified with the routing alias field conf.mailhandler.alias.<recipientName>=<routing> in custom.properties.
A destination key value pair such as [DestinationPMUUID=<ProcessModelUUID>] is not being used when sending emails.
The recipient name is specified in the Bcc field of an email.

The following error also appears in mail-listener.log:

[Appian EmailHandlerBean - 64] INFO com.appiancorp.process.emailpoller.EmailHandlerBean - EmailHandlerBean received email message. (email subject)
[Appian EmailHandlerBean - 64] ERROR com.appiancorp.process.emailpoller.EmailHandlerBean - Error receiving message in EmailHandlerBean MDB
javax.mail.MessagingException: Message could not be sent;
 nested exception is:
 com.appiancorp.messaging.ProcessRouteMissingException: APNX-1-8001-001: No Process Routing Information Provided: Needs one of DestinationEventPersistentID, DestinationProcessID, DestinationPMID, DestinationPMUUID

Cause

This issue has been reported to the Appian Product Team.

Workaround

Appian receive email still functions properly if used in the following ways:

Specify recipient name in the 'To' email field instead of Bcc
Specify recipient name in the 'Cc' email field instead of Bcc
Specify [DestinationPMUUID=<ProcessModelUUID>] in the subject line or body of the email when recipient name is in the 'Bcc' email field.

See the Routing Email Messages section of the Mail Server Setup guide for more details on specifying a destination key value pair.

Affected Versions

This article applies to Appian 17.4 and later

Last Reviewed: October 2018

Tags: email, infrastructure

DRAFT-XXXX Appian receive email fails when using a routing alias with recipient name in 'Bcc' field

Zach Puderbach — Wed, 17 Oct 2018 14:17:51 GMT

Revision 4 posted to Appian Knowledge Base by Zach Puderbach on 10/17/2018 2:17:51 PM

Symptoms

Appian receive email fails when used in the following way:

Destination process model is specified with the routing alias field conf.mailhandler.alias.<recipientName>=<routing> in custom.properties.
A destination key/value pair such as [DestinationPMUUID=<ProcessModelUUID>] is not being used when sending emails.
The recipient name is specified in the 'Bcc' field of an email.

The following error also appears in mail-listener.log:

[Appian EmailHandlerBean - 64] INFO com.appiancorp.process.emailpoller.EmailHandlerBean - EmailHandlerBean received email message. (email subject)
[Appian EmailHandlerBean - 64] ERROR com.appiancorp.process.emailpoller.EmailHandlerBean - Error receiving message in EmailHandlerBean MDB
javax.mail.MessagingException: Message could not be sent;
 nested exception is:
 com.appiancorp.messaging.ProcessRouteMissingException: APNX-1-8001-001: No Process Routing Information Provided: Needs one of DestinationEventPersistentID, DestinationProcessID, DestinationPMID, DestinationPMUUID

Cause

This issue has been reported to the Appian Product Team.

Workaround

Appian receive email still functions properly if used in the following ways:

Specify recipient name in the 'To' email field instead of 'Bcc'
Specify recipient name in the 'Cc' email field instead of 'Bcc'
Specify [DestinationPMUUID=<ProcessModelUUID>] in the subject line or body of the email when recipient name is in the 'Bcc' email field.

See the Routing Email Messages section of the Mail Server Setup guide for more details on specifying a destination key/value pair.

Affected Versions

This article applies to Appian 17.4 and later

Last Reviewed: October 2018

Tags: email, infrastructure

DRAFT-XXXX Appian receive email fails when using a routing alias with recipient name in 'Bcc' field

Zach Puderbach — Wed, 17 Oct 2018 14:13:37 GMT

Revision 3 posted to Appian Knowledge Base by Zach Puderbach on 10/17/2018 2:13:37 PM

Symptoms

Appian receive email fails when used in the following way:

Destination process model is specified with the routing alias field conf.mailhandler.alias.<recipientName>=<routing> in custom.properties.
A destination key/value pair such as [DestinationPMUUID=<ProcessModelUUID>] is not being used when sending emails.
The recipient name is specified in the Bcc field of an email.

The following error also appears in mail-listener.log:

[Appian EmailHandlerBean - 64] INFO com.appiancorp.process.emailpoller.EmailHandlerBean - EmailHandlerBean received email message. (email subject)
[Appian EmailHandlerBean - 64] ERROR com.appiancorp.process.emailpoller.EmailHandlerBean - Error receiving message in EmailHandlerBean MDB
javax.mail.MessagingException: Message could not be sent;
 nested exception is:
 com.appiancorp.messaging.ProcessRouteMissingException: APNX-1-8001-001: No Process Routing Information Provided: Needs one of DestinationEventPersistentID, DestinationProcessID, DestinationPMID, DestinationPMUUID

Cause

This issue has been reported to the Appian Product Team.

Workaround

Appian receive email still functions properly if used in the following ways:

Specify recipient name in the 'To' email field instead of Bcc
Specify recipient name in the 'Cc' email field instead of Bcc
Specify [DestinationPMUUID=<ProcessModelUUID>] in the subject line or body of the email when recipient name is in the 'Bcc' email field.

See the Routing Email Messages section of the Mail Server Setup guide for more details on specifying a destination key/value pair.

Affected Versions

This article applies to Appian 17.4 and later

Last Reviewed: October 2018

Tags: email, infrastructure

DRAFT-XXXX Appian receive email fails when using a routing alias with recipient name in 'Bcc' email field

Zach Puderbach — Wed, 17 Oct 2018 14:13:17 GMT

Revision 2 posted to Appian Knowledge Base by Zach Puderbach on 10/17/2018 2:13:17 PM

Symptoms

Appian receive email fails when used in the following way:

Destination process model is specified with the routing alias field conf.mailhandler.alias.<recipientName>=<routing> in custom.properties.
A destination key/value pair such as [DestinationPMUUID=<ProcessModelUUID>] is not being used when sending emails.
The recipient name is specified in the Bcc field of an email.

The following error also appears in mail-listener.log:

[Appian EmailHandlerBean - 64] INFO com.appiancorp.process.emailpoller.EmailHandlerBean - EmailHandlerBean received email message. (email subject)
[Appian EmailHandlerBean - 64] ERROR com.appiancorp.process.emailpoller.EmailHandlerBean - Error receiving message in EmailHandlerBean MDB
javax.mail.MessagingException: Message could not be sent;
 nested exception is:
 com.appiancorp.messaging.ProcessRouteMissingException: APNX-1-8001-001: No Process Routing Information Provided: Needs one of DestinationEventPersistentID, DestinationProcessID, DestinationPMID, DestinationPMUUID

Cause

This issue has been reported to the Appian Product Team.

Workaround

Appian receive email still functions properly if used in the following ways:

Specify recipient name in the 'To' email field instead of Bcc
Specify recipient name in the 'Cc' email field instead of Bcc
Specify [DestinationPMUUID=<ProcessModelUUID>] in the subject line or body of the email when recipient name is in the 'Bcc' email field.

See the Routing Email Messages section of the Mail Server Setup guide for more details on specifying a destination key/value pair.

Affected Versions

This article applies to Appian 17.4 and later

Last Reviewed: October 2018

Tags: email, infrastructure