[JIRA] (JENKINS-3983) SMTP authentication not working

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-3983) SMTP authentication not working

JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163118#comment-163118 ]

SCM/JIRA link daemon commented on JENKINS-3983:
-----------------------------------------------

Code changed in jenkins
User: Christoph Kutzinski
Path:
 core/pom.xml
http://jenkins-ci.org/commit/jenkins/efce00a177bd4d6ac64cad481544729e90144358
Log:
  Update JavaMail dependency to 1.4.4. Should fix JENKINS-1152 and JENKINS-3983(cherry picked from commit 4afaf0bbc2c9f7298c45dc527269fb5c81cc710d)



               

> SMTP authentication not working
> -------------------------------
>
>                 Key: JENKINS-3983
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-3983
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: Platform: PC, OS: All
>            Reporter: marcb
>         Attachments: stacktrace.txt
>
>
> I've tried to use my Exchange 2007 server as an SMTP server for Hudson, which
> requires SMTP authentication. I configured the standard authentication settings
> which have been confirmed to work on Outlook, Outlook Express as well as our
> office printer (which can sending scans by email). When sending a test email, or
> having emails sent after a build, I get the following:
> com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.1 Client was not
> authenticated
> See attachment for full stack trace.
> It would appear the problem is related to the way JavaMail is called in Hudson.
> The following FAQ entry describes the problem:
> http://java.sun.com/products/javamail/FAQ.html#smtpauth
> I checked hudson.tasks.Mailer in core/src/main/java/hudson/tasks and it seems
> indeed that JavaMail is being called using Transport.send(msg) instead of the
> method suggested in the FAQ above.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira