Open irobot73 opened 6 months ago
Can you check within the diun container that the secret file exists and is not empty?
docker compose exec diun cat /run/secrets/smtp_username
Can you check within the diun container that the secret file exists and is not empty?
docker compose exec diun cat /run/secrets/smtp_username
Sorry for the response delay. Yes, CAT of both ..username & ..password SECRETS respond w/ the expected values
ddick@ubuntu:/nas/Data/diun$ docker compose exec diun cat /run/secrets/smtp_username
i_{rest_of_expected_email_addy}.comddick@ubdocker compose exec diun cat /run/secrets/smtp_password
p{rest_of_expected_pw}yddick@ubuntu:/nas/Data/diun$
Believe I 'hand-jammed' & utilized PRINTF as per...no /CR or /LF noted in the output
Support guidelines
I've found a bug and checked that ...
Description
Using SECRET file in the TO parameter of the NOTIF for mail generates an error upon init. self-test.
Working:
Either instance below throws error:
or
Expected behaviour
System can re-use the existing SECRET, same as if typed in directly
Actual behaviour
Errors:
Steps to reproduce
Diun version
Latest (v4.26.0)
Docker info
Docker Compose config
Logs
Additional info
No response