E-mail every minute: "Cron <www-data@sharky5> ..."
What am I missing? I *think* I have mailman3 *mostly* setup, but there are still some configuration things that are missing, but I am not sure how to fix them (the docs are NOT clear). I am getting an e-mail *every* minute that looks like:
From www-data@deepsoft.com Sat Jul 6 17:38:03 2024 Return-Path: <www-data@deepsoft.com> X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on sharky5.deepsoft.com X-Spam-Level: X-Spam-Status: No, score=-850.0 required=5.0 tests�YES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NO_RELAYS,URIBL_BLOCKED, USER_IN_WELCOMELIST autolearn=ham autolearn_force=no version=4.0.0 X-Original-To: www-data Delivered-To: www-data@deepsoft.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d�epsoft.com; s�epsoft.com; t20301883; bh=qGrVTBfV1NiqgxCIzSaXwoKZ0lKxKvaK56k31yXU2Sk=; h=From:To:Subject:Date:From; b=jTml1ZF+qGkmS2tcz5kgZHjOyPxeaWIQiX1mzAF3ZfZWb0ziVLxutkcej5mGapUOq PpH6ExYM1TEipMTYQ/JRY/74vz2dEpebDrZqjyY3KakxLWiyFFEb5glmQYZGvz9wr2 e5ljD0Shku4fbRoaxO7XMQCn/fmx3+D8tI/ZPbMQReceived: by sharky5.deepsoft.com (Postfix, from userid 33) id 5257D4C1296; Sat, 6 Jul 2024 17:38:03 -0400 (EDT) From: root@deepsoft.com (Cron Daemon) To: www-data@deepsoft.com Subject: Cron <www-data@sharky5> [ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.minutely /usr/share/mailman3-web/manage.py runjobs minutely MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Cron-Env: <SHELL=/bin/sh> X-Cron-Env: <HOME=/var/www> X-Cron-Env: <PATH=/usr/bin:/bin> X-Cron-Env: <LOGNAME=www-data> Message-Id: <20240706213803.5257D4C1296@sharky5.deepsoft.com> Date: Sat, 6 Jul 2024 17:38:03 -0400 (EDT) X-Scanned-By: MIMEDefang 3.3 on 108.161.129.198 Status: R
/usr/lib/python3/dist-packages/django_q/conf.py:139: UserWarning: Retry and timeout are misconfigured. Set retry larger than timeout, failure to do so will cause the tasks to be retriggered before completion. See https://django-q.readthedocs.io/en/latest/configure.html#retry for details. warn( System check identified some issues:
WARNINGS: django_mailman3.MailDomain: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. django_mailman3.Profile: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Attachment: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Email: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Favorite: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.LastView: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.MailingList: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Profile: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Tag: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Tagging: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Thread: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.ThreadCategory: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Vote: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. postorius.EmailTemplate: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the PostoriusConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'.
And I get this output from sudo mailman-web check --no-color :
System check identified some issues:
WARNINGS: django_mailman3.MailDomain: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. django_mailman3.Profile: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Attachment: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Email: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Favorite: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.LastView: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.MailingList: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Profile: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Tag: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Tagging: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Thread: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.ThreadCategory: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Vote: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. postorius.EmailTemplate: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the PostoriusConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'.
System check identified 14 issues (0 silenced).
Again, the docs are not helpful (at least not to me).
-- Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services heller@deepsoft.com -- Webhosting Services
On 7/7/24 6:11 AM, Robert Heller wrote:
What am I missing? I *think* I have mailman3 *mostly* setup, but there are still some configuration things that are missing, but I am not sure how to fix them (the docs are NOT clear). I am getting an e-mail *every* minute that looks like: ... /usr/lib/python3/dist-packages/django_q/conf.py:139: UserWarning: Retry and timeout are misconfigured. Set retry larger than timeout, failure to do so will cause the tasks to be retriggered before completion. See https://django-q.readthedocs.io/en/latest/configure.html#retry for details.
Set something like
# Set retry > timeout.
Q_CLUSTER = {
'timeout': 300,
'retry': 360,
'save_limit': 100,
'orm': 'default',
}
in your settings_local.py
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Sun, Jul 7, 2024 at 4:12 PM Robert Heller <heller@deepsoft.com> wrote:
What am I missing? I *think* I have mailman3 *mostly* setup, but there are still some configuration things that are missing, but I am not sure how to fix them (the docs are NOT clear).
Which docs are you relying on?
How about this - https://docs.mailman3.org/en/latest/install/virtualenv.html ??
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
At Sun, 7 Jul 2024 18:52:05 +0300 Odhiambo Washington <odhiambo@gmail.com> wrote:
On Sun, Jul 7, 2024 at 4:12â¯PM Robert Heller <heller@deepsoft.com> wrote:
What am I missing? I *think* I have mailman3 *mostly* setup, but there are still some configuration things that are missing, but I am not sure how to fix them (the docs are NOT clear).
Which docs are you relying on?
https://docs.mailman3.org/en/latest/config-web.html
I presume these are the official docs for mailman3 -- maybe they aren't?
How about this - https://docs.mailman3.org/en/latest/install/virtualenv.html ??
I'm not using a virtual environment. I'm using all native Debian 12 packages, installed via apt. The virtual environment docs are actually even worse (even more confusing). Maybe I'm too smart and experienced?
Is there some reason NOT to use the native Debian 12 packages? Did the Debian package manager people waste their time and effort?
-- Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services heller@deepsoft.com -- Webhosting Services
On 7/7/24 9:16 AM, Robert Heller wrote:
I'm not using a virtual environment. I'm using all native Debian 12 packages, installed via apt. The virtual environment docs are actually even worse (even more confusing). Maybe I'm too smart and experienced?
Is there some reason NOT to use the native Debian 12 packages? Did the Debian package manager people waste their time and effort?
If you prefer to use the Debian packages, that's fine, but if using the Debian packages, your primary resource for support, documentation, bug reports, etc. should be Debian. See https://wiki.list.org/x/12812344
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Sun, Jul 7, 2024 at 7:16 PM Robert Heller <heller@deepsoft.com> wrote:
At Sun, 7 Jul 2024 18:52:05 +0300 Odhiambo Washington <odhiambo@gmail.com> wrote:
On Sun, Jul 7, 2024 at 4:12 PM Robert Heller <heller@deepsoft.com>
wrote:
What am I missing? I *think* I have mailman3 *mostly* setup, but there are still some configuration things that are missing, but I am not sure
how to
fix them (the docs are NOT clear).
Which docs are you relying on?
https://docs.mailman3.org/en/latest/config-web.html
I presume these are the official docs for mailman3 -- maybe they aren't?
How about this -
https://docs.mailman3.org/en/latest/install/virtualenv.html
??
I'm not using a virtual environment. I'm using all native Debian 12 packages, installed via apt. The virtual environment docs are actually even worse (even more confusing).
Worse? :-)
Maybe I'm too smart and experienced?
You're clearly overestimating your smartness :-)
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
At Sun, 7 Jul 2024 19:48:02 +0300 Odhiambo Washington <odhiambo@gmail.com> wrote:
On Sun, Jul 7, 2024 at 7:16â¯PM Robert Heller <heller@deepsoft.com> wrote:
At Sun, 7 Jul 2024 18:52:05 +0300 Odhiambo Washington <odhiambo@gmail.com> wrote:
On Sun, Jul 7, 2024 at 4:12âÃâ¬Ã¯PM Robert Heller <heller@deepsoft.com>
wrote:
What am I missing? I *think* I have mailman3 *mostly* setup, but there are still some configuration things that are missing, but I am not sure
how to
fix them (the docs are NOT clear).
Which docs are you relying on?
https://docs.mailman3.org/en/latest/config-web.html
I presume these are the official docs for mailman3 -- maybe they aren't?
How about this -
https://docs.mailman3.org/en/latest/install/virtualenv.html
??
I'm not using a virtual environment. I'm using all native Debian 12 packages, installed via apt. The virtual environment docs are actually even worse (even more confusing).
Worse? :-)
Even more confusing. Both sets of docs make various assumptions and don't really explain things properly. Like everywhere where "settings.py" is mentioned, it really means "/etc/mailman3/mailman-web.py"
In any case, the virtual environment docs are hard to relate to a "native" install and are generally hard to follow, since they seem to jump all over the place. (Spaghetti docs?) And it is hard to replace the various (and not always consistent) virtual environment paths and settings files to the "native" paths.
The "official" docs are just not useful to me, since I am not using a virtual environment. If a virtual environment is recomended, what is the point of the Debian 12 packages? Are they just not meant to be used? Really? Do you mean that I should use a separate package management system for Mailman3? That really sucks.
Maybe I'm too smart and experienced?
You're clearly overestimating your smartness :-)
Maybe. I am NOT an experienced Python programmer -- it is one of my *least* favorite programming languages.
At this point I am considering scrapping Mailman and either giving up on have mailling lists on my new server or using some other mailing list software,
-- Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services heller@deepsoft.com -- Webhosting Services
On Sun, Jul 7, 2024 at 8:43 PM Robert Heller <heller@deepsoft.com> wrote:
At Sun, 7 Jul 2024 19:48:02 +0300 Odhiambo Washington <odhiambo@gmail.com> wrote:
On Sun, Jul 7, 2024 at 7:16 PM Robert Heller <heller@deepsoft.com>
wrote:
At Sun, 7 Jul 2024 18:52:05 +0300 Odhiambo Washington <
wrote:
On Sun, Jul 7, 2024 at 4:12 PM Robert
Heller <heller@deepsoft.com> wrote:
What am I missing? I *think* I have mailman3 *mostly* setup, but
odhiambo@gmail.com> there
are still some configuration things that are missing, but I am not sure how to fix them (the docs are NOT clear).
Which docs are you relying on?
https://docs.mailman3.org/en/latest/config-web.html
I presume these are the official docs for mailman3 -- maybe they aren't?
How about this -
https://docs.mailman3.org/en/latest/install/virtualenv.html
??
I'm not using a virtual environment. I'm using all native Debian 12 packages, installed via apt. The virtual environment docs are actually even worse (even more confusing).
Worse? :-)
Even more confusing. Both sets of docs make various assumptions and don't really explain things properly. Like everywhere where "settings.py" is mentioned, it really means "/etc/mailman3/mailman-web.py"
No! It means /etc/mailman3/settings.py - literally!
In any case, the virtual environment docs are hard to relate to a "native" install and are generally hard to follow, since they seem to jump all over the place.
When one day you'll be able to internalize what a Python virtual environment is, you'll realize that it's VERY convenient. You will actually embrace it from that point onwards.
(Spaghetti docs?) And it is hard to replace the various (and not
always consistent) virtual environment paths and settings files to the "native" paths.
Actually, if you're this inclined to run everything natively, MM3 is perhaps not for you. Why? Because you'll not easily find help here. We focus on the virtual environment only as the standard.. Why? Because no one is willing to deal with ALL the OS-centric packaging out there. Python virtual environment is universal across all the OSes, I can say.
The "official" docs are just not useful to me, since I am not using a virtual environment. If a virtual environment is recomended, what is the point of the Debian 12 packages?
We cannot answer that here. I guess they are meant for people like you who strive under pain :-) With the Python virtual environment, I can install and manage MM3 in almost any *nix OS.
Are they just not meant to be used? Really? Do you mean that I should use a separate package management system for Mailman3? That really sucks.
Yes, they are meant to be used. Noone denies that. However, they are not packaged by the Mailman Developers. Did you read one response from Mark Sapiro where he said, and I quote:
If you prefer to use the Debian packages, that's fine, but if using the
Debian packages, your primary resource for support, documentation, bug
reports, etc. should be Debian. See https://wiki.list.org/x/12812344
So yes, go ahead and use the Debian packages. No one is stopping you.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
At Mon, 8 Jul 2024 00:16:48 +0300 Odhiambo Washington <odhiambo@gmail.com> wrote:
On Sun, Jul 7, 2024 at 8:43â¯PM Robert Heller <heller@deepsoft.com> wrote:
At Sun, 7 Jul 2024 19:48:02 +0300 Odhiambo Washington <odhiambo@gmail.com> wrote:
On Sun, Jul 7, 2024 at 7:16âÃâ¬Ã¯PM Robert Heller <heller@deepsoft.com>
wrote:
At Sun, 7 Jul 2024 18:52:05 +0300 Odhiambo Washington <
wrote:
On Sun, Jul 7, 2024 at 4:12ÃÆÃÆÃââÃÆÃââÃâìÃÆÃâÃâïPM Robert
Heller <heller@deepsoft.com> wrote:
What am I missing? I *think* I have mailman3 *mostly* setup, but
odhiambo@gmail.com> there
are still some configuration things that are missing, but I am not sure how to fix them (the docs are NOT clear).
Which docs are you relying on?
https://docs.mailman3.org/en/latest/config-web.html
I presume these are the official docs for mailman3 -- maybe they aren't?
How about this -
https://docs.mailman3.org/en/latest/install/virtualenv.html
??
I'm not using a virtual environment. I'm using all native Debian 12 packages, installed via apt. The virtual environment docs are actually even worse (even more confusing).
Worse? :-)
Even more confusing. Both sets of docs make various assumptions and don't really explain things properly. Like everywhere where "settings.py" is mentioned, it really means "/etc/mailman3/mailman-web.py"
No! It means /etc/mailman3/settings.py - literally!
In any case, the virtual environment docs are hard to relate to a "native" install and are generally hard to follow, since they seem to jump all over the place.
When one day you'll be able to internalize what a Python virtual environment is, you'll realize that it's VERY convenient. You will actually embrace it from that point onwards.
(Spaghetti docs?) And it is hard to replace the various (and not
always consistent) virtual environment paths and settings files to the "native" paths.
Actually, if you're this inclined to run everything natively, MM3 is perhaps not for you. Why? Because you'll not easily find help here. We focus on the virtual environment only as the standard.. Why? Because no one is willing to deal with ALL the OS-centric packaging out there. Python virtual environment is universal across all the OSes, I can say.
The "official" docs are just not useful to me, since I am not using a virtual environment. If a virtual environment is recomended, what is the point of the Debian 12 packages?
We cannot answer that here. I guess they are meant for people like you who strive under pain :-) With the Python virtual environment, I can install and manage MM3 in almost any *nix OS.
Are they just not meant to be used? Really? Do you mean that I should use a separate package management system for Mailman3? That really sucks.
Yes, they are meant to be used. Noone denies that. However, they are not packaged by the Mailman Developers. Did you read one response from Mark Sapiro where he said, and I quote:
If you prefer to use the Debian packages, that's fine, but if using the Debian packages, your primary resource for support, documentation, bug reports, etc. should be Debian. See https://wiki.list.org/x/12812344So yes, go ahead and use the Debian packages. No one is stopping you.
I uninstalled them and have given up on mm3. It means the main mailling list I have been hosting for the past while (more than a decade), will have to migrate to something else... :-(
-- Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services heller@deepsoft.com -- Webhosting Services
On Sun, Jul 7, 2024 at 8:43 PM Robert Heller <heller@deepsoft.com> wrote:
At Sun, 7 Jul 2024 19:48:02 +0300 Odhiambo Washington <odhiambo@gmail.com> wrote:
On Sun, Jul 7, 2024 at 7:16 PM Robert Heller <heller@deepsoft.com>
wrote:
At Sun, 7 Jul 2024 18:52:05 +0300 Odhiambo Washington <
wrote:
On Sun, Jul 7, 2024 at 4:12 PM Robert
Heller <heller@deepsoft.com> wrote:
What am I missing? I *think* I have mailman3 *mostly* setup, but
odhiambo@gmail.com> there
are still some configuration things that are missing, but I am not sure how to fix them (the docs are NOT clear).
Which docs are you relying on?
https://docs.mailman3.org/en/latest/config-web.html
I presume these are the official docs for mailman3 -- maybe they aren't?
How about this -
https://docs.mailman3.org/en/latest/install/virtualenv.html
??
I'm not using a virtual environment. I'm using all native Debian 12 packages, installed via apt. The virtual environment docs are actually even worse (even more confusing).
Worse? :-)
Even more confusing. Both sets of docs make various assumptions and don't really explain things properly. Like everywhere where "settings.py" is mentioned, it really means "/etc/mailman3/mailman-web.py"
In any case, the virtual environment docs are hard to relate to a "native" install and are generally hard to follow, since they seem to jump all over the place. (Spaghetti docs?) And it is hard to replace the various (and not always consistent) virtual environment paths and settings files to the "native" paths.
The "official" docs are just not useful to me, since I am not using a virtual environment. If a virtual environment is recomended, what is the point of the Debian 12 packages? Are they just not meant to be used? Really? Do you mean that I should use a separate package management system for Mailman3? That really sucks.
Maybe I'm too smart and experienced?
You're clearly overestimating your smartness :-)
Maybe. I am NOT an experienced Python programmer -- it is one of my *least* favorite programming languages.
No programming is required to install MM3. Just competence as a Sysadmin, IMHO.
At this point I am considering scrapping Mailman and either giving up on
have mailling lists on my new server or using some other mailing list software,
If you follow the documentation about the Python virtual environment to the letter, you can have MM3 running in not more than 1 hour. And don't give up! I do understand how frustrating it can be. I have walked that route before and I can easily feel you. If you need my personal help, talk to me offlist and I will be able to walk you through the process. I could install MM3 for you, but you'll be administering your system so you need to understand what is going on, right? I actually can install it for you for FREE, but I will not help you with administering it for free :-)
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
On 2024-07-07 13:43:49 -0400 (-0400), Robert Heller wrote: [...]
what is the point of the Debian 12 packages? Are they just not meant to be used? Really? Do you mean that I should use a separate package management system for Mailman3? That really sucks. [...]
I'm sure packages from any distribution are fine, but if you're using distro packaged software then your distribution is your first line of support because upstream developers don't know what changes have been made downstream by every distribution's package maintainers.
If you need assistance with Debian's packaged software, the debian-user mailing list[*] is generally your first line of support. If you believe you've found a bug in the software, file it in the Debian BTS[**] and the package maintainer can determine if it's specific to Debian's version of the software or not. If the problem is not Debian-specific, the package maintainer should then forward the bug upstream for further action.
[*] https://lists.debian.org/debian-user/ [**] https://www.debian.org/Bugs/Reporting
Jeremy Stanley
Robert Heller wrote:
I'm using all native Debian 12 packages, installed via apt.
Some notes from my install (Debian 12):
| # install missing dependencies: | apt install python3-pymysql python3-mysqldb | | apt install mailman3-full | | # fix broken settings: | vim /usr/share/mailman3-web/settings.py | #----- | Q_CLUSTER = { | 'timeout': 300, | 'save_limit': 100, | 'orm': 'default', | 'poll': 5, | 'retry': 360, | } | #----- | | # fix auto-generated passwords: | vim /etc/mailman3/mailman.cfg | # remove "/" and "-" from admin_pass | vim /etc/mailman3/mailman-web.py | # remove "/" and "-" from MAILMAN_REST_API_PASS | | # fix "django.db.models.AutoField" errors in log | vim /etc/mailman3/mailman-web.py | #----- | DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' | #-----
HTH -thh
participants (5)
-
Jeremy Stanley -
Mark Sapiro -
Odhiambo Washington -
Robert Heller -
Thomas Hochstein