- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2024 06:16 AM
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2024 06:23 AM
Hi Sture,
When an email is parsed, only the info up-to the separator is considered. This is largely for performance benefits as emails can be extremely nested and eventually truncated.
Seperators are stored in sys_email_reply_separator. They're used to cut off before the next email begins, something that isn't standardised across email clients.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2024 06:23 AM
Hi Sture,
When an email is parsed, only the info up-to the separator is considered. This is largely for performance benefits as emails can be extremely nested and eventually truncated.
Seperators are stored in sys_email_reply_separator. They're used to cut off before the next email begins, something that isn't standardised across email clients.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2024 06:45 AM
Hi Kieran, that did the trick, Thank You! I checked the separators table, sys_email_reply_separator.list, and then disable the one for outlook causing the problem. I Need to understand/check the performance benefit of this before go further.