-
I am trying to use shotrrr via the scrutiny project to send notifications over SMTP. Problem I am having is that my SMTP provider Mailgun issues usernames as an email address. However it seems that du…
-
**Describe the bug**
On the latest-dev, Watchtower fails to start up, giving me the below error message. I couldn't figure out what changed since I don't use Shoutrr but the native slack integration …
-
**When I tried** shoutrrr code for a rocket chat automated notification, and formatted the channel name with a '#' prefix - that is what I got:
```
go run cli/main.go send --url "rocketchat://shoutr…
-
By default, **send** is using the formatted hook, like this `"https://%s/hooks/%s/%s", host, tokenA, tokenB`. However, in cases when my 443 port is busy with a different service, and I've set the chat…
-
For example, pushover allows you to send a title but it looks like we can only send a message body. Here's the apprise example:
```bash
apprise -t 'my title' -b 'my notification body' \
'mailt…
-
I tried using shoutrrr with an SMTP URL that's using implicit TLS (port 465) earlier today and observed that the request timed out after a while. The same URL worked fine when using explicit TLS on po…
ghost updated
3 years ago
-
**Describe the bug**
It seems that in the latest version (1.1.6) mail sending is somehow broken. Currently, watchtower mails get tagged by my mail server because of a bad mail header.
Error msg:
``…
-
**Describe the bug**
SMTP Notifications - Username with @ symbol not supported. Mailgun only offers SMTP auth with usernames of the format `@`. I also tried URL encoding the @ however still didn't ge…
-
Since gotify is often hosted internally, it doesn't make much sense to force SSL.
-
**Is your feature request related to a problem? Please describe.**
Lots of providers are moving to ghcr.io for their images and this results in every watchtower Telegram notification getting what is …