Get JEMH to match incoming emails when the inbound address was a Blind Carbon Copy (BCC)
Scenario
For various reasons, an email may arrive at a JEMH mailbox but owing to its inbound addressee being in a Blind Carbon Copy list, that field will be stripped by mail server, resulting in no standard way to identify 'what' the inbound address was. This would result in mail forwarded as there was no matching catchEmail address:
Importing a BCC delivered email from JEMH Audit History, the recipients may be missing or show up as undisclosed
Solution
Since 1.5.31, JEMH has a new UI feature, whereby specific email headers that do contain the actual addressee can be nominated, and used when all other addressee matching fails. This approach will work on a system by system approach, for example, Gmail includes Delivered-To: jira@faraway.com. JEMH Configuration now has a field for catchEmail address headers, in this example, Delivered-To, more can be added in a comma separated manner.
Example:
Delivered-To: jemhtesting@gmail.com
Received: by 10.180.91.1 with SMTP id ca1csp41646wib;
Thu, 6 Feb 2014 11:18:00 -0800 (PST)
X-Received: by 10.50.238.162 with SMTP id vl2mr823472igc.45.1391714280294;
Thu, 06 Feb 2014 11:18:00 -0800 (PST)The configuration entry is shown below after the header was added:
When re-running a previously failed match Test Case, the match will be made and the message processed accordingly.
Forwarded messages
With this feature, JEMH can also now process a messages catchEmail to an 'original' mailbox that was forwarded to a common mailbox. This would matter when several Profiles were running against a shared mailbox, an example header there would be X-Forwarded-To .