Closed alteriks closed 3 months ago
This is a great find on your part. Thank you for sharing this.
I will keep with the regular Apprise Laws (if we call them that) and always ensure that ?arg=param
over-ride all to eliminate ambiguity. But the built in Apprise variables such as pass=
and others were definitely not being correctly parsed from the URL (found in YAML files) and arguments (if specified in-line thereafter).
I fixed this in the attached PR and added test cases thanks to the great examples you provided.
Code has been merged into master; so it will definitely make it to the next release.
Thank you so much for reporting this. :rocket: :pray:
Chris
:mega: Notification Service(s) Impacted Notify_email
:lady_beetle: Describe the bug Using Notify_email variables
user
andpass
in yaml doesn't work. Both variables are ignored in yaml, they only work in mailtos url. This should work and make config more readable:But unfortunately it doesn't :/![image](https://github.com/caronc/apprise/assets/6512767/113cee7d-9b23-447c-b31b-15ef189f65a5)
I've created test environment in my homelab with following:
✅User and pass specified in mailtos url:
❗Overiding
nonexistinguser
withtestuser
doesn't work:user: testuser@alt.lan
should override mailtosnonexistinguser@alt.lan
, mail should be send❗Overiding
testuser
withnonexistinguser
doesn't work:user: nonexistinguser@alt.lan
should override mailtostestuser@alt.lan
, mail shouldn't be send❗Not specifying user and pass in
mailtos
url doesn't work:❗Overriding good pass
xxxxXXXxxx
withnonexistingpass
sends email, but it shouldn't:computer: Your System Details: