E-mail Redirection Causing Comment Routing to Break

I've recently moved a support group from one Service Desk project to another. The switch over was facilitated by adding a "redirect" rule to Microsoft Exchange, moving the traffic over to the new inbox.

I've noticed, since the migration, that customer reply e-mails that do not have the issue key in their subject lines are no longer properly routed to the ticket as comments. Instead, these reply e-mails are creating new tickets.

Any thoughts on why this might be happening, and what I could do to correct or workaround the problem?

1 answer

1 accepted

I found that the "message-id" metadata field is changed by the Exchange 'redirect' rule, without updating the "references" or "in-reply-to" fields.

The workaround is to enable redirection at the server level in Microsoft Exchange. This preserves the message ID.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Jun 14, 2018 in Jira Service Desk

How the Telegram Integration for Jira helps Sergey's team take their support efficiency to the bank

...+ reading Fantasy). The same is true for him at the bank he works for: Efficiency is key when time literally equals money. Read on to learn how Sergey makes most of the time he has by...

793 views 5 7
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you