Domoticz

Posted: **Monday 09 January 2023 20:21**

I did the thnigs you say..:

Only still

Log and settings ..
Did not working?

xLink: value Temperature,idx=8,name=BR:-Ground-Temperature-(10-cm) value=5.6
2023-01-09 20:18:07.791 InfluxLink: value Temperature,idx=9,name=BR:-Feel-Temperature value=3.2
2023-01-09 20:18:07.759 Status: Notification: Het blijft droog voorlopig
2023-01-09 20:18:07.760 Error: SMTP Mailer: Error sending Email to: <[email protected]> !
2023-01-09 20:18:07.760 Error: libcurl: (3)
2023-01-09 20:18:07.760 Error: URL using bad/illegal format or missing URL
2023-01-09 20:18:07.760
2023-01-09 20:18:07.760 Error: Failed to send Email notification!
2023-01-09 20:18:08.396 Status: Incoming connection from: 192.168.5.73
2023-01-09 20:18:11.019 Notification sent (email) => Failed
2023-01-09 20:18:11.022 Active notification Subsystems: browser, email (2/13)
2023-01-09 20:18:11.109 EVK mqtt: General/Current (WPB Heater tank current)
2023-01-09 20:18:11.117 EVK mqtt: General/kWh (WPB Heater Tot)
2023-01-09 20:18:11.122 EVK mqtt: General/kWh (WPB Heater Tot)
2023-01-09 20:18:11.125 EVK mqtt: Usage/Electric (WPB Heater Act)
2023-01-09 20:18:11.129 EVK mqtt: General/Voltage (WPB Heater tank voltage)
2023-01-09 20:18:11.296 InfluxLink: value Instant,idx=216,name=WPB-Heater-Tot value=0.000
2023-01-09 20:18:11.296 InfluxLink: value Instant,idx=216,name=WPB-Heater-Tot value=0.000
2023-01-09 20:18:11.296 InfluxLink: value Usage,idx=199,name=WPB-Heater-Act value=0.000
2023-01-09 20:18:11.019 Status: Notification: Domoticz test
2023-01-09 20:18:11.019 Error: SMTP Mailer: Error sending Email to: <info@inxxxxxnl> !
2023-01-09 20:18:11.019 Error: libcurl: (3)
2023-01-09 20:18:11.019 Error: URL using bad/illegal format or missing URL
2023-01-09 20:18:11.019
2023-01-09 20:18:11.019 Error: Failed to send Email notification!

And

: ScreenShot327.png (29.55 KiB) Viewed 745 times

: ScreenShot328.png (4.65 KiB) Viewed 745 times

I Copy paste the password

Posted: **Monday 09 January 2023 20:23**

Seems one of the email adresses you are using has a type error.

Posted: **Monday 09 January 2023 20:36**

waltervl wrote: ↑Monday 09 January 2023 20:23 Seems one of the email adresses you are using has a type error.

No i make them xx for here

Posted: **Tuesday 10 January 2023 0:21**

Do you have special characters in the addresses? It says it cannot connect to the email host due to bad url. Or it is some firewall that is blocking you.

Posted: **Tuesday 10 January 2023 8:15**

waltervl wrote: ↑Tuesday 10 January 2023 0:21 Or it is some firewall that is blocking you.

To figure out if there is something wrong on the mail connect path, you can check manually. On old uncyphered mail servers (usually using port 25), we could use "telnet <smtpSrv> <smtpPort>" to connect and even send a few test commands manually.

For cyphered ones (using port 465 or 587), openssl command under Linux allows this using:
"openssl s_client -connect <smtpSrv>:<smtpPort>"

For instance, if using google smtp:

Code: Select all

openssl s_client -connect smtp.gmail.com:465
CONNECTED(00000003)

(...) all certs stuff skipped, then send a NOOP (No Operation) command to check basic server answer. => 250/OK response

noop
250 2.0.0 OKoop
250 2.0.0 OK

All smtp commands can be send manually, just as a mail client would do (but not reporting so many information in case of errors):
https://www.samlogic.net/articles/smtp- ... erence.htm

Unfortunately probably to avoid spam robots to check mail addresses validity, VRFY command to check this gives this laconic answer:

Code: Select all

vrfy [email protected]
252 2.1.5 Send some mail, I'll try my best

Server capabilities can 1st be checked using EHLO (smtp extended ) command on google domain:

Code: Select all

ehlo google.com
250-smtp.gmail.com at your service, [XXX]
250-SIZE 35882577
250-8BITMIME
250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-CHUNKING
250 SMTPUTF8

AUTH command may then also be used to check login credentials are OK taking care to use one among hereupper advertised login methods...

Posted: **Tuesday 10 January 2023 12:01**

No, I can't get it to work, even though I've done everything here. Have I written correctly?
should I write ?
Server:
smtp.gmail.com
Port:465
User name:[email protected]
Password:
••••••••••••••••

Posted: **Tuesday 10 January 2023 12:22**

losholmen wrote: ↑Tuesday 10 January 2023 12:01 No, I can't get it to work, even though I've done everything here. Have I written correctly?

libcurl returns 3 (CURLE_URL_MALFORMAT). So double check smtp server + port (that will be used to build the url), that indeed looks correct, does not include a non printable char that cannot be seen in your capture but that is taken into account by libcurl.

Otherwise, try hereupper proposed checks to be able to see is server can be reached and what is advertised as supported login methods. Those printed are the one I get and no issue with domoticz configured like you, provided you use the configured application password (Oauth is not implemented in Domoticz).

Domoticz

GMAIL: No more login/passwd soon...

Re: GMAIL: No more login/passwd soon...

Re: GMAIL: No more login/passwd soon...

Re: GMAIL: No more login/passwd soon...

Re: GMAIL: No more login/passwd soon...

Re: GMAIL: No more login/passwd soon...

Re: GMAIL: No more login/passwd soon...

Re: GMAIL: No more login/passwd soon...