Closed sinister3vil closed 9 months ago
You can try to implement these things via a custom module first.
Also try to figure out why the original message can't be loaded from your mail server. Maybe you deleting original emails from the mail server.
We've just added an alternative reply separation method in the master
branch, it will be published in the next release.
In order to enable it set APP_ALTERNATIVE_REPLY_SEPARATION=true
parameter in the .env file and clear cache.
Wow, thanks for the quick fix. We'll be sure to test this and revert on it's behavior.
Without wanting to sound like a wise-ass, just wanted to point out that the method is misspelled getHashedRelySeparator, instead of getHashedReplySeparator.
Hello and happy new year,
I'm revisiting a constant pain with Freescout. It's quite common for us to have communications made between other ticketing systems, not e-mail clients, which probably handle HTML in e-mails in a non-standard manner leading to issues when Freescout in parsing replies, in most cases incorrectly using the quoted text/signature part rather than the actual reply part, as the new reply text.
Related code https://github.com/freescout-helpdesk/freescout/blob/dist/app/Console/Commands/FetchEmails.php#L1287C9-L1327C10 Separators https://github.com/freescout-helpdesk/freescout/blob/1816aa276172cc3527fb0910a3376adb4a5ff5bb/app/Misc/Mail.php#L54C5-L73C7
Actual HTML examples are a bit hard to come by and, in any case, irrelevant as trying to support all different combinations is probably impossible.
Would any of the below workarounds be possible to implement in a future version :
Code-wise, 1. seems easy to implement by exposing a toggle button under settings and checking for that in the if clause. Maybe add a popup when toggling the option on that warns that "no parsing will be made and messages might get huge".
PHP version: PHP 7.4.33 FreeScout version: 1.8.115 Database: Mysql (5.5.5-10.1.48-MariaDB-0ubuntu0.18.04.1) Are you using CloudFlare: No