Unanswered requiring smtp authentication

  • 2007년 10월 3일 수요일 오전 12:12
     
     
    I am trying to secure our Exchange 2003 server by creating a second SMTP virtual server for off-network users to relay through after authenticating.

    I have a newly created SMTP virtual server running on porl 26.  I have enabled basic authentication without TLS, and disabled anonymous authentication and NTLM authentication.  Now I'm trying to authenticate from a workstation on the same subnet as the email server as a test.

    I first tried setting up a test email account in Outlook Express using port 26 and the same credentials for POP3 and SMTP.  The account receives mail properly, but continually prompts for a username/password when trying to send...

    Using telnet I can connect to the SMTP server on port 26.  An EHLO command shows that AUTH LOGIN is a recognized command.  When I try to authenticate using my Base64 encoded credentials, it always states Authentication Unsuccessful.

    I'm not yet trying to use TLS or SSL (as I'm just testing from the same subnet) so I don't have a certificate installed yet.  I think my setup is as basic as it can be made for authentication.  What am I missing?

    Thanks in advance.

모든 응답

  • 2007년 10월 8일 월요일 오전 1:54
     
     
  • 2007년 10월 9일 화요일 오후 3:40
     
     
    Thanks for the reply.  I think I may have been unclear in my original post.

    The link posted above shows how to make an Exchange server authenticate to another server.  I'm trying to make a client (Outlook Express) authenticate to our Exchange server before sending.  The client can authenticate on receiving without any problems, but I can't get it to work with sending.
  • 2007년 10월 11일 목요일 오전 9:28
     
     

    I have the exact same problem.

     

    I found many references to the problem but no one seems to have solved it.

     

    I am starting to suspect it’s a bug in exchange authentication.

     

    Authentication works for POP3 and IMAP but refuses to work for SMTP.

     

    Outlook express goes in a loop asking for credentials as you described.

     

    If I telnet to the server and login using auth login and base64, I receive the following error: "535 5.7.3 Authentication unsuccessful."

     

  • 2007년 10월 22일 월요일 오후 9:22
     
     
    I'm having the same problem.

    I have a front-end IIS SMTP server (as a VPS in a datacenter) to submit email back into the Exchange server. However, spam users send it directly towards the Exchange server.

    To overcome this issue, I disabled Anonymous Access (left Basic Authentication and Windows NTLM enabled) on the Exchange SMTP and configured the username and password on the IIS SMTP server. However, email doesn't come through. Testing through Telnet gives me "Authentication unsuccessful" as well.

    However, the Exchange server authenticates through the same method to relay at the IIS SMTP server and that works fine.

    The only difference I see is that the IIS SMTP server is in a workgroup and the Exchange server is part of the company domain.

    Any suggestions?
  • 2007년 10월 24일 수요일 오후 4:16
     
     

    The account must be specified in the following format "netbios domain name\windowaccount\alias\

     

  • 2007년 11월 7일 수요일 오후 2:30
     
     

    Creating second virtual server is not recommended by microsoft, more over you need to go virtual server relay permission and need to give the access to ip address of the machine or user name to relay the emails.

  • 2007년 11월 10일 토요일 오전 1:27
     
     

     

    I finally found the solution to my smtp authentication problem.

     

    You can find it here:

     

    http://www.apijunkie.com/APIJunkie/blog/post/2007/11/SMTP-535-573-Authentication-unsuccessful-error-on-Exchange-server-2003.aspx

     

     

  • 2012년 2월 22일 수요일 오전 4:17
     
     

    I finally found the solution to my smtp authentication problem. You can find it here:

    http://www.apijunkie.com/APIJunkie/blog/post/2007/11/SMTP-535-573-Authentication-unsuccessful-error-on-Exchange-server-2003.aspx

    I'm having this exact same problem but it appears that the site you reference no longer exists. Do you remember what you did to make this work?
  • 2012년 2월 29일 수요일 오후 4:02
     
     

    kroggy im having this issue too. the site just says to create a new user. this site is referencing 2003 so i'm not too sure if it applies.

    anyone help?

  • 2012년 2월 29일 수요일 오후 4:29
     
     

    In my case it turned out be because I was trying to authenticate with an administrative user. As soon as I tried a non-administrative user (just a plain old test user I created) it worked just fine.

    I proposed it as the answer here: http://serverfault.com/a/362687/44089