相关文章推荐
才高八斗的杯子  ·  C++ lambda表达式与函数对象 ...·  4 月前    · 
乖乖的手术刀  ·  quartz 报错：Failure ...·  5 月前    · 
气宇轩昂的葫芦  ·  OS X El Capitan に ...·  10 月前    · 
有腹肌的伤痕  ·  spark数据类型转换函数 - CSDN文库·  10 月前    · 
体贴的仙人掌  ·  RelativeSource Class ...·  10 月前    · 
小百科  ›  javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful | CA Service Managem
exchange broadcom
气势凌人的韭菜
3 月前
  • Home
  • Communities
  • Blogs
  • Events
  • Water Cooler
  • Betas
  • Flings
  • Education
  • Groups
  • Members
    • Hi Folks

    From past 10 days, CA sdm stopped sending notifications and all the mail are going in Mail_Undelivered folder.

    we are getting below error in mail_nxd log file (Check the snapshot below)

    javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful

    I found below related article for this issue but not specifically for " Authentication unsuccessful ".

    i also involved Exchange team to confirm if credentials has been changed or if the IP's are in whitelist  but they are saying nothing has been changed at exchange side.

    Can anyone advise why 'authentication unsuccessful' is coming? i also tried to reinstall the services in option manager and recycle services but the issue is still same. i still believe the issue is from Exchange side and not from SDM but is there anything to cross check more from SDM side?

    The nxd mail daemon is already in running mode

    please advise

    https://knowledge.broadcom.com/external/article/141278/error-failed-to-send-mail-reason-javaxma.html
    https://knowledge.broadcom.com/external/article/118908/how-to-fix-no-authentication-mechanisms.html
    https://knowledge.broadcom.com/external/article/186989/email-integration-with-exchange-2016.html
    https://knowledge.broadcom.com/external/article/101452/email-notifications-fail-with-the-error.html



    #caservicedesknotifications
    #casdm17.2
    #camail
    #CAServiceDesk

    ​​​​​​​ Might be useful to enable debug on pdm_mail_nxd to see if any further information is logged

    https://knowledge.broadcom.com/external/article/98428/how-to-enable-the-debug-or-trace-mode-fo.html

    ------------------------------
    Paul Coccimiglio
    Principal Support Engineer
    Broadcom Inc.
    ------------------------------

    Original Message Original Message:
    Sent: 04-13-2020 09:41 AM
    From: asim Shah
    Subject: javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful

    Hi Folks

    From past 10 days, CA sdm stopped sending notifications and all the mail are going in Mail_Undelivered folder.

    we are getting below error in mail_nxd log file (Check the snapshot below)

    javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful

    I found below related article for this issue but not specifically for " Authentication unsuccessful ".

    i also involved Exchange team to confirm if credentials has been changed or if the IP's are in whitelist  but they are saying nothing has been changed at exchange side.

    Can anyone advise why 'authentication unsuccessful' is coming? i also tried to reinstall the services in option manager and recycle services but the issue is still same. i still believe the issue is from Exchange side and not from SDM but is there anything to cross check more from SDM side?

    The nxd mail daemon is already in running mode

    please advise

    https://knowledge.broadcom.com/external/article/141278/error-failed-to-send-mail-reason-javaxma.html
    https://knowledge.broadcom.com/external/article/118908/how-to-fix-no-authentication-mechanisms.html
    https://knowledge.broadcom.com/external/article/186989/email-integration-with-exchange-2016.html
    https://knowledge.broadcom.com/external/article/101452/email-notifications-fail-with-the-error.html



    #caservicedesknotifications
    #casdm17.2
    #camail
    #CAServiceDesk

    ​​​​​​​     Original Message Original Message:
    Sent: 04-13-2020 12:08 PM
    From: PAUL COCCIMIGLIO
    Subject: javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful

    Might be useful to enable debug on pdm_mail_nxd to see if any further information is logged

    https://knowledge.broadcom.com/external/article/98428/how-to-enable-the-debug-or-trace-mode-fo.html

    ------------------------------
    Paul Coccimiglio
    Principal Support Engineer
    Broadcom Inc.

    Original Message:
    Sent: 04-13-2020 09:41 AM
    From: asim Shah
    Subject: javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful

    Hi Folks

    From past 10 days, CA sdm stopped sending notifications and all the mail are going in Mail_Undelivered folder.

    we are getting below error in mail_nxd log file (Check the snapshot below)

    javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful

    I found below related article for this issue but not specifically for " Authentication unsuccessful ".

    i also involved Exchange team to confirm if credentials has been changed or if the IP's are in whitelist  but they are saying nothing has been changed at exchange side.

    Can anyone advise why 'authentication unsuccessful' is coming? i also tried to reinstall the services in option manager and recycle services but the issue is still same. i still believe the issue is from Exchange side and not from SDM but is there anything to cross check more from SDM side?

    The nxd mail daemon is already in running mode

    please advise

    https://knowledge.broadcom.com/external/article/141278/error-failed-to-send-mail-reason-javaxma.html
    https://knowledge.broadcom.com/external/article/118908/how-to-fix-no-authentication-mechanisms.html
    https://knowledge.broadcom.com/external/article/186989/email-integration-with-exchange-2016.html
    https://knowledge.broadcom.com/external/article/101452/email-notifications-fail-with-the-error.html



    #caservicedesknotifications
    #casdm17.2
    #camail
    #CAServiceDesk

    ​​​​​​​
    HI Paul
    i have enabled trace in logback.xml file and also put parameter in nx file " @NX_MAIL_INITIAL_TRACING=Yes " and below error we are getting in logs which shows authentication issue.

    i engaged SMTP team but they are saying from our side  there is no issue because with the same smtp credentials old ca sdm 12.9 is running already and notification are firing and we are using same credentials in 17.2 and it was working fine before 2 weeks.

    Is there anything to check more on sdm side? i still believe that this is not application issue otherwise why would log says "Authentication Unsuccessful"

    How can we tackle this at the moment?


    Original Message Original Message:
    Sent: 04-13-2020 12:08 PM
    From: PAUL COCCIMIGLIO
    Subject: javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful

    Might be useful to enable debug on pdm_mail_nxd to see if any further information is logged

    https://knowledge.broadcom.com/external/article/98428/how-to-enable-the-debug-or-trace-mode-fo.html

    ------------------------------
    Paul Coccimiglio
    Principal Support Engineer
    Broadcom Inc.

    Original Message:
    Sent: 04-13-2020 09:41 AM
    From: asim Shah
    Subject: javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful

    Hi Folks

    From past 10 days, CA sdm stopped sending notifications and all the mail are going in Mail_Undelivered folder.

    we are getting below error in mail_nxd log file (Check the snapshot below)

    javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful

    I found below related article for this issue but not specifically for " Authentication unsuccessful ".

    i also involved Exchange team to confirm if credentials has been changed or if the IP's are in whitelist  but they are saying nothing has been changed at exchange side.

    Can anyone advise why 'authentication unsuccessful' is coming? i also tried to reinstall the services in option manager and recycle services but the issue is still same. i still believe the issue is from Exchange side and not from SDM but is there anything to cross check more from SDM side?

    The nxd mail daemon is already in running mode

    please advise

    https://knowledge.broadcom.com/external/article/141278/error-failed-to-send-mail-reason-javaxma.html
    https://knowledge.broadcom.com/external/article/118908/how-to-fix-no-authentication-mechanisms.html
    https://knowledge.broadcom.com/external/article/186989/email-integration-with-exchange-2016.html
    https://knowledge.broadcom.com/external/article/101452/email-notifications-fail-with-the-error.html



    #caservicedesknotifications
    #casdm17.2
    #camail
    #CAServiceDesk

    ​​​​​​​     The log shows the mail server telling you the authentication is wrong. I would suggest you try the following, in this order, to eliminate any mistakes.
  • Communicate with the SMTP server by hand and attempt the authentication with the credentials you think you are using. You can follow these instructions to the letter, just replace "perl" with "pdm_perl", all the required modules are shipped with SDM: https://www.ndchost.com/wiki/mail/test-smtp-auth-telnet
  • Snoop the network traffic from the SDM server to the mail server to verify the server is really sending the same credentials that you used on test 1. You can use Wireshark for this, but be aware that most security admins will balk at the idea of even suggesting the use of Wireshark.
  • Compare the results of tests 1 and 2 and, if the results differ, compare the encoded username and password to ensure they're exactly the same. Wouldn't be the first time when I see a trailing space/line feed from copy-pasting values messing up the auth.

    • One of those tests should reveal the root cause, good luck.
    Original Message Original Message:
    Sent: 04-19-2020 12:38 PM
    From: asim Shah
    Subject: javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful


    HI Paul
    i have enabled trace in logback.xml file and also put parameter in nx file " @NX_MAIL_INITIAL_TRACING=Yes " and below error we are getting in logs which shows authentication issue.

    i engaged SMTP team but they are saying from our side  there is no issue because with the same smtp credentials old ca sdm 12.9 is running already and notification are firing and we are using same credentials in 17.2 and it was working fine before 2 weeks.

    Is there anything to check more on sdm side? i still believe that this is not application issue otherwise why would log says "Authentication Unsuccessful"

    How can we tackle this at the moment?








    Original Message:
    Sent: 04-13-2020 12:08 PM
    From: PAUL COCCIMIGLIO
    Subject: javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful

    Might be useful to enable debug on pdm_mail_nxd to see if any further information is logged

    https://knowledge.broadcom.com/external/article/98428/how-to-enable-the-debug-or-trace-mode-fo.html

    ------------------------------
    Paul Coccimiglio
    Principal Support Engineer
    Broadcom Inc.

    Original Message:
    Sent: 04-13-2020 09:41 AM
    From: asim Shah
    Subject: javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful

    Hi Folks

    From past 10 days, CA sdm stopped sending notifications and all the mail are going in Mail_Undelivered folder.

    we are getting below error in mail_nxd log file (Check the snapshot below)

    javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful

    I found below related article for this issue but not specifically for " Authentication unsuccessful ".

    i also involved Exchange team to confirm if credentials has been changed or if the IP's are in whitelist  but they are saying nothing has been changed at exchange side.

    Can anyone advise why 'authentication unsuccessful' is coming? i also tried to reinstall the services in option manager and recycle services but the issue is still same. i still believe the issue is from Exchange side and not from SDM but is there anything to cross check more from SDM side?

    The nxd mail daemon is already in running mode

    please advise

    https://knowledge.broadcom.com/external/article/141278/error-failed-to-send-mail-reason-javaxma.html
    https://knowledge.broadcom.com/external/article/118908/how-to-fix-no-authentication-mechanisms.html
    https://knowledge.broadcom.com/external/article/186989/email-integration-with-exchange-2016.html
    https://knowledge.broadcom.com/external/article/101452/email-notifications-fail-with-the-error.html



    #caservicedesknotifications
    #casdm17.2
    #camail
    #CAServiceDesk

    ​​​​​​​     Original Message Original Message:
    Sent: 04-20-2020 01:16 AM
    From: Jussi Valkonen
    Subject: javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful

    The log shows the mail server telling you the authentication is wrong. I would suggest you try the following, in this order, to eliminate any mistakes.
    1. Communicate with the SMTP server by hand and attempt the authentication with the credentials you think you are using. You can follow these instructions to the letter, just replace "perl" with "pdm_perl", all the required modules are shipped with SDM: https://www.ndchost.com/wiki/mail/test-smtp-auth-telnet
    2. Snoop the network traffic from the SDM server to the mail server to verify the server is really sending the same credentials that you used on test 1. You can use Wireshark for this, but be aware that most security admins will balk at the idea of even suggesting the use of Wireshark.
    3. Compare the results of tests 1 and 2 and, if the results differ, compare the encoded username and password to ensure they're exactly the same. Wouldn't be the first time when I see a trailing space/line feed from copy-pasting values messing up the auth.

    One of those tests should reveal the root cause, good luck.
    Original Message:
    Sent: 04-19-2020 12:38 PM
    From: asim Shah
    Subject: javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful


    HI Paul
    i have enabled trace in logback.xml file and also put parameter in nx file " @NX_MAIL_INITIAL_TRACING=Yes " and below error we are getting in logs which shows authentication issue.

    i engaged SMTP team but they are saying from our side  there is no issue because with the same smtp credentials old ca sdm 12.9 is running already and notification are firing and we are using same credentials in 17.2 and it was working fine before 2 weeks.

    Is there anything to check more on sdm side? i still believe that this is not application issue otherwise why would log says "Authentication Unsuccessful"

    How can we tackle this at the moment?








    Original Message:
    Sent: 04-13-2020 12:08 PM
    From: PAUL COCCIMIGLIO
    Subject: javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful

    Might be useful to enable debug on pdm_mail_nxd to see if any further information is logged

    https://knowledge.broadcom.com/external/article/98428/how-to-enable-the-debug-or-trace-mode-fo.html

    ------------------------------
    Paul Coccimiglio
    Principal Support Engineer
    Broadcom Inc.

    Original Message:
    Sent: 04-13-2020 09:41 AM
    From: asim Shah
    Subject: javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful

    Hi Folks

    From past 10 days, CA sdm stopped sending notifications and all the mail are going in Mail_Undelivered folder.

    we are getting below error in mail_nxd log file (Check the snapshot below)

    javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful

    I found below related article for this issue but not specifically for " Authentication unsuccessful ".

    i also involved Exchange team to confirm if credentials has been changed or if the IP's are in whitelist  but they are saying nothing has been changed at exchange side.

    Can anyone advise why 'authentication unsuccessful' is coming? i also tried to reinstall the services in option manager and recycle services but the issue is still same. i still believe the issue is from Exchange side and not from SDM but is there anything to cross check more from SDM side?

    The nxd mail daemon is already in running mode

    please advise

    https://knowledge.broadcom.com/external/article/141278/error-failed-to-send-mail-reason-javaxma.html
    https://knowledge.broadcom.com/external/article/118908/how-to-fix-no-authentication-mechanisms.html
    https://knowledge.broadcom.com/external/article/186989/email-integration-with-exchange-2016.html
    https://knowledge.broadcom.com/external/article/101452/email-notifications-fail-with-the-error.html



    #caservicedesknotifications
    #casdm17.2
    #camail
    #CAServiceDesk

    ​​​​​​​
  • Terms of Use
    •  
    推荐文章
    才高八斗的杯子  ·  C++ lambda表达式与函数对象 详解_lamda表达式直接赋值给函数指针-CSDN博客
    4 月前
    乖乖的手术刀  ·  quartz 报错：Failure obtaining db row lock: Table ‘test.QRTZ_LOCKS‘ doesn‘t exist-CSDN博客
    5 月前
    气宇轩昂的葫芦  ·  OS X El Capitan に matplotlib をインストールする #Python - Qiita
    10 月前
    有腹肌的伤痕  ·  spark数据类型转换函数 - CSDN文库
    10 月前
    体贴的仙人掌  ·  RelativeSource Class (System.Windows.Data) | Microsoft Learn
    10 月前
    Link管理   ·   51好读   ·   Sov5搜索   ·   小百科
    小百科 - 百科知识指南