PHP version: 8.3.6
FreeScout version: 1.8.217
Database: MySQL / PostgreSQL: MySQL 8.0.44
Are you using CloudFlare: No
Are you using non-official modules: No
Are you using Cloudron: Yes
Summary:
Conversations sent between two FreeScout instances are getting mixed up intermittently in recipient threads. New messages added to thread is not related to the original message in conversation.
Steps to Reproduce:
- Two mailboxes managed in Single FreeScout instance
- Backup and Clone to a new instance (new URL)
- Update conversation start number in new instance,
- Delete other mailbox within the instance (keeping 1 mailbox per instance)
- Send (or forward ), or reply to an existing thread in one of the conversations where the other mailbox (in the other instance) is an recipient
- Notice that incoming messages are intermittently getting mixed to existing conversations that is not related to the original thread
Current Behavior:
Emails are getting mixed up when rendered by FreeScout in spite of different conversation numbers indicated in the subject.
Expected Behavior:
Each FreeScout instance should be able to discern the incoming messages based on thread numbers indicated in subject and should create a new conversation if the thread number is not found in the system / instance
Root Cause Analysis:
The issue appears to be related to tag as shown in email header where Freescout provides higher weight on identifying which conversation the incoming message belongs to.
PHP version: 8.3.6
FreeScout version: 1.8.217
Database: MySQL / PostgreSQL: MySQL 8.0.44
Are you using CloudFlare: No
Are you using non-official modules: No
Are you using Cloudron: Yes
Summary:
Conversations sent between two FreeScout instances are getting mixed up intermittently in recipient threads. New messages added to thread is not related to the original message in conversation.
Steps to Reproduce:
Current Behavior:
Emails are getting mixed up when rendered by FreeScout in spite of different conversation numbers indicated in the subject.
Expected Behavior:
Each FreeScout instance should be able to discern the incoming messages based on thread numbers indicated in subject and should create a new conversation if the thread number is not found in the system / instance
Root Cause Analysis:
The issue appears to be related to tag as shown in email header where Freescout provides higher weight on identifying which conversation the incoming message belongs to.