-
| Hi, I'm trying to configure this proxy on docker to improve some services that I have but I don't achieve it. For example(almost real), I have a personal wiki shared with a friend, or a git repository on my self-hosted infrastructure. It has been configured to send an email when someone public a pull-request, but it hasn't Oauth support. Ok, I tried to set up an O365 and a gmail account. I just copied the examples and I just added the client id and secret that O365 and gmail gave me. The process stucks on reading the documentation I thought that I needed an apppassword so I started that process on gmail... but same results. What thing am I doing wrong? By the way, I'm using --no-gui argument because I'm using a docker image, no GUI. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
| Adding more context. This could be my config file: [IMAP-1993] documentation = *** O365 server_address = outlook.office365.com server_port = 993 local_address = 0.0.0.0 [IMAP-2993] server_address = imap.gmail.com server_port = 993 local_address = 0.0.0.0 [SMTP-1587] documentation = *** O365 server_address = smtp-mail.outlook.com server_port = 587 server_starttls = True local_address = 0.0.0.0 [SMTP-2465] server_address = smtp.gmail.com server_port = 465 local_address = 0.0.0.0 [emailexample@outlook.com] permission_url = https://login.microsoftonline.com/common/oauth2/v2.0/authorize token_url = https://login.microsoftonline.com/common/oauth2/v2.0/token oauth2_scope = https://outlook.office.com/IMAP.AccessAsUser.All https://outlook.office.com/POP.AccessAsUser.All https://outlook.office.com/SMTP.Send offline_access redirect_uri = http://localhost client_id = balblablablablabla-idblablabla-idididididid client_secret = shhhhhhecretchheecret-blablablabla [emailexample@gmail.com] permission_url = https://accounts.google.com/o/oauth2/auth token_url = https://oauth2.googleapis.com/token oauth2_scope = https://mail.google.com/ redirect_uri = http://localhost client_id = balblablablablabla-idblablabla-idididididid.apps.googleusercontent.com client_secret = shhhhhhecretchheecret-blablablabla [emailproxy] delete_account_token_on_password_error = True encrypt_client_secret_on_first_use = False use_login_password_as_client_credentials_secret = False allow_catch_all_accounts = False |
Beta Was this translation helpful? Give feedback.
-
| Are you at any point actually authorising the account? The proxy can't remove the need to do this; it just moves it to a different place. Either do this separately and copy over the modified proxy configuration file, or use the shell in your docker image. See the readme for more details here. Also - you mention app passwords: if you can generate these then you don't need the proxy at all. Just use the app password instead of your actual password in your client's SMTP configuration. |
Beta Was this translation helpful? Give feedback.
-
No, and that was the problem. I feel stupid, but thanks! I was really stuck. If it hadn't been for your answer, although looking back on it now it was pretty obvious, I wouldn't have gotten it. I just apologize and thank you! |
Beta Was this translation helpful? Give feedback.
Are you at any point actually authorising the account? The proxy can't remove the need to do this; it just moves it to a different place. Either do this separately and copy over the modified proxy configuration file, or use the shell in your docker image. See the readme for more details here.
Also - you mention app passwords: if you can generate these then you don't need the proxy at all. Just use the app password instead of your actual password in your client's SMTP configuration.