On 12/15/19 9:46 AM, Ralph Seichter wrote: > > Milter-regex only needs a user to isolate the process and it's single > configuration file (/etc/milter-regex.conf). My PR adds acct-user/milter > without a home directory, because milter-regex does not need one, nor > does it write anything to disk. It is designed to hold everything in > memory only.
Right, this is what I was anticipating. > Could that lack of a home directory hurt OpenDMARC? I use OpenDMARC and > milter-regex on the same servers and did not run into problems. That's what I don't know. I think it's unlikely that OpenDMARC's user needs a home directory, but the daemon may expect /var/lib/milter to be writable and currently that happens as a side effect of the enewuser call. If acct-user/milter (with no home directory) is installed first, then /var/lib/milter won't exist and be writable. You might also affect people who have modified their OpenDMARC user's home directory or shell, if there's any reason to do that. Michał already posted the solution to that problem (override acct-user/milter in an overlay), but if that happens then people will be overriding one daemon's user to keep another unrelated daemon working -- not very aesthetically pleasing. tl;dr if I were you I would rather not have to worry about any of this. I'm sure someone will object to the name acct-user/_milter-regex, but that would be the easiest option, being the upstream default. It's also unlikely that someone will try to repurpose that user for another milter in the future, putting us back in the same situation as we are with OpenDMARC today.
