Re: Mailman 3 Keeps Forgettings Imported Lists
I do see the output of the script and it shows the mailing lists being created. If you put "${VARIABLE}"@domain.com it outputs correctly.
Also, to that end, the output of lists changes depending on which directory I am in which makes 0 sense.
On Tue, Jul 31, 2018 at 3:27 PM Ryan McClung <rmcclung@afilias.info> wrote:
I do see the output of the script and it shows the mailing lists being created. If you put "${VARIABLE}"@domain.com it outputs correctly.
On Tue, Jul 31, 2018 at 3:22 PM Mark Sapiro <mark@msapiro.net> wrote:
On 07/31/2018 07:04 AM, Ryan McClung wrote:
Scratch that. Ran with the corrected script and getting the following: [root@mailman3(stg) archives]# mailman lists No matching mailing lists found
Any thoughts?
This
for DIR in $DIRS; do mailman create "${DIR}"; mailman import21 "${DIR}"@ afilias.info "${DIR}"/config.pck;
is still wrong. The list name for mailman create needs to be fully qualified as in
for DIR in $DIRS; do mailman create ${DIR}@afilias.info; mailman import21 ${DIR}@afilias.info ${DIR}/config.pck;
(Do you look at the output from your script?)
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
--
Ryan McClung Systems Administrator @ Afilias Canada A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8 <https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8&entry=gmail&source=g> W. www.afilias.info T. +1.416.646.3304 x4186
--
Ryan McClung Systems Administrator @ Afilias Canada A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8 <https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8&entry=gmail&source=g> W. www.afilias.info T. +1.416.646.3304 x4186
On 07/31/2018 12:39 PM, Ryan McClung wrote:
I do see the output of the script and it shows the mailing lists being created. If you put "${VARIABLE}"@domain.com it outputs correctly.
Also, to that end, the output of lists changes depending on which directory I am in which makes 0 sense.
That is the problem. Either your mailman.cfg does not specify a fixed directory for var_dir or the mailman command(s) you run do not specify a fixed mailman.cfg.
If you look, you will probably see a var/ directory is every directory in which you ran a 'mailman' command and they will all have different databases, etc.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
That explains a lot. Is there any documentation you can provide to show me where I can set a static config/db?
On Tue, Jul 31, 2018, 4:22 PM Mark Sapiro, <mark@msapiro.net> wrote:
I do see the output of the script and it shows the mailing lists being created. If you put "${VARIABLE}"@domain.com it outputs correctly.
Also, to that end, the output of lists changes depending on which
On 07/31/2018 12:39 PM, Ryan McClung wrote: directory
I am in which makes 0 sense.
That is the problem. Either your mailman.cfg does not specify a fixed directory for var_dir or the mailman command(s) you run do not specify a fixed mailman.cfg.
If you look, you will probably see a var/ directory is every directory in which you ran a 'mailman' command and they will all have different databases, etc.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
On 07/31/2018 01:52 PM, Ryan McClung wrote:
That explains a lot. Is there any documentation you can provide to show me where I can set a static config/db?
See <http://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html>
That may not specifically address your question, but it will explain the issue in detail. An example of what I do on several servers I support is this.
First, I install Mailman in a virtualenv which is /opt/mailman/mm/venv. Then the commands I run are all put in /opt/mailman/mm/bin. the actual installed 'mailman' command is /opt/mailman/mm/venv/bin/mailman but I never run that directly or as 'mailman' with the venv active. My var/ directory is /opt/mailman/mm/var. My mailman.cfg is actually outside of the var/ directory in /opt/mailman/mm/mailman.cfg. (In some cases for historical reasons it's in /opt/mailman/mm/deployment/mailman.cfg, but ignore that.)
In /opt/mailman/mm/bin/mailman, I have
#!/bin/bash unset PYTHONSTARTUP
exec /opt/mailman/mm/venv/bin/mailman
-C "/opt/mailman/mm/mailman.cfg"
$@
The details such as installing in a venv or where things are are not the important things. The important thing is the only 'mailman' command I ever run invokes Mailman with a -C option that points to the only config I want to use and that in turn has a var_dir setting pointing to, in my case, /opt/mailman/mm/var.
Also, the 'unset PYTHONSTARTUP' is there to address an issue with 'mailman shell' that would double the size of the shell history file each time it was run. I'm not certain that's still needed.
-- 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 -
Ryan McClung