According to http://docs.mailman3.org/en/latest/config-core.html, I have to add "@daily mailman digests --send" to the crontab. Which crontab does it go in? In the system crontab, the thing after the time is the username, and there's no user named "mailman" in /etc/passwd. Or should I put a script in / etc/cron.daily/?
Pierre
loi mintu se ckaji danlu cu jmaji
On 11/03/2017 11:43 AM, Pierre Abbat wrote:
According to http://docs.mailman3.org/en/latest/config-core.html, I have to add "@daily mailman digests --send" to the crontab. Which crontab does it go in? In the system crontab, the thing after the time is the username, and there's no user named "mailman" in /etc/passwd. Or should I put a script in / etc/cron.daily/?
The partucular "@daily mailman digests --send" would have to go in the user crontab for the Mailman user. If this is not 'mailman' it is what ever user "owns" Mailman. Further it would require that the path to Mailman's bin/mailman command be in that users $PATH.
If it were to go in the system /etc/crontab it would need to be something like
@daily user /path/to/bin/mailman digests --send
where 'user' is the Mailman user as above. That could also go in a file in /etc/cron.d/
Or you could put an executable script to run '/path/to/bin/mailman digests --send' in /etc/cron.daily
Your choice.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Friday, November 3, 2017 12:26:06 PM EDT Mark Sapiro wrote:
The partucular "@daily mailman digests --send" would have to go in the user crontab for the Mailman user. If this is not 'mailman' it is what ever user "owns" Mailman. Further it would require that the path to Mailman's bin/mailman command be in that users $PATH.
There's nothing in http://docs.mailman3.org/en/latest/config-core.html or http://docs.mailman3.org/en/latest/prodsetup.html about adding a Mailman user. This should be a system user, right? Should it have a home directory? Could you add that to the documentation?
Pierre
I believe in Yellow when I'm in Sweden and in Black when I'm in Wales.
On 11/03/2017 02:08 PM, Pierre Abbat wrote:
There's nothing in http://docs.mailman3.org/en/latest/config-core.html or http://docs.mailman3.org/en/latest/prodsetup.html about adding a Mailman user. This should be a system user, right? Should it have a home directory? Could you add that to the documentation?
How about "user that installed Mailman" or "user that Mailman's runners run as"?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Friday, November 3, 2017 2:27:03 PM EST Mark Sapiro wrote:
How about "user that installed Mailman" or "user that Mailman's runners run as"?
I installed it as root.
From "man useradd" in Linux:
-r, --system
Create a system account.
System users will be created with no aging information in
/etc/shadow, and their numeric identifiers are chosen in the
SYS_UID_MIN-SYS_UID_MAX range, defined in /etc/login.defs, instead
of UID_MIN-UID_MAX (and their GID counterparts for the creation of
groups).
Note that useradd will not create a home directory for such an
user, regardless of the default setting in /etc/login.defs
(CREATE_HOME). You have to specify the -m options if you want a
home directory for a system account to be created.Pierre
lo ponse be lo mruli ku po'o cu ga'ezga roda lo ka dinko
On 11/05/2017 03:43 AM, Pierre Abbat wrote:
On Friday, November 3, 2017 2:27:03 PM EST Mark Sapiro wrote:
How about "user that installed Mailman" or "user that Mailman's runners run as"?
I installed it as root.
When you run
mailman info
it will report among other things the location of 'config file:'. The user who owns this file is the user that should run the
mailman digests --send
command. I.e., it should be in that user's crontab or in something like '/etc/cron.d/mailman' with that user specified.
Also see <https://gitlab.com/mailman/mailman/issues/436>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Sunday, November 5, 2017 12:09:53 PM EST Mark Sapiro wrote:
When you run
mailman info
it will report among other things the location of 'config file:'. The user who owns this file is the user that should run the
mailman digests --send
command. I.e., it should be in that user's crontab or in something like '/etc/cron.d/mailman' with that user specified.
Also see <https://gitlab.com/mailman/mailman/issues/436>.
/etc/mailman.cfg should be owned by mailman? I checked my primary mailserver, my laptop, and my new Mailman box. ALL files in /etc (except links, which are lrwxrwxrwx and I didn't check what they point to) are owned by root.root or owned by root.<other> and not group writable, except one, the directory /etc/ mailman/, which is owned by root.list and is group writable (drwxrwsr-x). Are you saying that Mailman should be able to change its own config file?
Pierre
Don't buy a French car in Holland. It may be a citroen.
On 11/05/2017 09:18 PM, Pierre Abbat wrote:
/etc/mailman.cfg should be owned by mailman? I checked my primary mailserver, my laptop, and my new Mailman box. ALL files in /etc (except links, which are lrwxrwxrwx and I didn't check what they point to) are owned by root.root or owned by root.<other> and not group writable, except one, the directory /etc/ mailman/, which is owned by root.list and is group writable (drwxrwsr-x). Are you saying that Mailman should be able to change its own config file?
It looks like your Mailman user is 'list'. That is the user that should be running mailman commands.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 11/06/2017 08:52 AM, Mark Sapiro wrote:
On 11/05/2017 09:18 PM, Pierre Abbat wrote:
/etc/mailman.cfg should be owned by mailman? I checked my primary mailserver, my laptop, and my new Mailman box. ALL files in /etc (except links, which are lrwxrwxrwx and I didn't check what they point to) are owned by root.root or owned by root.<other> and not group writable, except one, the directory /etc/ mailman/, which is owned by root.list and is group writable (drwxrwsr-x). Are you saying that Mailman should be able to change its own config file?
It looks like your Mailman user is 'list'. That is the user that should be running mailman commands.
This may be "off the wall" but is the mailman you installed perhaps a Debian/Ubuntu Mailman 2.1 package? If so, you are reading the wrong docs and posting to the wrong list.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Monday, November 6, 2017 8:52:25 AM EST Mark Sapiro wrote:
It looks like your Mailman user is 'list'. That is the user that should be running mailman commands.
Thanks! There is indeed a user "list".
On Monday, November 6, 2017 10:06:49 AM EST Mark Sapiro wrote:
This may be "off the wall" but is the mailman you installed perhaps a Debian/Ubuntu Mailman 2.1 package? If so, you are reading the wrong docs and posting to the wrong list.
It's Mailman 3.1.0 installed with pip.
Pierre
li ze te'a ci vu'u ci bi'e te'a mu du li ci su'i ze te'a mu bi'e vu'u ci
On 11/14/2017 07:57 PM, Pierre Abbat wrote:
On Monday, November 6, 2017 10:06:49 AM EST Mark Sapiro wrote:
This may be "off the wall" but is the mailman you installed perhaps a Debian/Ubuntu Mailman 2.1 package? If so, you are reading the wrong docs and posting to the wrong list.
It's Mailman 3.1.0 installed with pip.
OK, but the fact that you have a /etc/mailman directory which is user:group root:list and mode drwxrwsr-s indicates that there is or was a Debian/Ubuntu mailman 2.1 package installed on this machine. So it is unclear to me at least at this point what things on this machine are Mailman 3.1 and what are Mailman 2.1.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro -
Pierre Abbat