blob: f009e9a501eec914df48b03cc915e5c1c4e0e538 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
|
listen:
host: 127.0.0.1
port: 8025
configs:
# You can send to this config with "basic_assistant@mailrise.xyz".
#
# The "-" is *very* important, even when configuring just a single URL.
# Apprise requires urls to be a YAML *list*.
#
basic_assistant:
urls:
- hasio://HOST/ACCESS_TOKEN
# You can send to this config with "telegram_and_discord@mailrise.xyz".
#
#telegram_and_discord:
#urls:
#- tgram://MY_BOT_TOKEN
#- discord://WEBHOOK_ID/WEBHOOK_TOKEN
# You can also control the layout of the message with custom template
# strings.
#mailrise:
#title_template: "Urgent: ${body}"
#body_template: ""
#body_format: text
# You can send to this config with "my_cool_name@mycooldomain.com".
#
#my_cool_name@mycooldomain.com:
#urls:
#- pover://USER_KEY@TOKEN
# We also support wildcards with the fnmatch library; see
# https://docs.python.org/3/library/fnmatch.html for the full syntax.
#
# YAML requires characters like "*" and "[" to be enclosed in quoted
# strings.
#
# This pattern matches addresses like "awesomeperson@mycooldomain.com"
# and "awesomemail@mycooldomain.com".
#
#"awesome*@mycooldomain.com":
#urls:
#- pover://USER_KEY@TOKEN
# Of course, it's also possible to pattern match by the domain.
#
#"my_cool_name@*.net":
#urls:
#- pover://USER_KEY@TOKEN
# Wildcard targets are evaluated in the order they appear in the
# configuration file, and Mailrise uses the first match. So, this config
# will catch any addresses not matched by the previous targets.
#
# Note that if you use "*" as your pattern, Mailrise will expand that to
# "*@mailrise.xyz", which is probably not the catch-all target you wanted.
#
#"*@*":
#urls:
#- discord://WEBHOOK_ID/WEBHOOK_TOKEN
# You can also insert environment variables, a feature lifted directly
# from Home Assistant. This is useful for reading secrets from
# container orchestrators like Kubernetes.
#- !env_var MY_SECRET_URL
# Finally, you can enable TLS encryption and/or SMTP authentication if you
# want them.
#tls:
#mode: starttls
#certfile: /path/to/certificate.pem
#keyfile: /path/to/privatekey.pem
#smtp:
#auth:
#basic:
#username: password
#AzureDiamond: hunter2
|