From: Sean MacLennan <seanm@seanm.ca>
To: Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM>
Cc: supervision@list.skarnet.org
Subject: Re: smaclennan/doorknob
Date: Sat, 2 Feb 2019 13:32:58 -0500 [thread overview]
Message-ID: <20190202133258.71837b05@zonker.seanm.ca> (raw)
In-Reply-To: <085056a0-4548-1579-8747-8c057a9aad3c@NTLWorld.COM>
On Sun, 27 Jan 2019 14:39:16 +0000
Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM>
wrote:
> A lot of constructive comments on doorknob which I am not going to
> include here.
Well, I have updated doorknob to *hopefully* respond to all the
comments. I have pushed the changes to github if anybody is interested.
The big changes are moving the default location of the directories and
changing ownership.
Doorknob now has its own user. It basically does:
1. change to queue directory
2. setup inotify
3. drop privileges to doorknob user
4. read config
5. start handling messages
sendmail and mailq are now owned by the mail user and group
(configurable) and are +s.
The queues are now (by default):
chown mail.mail /var/spool/doorknob
chown mail.mail /var/spool/doorknob/queue
chown mail.mail /var/spool/doorknob/tmp
chmod 750 /var/spool/doorknob
chmod 777 /var/spool/doorknob/queue
chmod 700 /var/spool/doorknob/tmp
Everything is configurable. You can make the doorknob user root, the
mail user root, and everything is as before.
Comments welcome.
Cheers,
Sean
prev parent reply other threads:[~2019-02-02 18:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-27 3:15 s6 problems logging Sean MacLennan
2019-01-27 5:20 ` Colin Booth
2019-01-27 16:47 ` Sean MacLennan
2019-01-27 17:56 ` Laurent Bercot
2019-01-27 18:13 ` Colin Booth
2019-01-27 18:56 ` Sean MacLennan
2019-01-27 19:27 ` Roger Pate
2019-01-28 11:00 ` Peter Pentchev
2019-02-01 9:22 ` Jonathan de Boyne Pollard
2019-01-27 19:35 ` Guillermo
2019-01-27 14:39 ` smaclennan/doorknob Jonathan de Boyne Pollard
2019-02-02 18:32 ` Sean MacLennan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190202133258.71837b05@zonker.seanm.ca \
--to=seanm@seanm.ca \
--cc=J.deBoynePollard-newsgroups@NTLWorld.COM \
--cc=supervision@list.skarnet.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).