Hi, I am one step further with my e-mail notifications, but now I get the following error: Notification failed '1990': Target{type=CUSTOM, id=lxxx@web.de}, reason=Email send failed: 530 Authentication required
My docker-compose.yml looks like:
manager:
# privileged: true
restart: always
image: openremote/manager:${MANAGER_VERSION:-latest}
depends_on:
keycloak:
condition: service_healthy
environment:
OR_SETUP_TYPE:
OR_ADMIN_PASSWORD:
OR_SETUP_RUN_ON_RESTART:
OR_EMAIL_HOST: smtp.web.de
OR_EMAIL_USER: lxxx@web.de
OR_EMAIL_PASSWORD: xxx
OR_EMAIL_PORT: ${OR_EMAIL_PORT:-587}
OR_EMAIL_TLS: ${OR_EMAIL_TLS:-STARTTLS}
OR_EMAIL_X_HEADERS:
OR_EMAIL_FROM: lxxx@web.de
OR_EMAIL_ADMIN:
OR_DATA_POINTS_MAX_AGE_DAYS: 37000
OR_HOSTNAME: ${OR_HOSTNAME:-localhost}
OR_ADDITIONAL_HOSTNAMES: ${OR_ADDITIONAL_HOSTNAMES:-}
OR_SSL_PORT: ${OR_SSL_PORT:--1}
OR_DEV_MODE: ${OR_DEV_MODE:-false}
Where else do I need to authenticate?
It worked now! The problem was the localhost, which replaced the username with my windows username, deleted the password and changed the port from 587 to 25. Without localhost everything works fine with these settings:
manager:
# privileged: true
restart: always
image: openremote/manager:${MANAGER_VERSION:-latest}
depends_on:
keycloak:
condition: service_healthy
environment:
OR_SETUP_TYPE:
OR_ADMIN_PASSWORD:
OR_SETUP_RUN_ON_RESTART:
OR_EMAIL_HOST: ${OR_EMAIL_HOST:-smtp.web.de}
OR_EMAIL_USER: ${OR_EMAIL_USER:-lxxx@web.de}
OR_EMAIL_PASSWORD: ${OR_EMAIL_PASSWORD:-xxx}
OR_EMAIL_PORT: ${OR_EMAIL_PORT:-587}
OR_EMAIL_TLS: ${OR_EMAIL_TLS:-STARTTLS}
OR_EMAIL_X_HEADERS:
OR_EMAIL_FROM: ${OR_EMAIL_FROM:-lxxx@web.de}
OR_EMAIL_ADMIN: ${OR_EMAIL_ADMIN:-lxxx@web.de}
OR_HOSTNAME: ${OR_HOSTNAME:-xxx.de}
OR_ADDITIONAL_HOSTNAMES: ${OR_ADDITIONAL_HOSTNAMES:-}
Denis
April 14, 2023, 1:19pm
3
Hi @deputy-chief-hardy ,
glad to hear that! Sorry, that nobody responsed… it was eastertime
No worries! thanks for your answer now nevertheless do you have maybe an idea why the localhost grabs the windows username? actually docker should be isolated, shouldn’t it?
Denis
April 17, 2023, 7:46am
5
Hi @deputy-chief-hardy ,
this is strange, how do you start the docker?
Grüße nach Karlsruhe.
pcr
April 17, 2023, 8:17am
6
No idea how this is working, I’m always getting the same error (and my hostname is an fqdn so is not localhost)
Denis
April 17, 2023, 8:45am
7
did you tried it without expressions?
just:
OR_EMAIL_HOST: smtp.web.de
OR_EMAL_USER: test@test.de
OR_EMAIL_PASSWORD: xxxxxxxx
pcr
April 17, 2023, 9:08am
8
Same thing
manager_1 | 2023-04-17 11:07:45.569 WARNING [Messaging-NotificationQu..e-26] manager.notification.NotificationService : Error processing from REALM_RULESET - NOTIFICATION_HANDLER_CONFIG_ERROR (Handler is not valid: email): Notification{name='null', message=org.openremote.model.notification.EmailNotificationMessage@1e7e85fc, repeatFrequency=null, repeatInterval='null', targets=[Target{type=CUSTOM, id=my@email.com}]}
this is only with Google Workspace, on another mail domain I could send without problems
Denis
April 17, 2023, 9:09am
9
show your docker-compose.yml pls
pcr
April 17, 2023, 9:12am
10
This is from the other post where we discussed this issue
Let me know if you want the full yml
Denis
April 17, 2023, 9:16am
11
you sure you tested it this way too?
` environment:
OR_SETUP_TYPE:
OR_ADMIN_PASSWORD:
OR_SETUP_RUN_ON_RESTART:
OR_EMAIL_HOST: my.smtp.com
OR_EMAIL_USER: my@username.com
OR_EMAIL_PASSWORD: mypassword
OR_EMAIL_PORT: ${OR_EMAIL_PORT:--1}
#OR_EMAIL_TLS: ${OR_EMAIL_TLS:-STARTTLS}
OR_EMAIL_X_HEADERS:
OR_EMAIL_FROM: my@username.com
OR_EMAIL_ADMIN:
pcr
April 17, 2023, 9:19am
12
I just tried it when you asked me few minutes ago (except for port 1, you can’t really send on port 1?)
I need to try to comment TLS option, but i’m pretty sure Google will refuse it, give me a min
Denis
April 17, 2023, 9:21am
13
Google doesn’t allow it.
environment:
OR_SETUP_TYPE:
OR_ADMIN_PASSWORD:
OR_SETUP_RUN_ON_RESTART:
OR_EMAIL_HOST: my.smtp.com
OR_EMAIL_USER: my@username.com
OR_EMAIL_PASSWORD: mypassword
OR_EMAIL_PORT: ${OR_EMAIL_PORT:-587}
OR_EMAIL_TLS: ${OR_EMAIL_TLS:-true}
OR_EMAIL_X_HEADERS:
OR_EMAIL_FROM: my@username.com
OR_EMAIL_ADMIN:
could also try 465 instead of 587
pcr
April 17, 2023, 9:21am
14
yes but i’m using app-specific password
pcr
April 17, 2023, 9:37am
16
So I tried this configuration with 587, 465 and even regenerating the password, nothing works.
Fun fact: Google doesn’t even show the password as used
apurba
April 17, 2023, 5:11pm
17
I am using GoDaddy mail, and it worked .
Try another domain , i also face same problem from gmail.
pcr
April 18, 2023, 7:11am
18
I already make it work with another domain, but that’s not the point of course. We are trying to make it work with Google
Hi @Denis , I started Docker via docker-compose -p openremote up -d
Grüße zurück
Rich
April 25, 2023, 9:44pm
20
Apologies, please see this thread:
Apologies for the delayed response.
We had made a change to the mail library used internally and this broke the STARTTLS config option but this was fixed in the past few weeks so make sure you have the latest manager version and STARTTLS will work again.
pcr
April 26, 2023, 7:50am
21
Hi Rich
did another pull, but still no luck with Google
tried with this
OR_EMAIL_HOST: gmail.smtp.com
OR_EMAIL_USER: myemail@domain.com
OR_EMAIL_PASSWORD: xxxxxxxxxxxx
OR_EMAIL_PORT: ${OR_EMAIL_PORT:-587}
OR_EMAIL_TLS: ${OR_EMAIL_TLS:-true}
OR_EMAIL_X_HEADERS:
OR_EMAIL_FROM: myemail@domain.com
# OR_EMAIL_ADMIN: ${OR_EMAIL_ADMIN:-myemail@domain.com}
and this
OR_EMAIL_HOST: gmail.smtp.com
OR_EMAIL_USER: myemail@domain.com
OR_EMAIL_PASSWORD: xxxxxxxxxxxx
OR_EMAIL_PORT: ${OR_EMAIL_PORT:-587}
OR_EMAIL_TLS: ${OR_EMAIL_TLS:-STARTTLS}
OR_EMAIL_X_HEADERS:
OR_EMAIL_FROM: myemail@domain.com
# OR_EMAIL_ADMIN: ${OR_EMAIL_ADMIN:-myemail@domain.com}
The error is always the same
manager_1 | 2023-04-26 09:50:21.456 WARNING [Messaging-NotificationQu…e-26] manager.notification.NotificationService : Error processing from REALM_RULESET - NOTIFICATION_HANDLER_CONFIG_ERROR (Handler is not valid: email): Notification{name=‘null’, message=org.openremote.model.notification.EmailNotificationMessage@1d9e8e96, repeatFrequency=null, repeatInterval=‘null’, targets=[Target{type=CUSTOM, id=myemail@mydomain.com }]}
edit: app-specific password still shows as never used on Google side