Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-65312

Please allow underscore("_") after "@" part for Editable Email

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Minor Minor
    • email-ext-plugin
    • None

      Please allow underscore("_") after "@" part for Editable Email.

      As per requirement we need to send Email to a system Email id (xxxxx@xxx_xxx.com) , we could see Jenkins email validation is not allowing due to domain validation ( perhaps due to the reason it has underscore after @ part ).

      But as this is system Email id and we cannot use any other Email id can you please change the validation so that it can allow underscore after @ part of Email Id.

      Please see the attached screen shot.

       

       

          [JENKINS-65312] Please allow underscore("_") after "@" part for Editable Email

          Basil Crow added a comment -

          Hi ranajoy_paul, I would love to see this bug fixed. Pull requests are welcome!

          Basil Crow added a comment - Hi ranajoy_paul , I would love to see this bug fixed. Pull requests are welcome!

          Ranajoy added a comment -

          Thanks basil , so does it mean issue has fixed and we can use Editable Email plugin with "_" after @ part in Email Id? If so, please let us know which plugin version I should download to verify the fix?

          Ranajoy added a comment - Thanks basil , so does it mean issue has fixed and we can use Editable Email plugin with "_" after @ part in Email Id? If so, please let us know which plugin version I should download to verify the fix?

          Alex Earl added a comment -

          That error comes from the InternetAddress.parse method, not from email-ext itself. It looks like they only allow numbers, digits, hyphens and dots.

          Alex Earl added a comment - That error comes from the InternetAddress.parse method, not from email-ext itself. It looks like they only allow numbers, digits, hyphens and dots.

          That restriction is consistent with RFC 5321 (SMTP) section 4.1.2. Is the protocol between Jenkins and your mail servers SMTP or something else?

          InternetAddress.parse has an overload that may allow the strict syntax check to be skipped, but there might be additional checks done when the message is sent.

          Kalle Niemitalo added a comment - That restriction is consistent with RFC 5321 (SMTP) section 4.1.2. Is the protocol between Jenkins and your mail servers SMTP or something else? InternetAddress.parse has an overload that may allow the strict syntax check to be skipped, but there might be additional checks done when the message is sent.

          Alex Earl added a comment -

          Even with strict=false it still will not parse a domain with an underscore in it.

          Alex Earl added a comment - Even with strict=false it still will not parse a domain with an underscore in it.

            Unassigned Unassigned
            ranajoy_paul Ranajoy
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: