computing:synapse
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| computing:synapse [2022/11/23 07:17] – oemb1905 | computing:synapse [2022/11/23 15:17] – oemb1905 | ||
|---|---|---|---|
| Line 140: | Line 140: | ||
| sudo nano / | sudo nano / | ||
| < | < | ||
| - | email: | + | |
| - | smtp_host: haacksnetworking.org | + | |
| - | smpt_port: | + | |
| - | notif_from: " | + | |
| - | require_transport_security: | + | |
| Again, note that there is no need to set up an incoming email server nor tolerate spam on the server you are sending to. In my case, my smtp server / MTA is a relay with domains that are allowed to send through it explicitly white listed. Alright, so now it's time to carry on with setting up jitsi. Again, as with element and matrix, always check the [[https:// | Again, note that there is no need to set up an incoming email server nor tolerate spam on the server you are sending to. In my case, my smtp server / MTA is a relay with domains that are allowed to send through it explicitly white listed. Alright, so now it's time to carry on with setting up jitsi. Again, as with element and matrix, always check the [[https:// | ||
| Line 171: | Line 171: | ||
| Utilize rsync or similar to ensure you have those backups offsite as well as on site, and also provision a hot-spare in case your self-hosted or co-located hardware fails. | Utilize rsync or similar to ensure you have those backups offsite as well as on site, and also provision a hot-spare in case your self-hosted or co-located hardware fails. | ||
| - | --- // | + | --- // |
computing/synapse.txt · Last modified: 2024/01/30 03:17 by oemb1905
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: GNU Free Documentation License 1.3
