mailrise VS signal-cli

Edit: Using AWS SES for now (PITA to setup though) and will setup https://github.com/YoRyan/mailrise as suggested below once I get my full systems back up. After the suggestions and testing, the hardest hurdle was having a VoIP number rather than regular Cell and using without a custom domain (and even different providers handle this differently). Using an email service seems to be one of the easiest methods to use, just have to make sure they allow SMTP access on the free tier. Hopefully the comments on this thread will help other in the future or give them alternative ideas. Thanks all!

I use mailrise which hosts a private SMTP gateway for Apprise notifications.

Link to the repo: https://github.com/YoRyan/mailrise

https://github.com/YoRyan/mailrise might be a decent option.

This project is similar to and inspired by Mailrise. I wanted a little more configuration than was supported by Mailrise, so decided to create my own option.

FYI, a similar system can be achieved with https://github.com/YoRyan/mailrise + https://github.com/caronc/apprise, but requires more setup

I ended up having to build mailrise from source so I could change it to use the nightly build of apprise instead of version 1.1 (which still had the bug). I actually just went back and tested that apprise 1.2 seems to be splitting both markdown and text messages properly for discord. I'll have to build an updated mailrise docker image and try again there. I'll file an issue if I run into problems.

Not official but this works darn well: https://github.com/AsamK/signal-cli

If you want one for just personal use; this works well: https://github.com/AsamK/signal-cli

Just sign up with a Twilio number (using voice call) and you can make your own bot.

Here is my docker compose, maybe it is helpful: signal: #registerung tutorial # signal-cli --username +12345678 register --voice --captcha censored # https://github.com/AsamK/signal-cli/wiki/Registration-with-captcha # https://signalcaptchas.org/registration/generate.html IN CHROME # signal-cli -u +12345678 verify 123456 # signal-cli -u +1234567 send -m "This is a message" +12345678 #curl -X POST -H "Content-Type: application/json" -d '{"message": "bliblob", "number": "+41824174983", "recipients": ["+21412430"]}' 'http://signal:8080/v2/send' #external testing image: bbernhard/signal-cli-rest-api:latest container_name: signal restart: unless-stopped hostname: signal networks: - monitoring volumes: - /docker/prometheus/signal/client:/root/.local/share/signal-cli - /docker/prometheus/signal/client:/home/.local/share/signal-cli labels: - com.centurylinklabs.watchtower.enable=true environment: - USE_NATIVE=0 signalweb: # curl -X POST localhost:9100/api/v2/alertmanager -d '{"alerts": [{"status": "firing","labels": {"alertname": "test"},"annotations": {"message": "Test alert."}}]}' image: registry.gitlab.com/schlauerlauer/alertmanager-webhook-signal:latest container_name: signalweb restart: unless-stopped hostname: signalweb networks: - monitoring volumes: - /docker/prometheus/signal/web/config.yml:/root/config.yaml labels: - com.centurylinklabs.watchtower.enable=true

Yes, using the signal-cli program. It has a built in JSON RPC API that can be used to develop application integrations

Last commit was 2 days ago so it should still work: https://github.com/AsamK/signal-cli

Sorry to hear. Then the cheap backup may be a Signal CLI forwarded over to mqtt CLI

build, install and configure/register signal-cli. The code snippet below assumes you are running it in multi-account mode, but I'll leave a comment where it matters

No official API that is public from what I can tell, but appears this works https://github.com/AsamK/signal-cli