locked
Exchange Server 2003, SMTP client got '535 5.7.3 Authentication unsuccessful' RRS feed

  • Question


  • How to reproduce this Problem:

    I created a new user 'test01' with mailbox on Active Directory, and I can send email to 'test01' and can download from this email to local Thunderbird.

    I checked both 'Anonymous' and 'basic Authenticaion', when I tried to connect to Exchange server as below:

    C: telnet exchange.domain.com 25
    S: 220 xx
    C: ehlo
    S: 250 xx
    C: auth login
    S: 334 VXNlcm5hbWU6
    C: xxxxxx
    S: 334 UGFzc3dvcmQ6
    C: xxxxxx
    S: 535 5.7.3 Authentication unsuccessful.

    BTW, the use and password have been base64 encoded. I provided user/pass in Thunderbird to download email successfully, so they have no problem.

    History
    Someone met this problem and think it's a Exchange known issue:
    http://www.apijunkie.com/APIJunkie/blog/post/2007/11/SMTP-535-573-Authentication-unsuccessful-error-on-Exchange-server-2003.aspx

    I created new users but still got this response, and No matter what I tried, I always get this crazy error.

    Who knows how to work around this problem?  I am pulling my hair out :(:(

    Tuesday, August 4, 2009 5:49 AM

Answers

All replies

  • any suggestions/guess are welcome,  Thank you.

    Is it an Exchange Known Issue?  but this is basic functionality, there must be some workarounds.
    Tuesday, August 4, 2009 6:30 AM

  • I have come across this before and found it was the format the username was being provided...

    Have you tried:

    DOMAIN\username
    username AT domain.com

    This resolved it in my case...

    May also be worth selecting either anonymous or basic to see if this makes any difference...

    Let me know if this was any use, if not i'll have a think about what else it could be...

    Carl Ferrer
    Ci6 Ltd - Cheshire Based Exchange, AD and Virtualization Consultants.

    Check out my blog: http://www.ci6.co.uk/blog/


    Carl Ferrer Ci6 Ltd - Cheshire Based Exchange, AD and Virtualization Consultants. Check out my blog: http://www.ci6.co.uk/blog/
    Wednesday, August 5, 2009 1:31 PM
  • Hi,

    First, no such known issue exists in Exchange 2003. Based on your description, I suspect the cause is the user/password issue.

    I would like to share the resource with you as the below link:
    http://www.computerperformance.co.uk/exchange2003/exchange2003_SMTP_Auth_Login.htm

    Thanks

    Allen
    • Marked as answer by Allen Song Friday, August 14, 2009 8:38 AM
    Thursday, August 6, 2009 3:45 AM