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

Email-ext 2.72 and no SMTP auth cause MessagingException

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • email-ext-plugin
    • None
    • Jenkins 2.235.3, Email-Ext 2.72
    • 2.73

      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.

          [JENKINS-63311] Email-ext 2.72 and no SMTP auth cause MessagingException

          Alex Earl added a comment -

          From my testing, I believe this will fix the issue: https://github.com/jenkinsci/email-ext-plugin/pull/213

          This changed because of the way that things are pulled in from the configuration area to support JCasC. I'll do a release as soon as I merge in the change.

          Alex Earl added a comment - From my testing, I believe this will fix the issue: https://github.com/jenkinsci/email-ext-plugin/pull/213 This changed because of the way that things are pulled in from the configuration area to support JCasC. I'll do a release as soon as I merge in the change.

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

              Created:
              Updated:
              Resolved: