Proxy Can't Find Config File

[Selwoir]

I want to setup the proxy on my Windows 10 Pro laptop so that Eudora can POP & SMTP with my personal Microsoft email account.

I have copied the pre-built emailproxy.exe and emailproxy.config files into a folder under C:\Program Files (x86).

I edited emailproxy.config so that it only contains the 1995 and 1587 server sections, and a single account section with my MS email address in the header and the Application (client) ID I obtained from Azure. I deleted the Secret line as I understand that isn't needed.

When I run emailproxy.exe, I get the following:

2025-05-29 20:28:25: Initialising Email OAuth 2.0 Proxy (version 2025-03-14) from config file C:\Users\Selwyn Aickin\AppData\Local\Temp\onefile_2688_133930204944489128\emailproxy.config
2025-05-29 20:28:25: Email OAuth 2.0 Proxy config file not found - see https://github.com/simonrob/email-oauth2-proxy for full documentation and example configurations to help get started
2025-05-29 20:28:25: No server configuration(s) found in C:\Users\Selwyn Aickin\AppData\Local\Temp\onefile_2688_133930204944489128\emailproxy.config - exiting
2025-05-29 20:28:25: No server configuration(s) found. Please verify your account and server details in C:\Users\Selwyn Aickin\AppData\Local\Temp\onefile_2688_133930204944489128\emailproxy.config
2025-05-29 20:28:25: Stopping Email OAuth 2.0 Proxy

What am I doing wrong?

[simonrob]

The proxy tries to work out where the configuration file will be based on the particular variant you are using (see here).

The default with the prebuilt version is to look in the same directory as the executable, but here it is looking in C:\Users\Selwyn Aickin\AppData\Local\Temp\onefile_2688_133930204944489128\emailproxy.config instead. I'm not very familiar with the way Windows manages application support files, but this could be a sandboxing issue.

Which pre-built version are you using – Nuitka or PyInstaller?

[Selwoir]

I am using the Nuitka build. Each time I try running the proxy, the long number in the folder name is different. I also tried running it with the two files in an ordinary folder, i.e. one that is not a system folder, but that made no difference.

[simonrob]

It turns out Nuitka uses a different method to mark its executables. I'll fix this, but I'd recommend just using the PyInstaller version instead for now.

[Selwoir]

Hi Simon. Thanks for your suggestion to use the Pyinstaller version instead of the Nuitka version. I have now installed the 64-bit version of Python for Windows v3.13.3 on my laptop and tried running the command in your instructions [python -m pip install emailproxy] but it didn't work and I don't really know what I'm doing as I've never used Python before.

[simonrob]

Ah, I meant you should try the pre-built PyInstaller version rather than the Nuitka version. Since the latest release of the proxy, the pre-built binaries have been available using both approaches in case issues like this crop up. This can be confusing (as you've demonstrated), but is an attempt to give choice in case one or the other doesn't work well on a particular platform.

[Selwoir]

I've now tried the PyInstaller version and have the proxy running on my laptop, and Eudora successfully connecting to it. When I attempt to check my MS account email, I get the pop-up telling me to authorise the account. However, account authentication is not working. I've tried with 'External authorisation mode' both on and off but in either case, I get an error message saying "unauthorized_client: The client does not exist or is not enabled for consumers." I have doubled checked that I went through the application registration process per your instructions and everything seems to be correct so I don't know where it is failing now. Should there be anything defined under the 'Expose an API' or 'App roles' sections in the app registration settings?

[simonrob]

I can't really help with OAuth client setup I'm afraid. But you could try one of the ones linked from the readme, or the proxy's sponsor, auth-email.com, which offers this as a service.

[Selwoir]

Got there in the end! After reading discussion thread #301, I edited the following Manifest entries:
"accessTokenAcceptedVersion": 2,
"signInAudience": "AzureADandPersonalMicrosoftAccount",

I also had to enter the Redirect URI, i.e. http://localhost, under Authentication.