Post-installation documentation?
Is post-installation documentation available for a full Mailman3 installation on a new Debian 11 machine?
I am looking for a high-level "do these steps next to get a list working" document rather than an API command reference.
I followed the venv documentation and the installation went ok, but still have questions about what to do next, e.g.:
- why do the venv docs and admin FAQ give different nginx configs for the reverse proxy?
https://docs.mailman3.org/en/latest/faq.html#confirmation-emails-to-users-ha...
https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configurat...
Does the 'Secret_Hyperkitty_API_Key' need to go anywhere else besides /opt/mailman/mm/mailman-hyperkitty.cfg?
For Django (presumably in /etc/mailman3/settings.py, but the docs don't say), what values to use with Postfix to set up the email back end?
I have a working test list, but am not altogether sure it's set up correctly.
Thanks in advance for pointers to docs beyond the installation steps.
dn
David Newman writes:
I am looking for a high-level "do these steps next to get a list working" document rather than an API command reference.
There's no such documentation. "Get a list working" depends on what you mean by "working". The basic answer is
- Install Mailman 3 suite.
- Log in to Postorius as an admin user and create the list.
After that, it's case-specific.
- why do the venv docs and admin FAQ give different nginx configs for the reverse proxy?
Because the FAQ is providing a short snippet to solve a specific problem, the venv docs provide what I guess is somebody's full working config. Setting up a Mailman server is complex; usually any example you see in the docs is somebody's "works for me" configuration.
- Does the 'Secret_Hyperkitty_API_Key' need to go anywhere else besides /opt/mailman/mm/mailman-hyperkitty.cfg?
It needs to match MAILMAN_ARCHIVER_KEY in HyperKitty's settings.py. There are a couple of reasonable ways to organize HyperKitty and Postorius configs, I'm not sure where the appropriate settings.py would be on your server.
- For Django (presumably in /etc/mailman3/settings.py, but the docs don't say), what values to use with Postfix to set up the email back end?
The answer is "that depends on your mail environment". As far as I know, normally it just works with the default settings, but if your Postfix requires secure, you need to set that up: https://docs.djangoproject.com/en/3.2/ref/settings/#std:setting-EMAIL_USE_TL... and possibly the following 3 or 4 variables if authentication is needed.
There was a thread on this a couple of weeks ago.
On 11/23/21 4:40 AM, Stephen J. Turnbull wrote:
David Newman writes:
I am looking for a high-level "do these steps next to get a list working" document rather than an API command reference.
There's no such documentation. "Get a list working" depends on what you mean by "working".
Thanks for getting back to me.
IMO post-installation docs for list admins would be a big help in Mailman3 adoption. I'm willing to help with this.
When I say "working": I'm looking to migrate Mailman2 mailing lists to Mailman3, but am struggling with even basic setup tasks before we attempt list migtration.
For example, on admin page I've set up two lists, one public and one private (each with unique list IDs), but neither appear in the site's list index.
And I don't know where to add list members.
And clicking the site archives link throws this error:
The basic answer is
- Install Mailman 3 suite.
- Log in to Postorius as an admin user and create the list.
After that, it's case-specific.
- why do the venv docs and admin FAQ give different nginx configs for the reverse proxy?
Because the FAQ is providing a short snippet to solve a specific problem, the venv docs provide what I guess is somebody's full working config. Setting up a Mailman server is complex; usually any example you see in the docs is somebody's "works for me" configuration.
- Does the 'Secret_Hyperkitty_API_Key' need to go anywhere else besides /opt/mailman/mm/mailman-hyperkitty.cfg?
It needs to match MAILMAN_ARCHIVER_KEY in HyperKitty's settings.py. There are a couple of reasonable ways to organize HyperKitty and Postorius configs, I'm not sure where the appropriate settings.py would be on your server.
- For Django (presumably in /etc/mailman3/settings.py, but the docs don't say), what values to use with Postfix to set up the email back end?
The answer is "that depends on your mail environment". As far as I know, normally it just works with the default settings, but if your Postfix requires secure, you need to set that up: https://docs.djangoproject.com/en/3.2/ref/settings/#std:setting-EMAIL_USE_TL... and possibly the following 3 or 4 variables if authentication is needed.
There was a thread on this a couple of weeks ago.
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/
(sorry, hit send too soon)
On 11/23/21 4:40 AM, Stephen J. Turnbull wrote:
David Newman writes:
I am looking for a high-level "do these steps next to get a list working" document rather than an API command reference.
There's no such documentation. "Get a list working" depends on what you mean by "working".
Thanks for getting back to me.
IMO post-installation docs for list admins would be a big help in Mailman3 adoption. I'm willing to help with this.
When I say "working": I'm looking to migrate Mailman2 mailing lists to Mailman3, but am struggling with even basic setup tasks before we attempt list migtration.
For example, on admin page I've set up two lists, one public and one private (each with unique list IDs), but neither appear in the site's list index.
And I don't know where to add list members.
And clicking the site archives link throws this error:
django.urls.exceptions.NoReverseMatch: Reverse for 'hk_list_overview' with keyword arguments '{'mlist_fqdn': 'wheee'}' not found. 1 pattern(s) tried: ['archives/list/(?P<mlist_fqdn>[^/@]+@[^/@]+)/$']
etc.
I am 100.00% certain these and other issues are all down to misconfigurations on my part, but don't know where to turn for direction on correct list setup and maintenance with mailman3.
- For Django (presumably in /etc/mailman3/settings.py, but the docs don't say), what values to use with Postfix to set up the email back end?
The answer is "that depends on your mail environment". As far as I know, normally it just works with the default settings, but if your Postfix requires secure, you need to set that up: https://docs.djangoproject.com/en/3.2/ref/settings/#std:setting-EMAIL_USE_TL... and possibly the following 3 or 4 variables if authentication is needed.
There was a thread on this a couple of weeks ago.
Thanks for the pointers. Both resolved this issue.
dn
On 11/24/21 9:40 AM, David Newman wrote:
IMO post-installation docs for list admins would be a big help in Mailman3 adoption. I'm willing to help with this.
Thank you for being willing to contribute. I think the place for list admin docs would be in the https://gitlab.com/mailman/mailman-suite-doc project which is the source for https://docs.mailman3.org/en/latest/. There is currently a userguide there at source/userguide.rst and referenced from source/index.rst. the addition of an adminguide.rst would be welcom if you want to work on that.
When I say "working": I'm looking to migrate Mailman2 mailing lists to Mailman3, but am struggling with even basic setup tasks before we attempt list migtration.
For example, on admin page I've set up two lists, one public and one private (each with unique list IDs), but neither appear in the site's list index.
Here are the steps to migrate a 2.1 list named alist@example.com and
its archives.
run Mailman's bin/mailman create alist@example.com
follow that with
bin/mailman import21 alist@example.com
/path/to/mailman2.1/lists/alist/config.pck
That will create the list and import its members and settings.
To import archives run the Django admin command with arguments
hyperkitty_import -l alist@example.com
/path/to/mailman2.1/archives/private/alist.mbox/alist.mbox
And I don't know where to add list members.
For imported lists, they are already added, but for new lists, you can
add them in Postorius under Mass operations -> Mass subscribe or via the
bin/mailman commands addmembers or syncmembers. See
https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/do...
And clicking the site archives link throws this error:
django.urls.exceptions.NoReverseMatch: Reverse for 'hk_list_overview' with keyword arguments '{'mlist_fqdn': 'wheee'}' not found. 1 pattern(s) tried: ['archives/list/(?P<mlist_fqdn>[^/@]+@[^/@]+)/$']
Did you specify the list's fqdn as in https://www.example.com/archives/list/list@example.com/
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Sapiro writes:
On 11/24/21 9:40 AM, David Newman wrote:
IMO post-installation docs for list admins would be a big help in Mailman3 adoption. I'm willing to help with this.
Thank you for being willing to contribute.
+1
I think the place for list admin docs would be in the https://gitlab.com/mailman/mailman-suite-doc project which is the source for https://docs.mailman3.org/en/latest/.
+1
Here are the steps to migrate a 2.1 list named
alist@example.comand its archives.
This is documented at https://docs.list.org/en/latest/ (prominent link in sidebar). This appears to be completely different from https://docs.mailman3.org/ (and https://mailman.readthedocs.io/ which I guess is just a redirect). But it looks like the sources are in the some gitlab repo?!
And I don't know where to add list members.
I guess it would be a good idea to provide an image of the menu tree for Postorius.
Did you specify the list's fqdn as in https://www.example.com/archives/list/list@example.com/
That's not an FQDN, though. "example.com" might be one, but that whole thing is the URL to the archive.
Pedantry aside, I think we should probably have a Mailman-specific glossary for many terms, including the tests we use for validation. In this case, FQDN appears to be "sequence of characters not containing '@' or '/'."
Steve
On 11/24/21 7:50 PM, Stephen J. Turnbull wrote:
Mark Sapiro writes:
Here are the steps to migrate a 2.1 list named
alist@example.comand its archives.This is documented at https://docs.list.org/en/latest/ (prominent link in sidebar). This appears to be completely different from https://docs.mailman3.org/ (and https://mailman.readthedocs.io/ which I guess is just a redirect). But it looks like the sources are in the some gitlab repo?!
Both docs.list.org and docs.mailman3.org are CNAMEs the resolve ultimately to readthedocs.io. I.e. they both get to the same readthedocs pages the source for which is the https://gitlab.com/mailman/mailman-suite-doc project.
https://mailman.readthedocs.io/ also goes readthedocs.io, but to the documentation for Mailman core rather than that for Mailman Suite.
Did you specify the list's fqdn as in https://www.example.com/archives/list/list@example.com/
That's not an FQDN, though. "example.com" might be one, but that whole thing is the URL to the archive.
I meant did he go to a url like https://www.example.com/archives/list/list@example.com/ as opposed to https://www.example.com/archives/list/list/
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Sapiro writes:
Both docs.list.org and docs.mailman3.org are CNAMEs the resolve ultimately to readthedocs.io. I.e. they both get to the same readthedocs pages the source for which is the https://gitlab.com/mailman/mailman-suite-doc project.
https://mailman.readthedocs.io/ also goes readthedocs.io, but to the documentation for Mailman core rather than that for Mailman Suite.
That doesn't seem like a great idea. :-(
On 11/24/21 7:50 PM, Stephen J. Turnbull wrote:
Pedantry aside, I think we should probably have a Mailman-specific glossary for many terms, including the tests we use for validation. In this case, FQDN appears to be "sequence of characters not containing '@' or '/'."
Strongly agree about the glossary. For example, not every mailing list user will know the term "social login."
As for FQDN, is there some reason we shouldn't use the definition from RFC 1594, section 5.2?
5.2 What is a Fully Qualified Domain Name?
A Fully Qualified Domain Name (FQDN) is a domain name that
includes all higher level domains relevant to the entity named.
If you think of the DNS as a tree-structure with each node having
its own label, a Fully Qualified Domain Name for a specific node
would be its label followed by the labels of all the other nodes
between it and the root of the tree. For example, for a host, a
FQDN would include the string that identifies the particular host,
plus all domains of which the host is a part up to and including
the top-level domain (the root domain is always null). For
example, atlas.arc.nasa.gov is a Fully Qualified Domain Name for
the host at 128.102.128.50. In addition, arc.nasa.gov is the FQDN
for the Ames Research Center (ARC) domain under nasa.gov.This RFC has been obsoleted by RFC 2664, which no longer contains the FQDN definition -- likely because the RFC authors considered the term's meaning to be self-evident by the late 1990s, when the IETF published 2664. Many RFCs since then have used the term FQDN without defining it.
dn
David Newman writes:
As for FQDN, is there some reason we shouldn't use the definition from RFC 1594, section 5.2?
For the definition, yes, that's fine. But there's more to it if somebody needs to figure out how Mailman uses the term.
One issue is that we don't necessarily follow those definitions exactly, especially when validating. ISTR somebody got in trouble because they had a very unusual (but technically legal) character in an email address. It's a little risky to put implementation details like that in separate documentation rather than chanting "Use the Source, Luke", but on the other hand even if somebody knows where to find the source they may have difficulty reading a regular expression. And in this particular case, the regular expression used to parse the URL accepts almost anything (possibly including Chinese characters and emoji :-) in the FQDN.
Another thing we might want to put in such a glossary item would be under what circumstances we query DNS to check it's valid.
Doing that for *everything* would be a massive undertaking, of course, but it might be worth trying to add such items when we (core devs) get a question, rather than requiring people to search the archives to research it on their own. And for other contributors like you, if you remember having in issue with a term, eg, not recognizing its significance in an error message, you might add it to the glossary.
I'm not sure this is a great idea at all, just throwing things at the wall.
Steve
On 11/24/21 2:36 PM, Mark Sapiro wrote:
On 11/24/21 9:40 AM, David Newman wrote:
IMO post-installation docs for list admins would be a big help in Mailman3 adoption. I'm willing to help with this.
Thank you for being willing to contribute. I think the place for list admin docs would be in the https://gitlab.com/mailman/mailman-suite-doc project which is the source for https://docs.mailman3.org/en/latest/. There is currently a userguide there at source/userguide.rst and referenced from source/index.rst. the addition of an adminguide.rst would be welcom if you want to work on that.
Thanks, will get into this ASAP. Am happy to contribute once I acquire a bit more clue.
When I say "working": I'm looking to migrate Mailman2 mailing lists to Mailman3, but am struggling with even basic setup tasks before we attempt list migtration.
For example, on admin page I've set up two lists, one public and one private (each with unique list IDs), but neither appear in the site's list index.
Here are the steps to migrate a 2.1 list named
alist@example.comand its archives.run Mailman's
bin/mailman create alist@example.comfollow that with
bin/mailman import21 alist@example.com /path/to/mailman2.1/lists/alist/config.pckThat will create the list and import its members and settings.
To import archives run the Django admin command with arguments
hyperkitty_import -l alist@example.com /path/to/mailman2.1/archives/private/alist.mbox/alist.mbox
Good up to here, but ... hyperkitty_import not found.
This wasn't covered in the venv docs:
https://docs.mailman3.org/en/latest/install/virtualenv.html
or in the web frontend docs [1]:
https://docs.mailman3.org/en/latest/config-web.html
or in the howto Brian Carpenter (RIP) wrote for Debian 10:
https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10
Also, I had previously created two other lists under the site admin page. These do not appear in the site's mailing lists page, nor does the list I successfully imported from MM 2.1 appear in the admin page, under mailing lists.
> And I don't know where to add list members. For imported lists, they are already added, but for new lists, you can add them in Postorius under Mass operations -> Mass subscribe or via the bin/mailman commands `addmembers` or `syncmembers`. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/docs/commands.html > And clicking the site archives link throws this error: > > django.urls.exceptions.NoReverseMatch: Reverse for 'hk_list_overview' > with keyword arguments '{'mlist_fqdn': 'wheee'}' not found. 1 > pattern(s) tried: ['archives/list/(?P<mlist_fqdn>[^/@]+@[^/@]+)/$'] Did you specify the list's fqdn as in https://www.example.com/archives/list/list@example.com/
No. I clicked the archives icon at the top of a Postorious page. This is possibly related to the hyperkitty_import issue above.
Thanks again.
dn
[1] In addition to the web frontend docs, there is also a hyperkitty docs page:
https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html
I found this page unhelpful. For example it starts with this command:
sudo python setup.py install
but doesn't say where setup.py resides, or which directory the command should be run from. (And yes, different OSs use different locations. I'd setting for one being named, along with a YMMV disclaimer.)
Then this doc goes to database setup, with this example:
django-admin migrate --pythonpath example_project --settings settings
Again, this is unclear. I don't know what "example_project" is, or in what context it's used here.
This doc also describes a different, and less straightforward, import-from-2.1 procedure than Mark described above.
It's possible the hyperkitty doc is now outdated. I'd be glad to help bring the various different install guides together and update them -- once I better understand how they work. Thanks.
On 11/24/21 10:17 PM, David Newman wrote:
On 11/24/21 2:36 PM, Mark Sapiro wrote:
To import archives run the Django admin command with arguments
hyperkitty_import -l alist@example.com /path/to/mailman2.1/archives/private/alist.mbox/alist.mbox
Good up to here, but ... hyperkitty_import not found.
This wasn't covered in the venv docs:
It is covered at https://docs.mailman3.org/en/latest/migration.html#upgrade-strategy
Your issue is probably that the Django admin command you ran is not
accessing your settings.py. You may need to do
export DJANGO_SETTINGS_MODULE=settings
export PYTHONPATH=/path/to/directory/containing/settings.py
before running the Django admin command. These can also be given as --settings and --pythonpath options to the Django admin command.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 11/25/21 10:28 AM, Mark Sapiro wrote:
On 11/24/21 10:17 PM, David Newman wrote:
On 11/24/21 2:36 PM, Mark Sapiro wrote:
To import archives run the Django admin command with arguments
hyperkitty_import -l alist@example.com /path/to/mailman2.1/archives/private/alist.mbox/alist.mbox
Good up to here, but ... hyperkitty_import not found.
This wasn't covered in the venv docs:
It is covered at https://docs.mailman3.org/en/latest/migration.html#upgrade-strategy
Your issue is probably that the Django admin command you ran is not accessing your
settings.py. You may need to doexport DJANGO_SETTINGS_MODULE=settings export PYTHONPATH=/path/to/directory/containing/settings.pybefore running the Django admin command. These can also be given as --settings and --pythonpath options to the Django admin command.
Thanks for this. After setting these variables and restarting mailman3 and mailmanweb, the mailman user still cannot find a hyperkitty_import command (neither can root, btw). Again, I installed MM3 and Django/Postorius/Hyperkitty using the venv and web docs previously referenced.
On the plus side, all lists now appear in the admin web page. However, lists created from the admin page do not appear in a site list page, even though all lists are in the same site/domain.
Finally, how to make these exports permanent? I did not see this covered in the migration doc above. This is on a Debian system where the mailman user's shell is bash. Is this simply a matter of adding environment variables in the mailman user's .bashrc file?
Thanks
dn
On 11/25/21 10:56 AM, David Newman wrote:
Thanks for this. After setting these variables and restarting mailman3 and mailmanweb, the mailman user still cannot find a hyperkitty_import command (neither can root, btw). Again, I installed MM3 and Django/Postorius/Hyperkitty using the venv and web docs previously referenced.
Don't run mailman or django admin commands as root. This causes issues when files are created by root and can't be read by mailman.
What django admin command are you running? If you don't set
DJANGO_SETTINGS_MODULE in the environment and you have activated your
virtualenv and run mailman-web as the django admin command it will set
/etc/mailman3/settings.py as the settings.
On the plus side, all lists now appear in the admin web page. However, lists created from the admin page do not appear in a site list page, even though all lists are in the same site/domain.
By default, only lists that you are owner, moderator or subscriber for are shown. What if you click Filter by Role and select All?
Finally, how to make these exports permanent? I did not see this covered in the migration doc above. This is on a Debian system where the mailman user's shell is bash. Is this simply a matter of adding environment variables in the mailman user's .bashrc file?
You can do that but as I note above, if you run mailman-web you
shouldn't need to. You can add a source /opt/mailman/venv/bin/activate
command as mentioned at
https://docs.mailman3.org/en/latest/install/virtualenv.html#activate-virtual....
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 11/25/21 1:16 PM, Mark Sapiro wrote:
On 11/25/21 10:56 AM, David Newman wrote:
Thanks for this. After setting these variables and restarting mailman3 and mailmanweb, the mailman user still cannot find a hyperkitty_import command (neither can root, btw). Again, I installed MM3 and Django/Postorius/Hyperkitty using the venv and web docs previously referenced.
Don't run mailman or django admin commands as root. This causes issues when files are created by root and can't be read by mailman.
Understood, thanks. I'd only tried root to determine if there was a permissions issue, where hyperkitty_import really did exist but wasn't available to the mailman user.
What django admin command are you running?
As the mailman user, with venv activated:
(venv) mailman@lists:~$ hyperkitty_import -l testlist@lists.domain.com /var/lib/mailman/archives/private/testlist.mbox/testlist.mbox
'testlist' and 'lists.domain.com' are redactions; they are correct in the given command, but the command fails because the system can't find hyperkitty_import.
(BTW
Also, because I'm looking to migrate from Mailman 2.1 installed from Debian packages, all the 2.1 stuff is owned by the 'list' user. I'd changed ownership of the above private archive to mailman:mailman for the command not to complain about permissions.
If you don't set DJANGO_SETTINGS_MODULE in the environment and you have activated your virtualenv and run
mailman-webas the django admin command it will set /etc/mailman3/settings.py as the settings.
I'd run these two environment commands as the mailman user with virtualenv activated:
export DJANGO_SETTINGS_MODULE=settings export PYTHONPATH=/etc/mailman3/settings.py
Am I being overly literal here with 'settings' in that first command? Asking because 'mailman-web check' runs clean before running these commands and returns this error afterward:
ModuleNotFoundError: No module named 'settings'
Either way, the hyperkitty_import command still isn't found.
On the plus side, all lists now appear in the admin web page. However, lists created from the admin page do not appear in a site list page, even though all lists are in the same site/domain.
By default, only lists that you are owner, moderator or subscriber for are shown. What if you click Filter by Role and select All?
Same result. In this case, the ID of the admin and list owner are the same.
Finally, how to make these exports permanent? I did not see this covered in the migration doc above. This is on a Debian system where the mailman user's shell is bash. Is this simply a matter of adding environment variables in the mailman user's .bashrc file?
You can do that but as I note above, if you run
mailman-webyou shouldn't need to. You can add asource /opt/mailman/venv/bin/activatecommand as mentioned at https://docs.mailman3.org/en/latest/install/virtualenv.html#activate-virtual....
Yes, this is what I have in mailman's .bashrc file. I'd followed that venv doc for initial installation, and it activates the virtualenv whenever launching a shell for mailman.
dn
On 11/26/21 9:49 AM, David Newman wrote:
On 11/25/21 1:16 PM, Mark Sapiro wrote:
What django admin command are you running?
As the mailman user, with venv activated:
(venv) mailman@lists:~$ hyperkitty_import -l testlist@lists.domain.com /var/lib/mailman/archives/private/testlist.mbox/testlist.mbox
hyperkitty_import is not a command. it is a subcommand to the django administration command. You need to run
mailman-web hyperkitty_import -l testlist@lists.domain.com
/var/lib/mailman/archives/private/testlist.mbox/testlist.mbox
...
If you don't set DJANGO_SETTINGS_MODULE in the environment and you have activated your virtualenv and run
mailman-webas the django admin command it will set /etc/mailman3/settings.py as the settings.I'd run these two environment commands as the mailman user with virtualenv activated:
export DJANGO_SETTINGS_MODULE=settings export PYTHONPATH=/etc/mailman3/settings.py
That should be
export PYTHONPATH=/etc/mailman3/
but you don't need these.
Am I being overly literal here with 'settings' in that first command? Asking because 'mailman-web check' runs clean before running these commands and returns this error afterward:
ModuleNotFoundError: No module named 'settings'
Yes, the mailman-web command sets these up correctly if they aren't set, but if they are, it believes what you set which was wrong for PYTHONPATH.
Don't set those environment variables and let mailman-web do it for you.
Either way, the hyperkitty_import command still isn't found.
Again because it's not a command but a mailman-web subcommand.
By default, only lists that you are owner, moderator or subscriber for are shown. What if you click Filter by Role and select All?
Same result. In this case, the ID of the admin and list owner are the same.
Have you set FILTER_VHOST = True in your settings.py. If so, that could possibly explain it.
Can you access these lists at something like https://example.com/mailman3/lists/listname@example.com
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 11/26/21 10:21 AM, Mark Sapiro wrote:
On 11/26/21 9:49 AM, David Newman wrote:
On 11/25/21 1:16 PM, Mark Sapiro wrote:
What django admin command are you running?
As the mailman user, with venv activated:
(venv) mailman@lists:~$ hyperkitty_import -l testlist@lists.domain.com /var/lib/mailman/archives/private/testlist.mbox/testlist.mbox
hyperkitty_import is not a command. it is a subcommand to the django administration command. You need to run
mailman-web hyperkitty_import -l testlist@lists.domain.com /var/lib/mailman/archives/private/testlist.mbox/testlist.mbox
Bingo. Thank you!
When running the subsequent 'mailman-web update_index_one_list' command to index the imported archive, the command failed with a permissions error on '/opt/mailman/web/fulltext_index' because that directory didn't yet exist. Creating that directory and chown'ing it to mailman resolved that.
I'm still getting an error from the list page when clicking archives, but I'll investigate further and open a new thread if needed. Let's close this already overly long thread here.
Thanks *very* much for your patience in resolving the import issue. If nothing else this is good fodder for an eventual admin guide.
dn
On 11/26/21 10:38 AM, David Newman wrote:
When running the subsequent 'mailman-web update_index_one_list' command to index the imported archive, the command failed with a permissions error on '/opt/mailman/web/fulltext_index' because that directory didn't yet exist. Creating that directory and chown'ing it to mailman resolved that.
Yes, that instruction assumes you're importing the archive into an
installation that already has other lists indexed. The very first time,
you should be able to run mailman-web rebuild_index to build the index
for all lists.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
David Newman -
Mark Sapiro -
Stephen J. Turnbull