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

Email-ext 2.72 and no SMTP auth cause MessagingException

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Blocker
    • Resolution: Fixed
    • Component/s: email-ext-plugin
    • Labels:
      None
    • Environment:
      Jenkins 2.235.3, Email-Ext 2.72
    • Similar Issues:
    • Released As:
      2.73

      Description

      Sending mails without SMTP authentication does not work anymore after upgrading from 2.71 to 2.72. Both SMTP Username and SMTP Password fields are empty in Jenkins config. When using emailext form a Jenkins Pipeline script, I get the following error:

      ...
       Successfully created MimeMessage
       Sending email to: XXX
       MessagingException message: No authentication mechanisms supported by both server and client
       Sending email for trigger: Always
       messageContentType = text/plain; charset=UTF-8
       Adding recipients from project recipient list
       Adding recipients from trigger recipient list
       Successfully created MimeMessage
       An attempt to send an e-mail to empty list of recipients, ignored.
       ...

      I downgraded to 2.71, cleaned the Jenkins system configuration (because downgrading actived the Use SMTP Authentification checkbox) and sending mails worked again.

        Attachments

          Activity

          skycaptain Manuel Leonhardt created issue -
          skycaptain Manuel Leonhardt made changes -
          Field Original Value New Value
          Description Sending mails without SMTP authentification does not work anymore after upgrading from 2.71 to 2.72. Both SMTP Username and SMTP Password fields are empty in Jenkins config. When using emailext form a Jenkins Pipeline script, I get the following error:
          {code:java}
          ...
           Successfully created MimeMessage
           Sending email to: XXX
           MessagingException message: No authentication mechanisms supported by both server and client
           Sending email for trigger: Always
           messageContentType = text/plain; charset=UTF-8
           Adding recipients from project recipient list
           Adding recipients from trigger recipient list
           Successfully created MimeMessage
           An attempt to send an e-mail to empty list of recipients, ignored.
           ...{code}
          I downgraded to 2.71, cleaned the Jenkins system configuration (because downgrading actived the Use SMTP Authentification checkbox) and sending mails worked again.
          Sending mails without SMTP authentication does not work anymore after upgrading from 2.71 to 2.72. Both SMTP Username and SMTP Password fields are empty in Jenkins config. When using emailext form a Jenkins Pipeline script, I get the following error:
          {code:java}
          ...
           Successfully created MimeMessage
           Sending email to: XXX
           MessagingException message: No authentication mechanisms supported by both server and client
           Sending email for trigger: Always
           messageContentType = text/plain; charset=UTF-8
           Adding recipients from project recipient list
           Adding recipients from trigger recipient list
           Successfully created MimeMessage
           An attempt to send an e-mail to empty list of recipients, ignored.
           ...{code}
          I downgraded to 2.71, cleaned the Jenkins system configuration (because downgrading actived the Use SMTP Authentification checkbox) and sending mails worked again.
          slide_o_mix Alex Earl made changes -
          Released As 2.73
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Resolved [ 5 ]

            People

            Assignee:
            slide_o_mix Alex Earl
            Reporter:
            skycaptain Manuel Leonhardt
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: