Possible to have separate client_id/client_secret for IMAP and SMTP for the same user account?

[pano9000]

Hi,

we have OAUTH2 set up with O365 (we are using CCG), we do however have two separate application registrations at O365:
One for IMAP (i.e. "reading/managing" the inbox) and one for SMTP (i.e. "sending mails").
In other words: we have two differen client_id and client_secrets for these.

In more modern apps, that support OAUTH2 out of the box, this is working correctly, however we do have some "less modern" apps, where we now need to rely on your promisingly looking proxy :-)

And now to the question:
We have one account, where we need to have both SMTP and IMAP working.
From what I understood from the sample /emailproxy.config though, you can only setup one client_id/client_secret per Account?
But I would need to be able to differentiate the account setup based on the used protocol.
Is there a way to achieve this "natively" with the config file? maybe I am blind, but I cannot see any info about it in the example config file.

If not, I'll probably just end up running two instances of the proxy (one for SMTP, one for IMAP), but it'd be nice to have confirmation first :-)

Thanks in advance!

[simonrob]

No, I'm afraid not – this is not a configuration that I imagined would be needed. Your solution of running two proxy instances is the best approach here for now.

Out of interest, why are you using two separate registrations for this?

[pano9000]

no worries, thanks for confirming my first hunch here.

regarding your question:
I think it could help with having more fine grained control over which mailbox can send (i.e. SMTP) and which ones can only read/manage mails (i.e. IMAP)