Bug: fail in SMTP notification service via Shoutrrr #306

New Issue

saavagebueno · 2025-11-20T04:22:32-05:00

saavagebueno commented

2025-11-20 04:22:32 -05:00

Originally created by @pbodq2 on GitHub (Aug 30, 2023).

SMTP authentication fails in v2.5.0 onward but not v2.4.1

Is this urgent: No
DNS provider(s) you use: Cloudflare
Program version:
Running Docker images
v2.5.0
Digest:sha256:71322af80a53fbafa8106c2a111ba8f21e8f1c72d8df01282422e837ff616c39
latest built on Aug-8-2023
Digest:sha256:834268eaa69c802e51e9fa377074fc95ccf58201a2592126367b1a072369d7d7
What are you using to run the container: Synology DSM built Docker package v20.10.3
Extra information (optional)

Logs:

Both v2.4.1 and v2.5.0 are fresh download and created. Using the same SHOUTRRR_ADDRESSES as below, problem only occurs in v2.5.0. Now, I roll back to v2.4.1 and I can receive emails.
Under v2.5.0, no matter what protocals I tried, Gmail at port 587 still rejects my connection.

I explicitly run a Windows x64 exe which I downloaded from Shoutrrr site. The below address URI runs very well and I can receive emails.

Configuration file (remove your credentials!):

-e SHOUTRRR_ADDRESSES=smtp://sender@gmail.com:password@smtp.gmail.com:587/?from=sender@gmail.com&to=receiver@gmail.com

Host OS: Synology DSM 6.2.2-24922 Update 4

Originally created by @pbodq2 on GitHub (Aug 30, 2023). SMTP authentication fails in v2.5.0 onward but not v2.4.1 1. Is this urgent: No 2. DNS provider(s) you use: Cloudflare 3. Program version: Running Docker images **_v2.5.0_** Digest:sha256:71322af80a53fbafa8106c2a111ba8f21e8f1c72d8df01282422e837ff616c39 **_latest built on Aug-8-2023_** Digest:sha256:834268eaa69c802e51e9fa377074fc95ccf58201a2592126367b1a072369d7d7 4. What are you using to run the container: Synology DSM built Docker package v20.10.3 5. Extra information (optional) Logs: ![v250](https://github.com/qdm12/ddns-updater/assets/25418300/a0677975-c0c3-4a20-bb78-caf44378afb1) Both v2.4.1 and v2.5.0 are fresh download and created. Using the same SHOUTRRR_ADDRESSES as below, problem only occurs in v2.5.0. Now, I roll back to v2.4.1 and I can receive emails. Under v2.5.0, no matter what [protocals](https://containrrr.dev/shoutrrr/v0.7/services/email/) I tried, Gmail at port 587 still rejects my connection. I explicitly run a Windows x64 exe which I downloaded from Shoutrrr site. The below address URI runs very well and I can receive emails. Configuration file (**remove your credentials!**): -e SHOUTRRR_ADDRESSES=smtp://sender@gmail.com:password@smtp.gmail.com:587/?from=sender@gmail.com&to=receiver@gmail.com Host OS: Synology DSM 6.2.2-24922 Update 4

saavagebueno added the Priority: 💤 Low priority Closed: ⚰️ Inactive Category: Shoutrrr 📢 labels 2025-11-20 04:22:32 -05:00

saavagebueno closed this issue

2025-11-20 04:22:32 -05:00

saavagebueno commented

2025-11-20 04:22:33 -05:00

@qdm12 commented on GitHub (Jan 18, 2024):

Can you try pulling and running the latest image? Shoutrrr just got upgraded to v0.8.0 in commit e02880fe1f8b738d47cd2b52583d1e32d5d2d734 maybe this solves it for you? Otherwise I'm not too sure, since this error comes from the Shoutrrr library so it's rather hard to debug etc. and I don't really want to downgrade either 😢

@qdm12 commented on GitHub (Jan 18, 2024): Can you try pulling and running the latest image? Shoutrrr just got upgraded to v0.8.0 in commit e02880fe1f8b738d47cd2b52583d1e32d5d2d734 maybe this solves it for you? Otherwise I'm not too sure, since this error comes from the Shoutrrr library so it's rather hard to debug etc. and I don't really want to downgrade either 😢

saavagebueno commented

2025-11-20 04:22:33 -05:00

@qdm12 commented on GitHub (Jun 16, 2024):

Closing this due to inactivity, and might be solved in the latest versions.

@qdm12 commented on GitHub (Jun 16, 2024): Closing this due to inactivity, and might be solved in the latest versions.

saavagebueno referenced this issue

2025-11-20 04:25:39 -05:00

[PR #306] [CLOSED] Added provider all inkl #670

Sign in to join this conversation.