A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/simonrob/email-oauth2-proxy/discussions/301 below:

Hotmail/Free Outlook accounts · simonrob/email-oauth2-proxy · Discussion #301 · GitHub

Hi Simon,

First thanks for writing this proxy server, both my spam filter and pop checker are working.

I just saw your update regarding Hotmail/Free Outlook accounts; I was trying to use the Azure Portal website to set everything up, although everything appeared to be OK, I kept on getting authentication errors.

Just about to give when I came across another proxy server, Raiden Mail Oauth Proxy. On Raidens website it gave instructions on how to setup client_id/client_secret but using the Microsoft Entra website, not the Azure Portal website.

However, this gave me the following error:

2024-10-20 22:56:08,123: Authorisation request received for xxxxxxxxxx@outlook.com (interactive mode)
2024-10-20 22:56:17,170: Returning authorisation request result for xxxxxxxxxx@outlook.com
2024-10-20 22:56:17,172: Authorisation result error for account xxxxxxxxxx@outlook.com - aborting login. OAuth 2.0 authorisation error for account xxxxxxxxxx@outlook.com: invalid_request; The request is not valid for the application's 'userAudience' configuration. In order to use /common/ endpoint, the application must not be configured with 'Consumer' as the user audience. The userAudience should be configured with 'All' to use /common/ endpoint.
2024-10-20 22:56:17,174: POP (127.0.0.1:54802-{127.0.0.1:3995}-outlook.office365.com:995)     --> b'*\r\n'
2024-10-20 22:56:17,192: POP (127.0.0.1:54802-{127.0.0.1:3995}-outlook.office365.com:995)     <-- b'-ERR The AUTH protocol exchange was canceled by the client.\r\n'
2024-10-20 22:56:17,193: POP (127.0.0.1:54802-{127.0.0.1:3995}-outlook.office365.com:995) <-- b"-ERR Authentication failed. Email OAuth 2.0 Proxy: Login failed for account xxxxxxxxxx@outlook.com: OAuth 2.0 authorisation error for account xxxxxxxxxx@outlook.com: invalid_request; The request is not valid for the application's 'userAudience' configuration. In order to use /common/ endpoint, the application must not be configured with 'Consumer' as the user audience. The userAudience should be configured with 'All' to use /common/ endpoint.\r\n"
2024-10-20 22:56:17,205: POP (127.0.0.1:54802-{127.0.0.1:3995}-outlook.office365.com:995) --> b'QUIT\r\n'

A quick Google search and the suggestions were to edit the Manifest and change the "signInAudience" from "PersonalMicrosoftAccount" to "AzureADandPersonalMicrosoftAccount", then everything authenticated successfully:

2024-10-20 23:03:05,508: Accepting new connection from 127.0.0.1:54998 to POP server at 127.0.0.1:3995 (unsecured) proxying outlook.office365.com:995 (SSL/TLS)
2024-10-20 23:03:05,508: Ignoring incoming connection to POP server at 127.0.0.1:3995 (unsecured) proxying outlook.office365.com:995 (SSL/TLS) - no connection information
2024-10-20 23:03:05,615: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995) --> [ Client connected ]
2024-10-20 23:03:05,615: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995) <-> [ Starting TLS handshake ]
2024-10-20 23:03:06,041: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995) <-> [ TLSv1.2 handshake complete ]
2024-10-20 23:03:06,043: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995)     <-- b'+OK The Microsoft Exchange POP3 service is ready. [TABPADQAUAAyADYANQBDAEEAMAAwADcANAAuAEcAQgBSAFAAMgA2ADUALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]\r\n'
2024-10-20 23:03:06,043: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995) <-- b'+OK The Microsoft Exchange POP3 service is ready. [TABPADQAUAAyADYANQBDAEEAMAAwADcANAAuAEcAQgBSAFAAMgA2ADUALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]\r\n'
2024-10-20 23:03:06,046: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995) --> b'USER xxxxxxxxxx@outlook.com\r\n'
2024-10-20 23:03:06,046: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995) <-- b'+OK\r\n'
2024-10-20 23:03:06,062: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995) --> b'PASS [[ Credentials removed from proxy log ]]\r\n'
2024-10-20 23:03:06,062: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995)     --> b'AUTH XOAUTH2\r\n'
2024-10-20 23:03:06,077: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995)     <-- b'+ \r\n'
2024-10-20 23:03:07,025: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995)     --> b'[[ Credentials removed from proxy log ]]\r\n'
2024-10-20 23:03:07,698: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995; xxxxxxxxxx@outlook.com)     <-- b'+OK User successfully authenticated.\r\n'
2024-10-20 23:03:07,698: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995; xxxxxxxxxx@outlook.com) [ Successfully authenticated POP connection - releasing session ]
2024-10-20 23:03:07,698: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995; xxxxxxxxxx@outlook.com) <-- b'+OK User successfully authenticated.\r\n'
2024-10-20 23:03:07,701: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995; xxxxxxxxxx@outlook.com) --> b'STAT\r\n'
2024-10-20 23:03:07,810: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995; xxxxxxxxxx@outlook.com) <-- b'+OK 2 212965\r\n'
2024-10-20 23:03:07,812: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995; xxxxxxxxxx@outlook.com) --> b'LIST\r\n'
2024-10-20 23:03:07,895: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995; xxxxxxxxxx@outlook.com) <-- b'+OK 2 212965\r\n1 133774\r\n2 79191\r\n.\r\n'
2024-10-20 23:03:07,899: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995; xxxxxxxxxx@outlook.com) --> b'UIDL\r\n'
2024-10-20 23:03:07,964: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995; xxxxxxxxxx@outlook.com) <-- b'+OK\r\n1 7425\r\n2 7429\r\n.\r\n'
2024-10-20 23:03:07,967: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995; xxxxxxxxxx@outlook.com) --> b'RETR 1\r\n'
2024-10-20 23:03:08,116: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995; xxxxxxxxxx@outlook.com) <-- b'+OK\r\n'
2024-10-20 23:03:08,250: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995; xxxxxxxxxx@outlook.com) --> b'DELE 1\r\n'
2024-10-20 23:03:08,305: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995; xxxxxxxxxx@outlook.com) <-- b'+OK\r\n'
2024-10-20 23:03:08,307: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995; xxxxxxxxxx@outlook.com) --> b'RETR 2\r\n'
2024-10-20 23:03:08,425: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995; xxxxxxxxxx@outlook.com) <-- b'+OK\r\n'
2024-10-20 23:03:08,462: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995; xxxxxxxxxx@outlook.com) --> b'DELE 2\r\n'
2024-10-20 23:03:08,507: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995; xxxxxxxxxx@outlook.com) <-- b'+OK\r\n'
2024-10-20 23:03:08,514: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995; xxxxxxxxxx@outlook.com) --> b'QUIT\r\n'
2024-10-20 23:03:09,271: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995; xxxxxxxxxx@outlook.com) <-- b'+OK Microsoft Exchange Server POP3 server signing off.\r\n'
2024-10-20 23:03:09,275: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995; xxxxxxxxxx@outlook.com) --> [ Client disconnected ]
2024-10-20 23:03:09,278: POP (127.0.0.1:54998-{127.0.0.1:3995}-outlook.office365.com:995) <-- [ Server disconnected ]

So instead of trying to use another applications client_id which has the potential to change and cause problems, you can create your own using Microsofts Entra website.

Colin.


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4