Summary

      Customer has specified a Mail Handler to Add a comment before a specified marker or separator in the email body however the Split Regex is not being used.

      Environment

      • 7.0.0-OD-04

      Steps to Reproduce

      1. Create a New Mail Handler using the option Add a comment before a specified marker or separator in the email body
      2. Specify a Split Regex Expression /From: |___.|On .wrote:|----Orig.|On .(JIRA).|.(JIRA).*wrote:/
      3. When messages from Outlook are received, the message is not split and show the Old/Quoted Replies
        • Also note, if a value is added to the message which would match the Regex Expression, it is not split at that point.

      Expected Results

      Message is Split

      Actual Results

      If a message is sent that matches the Regex Expression, the quoted text is not removed before the comment is added.

      Testing the Regex Expression:

      We see that the strings match.

      Replied to a JIRA message which contains one of the strings however the text after the string is added as a comment:

      Notes

      (Optional - If Necessary)

      Workaround

      None

        1. FromExample.png
          89 kB
          Shawn C
        2. image (1).png
          146 kB
          Lavakumar Thatisetti
        3. image (2).png
          99 kB
          Lavakumar Thatisetti
        4. image (3).png
          191 kB
          Lavakumar Thatisetti
        5. image (4).png
          601 kB
          Lavakumar Thatisetti
        6. image (5).png
          657 kB
          Lavakumar Thatisetti
        7. OnExample.png
          83 kB
          Shawn C
        8. RegexTest.png
          32 kB
          Shawn C

            [JRACLOUD-65977] Mail Handlers Not Splitting Messages with Regex

            added Comment

            Lavakumar Thatisetti added a comment - added Comment

            I tried the recommendation from Simon without success.

            Chuck Virtu added a comment - I tried the recommendation from Simon without success.

            I had a similar problem when i was using regex /From: / and it wasn't working even though the word From:  was clearly present in the text.

            I looked at the hmtl mail and realized that the mail did not use a space character but a nbsp(non breaking space) which i'm guessing was causing issues with the regex filter.

            I changed the regex to /From:./ and it was working after that.

            Simon Thériault added a comment - I had a similar problem when i was using regex /From: / and it wasn't working even though the word From:  was clearly present in the text. I looked at the hmtl mail and realized that the mail did not use a space character but a nbsp(non breaking space) which i'm guessing was causing issues with the regex filter. I changed the regex to /From:./ and it was working after that.

            I reported this as an issue, hoping that somehow my use case had a workaround/solution, but apparently not. Basically, I'm looking to split the message before the email signature pollutes the comment with excess. Unfortunately, the split regex expression doesn't work on the most basic of tasks, matching a vanilla string: "Regards"

            I'm going to play with the regex string a bit more, but am not optimistic. 

            Deleted Account (Inactive) added a comment - I reported this as an issue, hoping that somehow my use case had a workaround/solution, but apparently not. Basically, I'm looking to split the message before the email signature pollutes the comment with excess. Unfortunately, the split regex expression doesn't work on the most basic of tasks, matching a vanilla string: "Regards" I'm going to play with the regex string a bit more, but am not optimistic. 

            Alexey's solution work in thunderbird.  Thanks Alexey!

             

            Jonathan Donley

            Jonathan Donley added a comment - Alexey's solution work in thunderbird.  Thanks Alexey!   Jonathan Donley

            Alexey Ossikine added a comment - - edited

            That just looks like invalid regex because the dots are requiring a single character instead of any number of characters. Shouldn't every dot in the regex be followed by an asterisk, like this?

            /From: |___.*|On .*wrote:|----Orig.*|On .*(JIRA).*|.*(JIRA).*wrote:/

            Tested and works for me.

            Alexey Ossikine added a comment - - edited That just looks like invalid regex because the dots are requiring a single character instead of any number of characters. Shouldn't every dot in the regex be followed by an asterisk, like this? /From: |___.*|On .*wrote:|----Orig.*|On .*(JIRA).*|.*(JIRA).*wrote:/ Tested and works for me.

            Facing the same issue! Communication with our clients is a mess! Since with the reply we send all history of the comments every next reply doubles the text. Several times we even have reached the text limit in incoming emails. It make the tool totally unusable. 

            Just don't how come this issue has not been fixed since 2015.

            Kirill Faminskiy added a comment - Facing the same issue! Communication with our clients is a mess! Since with the reply we send all history of the comments every next reply doubles the text. Several times we even have reached the text limit in incoming emails. It make the tool totally unusable.  Just don't how come this issue has not been fixed since 2015.

            Any update on this one? This is a very serious issue as it renders one of the channels for recieving issues unsuable! How come priority on this is set to LOW?!

            Ivan Tovbin added a comment - Any update on this one? This is a very serious issue as it renders one of the channels for recieving issues unsuable! How come priority on this is set to LOW ?!

            We experience the same problem reported here.

            Alexandre Macedo added a comment - We experience the same problem reported here.

            We experience this as well. It renders recieving email requests almost unusable since after a while the comments in an issue turn into a mess, because every customer reply contains ALL the previous comments and thus becomes almost impossible to read.

            Ivan Tovbin added a comment - We experience this as well. It renders recieving email requests almost unusable since after a while the comments in an issue turn into a mess, because every customer reply contains ALL the previous comments and thus becomes almost impossible to read.

              Unassigned Unassigned
              scranford Shawn C (Inactive)
              Affected customers:
              65 This affects my team
              Watchers:
              61 Start watching this issue

                Created:
                Updated:
                Resolved: