[Pkg-mlmmj-devel] Bug#617242: mlmmj-make-ml does not ensure correct permissions for created files and directories

[Chris Knadle]

Reuben Thomas:
> On 6 November 2017 at 03:07, Chris Knadle <Chris.Knadle at coredump.us> wrote:
> Do you believe there are specific permissions that always neeed to be
>> used regardless of specific MTA and setup?
>>
> 
> ​No. However, it would be good to have some opinionated defaults.

I don't know what this means, and I don't think it could sanely be
accomplished.

> Otherwise, this is just another hard-to-set-up package that requires lots
> of reading and fiddling, one is not sure (unless one becomes an expert)
> that it is set up properly, securely etc., and one gravitates towards
> proprietary products or cloud offerings that are simply easier and make
> this sort of thing Someone Else's Problem, which is a shame.

I agree with this. At the same, time it's my experience that everything
in email configuration likewise has this "open-ended" issue. Postfix
doesn't by default come with configuration for Amavis, ClamAV,
SpamAssassin, etc, yet any Internet-facing mail server would
realistically need these things and setting them up requires a lot of
fiddling and reading because there are multiple ways to configure them.
And all that would normally come before mlmmj setup. Email server
configuration are specifically allowed to be different, so default
configuration can come only for certain pieces when there are sane
defaults that can be shipped.

Sometimes the MTA and mlmmj are set up by an administrator, and
sometimes it's set up via a web panel. If any default configuration came
with mlmmj on Debian but not upstream, then web panels would need to be
updated to remove whatever default configuration was shipped only on
Debian. i.e. there are unforeseen consequences for this kind of change.

The best thing I can suggest is to sign up for the mlmmj "discussion"
mailing list and discuss this idea there.

   http://mlmmj.org/lists

If there are good default permissions that could be set, upstream would
be the place to make the change, and if there aren't then upstream would
know more about the reason why there aren't.

In the meantime I'm going to mark this bug "wontfix" because I don't see
any better way of handling it.

   -- Chris

-- 
Chris Knadle
Chris.Knadle at coredump.us