...
Whilst Project Mappings reduce the need for many Profiles, if there are lots of Incoming Mail Servers, then there is still a performance issue (at retrieval time). Where mail comes from a common mail server, and where JEMH is consuming all mail from those mailboxes, consider setting up a Common mailbox for mail pickup (eg issues@blah.com), using Alias addresses for that mailbox such that alternate addresses (eg other@blah.com) are delivered for pickup from the common mailbox. Verify correct behaviour by adding the Alias address to your Profile > Email > Catchemail, and running a test case through, it should create in the Default Project Mapping (discussed later).
Some mailservers do not retain ‘alias’ addresses
If your mailserver does not retain the ‘alias’ address, we can’t help, you need to discuss with your mailserver admin on perhaps adding a Delivered-To header that contains such information, that JEMH can then find (which it does by default).
...
For the above, you would have a Master Profile and:
update catchemail addresses to include any that are 'new' from the imported profile
add a new Project Mapping for that project, adding a Domain Rule to match the inbound mailbox address
Testing is simple, create a JEMH Test Case and set the to: address to be the mailbox address from the first profile, that was added to the master. Prove when running the Test Case against the master that the Rule matches, and the issue is created in the right Project, with correct issue types etc, and repeat.
...