Hi Charles, Yes, it was an incorrectly escaped forward slash in a subject rule.
On 2019/06/24 16:12, Charles Amstutz wrote:
Hi Charles, My apologies, I forgot to provide feedback to the mailing list. Bad regex was the cause of this problem for us, too. As soon as the custom rule was fixed, the problem went away.If I can ask, was it an incorrectly escaped special character? I think it is the @ symbol breaking mine.
