From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Gaute Hope <eg@gaute.vetsj.com>, Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: umask/permissions on new files created via notmuch-insert(1) ?
Date: Sun, 04 Feb 2018 15:59:56 -0500 [thread overview]
Message-ID: <87efm01neb.fsf@fifthhorseman.net> (raw)
In-Reply-To: <1517772761.o1m1n3158p.astroid@strange.none>
[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]
On Sun 2018-02-04 20:34:09 +0100, Gaute Hope wrote:
> Daniel Kahn Gillmor writes on februar 4, 2018 20:25:
>> is there a reason that "notmuch insert" should be stricter than the
>> umask? does this ring any bells for people?
>
> Are you asking why it is or why it should? If former; maybe because of
> line 230 in notmuch-insert.c ?
yep, that's definitely the cause of it, but looking through the git
history, it seems to have no clear justification.
do other LDA programs behave this way? is there a reason to not 0666 or
0644 ? seems like the umask is where people should be making these
choices, and mail being delivered doesn't necessarily need this kind of
lockdown.
we're running into this when looking at a mailing list archiver -- i
want messages to be delivered via "notmuch insert" as the mailbox owner.
but the mailbox viewer is going to be a different user, and they need
read-only access to the archive. instead, they're completely locked
out.
am i missing something?
--dkg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2018-02-04 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-04 19:25 umask/permissions on new files created via notmuch-insert(1) ? Daniel Kahn Gillmor
2018-02-04 19:34 ` Gaute Hope
2018-02-04 20:59 ` Daniel Kahn Gillmor [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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87efm01neb.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=eg@gaute.vetsj.com \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).