I am installing a process that reads emails from external clients. Some clientshttps://community.appian.com/discussions/f/general/3404/i-am-installing-a-process-that-reads-emails-from-external-clients-some-clientsI am installing a process that reads emails from external clients. Some clients put our address in the bcc field. This seems to prevent appian from routing the email to the correct process as custom properties uses the alias which apparently is blanken-USTelligent Community 12RE: I am installing a process that reads emails from external clients. Some clientshttps://community.appian.com/thread/11881?ContentTypeID=1Tue, 09 Sep 2014 05:54:36 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:113f87d2-5d34-4cf8-ac4b-ea8f74db9f49Eduardo FuentesThat&#39;s correct, only CC and TO are supported for routing alias, this seems to be related to the nature and meaning of BCC who are those recipients are those being discreetly informed of the communication and cannot be seen by any of the other addressees.<br /><br />You can check with your MS Exchange Administrator if he can create a rule to forward messages where the alias is in the BCC to the alias itself (and delete the original message) so that the alias email address is moved to the TO in the new email. <br /><br />Looking at the options I have in Outlook I don&#39;t think it&#39;s possible to inspect the BCC but you may want to double check with them.<br /><br />The reference number for this feature to support BCC is AN-46447.<br /><br />-Eduardo Fuentes<br />Appian Technical Support<div style="clear:both;"></div>