-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Microsoft Auth #15
Comments
The exact error message would be helpful. Try going to your webbrowswer and goto http://accounts.microsoft.com and log out of the account. Then try login again |
The error message is
It happens in IdSASLCollection unit.
The Cmd command is returning error. Maybe microsoft has changed any protocol urls? Or is it a problem with my user? I wonder why might be happening. The cmd string passed is like this:
|
@p-samuel |
@marcin-bury, thanks for noticing! I'll try making the appropriate changes. It seems the only problem is not encoding the login credentials. The SMTP docs states that it should be as follows:
|
@p-samuel, it is doing! No error from the library's part. The |
The case is that there should be addtional characters Char(1) in the string. |
In the past few days Microsoft has tightened up security restrictions for access. They appear to be forcing 2fa as well. For the moment this means that the account I was using to test my code becomes unavailable to me. |
any news on this? i also cannot resolve the "Authentication unsuccessful" error |
Has anyone got Office365 credentials to work?. I'm getting the 5.7.3 Authentication Unsuccessful error as well. IdSASLCollection.PerformSASLLogin is not adding the extra ("^A^A") characters to the end of the AUTH XOAUTH2 command. |
Hi @geoffsmith82! Have you tried connecting with Microsoft's credentials? I don't know if I'm missing something, but after credentials login page is closed (in microsoft's login page), a message error is displayed stating that was not able to authenticate if you try sending a message.
The text was updated successfully, but these errors were encountered: