I created 2 identical user, one with my personal email and one with the customer email. The customer uses jira as well and he has to open issue in my jira with email originated from its installation.
the error I get is:
JIRA fingerprints found on on incoming email message:
Received message with another JIRA instance's fingerprint
Ignoring email with bulk delivery type
I already whitelisted its domain...
any clue ?
thanks a lot
The problem here is that it seems that you're using an email that was originated from the other Jira instance. If you look at the full headers of the email, you'll see the Jira fingerprint mentioned in the error message.
The above-linked article explains where the check is coming from in the Email class. The workaround is to remove that code, but it also will remove your instance from our Supported Offerings, so please be aware of that.
We do have the following feature request here regarding that check:
Please watch and vote on it in order to show your support for this particular change.
Let us know if you have any questions about any of this.
thanks a lot for the update, and sorry for my Jira skills that are still quite low !
My confusion was also originated by the fact that on the link
I cannot see how I can avoid the check of the figerprint.
That would be in the first link I sent:
It shows you in the Email Class section where exactly it's coming from, so if you're familiar with modifying the source code, you could make the change.
However, I want to reiterate, this would cause your instance to be unsupported by Atlassian Support Offerings so please take care when making those modifications.
Sorry about that. The article is visible to me, but I just tried to log out and back in as a non-Atlassian user, and then I get the same error as you. It appears that it has been removed from public view.
However, the article essentially said that's controlled in the Jira Email Class.
There's a part in it that checks for the fingerprint:
However, I would advise against modifying the class in this way. You can see the procedure for JIRA 6.4 here: How to Make a JIRA Patch. The procedure may be different depending on your JIRA version, and you can likely run into issues from this.
The best option would be to leave your feedback on the feature request I sent you and include your use case to help understand why this feature is crucial to your business.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in talking to 20 people planning t...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs