On 6/7/23 11:58, {16/7} wrote:
I have both the mailman and mailman3-full packages installed on my machine and I'm following the migration guide located here: https://docs.mailman3.org/en/latest/migration.html
Which is the source of at least one of your issues. The Debian packages are behind and are missing multiple bug fixes and enhancements.
Running the command { mailman import21 mylist@mysite.com /var/lib/mailman/lists/mylist/config.pck } completes once I create the list but states that it cannot convert the msg_footer and digest_footer mailing list attributes. (I might also point out that the { mailman create mylist@mysite.com } command isn't actually documented on that webpage.)
import21 tries to make Mailman 3 compatible versions of your Mailman 2.1 msg_footer and digest_footer. It will put these in Mailman's var/templates/lists/<list-id>/<lc>/ directory as list:member:regular:footer.txt and list:member:digest:footer.txt respectively. You need to examine those files as they probably contain Mailman 2.1 style replacements that haven't been converted. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/t... for the Mailman 3 replacements which are encoded as dollar strings, e.g. $listname gets replaced with the list's posting address.
I can't seem to find the manage.py script in my $PATH and after searching, I find it as part of the mailman3-web package.
As you report in a followup, in the Debian package it's called mailman-web
Next, I changed the file's group back to list and decided to try running the manage.py script as the www-data user. This results in "/usr/lib/python3/dist-packages/django_q/conf.py:139: UserWarning: Retry and timeout are misconfigured." and "System check identified some issues:" followed by a list of "Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'" warnings for a number of Django tables.
Recent mailman installed following https://docs.mailman3.org/en/latest/install/virtualenv.html will include
DEFAULT_AUTO_FIELD = 'django.db.models.AutoField'
in Django's settings which will avoid that warning with Django>=3.2
My questions are:
- How do I undo any damage (if any) my efforts may have caused?
You probably didn't do any damage as the commands failed before doing anything.
- What's the correct way to run manage.py?
I see from your follow up that you figured this out.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan