com.atlassian.mail.MailException: com.sun.mail.smtp.SMTPSendFailedException: 530 <noreply@atlassian.com>, Authentication does not match this account

Atlassian JIRA | Milovan Tosic | 3 years ago
  1. 0

    Original Claim from customer: {quote} Scheduled log scan does not succeed in sending me an email because MAIL FROM field contains noreply@atlassian.com, and my mail server rejects emails. I couldn't find out how to configure this email address in JIRA. SMTP configuration mail from address is set to other email address. All other (project related) emails are successfully sent. Here is a part of debug outgoing mail log file: {quote} And below is seen in the logs: {noformat} 2013-11-20 13:26:30,639 ERROR [Mozzart POP] Sending mailitem com.atlassian.support.tools.salext.mail.SimpleSupportMailQueueItem@1a8d597f milovan 806x9587835x3 1t0xmj 192.168.182.52 /secure/admin/MailQueueAdmin.jspa Error occurred in sending e-mail: com.atlassian.support.tools.salext.mail.SimpleSupportMailQueueItem@1a8d597f com.atlassian.mail.MailException: com.sun.mail.smtp.SMTPSendFailedException: 530 <noreply@atlassian.com>, Authentication does not match this account at com.atlassian.mail.server.impl.SMTPMailServerImpl.sendWithMessageId(SMTPMailServerImpl.java:201) at com.atlassian.mail.server.impl.SMTPMailServerImpl.send(SMTPMailServerImpl.java:149) at com.atlassian.support.tools.salext.mail.AbstractSupportMailQueueItem.send(AbstractSupportMailQueueItem.java:52) at com.atlassian.support.tools.salext.mail.SimpleSupportMailQueueItem.send(SimpleSupportMailQueueItem.java:15) at com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66) {noformat} Upon confirmation, configuring the schedule log scan and enable the debug log shows the following result: *Expected*: the mail is sent with the email that is configured on the SMTP outgoing mail server email address. *Actual Result* It follows the below template: {noformat} From: noreply@atlassian.com To: xxxx@yyyy.com Message-ID: <988686800.0.1385392057951.JavaMail.richie@Richie-PC> Subject: [JIRA]TEST Log scan results for 2013-11-25... MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk Auto-Submitted: auto-generated <HTML> <HEAD> </HEAD> <BODY> <DIV CLASS="message_box" style='border: solid 1px #DEDEDE;background: #EAFFEF;color: #222222;padding: 4px;padding-left: 1em;'> This is a report generated by a regular scan of your JIRA instance for known problems.. <p>Found 3 known problems in the log file atlassian-jira.log (see below for details).</p> <UL> <LI><A HREF="https://confluence.atlassian.com/display/JIRAKB/JIRA+not+Functioning+due+to+IllegalStateException+zip+file+closed+error?utm_source=STP&amp;utm_medium=scheduledLogScan">JIRA not Functioning due to IllegalStateException zip file closed error</A></LI> <LI><A HREF="https://jira.atlassian.com/browse/JRA-24453?utm_source=STP&amp;utm_medium=scheduledLogScan">Unable to read bytes error on JIRA startup</A></LI> <LI><A HREF="https://confluence.atlassian.com/display/JIRAKB/Multiple+Redmine+projects+with+the+same+name+will+lead+to+error+when+importing+to+JIRA?utm_source=STP&amp;utm_medium=scheduledLogScan">Multiple Redmine projects with the same name will lead to error when importing to JIRA</A></LI> </UL> <p>If you no longer wish to receive these reports, contact your JIRA administrator.</p> </DIV> </BODY> </HTML> {noformat} As you can see, the From field is populated with noreply@atlassian.com for default and it might hit into problem if the customer's mail server has domain checking and you might see the error on logs like earlier which is returned from the mail server.

    Atlassian JIRA | 3 years ago | Milovan Tosic
    com.atlassian.mail.MailException: com.sun.mail.smtp.SMTPSendFailedException: 530 <noreply@atlassian.com>, Authentication does not match this account
  2. 0

    Original Claim from customer: {quote} Scheduled log scan does not succeed in sending me an email because MAIL FROM field contains noreply@atlassian.com, and my mail server rejects emails. I couldn't find out how to configure this email address in JIRA. SMTP configuration mail from address is set to other email address. All other (project related) emails are successfully sent. Here is a part of debug outgoing mail log file: {quote} And below is seen in the logs: {noformat} 2013-11-20 13:26:30,639 ERROR [Mozzart POP] Sending mailitem com.atlassian.support.tools.salext.mail.SimpleSupportMailQueueItem@1a8d597f milovan 806x9587835x3 1t0xmj 192.168.182.52 /secure/admin/MailQueueAdmin.jspa Error occurred in sending e-mail: com.atlassian.support.tools.salext.mail.SimpleSupportMailQueueItem@1a8d597f com.atlassian.mail.MailException: com.sun.mail.smtp.SMTPSendFailedException: 530 <noreply@atlassian.com>, Authentication does not match this account at com.atlassian.mail.server.impl.SMTPMailServerImpl.sendWithMessageId(SMTPMailServerImpl.java:201) at com.atlassian.mail.server.impl.SMTPMailServerImpl.send(SMTPMailServerImpl.java:149) at com.atlassian.support.tools.salext.mail.AbstractSupportMailQueueItem.send(AbstractSupportMailQueueItem.java:52) at com.atlassian.support.tools.salext.mail.SimpleSupportMailQueueItem.send(SimpleSupportMailQueueItem.java:15) at com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66) {noformat} Upon confirmation, configuring the schedule log scan and enable the debug log shows the following result: *Expected*: the mail is sent with the email that is configured on the SMTP outgoing mail server email address. *Actual Result* It follows the below template: {noformat} From: noreply@atlassian.com To: xxxx@yyyy.com Message-ID: <988686800.0.1385392057951.JavaMail.richie@Richie-PC> Subject: [JIRA]TEST Log scan results for 2013-11-25... MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk Auto-Submitted: auto-generated <HTML> <HEAD> </HEAD> <BODY> <DIV CLASS="message_box" style='border: solid 1px #DEDEDE;background: #EAFFEF;color: #222222;padding: 4px;padding-left: 1em;'> This is a report generated by a regular scan of your JIRA instance for known problems.. <p>Found 3 known problems in the log file atlassian-jira.log (see below for details).</p> <UL> <LI><A HREF="https://confluence.atlassian.com/display/JIRAKB/JIRA+not+Functioning+due+to+IllegalStateException+zip+file+closed+error?utm_source=STP&amp;utm_medium=scheduledLogScan">JIRA not Functioning due to IllegalStateException zip file closed error</A></LI> <LI><A HREF="https://jira.atlassian.com/browse/JRA-24453?utm_source=STP&amp;utm_medium=scheduledLogScan">Unable to read bytes error on JIRA startup</A></LI> <LI><A HREF="https://confluence.atlassian.com/display/JIRAKB/Multiple+Redmine+projects+with+the+same+name+will+lead+to+error+when+importing+to+JIRA?utm_source=STP&amp;utm_medium=scheduledLogScan">Multiple Redmine projects with the same name will lead to error when importing to JIRA</A></LI> </UL> <p>If you no longer wish to receive these reports, contact your JIRA administrator.</p> </DIV> </BODY> </HTML> {noformat} As you can see, the From field is populated with noreply@atlassian.com for default and it might hit into problem if the customer's mail server has domain checking and you might see the error on logs like earlier which is returned from the mail server.

    Atlassian JIRA | 3 years ago | Milovan Tosic
    com.atlassian.mail.MailException: com.sun.mail.smtp.SMTPSendFailedException: 530 <noreply@atlassian.com>, Authentication does not match this account
  3. 0

    [JRA-27623] No authentication mechansims supported by both server and client - Atlassian JIRA

    atlassian.com | 1 year ago
    com.atlassian.mail.MailException: javax.mail.AuthenticationFailedException: No authentication mechansims supported by both server and client
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Since JIRA 4.4.4 some configurations of Exchange smtp mailboxes are receiving errors when connecting to the mailbox. {noformat} com.atlassian.mail.MailException: javax.mail.AuthenticationFailedException: No authentication mechansims supported by both server and client at com.atlassian.mail.server.impl.SMTPMailServerImpl.send(SMTPMailServerImpl.java:183) at com.atlassian.jira.web.action.admin.mail.SendTestMail.doExecute(SendTestMail.java:102) at webwork.action.ActionSupport.execute(ActionSupport.java:165) at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:76) at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:39) at webwork.interceptor.NestedInterceptorChain.proceed(NestedInterceptorChain.java:31) at webwork.interceptor.ChainedInterceptor.intercept(ChainedInterceptor.java:16) at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:35) at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:205) at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:143) at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.service(JiraWebworkActionDispatcher.java:152) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) ... Caused by: javax.mail.AuthenticationFailedException: No authentication mechansims supported by both server and client at com.sun.mail.smtp.SMTPTransport.authenticate(SMTPTransport.java:756) at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:669) at javax.mail.Service.connect(Service.java:317) at javax.mail.Service.connect(Service.java:176) at javax.mail.Service.connect(Service.java:125) at com.atlassian.mail.server.impl.SMTPMailServerImpl.send(SMTPMailServerImpl.java:154) ... {noformat} I think this came about from a change in javamail. Versions earlier than 4.4.4 use javamail 1.4.1 and the newer versions use 1.4.4. Workaround: [JIRA KB|https://confluence.atlassian.com/display/JIRAKB/%27No+authentication+mechansims+supported+by+both+server+and+client%27+when+Configuring+Microsoft+Exchange+SMTP+Server]

    Atlassian JIRA | 5 years ago | Ivan Tse
    com.atlassian.mail.MailException: javax.mail.AuthenticationFailedException: No authentication mechansims supported by both server and client

    1 unregistered visitors
    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. com.atlassian.mail.MailException

      com.sun.mail.smtp.SMTPSendFailedException: 530 <noreply@atlassian.com>, Authentication does not match this account

      at com.atlassian.mail.server.impl.SMTPMailServerImpl.sendWithMessageId()
    2. com.atlassian.mail
      SMTPMailServerImpl.send
      1. com.atlassian.mail.server.impl.SMTPMailServerImpl.sendWithMessageId(SMTPMailServerImpl.java:201)
      2. com.atlassian.mail.server.impl.SMTPMailServerImpl.send(SMTPMailServerImpl.java:149)
      2 frames
    3. com.atlassian.support
      SimpleSupportMailQueueItem.send
      1. com.atlassian.support.tools.salext.mail.AbstractSupportMailQueueItem.send(AbstractSupportMailQueueItem.java:52)
      2. com.atlassian.support.tools.salext.mail.SimpleSupportMailQueueItem.send(SimpleSupportMailQueueItem.java:15)
      2 frames
    4. com.atlassian.mail
      MailQueueImpl.sendBuffer
      1. com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)
      1 frame