update problems in virtualenv
Hi all,
i followed https://docs.mailman3.org/en/latest/install/virtualenv.html and ran in different problems. Here's the first.
All mailman-web runjobs report:
System check identified some issues:
WARNINGS: ?: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated, use: settings.ACCOUNT_LOGIN_METHODS = {'username', 'email'} ?: settings.ACCOUNT_EMAIL_REQUIRED is deprecated, use: settings.ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*']
I get those eMails every minute which is a bit annoying.
(venv) mailman@bywater:~/mm/var/data$ python -m pip --version pip 25.3 from /opt/mailman/venv/lib/python3.13/site-packages/pip (python 3.13) (venv) mailman@bywater:~/mm/var/data$ python --version Python 3.13.3 (venv) mailman@bywater:~/mm/var/data$ python -m pip --version pip 25.3 from /opt/mailman/venv/lib/python3.13/site-packages/pip (python 3.13) (venv) mailman@bywater:~/mm/var/data$ pip list --outdated Package Version Latest Type
mailman 3.3.9 3.3.10 wheel (venv) mailman@bywater:~/mm/var/data$ pip install --upgrade mailman==3.3.10 Collecting mailman==3.3.10 Using cached mailman-3.3.10-py3-none-any.whl.metadata (2.4 kB) Requirement already satisfied: aiosmtpd>=1.4.3 in /opt/mailman/venv/lib/python3.13/site-packages (from mailman==3.3.10) (1.4.6) Requirement already satisfied: alembic!=1.7.0,>=1.6.2 in /opt/mailman/venv/lib/python3.13/site-packages (from mailman==3.3.10) (1.17.1) Requirement already satisfied: atpublic in /opt/mailman/venv/lib/python3.13/site-packages (from mailman==3.3.10) (6.0.2) Requirement already satisfied: authheaders>=0.16 in /opt/mailman/venv/lib/python3.13/site-packages (from mailman==3.3.10) (0.16.3) Requirement already satisfied: authres>=1.0.1 in /opt/mailman/venv/lib/python3.13/site-packages (from mailman==3.3.10) (1.2.0) Requirement already satisfied: click>=8.0.0 in /opt/mailman/venv/lib/python3.13/site-packages (from mailman==3.3.10) (8.3.0) Requirement already satisfied: dnspython>=1.14.0 in /opt/mailman/venv/lib/python3.13/site-packages (from mailman==3.3.10) (2.8.0) Requirement already satisfied: falcon>=3.1.3 in /opt/mailman/venv/lib/python3.13/site-packages (from mailman==3.3.10) (4.1.0) Requirement already satisfied: flufl.bounce>=4.0 in /opt/mailman/venv/lib/python3.13/site-packages (from mailman==3.3.10) (4.0) Requirement already satisfied: flufl.i18n>=3.2 in /opt/mailman/venv/lib/python3.13/site-packages (from mailman==3.3.10) (5.2.0) Requirement already satisfied: flufl.lock>=5.1 in /opt/mailman/venv/lib/python3.13/site-packages (from mailman==3.3.10) (8.2.0) Requirement already satisfied: gunicorn in /opt/mailman/venv/lib/python3.13/site-packages (from mailman==3.3.10) (23.0.0) Requirement already satisfied: lazr.config in /opt/mailman/venv/lib/python3.13/site-packages (from mailman==3.3.10) (3.1) INFO: pip is looking at multiple versions of mailman to determine which version is compatible with other requirements. This could take a while. ERROR: Could not find a version that satisfies the requirement nntplib; python_version >= "3.13" (from mailman) (from versions: none) ERROR: No matching distribution found for nntplib; python_version >= "3.13"
standard-nntplib 3.13.0 is installed.
How can i get rid of those mails?
TIA QNo
On 11/4/25 11:47, Christian H. Kuhn via Mailman-users wrote:
Hi all,
i followed https://docs.mailman3.org/en/latest/install/virtualenv.html and ran in different problems. Here's the first.
All mailman-web runjobs report:
System check identified some issues:
WARNINGS: ?: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated, use: settings.ACCOUNT_LOGIN_METHODS = {'username', 'email'} ?: settings.ACCOUNT_EMAIL_REQUIRED is deprecated, use: settings.ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*']
This is https://gitlab.com/mailman/mailman-web/-/issues/37 fixed for the next release. There are two ways to fix this. You can upgrade mailman-web in your venv by activating the venv and doing
pip install --upgrade git+https://gitlab.com/mailman/mailman-web
Or you can add the following to your settings.py after the imports from mailman_web.settings.base and mailman_web.settings.mailman
del ACCOUNT_EMAIL_REQUIRED
del ACCOUNT_AUTHENTICATION_METHOD
ACCOUNT_SIGNUP_FIELDS = ['username*', 'email*', 'password1*', 'password2*']
ACCOUNT_LOGIN_METHODS = {'email', 'username'}
(venv) mailman@bywater:~/mm/var/data$ pip install --upgrade mailman==3.3.10 Collecting mailman==3.3.10 ... INFO: pip is looking at multiple versions of mailman to determine which version is compatible with other requirements. This could take a while. ERROR: Could not find a version that satisfies the requirement nntplib; python_version >= "3.13" (from mailman) (from versions: none) ERROR: No matching distribution found for nntplib; python_version >= "3.13"
standard-nntplib 3.13.0 is installed.
This is an issue with Mailman 3.3.10 and Python >= 3.13 fixed by https://gitlab.com/mailman/mailman/-/merge_requests/1348
Here again if you want to upgrade Mailman core you can do
pip install --upgrade git+https://gitlab.com/mailman/mailman
to get the latest from gitlab.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi Mark,
thank you for your answer. I did both updates, and haven't seen the warning since.
KR QNo
Am 05.11.2025 um 01:40 schrieb Mark Sapiro:
On 11/4/25 11:47, Christian H. Kuhn via Mailman-users wrote:
Hi all,
i followed https://docs.mailman3.org/en/latest/install/virtualenv.html and ran in different problems. Here's the first.
All mailman-web runjobs report:
System check identified some issues:
WARNINGS: ?: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated, use: settings.ACCOUNT_LOGIN_METHODS = {'username', 'email'} ?: settings.ACCOUNT_EMAIL_REQUIRED is deprecated, use: settings.ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*']
This is https://gitlab.com/mailman/mailman-web/-/issues/37 fixed for the next release. There are two ways to fix this. You can upgrade mailman- web in your venv by activating the venv and doing
pip install --upgrade git+https://gitlab.com/mailman/mailman-web
Or you can add the following to your settings.py after the imports from mailman_web.settings.base and mailman_web.settings.mailman
del ACCOUNT_EMAIL_REQUIRED del ACCOUNT_AUTHENTICATION_METHOD ACCOUNT_SIGNUP_FIELDS = ['username*', 'email*', 'password1*', 'password2*'] ACCOUNT_LOGIN_METHODS = {'email', 'username'}(venv) mailman@bywater:~/mm/var/data$ pip install --upgrade mailman==3.3.10 Collecting mailman==3.3.10 ... INFO: pip is looking at multiple versions of mailman to determine which version is compatible with other requirements. This could take a while. ERROR: Could not find a version that satisfies the requirement nntplib; python_version >= "3.13" (from mailman) (from versions: none) ERROR: No matching distribution found for nntplib; python_version >= "3.13"
standard-nntplib 3.13.0 is installed.
This is an issue with Mailman 3.3.10 and Python >= 3.13 fixed by https://gitlab.com/mailman/mailman/-/merge_requests/1348
Here again if you want to upgrade Mailman core you can do
pip install --upgrade git+https://gitlab.com/mailman/mailman
to get the latest from gitlab.
Christian H. Kuhn via Mailman-users writes:
thank you for your answer. I did both updates, and haven't seen the warning since.
You're welcome to ask here, but depending on sleep schedules you often will get a quicker answer by web-searching or searching our archives for keywords like "ACCOUNT_AUTHENTICATION_METHOD" and so on. You may need to search more than one key in this case, because IIRC the warnings showed up in different releases of Django.
Also, as far as I know there are no known cases where warnings, especially deprecation warnings, actually cause Mailman apps to fail. So you can breathe easier.
Obviously you want to deal with these early because they're authentication, and similarly for things related to security. But the system will keep running.
Steve
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan
Hello,
This is an issue with Mailman 3.3.10 and Python >= 3.13 fixed by https://gitlab.com/mailman/mailman/-/merge_requests/1348
Here again if you want to upgrade Mailman core you can do
pip install --upgrade git+https://gitlab.com/mailman/mailman
to get the latest from gitlab.
Is it safe to use latest from gitlab for production usage?
With python-3.13 in Debian stable it would be nice if we could get a new relase of mailman3 with all the fixes for python-3.13.
Regards, Bernhard
On 11/6/25 05:55, Lichtinger, Bernhard wrote:
Is it safe to use latest from gitlab for production usage?
Yes. Officially, we say it's beta quality, but we run it in production for this list and for hundreds of lists on mail.python.org.
With python-3.13 in Debian stable it would be nice if we could get a new relase of mailman3 with all the fixes for python-3.13.
We know, but the release manager is an unpaid volunteer with a day job.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (4)
-
Christian H. Kuhn -
Lichtinger, Bernhard -
Mark Sapiro -
Stephen J. Turnbull