e-mail not longer working

[eddydc]

Describe the bug

Hi,
I didn't notice it, but since a month or so, I don't get any e-mails from watchtower.
It used to work properly with

          environment:
            - WATCHTOWER_NOTIFICATIONS=email
            - WATCHTOWER_NOTIFICATION_EMAIL_FROM=XXXX
            - WATCHTOWER_NOTIFICATION_EMAIL_TO=XXX
            - WATCHTOWER_NOTIFICATION_EMAIL_SERVER=XXXX
            - WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PORT=465
            - WATCHTOWER_NOTIFICATION_EMAIL_SERVER_USER=XXXX
            - WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PASSWORD=XXX
            - WATCHTOWER_NOTIFICATION_EMAIL_DELAY=2

I'm getting

level=error msg="Failed to send shoutrrr notification" error="error authenticating: 535 5.7.0 Incorrect username or password."

The credentials are still valid and work when trying this

docker run --rm -it containrrr/shoutrrr send -v "smtp://xxx:xxx@xxxx:465/?auth=Plain&encryption=Auto&fromaddress=xxx&fromname=Watchtower&starttls=No&subject=Watchtower_updates_on_xxx&toaddresses=xxx&usehtml=No" TestMessage

So I tried

          environment:
            - WATCHTOWER_NOTIFICATION_URL="smtp:/xxx:xxx@xxx:465/?auth=Plain&encryption=Auto&fromaddress=xxx&fromname=Watchtower&starttls=No&subject=Watchtower_updates_on_xxx&toaddresses=xxx&usehtml=No"

and that fails too with the same error

What can I do in order to resolve this?
Many thanks in advance

Expected behavior

Sending e-mails as it used to be

Screenshots

No response

Environment

• Platform
• Architecture
• Docker Version Watchtower 1.5.3

Your logs

"Failed to send shoutrrr notification" error="error authenticating: 535 5.7.0 Incorrect username or password."

Additional context

No response

[github-actions]

Hi there! 👋🏼 As you're new to this repo, we'd like to suggest that you read our code of conduct as well as our contribution guidelines. Thanks a bunch for opening your first issue! 🙏

[piksel]

Try using:

environment:
            - "WATCHTOWER_NOTIFICATION_URL=smtp://xxx:xxx@xxx:465/?auth=Plain&encryption=Auto&fromaddress=xxx&fromname=Watchtower&starttls=No&subject=Watchtower_updates_on_xxx&toaddresses=xxx&usehtml=No"

(two slashes and the quotes around the whole string, not just the value)

[eddydc]

The two slashes were already there. I was a bit enthusiastic when trying to obfuscate the credentials.
Quotes around the whole strings doesn't seem to make a difference.

[piksel]

The only thing I can think of is that there is some character in the username or password that gets interpreted differently when running from command line compared to when set in YAML.

You could try using

encodeURIComponent('username')+':'+encodeURIComponent('password') 

in either nodejs or the browser console and see if any part of them gets escaped perhaps (and if so, use the escaped form in the URL).

[eddydc]

The username is an e-mail address, so I escaped @ with %40. Same result though when I restart the container.
Also tried the bare minimum with only server witch credentials, from and to. That doesn't work either
Wondering why it used to work with the same credentials, even with the legacy syntax.
Postfix and docker run --rm -it containrrr/shoutrrr send -v doesn't make any problems either.

[mundeczek]

I have the same problem, watchtower 1.5.3
level=error msg="Failed to send shoutrrr notification" error="error authenticating: 535 Incorrect authentication data" index=0 notify=no service=smtp
I checked the login details, they are correct.