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

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