Hi,
On https://docs.mailman3.org/en/latest/faq-migration.html it says "Mailman 3
has a completely new account management system, none of the passwords from
Mailman 2 will work with Mailman 3. Each user needs to sign up in Postorius for
a new account to manage their memberships on all lists on a
> There is no guarantee that any Mailman Core installation into which a MM 2.1
> list is imported actually also supports Django users for Postorius and/or
> HyperKitty.
There is no guarantee that a mailman-core installation also includes Postorius
and/or HyperKitty. However we can imagine that
Interesting.
As far as slow import times that should be left to the discretion of the user.
If they are willing to opt-in to a passwords step, and spend hours on it, then
why not...
This is a relevant drawback: "What about an import of two lists with members
which are the same person, but wit
Ubuntu 20.04 will be end-of-life, from a standard perspective, in a year.
If you possibly can, prefer to install on the latest version which is
Ubuntu 24.04.
Another option is upgrading the original server to 22.04.And then,
24.04.Upgrade procedures usually go fine.
On Fri, Oct 4, 2024 a
In the earlier screen dump
"Clusters 0 Workers
0"
doesn't seem right. I get:
"Clusters 1Workers
2"
___
Ma
> What is missing
check on the status of the qcluster component. see documentation. Did you
install that? Is it running?
___
Mailman-users mailing list -- mailman-users@mailman3.org
To unsubscribe send an email to mailman-users-le...@mailman3.org
https
> The venv installation doesn't seem to ship those wrappers, which is why
> people write them themselves or use the whole explicit su mechanism to change
> to the correct users.
>From the mailman suite docs:
"Virtualenv Installation, recommended for Production"
It's recommended for production.
Hi Marc,
I might post more later about this topic, but for now,
You wrote:
su - -u list -s /bin/bash -c "mailman-web makemigrations --merge"
Let's switch to harmless test without migrations. Try:
su - -u list -s /bin/bash -c "pwd"
That fails on Ubuntu 24.04. Did you mean sudo instead of su
Hi @Mihai,
Right. The user 'list' goes at the end, instead of -u.
> The list user is typically used by the mailman-wrapper wrapper.
I'm discovering the great usefulness of the mailman-wrapper. :-) So the next
question: I used git to check out a bunch of the official gitlab repositories.
And
Thanks for the feedback.
> an influx of requests along the lines of "I don't have a variable called
> $LIST_USER"
True. But if it's described abstractly enough, as you are explaining here in
this thread, might be ok.
___
Mailman-users mailing list --
Thanks. That fixed it.
Comments:
1. In the docs, the instructions say "POSTORIUS_TEMPLATE_BASE_URL =
'http://localhost:8000'. As a reader, you are thinking, I'm running both
hyperkitty and postorius. Hyperkitty is at /archives/ and postorius is at
/mailman3/ . What about the path '/mailman3/
> Actually, it assumes whatever the default is which might be
> http://localhost:8000. See
> https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/settings/mailman.py?ref_type=heads#L16
This is just tossing out some ideas, and it may not be worth it, but in the
code instead of hardcodi
It seems templates can be configured in the filesystem or via postorius. When I
place a footer template in the filesystem it worked fine. Then without
adjusting any configuration, without removing that, I tried to use the
postorius control panel to add a footer template, which ends up in the
d
It takes time to figure out a new feature. I see what is happening. :-) Or,
merely one step further.
After a template is stored in the DB you can remove POSTORIUS_TEMPLATE_BASE_URL
because the value is cached in the DB. That explains the caching.
Next, without POSTORIUS_TEMPLATE_BASE_URL,
> Have you also ran update_index_one_list later on?
Right. I did run "update_index_one_list" also.
___
Mailman-users mailing list -- mailman-users@mailman3.org
To unsubscribe send an email to mailman-users-le...@mailman3.org
https://lists.mailman3.org/m
> did you restart mailman-web?
After encountering the problem, one thing I tried is rebooting, which would
restart mailman-web. Didn't help.
> See the thread (started by you)
I had updated other threads, but not that one - the problem discovered a few
weeks later was: qcluster not running.
I will update this thread in retrospect, from another thread later in June 2024:
"""
Besides "delete this thread" not working, the number of comments, participants,
and unread messages were updating sporadically, rather than immediately. Can
you guess what it was?
qcluster wasn't running. Th
Make sure to "trust" all websites that need to be trusted.
https://stackoverflow.com/questions/49324802/pip-always-fails-ssl-verification
Example:
python -m pip install --trusted-host pypi.python.org --trusted-host
files.pythonhosted.org --trusted-host pypi.org --upgrade pip
"blocking outbou
Thanks for the reply. There is double evidence they were imported:
1. I did include --since 1970. The command was mailman-web-wrapper
hyperkitty_import --since 1970
2. The messages are present. If I navigate to "All threads", and the last page,
it's full of emails from 2004, as is the second-
Hi,
After running hyperkitty_import to import thousands of emails from mailman2
(the years 2013-2025) I then ran another import for years 2004-2013 from
another mbox file. It was an entirely earlier timeframe, which may be relevant.
After the first import, the "Thre
Haystack supports multiple backends
https://django-haystack.readthedocs.io/en/master/backend_support.html
- Solr
- ElasticSearch
- Whoosh
- Xapian
You should rephrase the question to something like "Why ElasticSearch instead
of PostgreSQL?" And the answer: ElasticSearch is a focused, pur
Solved. Or at least one solution.
https://gitlab.com/mailman/hyperkitty/-/merge_requests/671
___
Mailman-users mailing list -- mailman-users@mailman3.org
To unsubscribe send an email to mailman-users-le...@mailman3.org
https://lists.mailman3.org/mailm
22 matches
Mail list logo