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

Sending mail issue with email-ext plugin

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Not A Defect
    • Component/s: email-ext-plugin
    • Labels:
    • Environment:
      JavaMail version: 1.4.4
      Jenkins version: 2.190.3
      Email Extension Plugin version: 2.68
      Mailer Plugin version: 1.29
    • Similar Issues:

      Description

      The Email-ext plugin fails to send mail notification after a build. I have the following error: 

      "MessagingException message: failed to connect, no password specified?"

      I've tried different things regarding existing issue:

      • Send to the Recipient List in the Trigger option
      • Change SMTP port to 25, 465, 587
      • Play with the "-Dmail.smtp.starttls.enable" configuration in jenkins.xml

      None of these manage to solve the issue.

      However, the test with the basic mailer plugin works perfectly.

      Maybe it is stupid, but I think I don't need ssl encryption (working on lan), and that's why I have uncheck "ssl" configuration. Also delete "-Dmail.smtp.starttls.enable=true" in the jenkins.xml.

       

      Any ideas ?

       

      Environment:

      JavaMail version: 1.4.4
      Jenkins version: 2.190.3
      Email Extension Plugin version: 2.68
      Mailer Plugin version: 1.29

       

        Attachments

          Activity

          Hide
          slide_o_mix Alex Earl added a comment -

          Did you specify a username and password? Without more information about how you have your setup configured, it will be very difficult to help.

          Show
          slide_o_mix Alex Earl added a comment - Did you specify a username and password? Without more information about how you have your setup configured, it will be very difficult to help.
          Hide
          p13rr3 Pierre Lemasson added a comment -

          Thank you for your answer.

          Well no, I have not specify username and password, (I thought I don't need because the jenkins server is accessible in a lan, but I don't know, maybe it's a stupid idea...)

          Here is a picture of the plugin configuration (all hidden field are filled with default value):

           

           

          Show
          p13rr3 Pierre Lemasson added a comment - Thank you for your answer. Well no, I have not specify username and password, (I thought I don't need because the jenkins server is accessible in a lan, but I don't know, maybe it's a stupid idea...) Here is a picture of the plugin configuration (all hidden field are filled with default value):    
          Hide
          slide_o_mix Alex Earl added a comment -

          Even if it's available on your lab it may still require a username/password. Find out from your IT department.

          Show
          slide_o_mix Alex Earl added a comment - Even if it's available on your lab it may still require a username/password. Find out from your IT department.
          Hide
          p13rr3 Pierre Lemasson added a comment -

          I have modified the value of the argument "-Dmail.smtp.auth" in the jenkins.xml, and it seems to work correctly now.

          Thank you for your answers

          Show
          p13rr3 Pierre Lemasson added a comment - I have modified the value of the argument "-Dmail.smtp.auth" in the jenkins.xml, and it seems to work correctly now. Thank you for your answers

            People

            • Assignee:
              slide_o_mix Alex Earl
              Reporter:
              p13rr3 Pierre Lemasson
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: