Normally JEMH creates a ticket in our jira 'project' when we send an email to 'firstname.lastname@example.org'. It fails to do so when our other mail server forwards a message to jira originally sent to 'email@example.com'. JEMH replies with:
#1 project could be assocaited with the email #2 The configured default project could not be found #3 Insufficient valid information was found, no issue was created.
The forwarded email contains the following headers, which seems right:
X-Original-To : firstname.lastname@example.org Delivered-To : email@example.com
I think this is due to the 'To' header being set to 'firstname.lastname@example.org'. Is there a way around this?
More info needed; Use JEMH Auditing, locate the actual email entry that caused this, convert it to a JEMH Test Case, view the email. If the to: address does not match an existing Project Mapping (please clarify how you are routing email), then, with no fallback project, it will result in the above.
Consider adding an additional Project Mapping for the inbound address, or set a fallbackProject?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG