paritybit.ca

Raw content of https://www.paritybit.ca.
git clone https://git.sr.ht/~jbauer/paritybit.ca
Log | Files | Refs | README | LICENSE

commit 95f1e4a7caf47bafebe901ad5682d81d27c9057b
parent 93f1775f2bebe8af8ead8143dfcbdf81647779a9
Author: Jake Bauer <jbauer@paritybit.ca>
Date:   Tue, 20 Sep 2022 19:01:38 -0400

*

Diffstat:
Mcontent/garden/arboretum/knowledge/sysadmin/relaying-service-mail-with-opensmtpd.gmi | 4++--
Mcontent/garden/greenhouse/index.gmi | 1+
2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/content/garden/arboretum/knowledge/sysadmin/relaying-service-mail-with-opensmtpd.gmi b/content/garden/arboretum/knowledge/sysadmin/relaying-service-mail-with-opensmtpd.gmi @@ -4,11 +4,11 @@ This configuration is very useful for allowing services to send email, especiall This requires an email server which is already set up to accept submissions from remote hosts. I use SMTPS (port 465) but this also works with SMTP+STARTTLS (port 587). -First, create one or more accounts on the central mail server to handle the email (could be servicename@example.com or no-reply@example.com, etc). Creating multiple accounts when using SMTP AUTH is convenient in the case that a machine gets compromised and therefore the password used to authenticate with the mailserver gets compromised. If only one account is used, when you need to change the password for the service account, you need to update the configuration on all machines. On the other hand, one account for all service emails is easier to manage up front. +First, create one or more accounts on the central mail server to handle the email (could be servicename@example.com or no-reply@example.com, etc). Creating multiple accounts is convenient in the case that a machine gets compromised and therefore the password used to authenticate with the mailserver gets compromised. In such a case, only one account will need to be changed. If only one account is used for all services, however, when you need to change the password for the service account you will need to update the configuration on all machines. On the other hand, one account for all service emails is easier to manage up front. On the machine which will be sending email, add an alias for the relevant users to `/etc/mail/aliases`. For example: `root: jbauer@paritybit.ca` which will send all emails that would normally be sent to the root user (for output of cron jobs, etc.) to my personal email. -Modify the `/etc/mail/smtpd.conf` file as follows (this configuration uses the account service@example.com and SMTP AUTH PLAIN): +Modify the `/etc/mail/smtpd.conf` file as follows (this configuration uses the account service@example.com and SMTP AUTH PLAIN to send mail for the machine 'host'): ```/etc/mail/smtpd.conf table aliases file:/etc/mail/aliases diff --git a/content/garden/greenhouse/index.gmi b/content/garden/greenhouse/index.gmi @@ -34,6 +34,7 @@ A collection of notes and clippings from articles that don't yet fit anywhere el Here are links, documents, and other things I found interesting that I want to get around to reading and possibly taking notes on. +=> https://samkriss.substack.com/p/the-internet-is-already-over => https://theanarchistlibrary.org/ => https://skeeto.s3.amazonaws.com/share/onward17-essays2.pdf => https://en.wikipedia.org/wiki/Postmodernism