-
Notifications
You must be signed in to change notification settings - Fork 513
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Customer replies are added to the wrong thread. #2375
Comments
|
We'll close this as it's impossible to investigate it without direct access to the server. If you'll have any other questions - feel free to ask. |
The only messages with the message_id marker, is the one which is added to the wrong thread. Any idea where to go from here? @freescout-helpdesk |
…uld be connected to the wrong conversation - closes #2375
We've managed to reproduce and fix the issue. It could happen when the customer was also using FreeScout. The fix will be included in the next release. |
Hey.
We have a issue where sometimes, a customer reply, will be submitted into the wrong thread/conversation.
I've looked at the headers to see if I could find whats wrong, both comparing 2 customer replies thats assigned to the right thread and comparing the mismatch reply to those.
Having compared those headers, I can't really tell how even the original messages were added to the same conversation/thread, being that both the Message-ID and In-Reply-To are not matching.
How exactly does FreeScout decide which thread to add new replies? I've looked at the code in app\Console\Commands\FetchEmails.php, where it seems its deciding a previous Message-ID, but Im struggling to find out how Right message 1 and 2 got put into the same thread, and why the wrong header got added aswell.
Right headers 1:
Right headers 2:
Wrong header:
Im hoping you can cast some light on this issue for me.
The text was updated successfully, but these errors were encountered: