Search results for "dO" - lists.mailman3.org

[MM3-users] Re: setup of URLs

by Abhilash Raj

On Sun, Jan 28, 2018, at 12:24 PM, Peter Münster wrote: > Hi, > > I would like to point "https://my-domain.org/" to the list of > mailing-lists of this domain. How should I setup my Apache configuration > and/or the urlpatterns please? > > With my actual configuration, the above URL is always rewritten to > https://my-domain.org/postorius/lists/ > > These are my urlpatterns: > > urlpatterns = [ > url(r'^$', RedirectView.as_view( > url=reverse_lazy('list_index'), > permanent=True)), ^ This is responsible for re-writing your URL to `/postorius/lists/` as Redirect from `/`. This patch should do what you want: ``` index a5ea108..bff54f3 100644 --- a/example_project/urls.py +++ b/example_project/urls.py @@ -25,11 +25,10 @@ try: except ImportError: from django.urls import reverse_lazy from django.views.generic import RedirectView +from postorius.views.list import list_index urlpatterns = [ - url(r'^$', RedirectView.as_view( - url=reverse_lazy('list_index'), - permanent=True)), + url(r'^$', list_index), url(r'^postorius/', include('postorius.urls')), ``` Just as an FYI, my browser would always re-direct me to /posotrius/lists, even after I applied this patch, not sure if it was some sort of caching or something else. I tried it from an incognito-mode and it seemed to work. -- Abhilash Raj maxking(a)asynchronous.in

7 years, 2 months

[MM3-users] Re: Verification Failed Error

by Stephen J. Turnbull

Abhilash Raj writes: > Exim experts would be able to help you better with this. I'm the one who set up the original sample Exim .conf, because (a) I didn't want to migrate all my bots to Postfix, and (b) the one-real- host .conf turned out to be trivial. I'm an Exim expert only for my own configuration, which is a (pre-global-warming) glacially-moving target. I've never seen anything like the problems described here, sorry. Can't help. Since it's looking like we don't have any real Exim experts hanging around here, perhaps we should move the sample containers and other default configs to assume Postfix and document "Exim should work but you're kinda on your own, we'll do what we can but it's limited." At least Mark is maintaining such systems, and they're probably better documented than Exim for the single-real-host configuration, though they would probably run into similar problems with the containerized setup. WDOT? Steve -- Associate Professor Division of Policy and Planning Science http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN

6 years, 4 months

[MM3-users] Re: Change language to welcome message in mailman3

by Massimo Zappalà

> What is the ownership of the other directories in > /usr/lib/python3/dist-packages/mailman/? They are probably also owned by > root and that should be OK as long as they are world readable. I have checked the permissions and properties of the it directory. They are the same as the en directory. > Please tell me what messages. Do you mean if I subscribe to the list, I > get a welcome message in English, but the list owner gets the > notification of a new member in Italian? Not exactly. If you subscribe a user to a list, the Welcome email arrives in English. On the other hand, if an admin is registered for a list, he receives the email in Italian. But I solved it by changing the value "en" with "it" in the mailman3 database, the mailinglist table, the preferred_language column. Now those who subscribe to the list receive a Welcome email in Italian. > I think you need to set the system default_language. In mailman.cfg, set > [mailman] > default_language: it I had changed this value from the beginning. Thank you very much for your valuable advice and patience Max

4 years, 8 months

[MM3-users] Re: installation

by Mark Sapiro

On 11/21/20 10:42 AM, Christian Stalberg via Mailman-users wrote: > I am working through installing mailman3 on Ubuntu 20.04.1 LTS / apache > 2.4.41 / postfix 3.4.13 and have a couple of questions. > > > > I've installed Django, cloned the mailman-suite repo, installed and tested > apache with Mod_wsgi [ according to > https://tecadmin.net/install-apache-with-python-mod-wsgi-on-ubuntu-20-04/ ] > and it worked fine. Now I am at 'Setting up a WSGI' server in the MM3 > instructions where it says I am to configure uwsgi.ini file. Does that .ini > file go in /opt/mailman/mailman where other .ini files reside? You are mixing apples and oranges. The doc at <https://tecadmin.net/install-apache-with-python-mod-wsgi-on-ubuntu-20-04/> uses mod_wsgi in apache, It doesn't use uwsgi at all. > In setting up the apache virtual server [ according to > https://docs.mailman3.org/projects/postorius/en/latest/deployment.html?highl > ight=apache#apache-with-mod-wsgi ] I do not find a postorius.wsgi which > WSGIScriptAlias points to. The file in your WSGIScriptAlias directive should be the wsgi.py file in mailman-suite/mailman-suite_project/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: Still unable to get mailman3 working on Ubuntu 20.04 LTS

by Mark Sapiro

On 1/6/22 1:20 AM, Michael Heseltine wrote: > Hi all, > I've done the additional steps > > /opt/mailman/mm/bin/django-admin migrate > /opt/mailman/mm/bin/django-admin createsuperuser > > without error, and also started the services mailman, qcluster and gunicorn without error messages. Did you see my post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and did you run /opt/mailman/mm/bin/django-admin migrate before starting services? > However, I just get an internal server error when I try to access https://lists.mydomain.com/ (which is served by a local apache virthost). > > The apache log shows just one error: > > [Thu Jan 06 10:01:39.201833 2022] [proxy:warn] [pid 3627279] [client 333.333.333.333:59328] AH01144: No protocol handler was valid for the URL / (scheme 'http'). If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule. Do you have all of these apache modules enabled, proxy.conf, proxy_http.load and proxy.load, in particular proxy_http.load? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Mailman 3 Installation Assistance

by Abhilash Raj

On Sun, Apr 1, 2018, at 12:40 PM, brian(a)emwd.com wrote: > Ok I just discovered the docker-compose-mysql.yaml file. I assume I can > just use that file: > > docker-compose-mysql -d Yes, you can try using this and update the variables in the compose file similar to postgres. If you update the environment variables to point to your local installation, you should be able to use just that instead of the the docker-version. You'd have to manually change the docker-compose.yaml file to use the on-host database though. > > Is that correct? Do I need to remove the previous docker installation > that I did using docker-compose.yaml? > > Sorry for being so needy. This is the 2nd time I am installing an > application using Docker. The first one was Discourse which had really > good installation instructions. I am struggling with the instructions > for Mailman 3 via Docker. I am happy to update the docs to be more friendly and useful if you can point out the specifics of what isn't clear. Please feel free to open an issue on Github if you feel something isn't clear :) -- Abhilash Raj maxking(a)asynchronous.in

7 years

[MM3-users] Re: Issues with @gmail.com addresses

by Danil Smirnov

Hi Mohsen, Do you send via AWS SES? You might find some useful logs in there rather than in your local MTA. Danil Smirnov On Tue, Sep 5, 2023 at 11:00 PM Mohsen Masoudfar <mmasoudf(a)aaas.org> wrote: > Hi, > > since 8/1/2023 I get complains from users with @gmail.com addresses, that > they are not getting any emails. > I checked the logs and I see that the emails are going out: > > to=<xxxx(a)gmail.com>, relay=email-smtp.us-east-1.amazonaws.com[35.169.171.20]:587, > delay=0.46, delays=0.03/0.06/0.13/0.24, dsn=2.0.0, status=sent (250 Ok xxx ) > > But it seems the users are getting email delivered to them. > I’ve advised them to check their spam, promotions, and social folders and > to add the list address to their email safe-senders lists, but still no > success. > Is there any way to help this list members? > > Thanks > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to danil(a)smirnov.la >

1 year, 7 months

[MM3-users] Re: Notifying owners of membership changes but not moderators

by Mark Sapiro

On 11/26/24 4:54 PM, Perry Kollmorgen wrote: > > Is there any way to have these only for Owners ? No. Essentially all admin notices are sent to LISTNAME-owner@DOMAIN and that in turn resends to owners and moderators. There are no controls to restrict this to only owners and not moderators, however it doesn't send to those with delivery disabled, so you could do something like this in `mailman shell` ``` $ mailman shell -l LIST_ID Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the LIST_ID mailing list >>> for moderator in m.moderators.members: ... moderator.preferences.delivery_status = DeliveryStatus.by_moderator ... >>> commit() ``` This will not affect the delivery status of the user's role as list member. This is not available in Postorius and also, the moderator can't set the delivery_status for their moderator role either, only for their member role. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 4 weeks

[MM3-users] Re: MAILMAN_HOST_IP_AUTO

by Abhilash Raj

On Tue, Jan 22, 2019, at 9:01 AM, Johannes Winter wrote: > Dear MM3 list, > > while doing some reboot proofing for our mailman setup, I once more ran > into https://github.com/maxking/docker-mailman/issues/133. > May it be that https://github.com/maxking/docker-mailman/pull/143 > hasn't made it yet into the docker image maxking/mailman-web:0.2 which > is the current recommended stable version? I think I messed up and forgot to tag 0.2 in the repo, so I am not sure if that commit was included in 0.2 release. I need to figure out some more automation for the tagged releases. Anyway, I'd recommend that you set your IP address for Mailman Core manually, if you can. That should avoid having that issue. Eventually, there will be no IP addresses and thing, you can see my WIP MR to remove all the hard coded addresses[1]. [1]: https://github.com/maxking/docker-mailman/pull/292 > > Would be real nice (for stability!) to have this feature included. > > Best regards, > > Johannes Winter > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 3 months

[MM3-users] SECRET_KEY is not defined. Aborting.

by Steven Jones

8><--- root@debian-mailman-001:/opt/mailman/docker-mailman# docker run maxking/mailman-web:0.2 SECRET_KEY is not defined. Aborting. root@debian-mailman-001:/opt/mailman/docker-mailman# 8><--- I keep getting this, I have attempted to set a SECRET_KEY in /opt/mailman/web/settings_local.py and, docker-compose.yaml No joy, can you tell me how I set this variable? or where I get it from? is it pre-generated somewhere? your documentation just does not explain this that I can find, despite even a lot of time googling. PS I have assumed the hyprekitty key is something I set myself, just like a manual password sort of thing, again there is no explanation I can find that explains how to do this properly either. Can this documentation be improved please. To get anywhere at all I finally found this, https://xiaoxing.us/2018/01/01/deploy-mailman-3-on-aws-using-docker/ So I have core running OK I think, ====== root@debian-mailman-001:/opt/mailman/docker-mailman# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 99f434ef3664 maxking/mailman-core:0.2 "docker-entrypoint.s…" 2 hours ago Up About an hour 8001/tcp, 8024/tcp mailman-core 4c0e165d3a90 postgres:9.6-alpine "docker-entrypoint.s…" 2 hours ago Up About an hour 5432/tcp dockermailman_database_1 root@debian-mailman-001:/opt/mailman/docker-mailman# ====== regards Steven

5 years, 9 months

[MM3-users] Re: django 2.2.5 which is incompatible

by Abhilash Raj

On Mon, Sep 9, 2019, at 6:59 PM, Mark Dale wrote: > Hi, > > On Debian, in the process of setting up Mailman 3.3.0 I'm getting: > > $ pip3 install postorius > ... > django-mailman3 1.3.0 has requirement Django<2.2,>=1.11, but you'll have > django 2.2.5 which is incompatible. > ... > Successfully installed Django-2.2.5 ... This shouldn't be a problem and will be fixed in a future release. It is compatible with 2.2.5, but due to lack of a proper dependency resolution in pip, we don't end up with right version of a dependency. You can ignore this, for now. > > > > Which may or may not be causing a later error when creating superuser: > > ImportError: No module named django.core.management > What command did you run to do this? The error makes me feel you haven't activated either the virtualenv or you haven't installed things correctly. > > Am I missing the obvious somewhere? > > Thanks, > Mark > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years, 7 months

[MM3-users] Handling of SPAM mails in mailman3 - Check for X-Spam Header

by Torge Riedel

Hi, we migrated successfully to mailman3 so far. I have some questions regarding handling of SPAM mails in mailman, this is the second question: Such SPAM mails are currently hold for moderation with reason "not from a list member". Is there no check for the "X-Spam: Yes" header or is this check done later? I would prefer that a check for such a header is done first and is reported as the reason. Which is IMHO a very important information. Or maybe show "This is detected as SPAM" in big bold red letters in a new column in the list of mails to moderate for such a mail. Maybe there is more eye-candy solution for it. Sometimes mail accounts of allowed users are hacked and we do not want spread SPAM accidently. On my setup all mails are checked by rspamd before local delivery and I see that the "X-Spam" header is set for such mails. So even mails from allowed members with header "X-Spam: Yes" should be hold for moderation. Maybe this is already the case, did not gave it a try yet. Best regards Torge

5 years, 3 months

[MM3-users] Moderation emails

by peter＠chubb.wattle.id.au

Hi Folks, Whenever a non-member posts to a members-only list, the owners (because I haven't set any moderators) get a 3-part MIME message, from the xxx-owner email address. The first part is the template from .../mailman/templates/en/list:admin:action:post.txt The second part is a message/rfc822 copy of the held message. The third part is another message/rfc822 part that says, If you reply to this message, keeping the Subject: header intact, Mailman will discard the held message. Do this if the message is spam. If you reply to this message and include an Approved: header with the list password in it, the message will be approved for posting to the list. The Approved: header can also appear in the first line of the body of the reply. This is really confusing, as replying to the whole message will go to the '-owner' not the '-request' address, which will neither discard nor authorise the message, and will not contain the subject: heading from the encapsulated message. Is there any easy way, either to turn off generation of the third message, or make it so that acting on the message (hitting reply in your email client) will actually discard the message? Peter C

4 years, 1 month

[MM3-users] Re: is there a mailman command/setting to periodically clean archives?

by Mark Sapiro

On 12/29/21 3:58 PM, William Oliver wrote: > > I'd like to delete all my archives that are more than a certain age, > e.g. more than a week old. I can easily do that with a cron job, > deleting old files in > > > /opt/mailman/mm/var/archives/prototype/testlist(a)example.com/* > > which is, as far as I can see the only place archive emails live. Those are emails archived in the prototype archiver. That's all the prototype archiver does - store the mail there. The HyperKitty archived emails are stored in the mailmanweb database in the hyperkitty_email table. Attachments are in the hyperkitty_attachment table and other tables are also involved. > However... I was wondering if there was some mailman command or config > variable that would accomplish this without using cron. The cron will work for the prototype archives, but it's probably easier to just disable the prototype archiver. For HyperKitty, see the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Import old mails into list

by Stephen J. Turnbull

franklin(a)slat.org writes: > Import list data (from 2.1): > https://docs.mailman3.org/projects/mailman/en/release-3.0/src/mailman/comma… You should have a "mailman" command, with "mailman import21 -h" giving brief usage instructions. I gather this succeeded in importing your list configuration(s). > How do I import an archive into a new mailing list: > https://wiki.list.org/DOC/How%20do%20I%20import%20an%20archive%20into%20a%2… > The second is very old, written in 2007, and now I even can't find > bin/arch commands. Mailman 3's initial public release was at the end of April 2015. Any information dated before that is likely dangerously wrong for recent Mailman 3. > And when I tried `django-admin hyperkitty_import` it even told me > "Unknown command: 'hyperkitty_import'". django-admin is somewhat finicky because it is intended to serve multiple Django instances, applications, and projects on the same host. It depends on where you start it and which settings.py you feed it. On Debian, you should install the "mailman3-web" package, which provides the "mailman-web" command which integrates django-admin functions from HyperKitty, Postorius, and django-mailman3. "mailman-web help hyperkitty_import" should tell you how to import your archives. Steve

1 year, 9 months

[MM3-users] Re: Deleting moderation requests in database

by Joachim Schrod

Mark Sapiro writes: > On 12/2/24 6:40 PM, Joachim Schrod wrote: > > > > First: I assume that all information about moderation is in the > > database mailman3. If that's not the case, please tell me. > > > It is the case, but it's easier to use mailman shell. Something like > ``` > $ mailman shell -l test.example.com > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > The variable 'm' is the test.example.com mailing list > >>> pendingsdb = getUtility(IPendings) > >>> for token, data in pendingsdb.find(m): > ... if data.get('token_owner') == 'moderator': > ... if data['type'] == 'unsubscription': > ... pendingsdb.confirm(token, expunge=True) > ... > >>> commit() > ``` Thanks a lot, worked like a charm! Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Joachim Schrod Email: joachim(a)schrod.org Roedermark, Germany ``How do we persuade new users that spreading fonts across the page like peanut butter across hot toast is not necessarily the route to typographic excellence?'' -- Peter Flynn

4 months, 2 weeks

[MM3-users] Re: Moderating posts via email

by Dmitry Makovey

On 10/26/2017 02:46 PM, Abhilash Raj wrote: > On Thu, Oct 26, 2017, at 02:21 PM, Dmitry Makovey wrote: >> Hi, >> >> we are trying to figure out what is that we're doing wrong as we can't >> use instructions that mailman sends with information on held messages as >> referenced in: >> https://gitlab.com/mailman/mailman/blob/master/src/mailman/chains/hold.py#L… >> >> In particular - replying to the message with "Approved: listpassword" we >> were not able to approve any message. > > Did you add it to the body/subject of the email? We have added "Approved: listpassword" to the body of the message as a first line as advised. > AFAIK, Mailman looks for "Approed" header to approve the held messages. We did not try to inject "Approved: listpassword" header into the message body itself though. And if that is the way it is supposed to function I'm questioning whether average user would be able to operate it. If that function is broken - since message is hardcoded into the chains/hold.py - how can I change the message without code modification? -- Sr System and DevOps Engineer SoM IRT

7 years, 5 months

[MM3-users] Installation Wooes

by Samir Faci

A few questions about an Ubuntu install. I managed to add my domain to hyperkitty, created a new list and now i'm getting this behavior: ``` May 02 07:47:24 2020 (55358) deque: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman/app/workflow.py", line 69, in __next__ return step() File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", line 331, in _step_send_confirmation self._set_token(TokenOwner.subscriber) File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", line 157, in _set_token self.token = pendings.add(pendable, timedelta(days=3650)) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3/dist-packages/mailman/model/pending.py", line 91, in add token = token_factory.new() File "/usr/lib/python3/dist-packages/mailman/utilities/uid.py", line 79, in new return self._next_unpredictable_id() File "/usr/lib/python3/dist-packages/mailman/utilities/uid.py", line 155, in _next_unpredictable_id x = random.random() + right_now % 1.0 + time.clock() % 1.0 AttributeError: module 'time' has no attribute 'clock' ``` I'm on python 3.8.2 Question #2. I'm setting up mailman 3 on sqlite for simplicity's sake. Do people find the performance of mysql / postgres worth the upgrade? 2B. Is there a migration path if I want to switch to mysql at a later date? -- Thank you Samir Faci https://keybase.io/csgeek

4 years, 11 months

[MM3-users] New release candidates for Postorius and Hyperkitty

by Abhilash Raj

Hey Everyone, Happy new year to everyone! I am pleased to announce new release candidates for Postorius and Hyperkitty along with new releases for Mailmanclient and Django-mailman3! These include both new features and bug fixes. Complete change log for each components: Postorius 1.3.4rc1: https://docs.mailman3.org/projects/postorius/en/latest/news.html Hyperkitty 1.3.4rc1 : https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html Mailmanclient 3.3.2.: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… Django-mailman3 1.3.5: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst These releases require Mailman Core 3.3.2 and Python 3.6+. Since these are pre-releases, you can install them using: $ pip install --pre --upgrade postorius hyperkitty Or you can also specify the exact versions: $ pip install --upgrade 'postorius==1.3.4rc1' 'hyperkitty==1.3.4rc1' Unless there is a release-blocker bug, stable versions for Postorius and Hyperkitty will be released in 2 weeks time. If you can test these releases, we encourage you to report any bugs to us on Gitlab. If you'd like to help out with translations for some of the new strings in your native language, the documentation is available here[1] on how to do that. [1]: https://docs.mailman3.org/en/latest/translation.html -- thanks, Abhilash Raj (maxking) On behalf of GNU Mailman Team

4 years, 3 months

[MM3-users] Emails about moderation are sent to list owners, want them sent to moderators instead

by Elias Rudberg

Hello, This is about GNU Mailman 3.3.3 (Tom Sawyer). For each list there are both "owners" and "moderators". As I understand it, the idea is that owners have the power to change configuration for the list, while moderators have more limited power, they can only moderate but not change configuration. When an email is sent from a non-member to a list that requires moderation in such a case, an email with subject like "[listname] post from [sender] requires approval" is sent to the list owners. I would like those emails to be sent to moderators instead. The reason why I want it to work that way is that list owners sometimes want to delegate the work of moderating to the moderators. List owners then want to keep the power to change list configuration, but they do not want to be bothered by individual moderation emails. Is there a way to configure mailman3 to make it send moderation emails to moderators instead of owners? Or, have I misunderstood the purpose of "owners" and "moderators"? If so, I would be grateful if someone could explain. / Elias

2 years, 9 months

[MM3-users] Re: Help with fresh debian install

by Mark Sapiro

On 10/3/19 5:17 PM, Mark Dadgar wrote: > > I brought up a fresh install of Mailman3 via the current Debian package alongside my current 2.1 setup (installed and updated from source since 2002) on Ubuntu 18.04 LTS. > > Importing lists from 2.1 has been a real problem. > > I am trying to import a list with no archives to keep it simple while I prove out the process. If I run the mailman import21 comment as my user, I get the following errors: > > — > mark@mail:/tmp$ mailman import21 announce(a)pdc-racing.net ./announce-config.pck > Traceback (most recent call last): > File "/usr/bin/mailman", line 11, in <module> > load_entry_point('mailman==3.1.1', 'console_scripts', 'mailman')() > File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 94, in main > initialize(config_path) > File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 189, in initialize > initialize_2(propagate_logs=propagate_logs) > File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 152, in initialize_2 > mailman.core.logging.initialize(propagate_logs) > File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 157, in initialize > _init_logger(propagate, sub_name, log, logger_config) > File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 110, in _init_logger > handler = ReopenableFileHandler(sub_name, path_abs) > File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 50, in __init__ > self._stream = self._open() > File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 53, in _open > return codecs.open(self.filename, 'a', 'utf-8') > File "/usr/lib/python3.6/codecs.py", line 897, in open > file = builtins.open(filename, mode, buffering) > PermissionError: [Errno 13] Permission denied: '/var/log/mailman3/mailman.log' This is the issue. I don't know how the Debian packages do this, but I recommend having a 'mailman' user that owns everything and running commands as that user. > Error in atexit._run_exitfuncs: > Traceback (most recent call last): > File "/usr/lib/python3.6/logging/__init__.py", line 1945, in shutdown > h.flush() > File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 56, in flush > if self._stream: > AttributeError: 'ReopenableFileHandler' object has no attribute '_stream' This is due to the prior permissions error. > If I run it as root, it runs for a long time but spews a HUGE stream of these errors to /var/log/mailman3/mailman.log: If there are a lot of members to add, that can take a long time. The current version of import21 has a progress thermometer for this. > — > Oct 03 17:08:48 2019 (19118) Skipping and preserving unparseable message: 1570147727.3029191+80f1cc4d18f54868ad6162e8e41e52567185e983 > Oct 03 17:08:49 2019 (19118) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147728.618866+174175d39c301feab4ebb2aac0a51226334fa54c.pck' > Oct 03 17:08:49 2019 (19118) Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 156, in _one_iteration > msg, msgdata = self.switchboard.dequeue(filebase) > File "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 150, in dequeue > with open(filename, 'rb') as fp: > PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147728.618866+174175d39c301feab4ebb2aac0a51226334fa54c.pck' First, I don't know what these messages are. Normally import21 doesn't send any mail. I'm guessing it's trying to send 'you are subscribed' notices to the users, but it shouldn't be doing this. All these files should wind up in Mailman's var/queue/bad/ directory with a .psv extension. You should be able to examine them with the 'mailman qfile' command. Whatever they are, the error comes from virgin runner so import21 should have actually succeeded. Did it import the list? > It also dumps some mail footer templates into the template directory that are owned by root, which seems … incorrect? It makes a weak effort at converting the list's msg_footer and digest_footer into MM 3 templates in templates/list/<list-id>/<list-lang>/. These are owned by root in your case because you ran import21 as root. > Any thoughts on what’s going wrong here? It looks like this may be an issue with the Debian package, at least the sending of messages part. As for the rest, the Debian package should install stuff as a Mailman user, perhaps 'mailman' or 'list', and you should be running all commands as that user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Add old email address

by Quanah Gibson-Mount

--On Saturday, March 14, 2020 7:02 PM +0900 "Stephen J. Turnbull" <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Quanah Gibson-Mount writes: > > > By adding addresses I no longer have to my account and marking them > > verified, I can easily associate nearly 20 years of postings that > > I've made with myself when I look at the archives. > > That's a *great* point! And it generalizes to other authors, not just > "self". > > Hm. I don't think HyperKitty (and definitely not Pipermail for > Mailman 2) works that way, though. I'm pretty sure "authors" are > From: addresses, not the corresponding users. I'll have to look at > it. I was able to find my posts associated with myself doing this, going back to 2006 (When we switched to mailman2). ;) I.e., from my account drop down, I select "Posting activity", then go to page 651 (the last page), and the last item is: <https://lists.openldap.org/hyperkitty/list/openldap-software@openldap.org/m…> So yeah, it works quite well! ;) Regards, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

5 years, 1 month

[MM3-users] Re: Recommended way to backup a mailman3 instance

by Abhilash Raj

On Sun, Apr 12, 2020, at 7:23 AM, Gilles Filippini wrote: > Gilles Filippini a écrit le 10/04/2020 à 10:39 : > > Hi, > > > > I'd like to schedule periodic backup for our mailman3 instance. Are > > there recommended ways for doing this without down times? > > I should have precised that our mailman3 instance is dockerized. Then, > as I understand it, these backups should be sufficient: > * MailmanCore's volume (/opt/mailman/var folder) /opt/mailman/core/var > * Database dump > > Anything else? No, that should be enough. Mailman-web is fairly stateless and stores everything except the settings and logs in the database. If you have settings version controlled then you don't need anything else. There is also fulltext_index, but that doesn't need to be backed up because it can be easy re-generated with a single django-admin command. Mailman core's entire state is in the var/ directory above. > > Thanks, > > _g. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Mark Sapiro

On 6/16/20 5:03 PM, kelly.close(a)lrewater.com wrote: > I resolved this myself with a search that turned up a 2018 post from Mark that suggested typing "mailman aliases" to create the hash/alias/lookup table/file things in /var/lib/mailman3/data (that's where they are on Ubuntu 18.04). I looked in that folder and sure enough it was empty so I typed "sudo mailman aliases" which did indeed create the 4 things that needed to be there: > postfix_domans > postfix_domains.db > postfix_lmtp > postfix_lmtp.db > > But, they were owned by root:root and everything else under that /ver/lib/mailman3 folder is owned by "list" so I took a guess changed the ownership on the 4 files to list:list. Because that's how you ran it. Run sudo -u list mailman aliases. > Seems to have worked! I was perplexed about why I had to do this though because these were created automatically last time I did this, but I figured that out too. Current `mailman start` should create the aliases. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 10/23/20 1:04 PM, Mark Sapiro wrote: > On 10/23/20 9:37 AM, Brian Carpenter wrote: >> How would a person already be a core user outside of a registration with >> Affinity? Via a list subscription or the import21 script? > > Yes, or even just by sending a post to a list as a nonmember. > > Everyone who is or has been a member, non-member, owner or moderator of > a list has a user and one or more address records in Mailman core. And those records are kept in the database? Is that correct? >> I do want to apologize for my tone Mark. I was wrong in the way I communicated. > > Apology accepted. I understand that it can be frustrating to be > dependent on something you don't control and that this can sometimes > lead to "anomalous" behavior. > > Here's a take on this that is intended to be humorous, but is actually > quite frightening. https://xkcd.com/2347/ I actually came across that cartoon months ago and that one person reminded me of you. So the fact that you are sharing that cartoon is ironic and very funny! -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 6 months

[MM3-users] Re: Member Issue Discovered

by Apollinaris Schöll

If this has been implemented already then that’s good. I have not tested with latest. Does this also happen when a user unsubscribes or a list admin unsubscribes? > On Oct 28, 2020, at 1:29 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 10/28/20 11:11 AM, Apollinaris Schöll wrote: >> >> Most important is to offer an UI to completely delete users for subscribers and list admins. Currently delete account shows this message "Are you sure you want to delete your account? This will remove your account along with all your subscriptions.” >> This is not true and needs to be done. > > > Why do you think it's not true? With current Mailman from the HEADs of > the GitLab branches, the only thing not removed is posts from the > archives. The Django account and the Mailman core user and address > records are all removed. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 5 months

[MM3-users] hyperkitty installation: Unclear instructions

by Johannes Rohr

Dear all, I just installed mailman and mailman3-web in virtualenv as described in https://docs.mailman3.org/en/latest/install/virtualenv.html Next I moved on to set up hyperkitty as described in https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html. I got confused by the instructions: "Install the code Install the HyperKitty package and its dependencies with the following commands: sudo python setup.py install" Obviously this is a python script in a package that has to be downloaded from somewhere. Why? Doesn't the command pip install mailman-web mailman-hyperkitty already do the job? Apparently, there is a second way of installing hyperkitty, using virtualenv, where you have to check out the code from gitlab and install from there. However, this still doesn't look right, as hyperkitty apparently can also be installed through pip install hyperkitty But then, hyperkitty seems to be already have been pulled in by mailman-web, looking at its dependencies. If that's the case, then neither the instructions at https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html nor those at https://docs.mailman3.org/projects/hyperkitty/en/latest/development.html are correct. Can someone enlighten me on what the canonical way is of installing and setting it up in virtualenv? Thanks a lot in advance! Johannes

2 years, 3 months

[MM3-users] Re: log rotation in maxking-docker-version

by Stephen J. Turnbull

Jens Günther writes: > Question in general: shall I put my questions regarding > docker-version on Github or is it ok on this list? Executive summary: docker issues are specialized, just post here. Details for the curious: Issues that only affect the docker version are going to be based on (1) network connectivity issues between the containers and (2) stuff like logging configuration where files are stored on the physical host, which has to do log rotation, but mailman lives in a container, so when logrotate does its thing it has to jump through a few extra hoops to tell mailman to reopen its log streams. Those are probably best addressed to the docker-version issue tracker on GitHub. > e.g.: now realised, that all requests are doubled, all errors, all > GET-requests ... this cannot be right and probably some > misconfiguration :-( would love to dig deeper and just ask myself > where. I think it's in settings.py there's a log stream that both has a file handler and is set to propagate to root, which goes to the same file. Turn off the propagation. Find the stanza by searching for "LOGGING" if I remember correctly.

1 year, 7 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Ok, I could setup env with python3 and env2 with python 2.7 I visited http://192.168.1.42:8000 in my browser and I could not see the web UI. Should I install WSGI server?? doing: pip3 install uwsgi ??? Thanks El vie., 21 jul. 2017 a las 15:03, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 12:44 PM, Rafael Mora wrote: > > I did this: > > > > (env) [mailman@localhost mailman-suite_project]$ pip install Django > > Requirement already satisfied: Django in > > /var/lib/mailman/env/lib/python3.6/site-packages > > Requirement already satisfied: pytz in > > /var/lib/mailman/env/lib/python3.6/site-packages (from Django) > > > > > > Does Django is already installed?? with python3.6 ??? > > > Your 'env' vitrualenv is a Python 3 virtualenv. You need this for > Mailman core, but Django and mailman-suite are Python 2. They need to be > installed and run in a Python 2 virtualenv. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 9 months

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by brian＠emwd.com

Ok. I went ahead and did a server wipe and tried again. This time I went with nginx as the webserver. Everything worked fine but I got the dreaded hyperkitty "auth required" error that Kelly mentioned in her walkthrough. However no matter how hard I tried to make sure the keys matched in mailman-hyperkitty.cfg and mailman-web.py, I kept getting the same error. However I noticed that a key was already there originally in mailman-web.py in the MAILMAN_ARCHIVER_KEY setting. So I decided to use that in mailman-hyperkitty.cfg and viola, it worked! Also Kelly are you sure this is correct: "There are two configuration files that have a key in them that must match for Hyperhitty to authorize and be able to store archives (the paths should be as follows): /etc/mailman3/mailman-hyperkitty.cfg (set the api_key without any quotes) /etc/mailman3/mailman-web.py (set the ‘SECRET_KEY’ - include single quotes around the key)" It was the MAILMAN_ARCHIVER_KEY that I needed to make sure it was being matched by the API key in mailman-hyperkitty.cfg. I believe the SECRET_KEY setting has nothing to do with the auth errors that Hyperkitty was displaying. Brian

6 years

[MM3-users] Google auth issue redirect_uri_mismatch

by Ugnius S

Hi. New question about configuration, maybe somebody has experience and know what I should change it. I have tried to implement Google authorisation. I have created Google credentials keys and successfully added using Django admin page. I use UWSGI proxy for apache setup like "ProxyPass / http://127.0.0.1:8002", UWSGI runs on 0.0.0.0:8002. (So Appache from external address redirects to internal) What happens when I try Google auth... If I set Authorised redirect URIs: http://lists.example.com/accounts/google/login/callback/ , Google gives me error 400 Error: redirect_uri_mismatch and requests for: http://127.0.0.1:8002/accounts/google/login/callback/ If I set that requested address to Google, then Google authorises me, but and after authorisation redirects to http://127.0.0.1:8002/accounts/google....../.... (very long line) Of course this internal address does not open, but... If I just manually replace part of address just: http://127.0.0.1:8002 replace to https://lists.example.com/.../...(long line) this makes me get in as authorised user to the page. How to make django to send external request to Google? Because Google should not point back to internal address... This seems simple, but I do not find what I should change in the configuration: Apache or Django or uwsgi.ini I hope anybody of You have experience and made it to run. Kind regards Ugnius

5 years, 7 months

[MM3-users] Re: Performance of member listing [was: How to remove a nonmember...]

by Abhilash Raj

On Sat, Apr 18, 2020, at 8:25 AM, skenny(a)scss.tcd.ie wrote: > Well, it is quite possible that something is seriously wrong with my > configuration. > > The database backend is Postgres - not something I configured. It is > specified in my docker-compose file, which in turn is based on the > compose files at https://github.com/maxking/docker-mailman. > > (At one point I thought maybe the virtual machine I'm running on was > under-resourced. I've since doubled memory and the number of CPUs but > that hasn't really improved things.) > > I'm wondering where to go next - try tweaking the Postgres config, > switch to SQLlite .... How many entries do you have in your member table? You can just use psql command in the postgres container to dump a count of all the rows? > > Thanks for giving time to helping me with this, much appreciated. > > Stephen > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years

[MM3-users] Re: migration

by Mark Sapiro

On 7/30/21 12:06 PM, Dave McGuire wrote: > > Is there a way that I can "dump" the configuration from an existing > mailman3 server, and "import" it into a new instance? I'd really like > to avoid re-doing all of the configuration, etc, as there are quite a > few lists and everything is set up pretty much the way I want it. If you use the same database manager it should be no problem to get a dump of the existing Mailman database to load into the new instance, or if these are on the same server, just point the new instance to the existing database. In either case, the database should be loaded and the Django commands `migrate`, collectstatic`, `compress` and `compilemessages` run[1] before starting Mailman services. Mailman core will run any necessary updates to its database upon startup. You may also need to rebuild the HyperKitty search index with the `update_index` Django command, but you may be able to use the existing one if the search engine is the same. [1] See https://docs.mailman3.org/en/latest/install/virtualenv.html?highlight=colle… et seq. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: (venv) mailman-web migrate (as explained) fails with "django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE"

by Odhiambo Washington

On Thu, Oct 19, 2023 at 3:02 PM Wikinaut <mail(a)tgries.de> wrote: > I used this > x = list(MIDDLEWARE) > x.insert(0, 'allauth.account.middleware.AccountMiddleware') > MIDDLEWARE = x > > but got (running mysql! with all the needed settings) > SystemError: initialization of _psycopg raised unreported exception > > arrrgh > [snip] > File > "/opt/mailman/venv/lib/python3.11/site-packages/psycopg2/__init__.py", line > 51, in <module> > from psycopg2._psycopg import ( # noqa > SystemError: initialization of _psycopg raised unreported exception > If you say you are using MySQL, then I don't understand why you are having issues with psycopg as this has nothing to do with MySQL, but PostgreSQL. Which is which? Maybe you need to relax a bit, then start over again? Can we see what you have in /etc/mailman3/mailman.cfg and /etc/mailman3/settings.py? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 6 months

[MM3-users] Re: Another interesting error...

by Darren Smith

Very good, I'll give that a try and let you know! On Mon, Apr 23, 2018 at 3:37 PM, Simon Hanna <simon(a)hannaweb.eu> wrote: > On 04/23/2018 11:29 PM, Darren Smith wrote: > > "It's in Mailman's database in the 'message' table." > > > > I can see the message table - is there a way to see where it is marked as > > "held"? All I'm seeing in that table is id, message_id, message_id_hash, > > and path. > > > > I'm wanting to be able to query for held messages for a given mailing > list, > > as there are currently over 98,000 entries in the message table. > This should be possible using the mailman shell > http://mailman.readthedocs.io/en/latest/src/mailman/model/ > docs/requests.html?highlight=held > > I haven't used the shell extensively and didn't read the whole docs, but > it looks like it's the right place to look. If you can't do that using > the shell, I'd say it's worth a bug report :-) > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

7 years

[MM3-users] Re: Include receipant address as a variable

by Mark Sapiro

On 6/4/22 09:22, chucka(a)blackforest-co.com wrote: > Thanks for the quick reply - I'm going to need a bit of schooling. I've looked at the page you point to and ... I'm lost - do I need to create a NL template? Can you give an example? &lt a href=https://mysite.com/my.pdf? &gt CLICK HERE ... The bad news is list headers and footers are plain text so HTML tags don't work. The good news is that many if not most MUAs will render things that look like URLs as clickable links. So, if you create a list:member:regular:header or list:member:regular:footer footer template that contains a line like ``` Go to https://mysite.com/my.pdf?$user_email to ... ``` That will replace the $use_email part with the recipient's lower cased email address. If you want the case-preserved email address, use `$user_delivered_to` instead of `$user_email`. For this to work, the list's Settings -> Alter Messages -> Personalize setting must be `individualize` or `full`. Also see https://wiki.list.org/x/4030707 for some caveats. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Sun, Dec 25, 2022 at 3:47 PM Stephen J. Turnbull < stephenjturnbull(a)gmail.com> wrote: > Mark Sapiro writes: > > > You don't need all of those. ^postorius/ and ^mailman3/ are two > > different ways to access Postorius, and ^hyperkitty/ and ^archives/ are > > two different ways to access HypereKitty. You only need one of each, > > That's true from "outside", but there are internal links as well. For > example, in Postorius top page, the link to HyperKitty is .../archives. > I guess it's a good idea to grep the templates to see which URLS are > used. > > > > Now my question is about what could be adding the /mailman3. Is it > possible > > > that I installed something out of the ordinary? > > Besides mod_wsgi as Mark suggests and the uwsgi configuration, the > only thing I can think of is an Apache rewrite rule. It's not in the > Postorius and HyperKitty templates. > And I do not have any rewrite rules in my VHOST config: https://pastebin.ubuntu.com/p/9MRMJST9zZ/ -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 3 months

[MM3-users] Re: No option 'postmap_command' in section: 'postfix'

by Mark Sapiro

On 1/30/23 10:12, Odhiambo Washington wrote: > > So, since the creation of that file is prominent in the doco, maybe a note > can be added to that effect? I'm looking at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… and my thought is at the paragraph Regular Expression tables remove the additional dependency of having postmap command available to Mailman. If you want to use regexp or Regular Expression tables, then add the following to Postfix’s main.cf file: add another section header Regular Expression Tables ------------------------- and change that text to Regular Expression tables are less efficient than hash tables, but they remove the additional dependency of having ``postmap`` command available to Mailman. If you want to use ``regexp`` or Regular Expression tables, then add the following to Postfix's ``main.cf`` file My thought is adding the section header makes it more clear that everything down to the Postfix + Dovecot section is for Regular Expression Tables and adding the `less efficient` phrasing notes the down side. What do you think? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: Remove ALL Members button - was: Re: Setting base_url for the domain to use it in the templates.

by Odhiambo Washington

On Thu, Jul 11, 2024 at 6:28 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/10/24 10:46 PM, Odhiambo Washington via Mailman-users wrote: > > > > I find the unsubscribe_all button quite scary! I have never used it > though, > > so I am not quite sure about its behavior. What scares me > > is the possibility of clicking it and then in one fell swoop you've > removed > > ALL the members without a "confirmation". > > See the thread at > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > and the issue at https://gitlab.com/mailman/postorius/-/issues/545. > > Bottom line - there is a confirmation. Try it, perhaps on a test list if > you're really scared. > Will do that test :) -- 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]

9 months, 1 week

[MM3-users] Re: Prototype import [was: Re: Setup Question: Disk-Layout (Migrating from Mailman 2.1)]

by Mihai Moldovan

* On 4/18/25 04:23, Mark Sapiro wrote: > On 4/17/25 11:35 AM, Mihai Moldovan wrote: >> >> New incoming messages will have the correct data, of course, but >> imported ones wouldn't, so I'll have to use a more sophisticated >> approach to handle them, probably by going through mailman's email >> wrapper, figuring out how to generate a msgdata object for a message, >> using RFC2369.process and maybe more. > > Here's an example script. You need to run this with > /opt/mailman/mm/venv/bin/python to get access to the mailman imports. > ``` > from mailbox import Maildir, mbox > from mailman.email.message import Message > from mailman.handlers.rfc2369 import process > from mailman.interfaces.listmanager import IListManager > from mailman.utilities.email import add_message_hash > from zope.component import getUtility > mb = mbox('path/to/mbox', factory=Message, create=False) > md = Maildir('path/to/maildir', create=False) > mlist = getUtility(IListManager).get_by_list_id('your.list.id') > for msg in mb: > add_message_hash(msg) > process(mlist, msg, {}) > md.add(msg) > mb.close() > md.close() > ``` Thank you. Unfortunately, I'm having a hard time getting this to work correctly. My current approach is (which is modified from yours, for instance to use Prototype.archive_message() instead of writing directly to a Maildir): ```py import copy import sys from mailbox import mbox from mailman.archiving.prototype import Prototype from mailman.core import initialize from mailman.email.message import Message from mailman.handlers.rfc_2369 import process from mailman.interfaces.listmanager import IListManager from mailman.interfaces.mailinglist import IMailingList from mailman.utilities.email import add_message_hash from zope.component import getUtility initialize.initialize() if (len(sys.argv) < 3): print('Usage: {0} <list-id> <mbox-file>'.format(sys.argv[0]), file=sys.stderr) exit(1) mb = mbox(sys.argv[2], factory=Message, create=False) mlist = getUtility(IListManager).get_by_list_id(sys.argv[1]) for msg in mb: try: add_message_hash(msg) process(mlist, msg {}) Prototype.archive_message(mlist, msg) except Exception as e: print("Error when adding {0}: {1}".format(msg['message-id'], str(e)), file=sys.stderr) mb.close() ``` This returns "Error when adding None: '_PartialFile' object has no attribute 'header_max_count'" for each message. This, including getting None for the Message-ID, stumped me and I got on to debugging this. Indeed, even something as simple as ```py for msg in mb: print(type(msg)) print(msg['message-id']) print(msg) exit(0) ``` results in getting a None for the Message-ID and a stack trace: <class 'mailman.email.message.Message'> None Traceback (most recent call last): File "/root/mailman3/prototype-import.py", line 29, in <module> print(msg) File "/usr/lib/python3.12/email/message.py", line 165, in __str__ return self.as_string() ^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman/email/message.py", line 55, in as_string value = email.message.Message.as_string(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/email/message.py", line 188, in as_string g.flatten(self, unixfrom=unixfrom) File "/usr/lib/python3.12/email/generator.py", line 98, in flatten policy = policy.clone(max_line_length=self.maxheaderlen) ^^^^^^^^^^^^ AttributeError: '_PartialFile' object has no attribute 'clone'. Did you mean: 'close'? This eventually led me to realize that passing mailman.email.message.Message as the factory to mbox() internally calls factory(msg), and the base class of Message (email.message.Message) has an __init__ function that takes the policy parameter, so it looks as if it's registering the mailbox message incorrectly as the policy handler, which is totally wrong of course. If I change the call to mb = mbox(sys.argv[2], factory=None, create=False), the output looks more promising, so converting the data to mailman.email.message.Message first seems to have been the wrong idea on my part: ``` <class 'mailbox.mboxMessage'> <mailman.1.1399151409.10314.x2go-i18n(a)lists.x2go.org> Return-Path: <mailman-bounces(a)lists.x2go.org> [...] ``` and indeed, if I let the import actually happen, it works. The imported messages, do have a Message-ID-Hash, but the Archived-At and List-Archive headers are empty (literally <>). Do you have an example message that was archived through Prototype? What are the proper header values for this module? I believe that Archived-At should be the Message-ID-Hash and the List-Archive header contain... well, given that the Prototype archiver is not meant to be publicly available, probably a file:// URL? Mihai

4 days, 10 hours

[MM3-users] Re: List is down - RemovedInDjango30Warning

by Mark Sapiro

On 2/15/21 9:07 PM, Mark Dadgar wrote: > So I did the latest mailman upgrades within my venv (per the instructions got from Brian Carpenter when he installed it for me) to the latest version. I had a strange CPU pegging issue that turned out to be mailman struggling with a malformed message but in the process of debugging that I downgraded to the previous mailman release. > > The resulted in a broken web interface. > > Today, while debugging, I did a pip install --upgrade of all the components as listed in a previous thread. Now none of the mailman3 processes will start. > > Doing a bin/mailman-post-update results in the error message below, which are consistent with the issues I saw earlier when trying to access the web interface. > > Anyone got a solution to this? From the tracebacks it looks like Django is broken. I would suggest starting over with a new venv. I.e., just move /opt/mailman/mm/venv/ aside and create a new venv virtualenv /opt/mailman/mm/venv/ and then activate it and pip install everything. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Mailman Core 3.3.4 is now out

by Abhilash Raj

Hey Everyone, I am pleased to announce that Mailman Core 3.3.4 is now out. Because of incompatibility with the new version of a downstream library (SQLAlchemy), this release add is setting 1.3.x as the max supported version of SQLAlchemy. Even though it comes soon after 3.3.3, it has a lot of bug fixes and new features. Some notable ones are: * Email -join command now supports subscribing as digests with digest=<no|mime|plain> options being honored. * For anonymous lists, Mailman will filter all the headers except a few that can be configured using a new config option. * Mailman can do max_size checks on filtered message rather than original message (which might be larger before being filtered) * Previously deprecated --add, --del and --sync options from `mailman members` command are now removed. Their alternatives are `addmembers`, `delmembers` and `syncmembers` subcommands. * If configured, Mailman will add a report about content filtering. A complete change log is available here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… This release is available via PyPI: https://pypi.org/project/mailman/3.3.4/ You can install or upgrade using: ``` $ pip install --upgrade mailman ``` Thanks to all the contributors who helped with this release! -- On behalf of Mailman Core Team Abhilash Raj

4 years, 1 month

[MM3-users] Re: Permission denied for fulltext_index

by Mark Sapiro

On 11/27/22 00:35, Jan Eden via Mailman-users wrote: > > – but the existing directory /opt/mailman/fulltext_index (and its > contents) are readable and writeable by mailman:mailman: > >> drwxrwxr-x 2 mailman mailman 4096 Nov 27 08:00 fulltext_index/ >> >> -rw-rw-r-- 1 mailman mailman 4473 Nov 27 08:00 _MAIN_65.toc >> -rw-rw-r-- 1 mailman mailman 15456 Nov 27 08:00 MAIN_bc0cs2aohovftat6.seg >> -rw-rw-r-- 1 mailman mailman 15454 Nov 27 06:00 MAIN_brbo8i8edmlz0za4.seg >> -rw-rw-r-- 1 mailman mailman 15462 Nov 27 07:00 MAIN_ewnemc7lsnodd3y7.seg >> -rw-rw-r-- 1 mailman mailman 157324 Nov 27 04:00 MAIN_qag60g1rrumshtc2.seg >> -rw-rw-r-- 1 mailman mailman 15459 Nov 27 05:00 MAIN_w6e0ohurasusy61d.seg >> -rwxrwxr-x 1 mailman mailman 0 Nov 24 16:00 MAIN_WRITELOCK* > > I fail to see where haystack tries (and fails) to create the directory. > FWIW, deleting threads is not a problem. It is uwsgi trying to do this. What user is it running as? Maybe you need to add that user to the `mailman` group. Deleting threads is not an issue, apparently because it doesn't try to update the search index. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Hyperkitty CPU usage

by Alain Kohli

I have run "python manage.py rebuild_index" before, doesn't that do clear_index as well? Apart from that, I run hyperkitty in a docker container and didn't know fulltext_index should be persistent, so that got deleted after every version update for sure. On 4/26/19 10:18 PM, Mark Sapiro wrote: > On 4/26/19 11:14 AM, Alain Kohli wrote: >> I see loads of "A string literal cannot contain NUL (0x00) characters." >> messages, but I haven't found missing messages in the archives yet. Not >> sure how that could be related, though. Apart from that I don't see >> anything unusual. The other jobs (quarter_hourly, hourly, etc.) seem to >> run and finish normally. > > Did you upgrade from a Python 2.7 version of HyperKitty to a Python 3 > version? The Haystack/Whoosh search engine databases are not compatible > between the two and "A string literal cannot contain NUL (0x00) > characters." is the symptom. > > You need to run 'python manage.py clear_index' or just remove all the > files from the directory defined as 'PATH' under HAYSTACK_CONNECTIONS in > your settings file (normally 'fulltext_index' in the same directory that > contains your settings.py. >

5 years, 11 months

[MM3-users] Re: Trying to configure a list (hosted)

by Abhilash Raj

On Sat, Aug 31, 2019, at 6:29 PM, paul(a)arenson.org wrote: > And this post is the other part of my question: > > I actually only want users who register email, username and password. > > It is a discussion list. > > I was told to make it private. > > Therefore, to ONLY show this form: > > https://list.tokyoprogressive.org/accounts/signup/ As I said in the previous response, you can't disable sign ups through the email commands or without signing up. Although, you can set subscription policy in the list's settings to Confirm where all users would have to confirm their subscription using an email sent to them. Optionally, you can also enable moderation where each subscription needs explicit approval too. > > > Hopefully those are my major questions. > > I do not want to make trial and error posts and therefor have an > unprofessional archive, so hopefully someone can answer these two, > hopefully, clear questions. > > Thank you! > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years, 7 months

[MM3-users] Re: Hipperkitty failing to archive messages in a list

by Guillermo Hernandez (Oldno7)

On 6/1/22 19:19, Mark Sapiro wrote: > On 1/6/22 4:25 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> In the last part of your suggestions you wrote: >> >> "I suggest you do >> >> pip install --upgrade hyperkitty mailman-hyperkitty >> >> and ensure it installs hyperkitty 1.3.5 and mailman-hyperkitty 1.2.0" >> >> But this is exactly what made me fall in this mess: > > > Sorry, I was confused. I thought the error message you were seeing was > changed before HyperKitty 1.3.5 was released, but that isn't correct. > > The problem is probably in Apache. See the last 2 posts in the thread > at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > I'll try tomorrow, now I'm a bit slow-head after a hard day (and the collateral effects of the third vaccine). It looks the right way (I have apache running in that server) to solve it. What intrigues me is the fact that I didn't change anything in the apache config or update apache itself. Well, tomorrow will be antoher day. Thanks for the point.

3 years, 3 months

[MM3-users] Re: Gmail problems?

by Andrew Hodgson

Hi. By far and large this is the most admin I have to do with my Mailman lists. I don't know if its we don't send enough traffic or they are using private blacklists, but nearly all the list mail ends up in my junkmail folder using Office365. It’s a similar story for Google as well. I did think some time ago about paying for one of those spam services and sending my outbound mail through it, but the discussion here about using Google's relays not making a difference makes me think its not worth bothering with. In the heyday of my lists in 2020 I was sending over 5000 individual messages a day and didn't have this problem. That has dropped now to maybe a couple of hundred a week and it’s a real issue. Andrew. -----Original Message----- From: Stephen Daniel <swd(a)pobox.com> Sent: Saturday, April 22, 2023 6:25 PM To: Dave McGuire <mcguire(a)neurotica.com> Cc: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Gmail problems? Thanks. My email kinda does originate from their servers, in that my SMTP relay is smtp-relay.gmail.com. For now, explicit whitelisting appears to help, I just have to do a lot of hand holding with each user to get it set up. And, most of the users seem to think this is my problem / my fault / my responsibility to fix. Sigh. On Sat, Apr 22, 2023 at 1:19 PM Dave McGuire <mcguire(a)neurotica.com> wrote: > On 4/22/23 11:02, Stephen Daniel wrote: > > I run a number of small lists for my neighborhood association. The > largest > > of these is ~120 users. Typical volumes are about 2 messages/day. > > > > In the past week or so a number of users who use gmail as their > > email client have complained that list emails have been going to > > spam or "promotions" folders. I've always had 1 or 2 users who had > > trouble receiving mails, but this seems to be a significant > > percentage of all > gmail > > users. > > > > I have DMARC mitigation set to unconditional, and the DMARC action > > set to "Replace From: with list address". > > > > My emails are sent using google workspace as my SMTP relay. > > > > I'm trying to teach my users to whitelist the list domain, but they > > are not, in general, a tech-savvy bunch, so it is slow going. > > > > Anyone else suddenly having trouble with gmail? > > Any suggestions? > > This started a couple of years ago, and it has become much worse > over time. It's not just lists, it's any email that originates from a > server that isn't Google's. Even servers with sterling reputations, > and ones which have gone through the BS of "registering" with Google. > It does nothing. > > It's a not-so-subtle hint that Google wants to handle YOUR mail > too, so they can data-mine it and make even more money. > > By and large, gmail users are blissfully ignorant of this and for > the most part don't seem to care. All they know is they don't see > much spam. You get blank stares when you tell them about this and > explain to them that if they receive a service for free, THEY are the product. > "But it's eeeeaaaaasier!" > > It's disgusting, Google ignores any attempt at communication, and > there doesn't appear that anything can be done. > > -Dave > > -- > Dave McGuire, AK4HZ > New Kensington, PA > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org To > unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/me > ssage/CIC6JI5JRG7UXTBVIHNF4CXBC7IBYZRP/ > > This message sent to swd(a)pobox.com > _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to andrew(a)hodgson.io

2 years

[MM3-users] Re: Docker Installation of Mailman -- The Hyperkitty Chronicles

by brian＠emwd.com

Hi Mark, Merry Christmas (or Happy Holidays!). I have the list settings set to Public archives and hyperkitty checked in the Active archivers box. As for the cron jobs. I am not sure how to change the following to reflect my setup: # This goes in /etc/cron.d/mailman # Replace "apache" by your webserver user ("www-data" on Debian systems) and # set the path to the Django project directory @hourly apache django-admin runjobs hourly --pythonpath /path/to/project --settings settings @daily apache django-admin runjobs daily --pythonpath /path/to/project --settings settings @weekly apache django-admin runjobs weekly --pythonpath /path/to/project --settings settings @monthly apache django-admin runjobs monthly --pythonpath /path/to/project --settings settings @yearly apache django-admin runjobs yearly --pythonpath /path/to/project --settings settings * * * * * apache django-admin runjobs minutely --pythonpath /path/to/project --settings settings 2,17,32,47 * * * * apache django-admin runjobs quarter_hourly --pythonpath /path/to/project --settings settings For instance, I am using nginx not apache. I also do not know what the /path/to/project should be using maxking's setup. I also am not sure how to call django-admin from the command line. I get the following: # django-admin -bash: django-admin: command not found Brian

6 years, 4 months

[MM3-users] Re: Weird response to postings after subscriptions and accounts

by Paul Arenson

Thank you Mark. I appreciate the response. Let me respond in two messages. The first is to confirm the rules for signing off for both types of used: The second is to clarify my problems with the signup procedure and how I might deal with it. (Mostly a very small change on your part and an explanation on my website for my users) 1) So, for both subscribers vi postorius only and hyperkitty users: email to discuss-leave(a)list.tokyoprogressive.org (or discuss-unsubscribe(a)list.tokyoprogressive.org) 2) Only for hyperkitty users, you can login, go to https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… and click the big red unsubscribe button. 3) Also only for hyperkitty users, log in and click the dropdown at the upper right, select Account and click the Delete Account tab or go directly to https://list.tokyoprogressive.org/user-profile/ and click the Delete Account tab or go directly to https://list.tokyoprogressive.org/user-profile/delete (Guessing that #3 will not unsubscribe the person and--if they have already done 1 or 2, failing to do number 3 is not going to be a big problem. Am I right?) Now in the next message my thoughts on the signup procedure and tentative conclusion.

5 years, 7 months

[MM3-users] How to run 'manage.py update_index_one_list' command.

by Frank van den Heuvel

I am importing old archives mbox files from Mailman2. I have fixed the archive mail address to reflect the address of the destination import. These are the steps: 1. sed 's|oldlist@oldexample\.org|testlist@example\.org|g' mbox > mbox.testlist 2. /opt/mailman/mm/bin/django-admin hyperkitty_import --since 01/01/1990 -l testlist(a)example.org mbox.testlist The output of the last command is: Computing thread structure Synchronizing properties with Mailman Warming up cache The full-text search index is not updated for this list. It will not be updated by the 'minutely' incremental update job. \ To update the index for this list, run the 'manage.py update_index_one_list testlist(a)example.org' command. The result is that the e-mail's are imported but not indexed. To finalize this process I am seeking manage.py that will execute the update index command. I am on a Debian 10 with Mailman3 in /opt. locate manage.py returns: /opt/mailman/mm/venv/lib/python3.7/site-packages/django/conf/project_template/manage.py-tpl /opt/mailman/mm/venv/lib/python3.7/site-packages/example_project/manage.py /opt/mailman/mm/venv/lib/python3.7/site-packages/falcon/bench/dj/manage.py None of these python files can execute the needed command. What can I do to get the newly imported posts indexed? Regards, Frank

5 years, 1 month

[MM3-users] Re: Delete Django profiles not signed up to a list

by Brian Carpenter

On 1/1/21 7:41 PM, Andrew Hodgson wrote: > I have noticed recently I have around 2000 bogus sign-ups that have created accounts in Django. Looking through the logs these have come from the Postorius sign-up pages. I checked and email confirmation is required before the accounts are created and the email addresses that have been used do seem like they could respond to these requests. > > I don't want to add captchas to the form right now but is there any way to clean out these users from the database perhaps periodically based on whether the accounts are subscribed to any list? I can't help with this but I want to say a bogus sign up will usually have a first/last name filled with randomly generated upper/lowercase letters eg. HiedfURW FHIUEYde. That was what we saw. I also implemented a server wide block against Russia and that cut bogus signups by 75%! What we did with our Affinity system is to auto-remove all unverified user accounts after 36 hours. You can perhaps put in a feature request for something similar with Postorius/Django on their Gitlab page. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 3 months

[MM3-users] Re: Mailman, etc. upgrade woes and persistent bugs

by Brian Carpenter

On 2/13/21 10:37 AM, Jim Popovitch via Mailman-users wrote: > On Sat, 2021-02-13 at 08:01 -0500, Brian Carpenter wrote: >> Features are not the only thing about a modern UI, UX design plays a >> MAJOR role in the modern UI. Postorius should have at least matched MM2 >> in features in regards to something as important as Member management >> but instead it took a step back into the dark ages. > I'm gonna be a dick and remind you that less than 1 year ago you were > trying to convince me that MM3 was a gift from god and that it was time > for me to jump from MM2 to MM3 because it was sooo easy and such a time > saver.. or something like that. The point being, you yourself just > still aren't happy with MM3. Welcome to the club. I am very happy with MM3 just not with Postorius. MM3 allowed me to come up with my own admin interface. Mailman 2 would never allowed me to do that. So please leave your Mailman 2 bondage and come over to Mailman 3. We have cookies! -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 2 months

[MM3-users] Re: Cannot request password reset: "The e-mail address is not assigned to any user account"

by Mark Sapiro

On 1/26/22 22:21, dave--- via Mailman-users wrote: > > Using the web API, I have created several mailing lists and I have added members to these lists also using the web API (most relevant: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) specifying that each member is already pre_verified, pre_confirmed, and pre_approved. The lists themselves seem to be working fine. > > The problem is when our staff try to reset their password (through Postorious) to get access and do moderation tasks. The error message "The e-mail address is not assigned to any user account" displays no matter which email address I enter (except the one from MAILMAN_ADMIN_USER which works). The password reset is for a Django user, which is distinct from a Mailman user. The users you added via the web API are Mailman users, but in order to access their lists via the web UI they have to `sign up` to create a Django account. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: Welcome message template errors

by Mark Sapiro

On 4/22/24 19:23, Mark wrote: > > > On 2024-04-23 11:33, Mark Sapiro wrote: >> On 4/22/24 17:06, Mark wrote: >> >>> Then, as site-owner, creating a new custom Welcome template (again >>> via the WebUI) I can see it correctly added to the database in >>> mailman.template.uri >>> >>> - >>> https://lists.mydomain.com/mailman3/api/templates/list/lists.mydomain.com/l… > > That URI should have been; > > https://lists.mydomain.com/mailman3/api/templates/list/mytestlist.lists.myd… I think you are saying the what you reported originally was not correct and the URL in the template table was in fact the latter URL. > If I go to the above URL, the text of the list's Custom welcome message > displays on an otherwise empty webpage. And that's what is expected. So you can go to that URL and get the template, but when Mailman Core tries to do the same thing, it gets a timeout. Is there some firewall or other security software blocking this access? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Mailman shutting down Hyperkitty: Request too large

by Stephen J. Turnbull

Arte Chambers via Mailman-users writes: > There is only 1 .pck file in $var_dir/archiver/hyperkitty/spool and > it is only 3.5M - Is there a way I can see what this pck file is? That file would be related to the response. The *request* in the HyperKitty protocol is going to be much smaller. I believe the normal upper limit is 4kB. The previous report raised the limit on the request to 16kb or maybe 64kB, but then ran into a different problem. None of these numbers should be big enough to cause consistent OOM conditions unless your memory is truly tiny. To view the file content, su to mailman, activate the virtual environment if you are using one, and type mailman qfile $var_dir/archiver/hyperkitty/spool/xxxx-xxxx.pck (with the correct name for the qfile, of course). mailman qfile -h will give you help, but IIRC qfile is one of the simplest subcommands: '-h' may be the only option it takes. There are two parts to the output. The first is the Message object flattened to an RFC 822 message file. The second is a mapping of metadata that gives hints about what Mailman was doing with the file. Steve

2 months, 3 weeks

[MM3-users] Re: How to change or create list styles

by Stephen J. Turnbull

Adam Minski writes: > What I like to do is creating new or modifying existing styles to > have reasonable defaults for creating new lists. If I create a new > style using the mailman shell as stated by the documentation, the > new style is gone as default after restarting mailman server. I didn't realize that was possible; I need to see how it's done. Anyway, the loss of the style is because the styles are implemented as Python functions. There is no place to store them in the database now. > If I understood you correctly the only way at the moment is hacking > the source code, which I always try to avoid without getting > changes upstream. Is this correct? That is correct. > What did you mean with "or write SQL"? Are the style defaults stored at > database level? No, they are not, they're hard-coded in the style/*.py files. If they were, they would persist. The SQL I'm referring to is a script that would manipulate the database directly for a given list. It wouldn't create a style in Mailman; it would be an "external" style. Steve

3 years, 6 months

[MM3-users] Re: Any possible way to reduce robot spam accounts?

by Franklin Weng

Hi Danil, (I just used the wrong account to reply. Feel free to reject the previous one which should be in moderated list) Danil Smirnov 於 2023/7/21 04:32 寫道: > Hi, > > On Thu, Jul 20, 2023 at 10:28 AM Franklin Weng <franklin(a)slat.org> wrote: > >> No matter what, what I want to ask is that, is there a way to either >> >> * just let users join from email (lists-join(a)lists.url) instead of >> registering on the mailman instance? or >> > I suppose you want this: > > https://docs.mailman3.org/en/latest/faq.html#how-to-disable-signup > > With my best regards, > Danil Smirnov Thank you. When I set it in my settings_local.py, I clicked register and got an error: ModuleNotFoundError at/accounts/signup/ No module named 'django_mailman3.views.user_adapter' (In the document the path is /etc/mailman3/settings.py but I installed it with Debian packages so I guess the path is somewhat different, and I thought setting in setting_local.py should work too. It seems work since it gave me the error above.) Do I have to install something else? Or disable some other options? Thanks, Franklin

1 year, 9 months

[MM3-users] Re: Fresh installation mailman3-suite via "pipx" - any experiences yet?

by Stephen J. Turnbull

Mark Sapiro writes: > But postorius and hyperkitty are dependencies of mailmanweb so only Are they? I'm pretty sure that in my current project which has a pre-existing archiver they wish to keep using I only installed postorius, not hyperkitty. ... oops, HyperKitty *is* there. OK, need to uninstall that. That's actually a bit annoying, since mailmanweb is a friendlier interface for control of either of HyperKitty and Postorius than the underlying Django utilities even if you don't want the other and its unique dependencies (such as Whoosh). (Issue #32 created) OK, so your two-venv approach should actually work. I still don't think it's much of a win since to finish setup you still have to do a lot of work as root and a lot of work outside of pipx's control. Basically it saves one "python3 -m venv", at the cost of "pipx run" to run each program in its own venv. Note, it doesn't save me any venv activationss because I put that in the mailman user's shell .rc. Wikinaut asks: > Has anyone tried that already? Why not you? Steve

1 year, 2 months

[MM3-users] Re: Hiding an ML from a site

by Odhiambo Washington

On Wed, Feb 7, 2024 at 9:45 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On February 6, 2024 7:45:14 AM PST, Odhiambo Washington > <odhiambo(a)gmail.com> wrote: > > > >I had this set to True in settings_local.py, but False in settings.py. > >So it seems to not make a difference in my setup. > > In a standard setup, anything set in settings_local.py overrides any > corresponding setting in settings.py. > > That said, FILTER_VHOSTS is not perfect. It only works for Postorius if > the separate web hosts also have different mail hosts. See lines 1051 et > seq at > < > https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/views/list… > > > What should I do then? Edit some file? Apply some patch? It's pretty easy for me to create a DNS record for the same server (IP) for use with the web host that I'd like to hide. -- 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]

1 year, 2 months

[MM3-users] Re: error changed after restart

by Guillermo Hernandez (Oldno7)

On 7/2/21 19:04, Abhilash Raj wrote: > > On Sun, Feb 7, 2021, at 1:07 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> On 6/2/21 21:19, Abhilash Raj wrote: >>> >>> On Sat, Feb 6, 2021 at 19:44, Guillermo Hernandez (Oldno7) via >>> Mailman-users <mailman-users(a)mailman3.org> wrote: >>>> On 6/2/21 18:08, Abhilash Raj wrote: >>>> >>>> On Sat, Feb 6, 2021, at 3:04 AM, Guillermo Hernandez (Oldno7) via >>>> Mailman-users wrote: >>>> >>>> I restarted de server and the error changed. Now the log >>>> shows "KeyError: 'subscription_mode'": >>>> >>>> Did you also restart Mailman Core after the upgrade? >>>> >>>> Yes, indeed: I stopped mailman core and all the processes related. >>>> Did the upgrades. Started all again. Find the errors in the web user >>>> interface. Stopped all again. Looked for errors in the log. Restarted >>>> the complete server. Found the second error that this second mail is >>>> about to. It happens when, in the main page that shows all the lists >>>> you click to see one of them. It seems to me that it has been >>>> database structure changes in django that the upgrade is not aware... >>>> but it's a very long shot from my side. >>> `subscription_mode` was added in Mailman Core 3.3.2 and it is actually >>> a derived atrribute and not stored in Database. Mailman's API should be >>> returning this attribute for each Member, but for some reason it seems >>> to me like it isn't doing that even though do have Mailman 3.3.3 running >>> like you said. >>> If you have Curl installed, can you send me the output of: >>> $ curl -u <user>:<pass> http://localhost:8001/3.1/members?count=5&page=1 >> This is the output you asked for (it's the same you can see when you try >> to interact with one list): >> >> /usr/local/mailman3 # curl -u XXXXXX:XXXXXX >> http://localhost:8001/3.1/members?count=5&page=1 >> /usr/local/mailman3 # <html> >> <head> >> <title>Internal Server Error</title> >> </head> >> <body> >> <h1><p>Internal Server Error</p></h1> >> >> </body> >> </html> >> >> No log entry has been produced... > This is weird, if you have working Core, then there should be *some* json returned > from the above command. Do you have the Gunicorn running? I have the uwsgi approach running... > What is the > output of `ps -ef | grep mailman`? none but if I do an ps ax | grep mailman it shows /usr/local/mailman3 # ps ax | grep mailman 26803 - IsJ 0:00.87 /usr/local/bin/python3.7 /usr/local/bin/master --force -C /usr/local/mailman3/var/et 26834 - SJ 0:07.57 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26835 - IJ 0:05.84 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26836 - SJ 0:07.16 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26837 - SJ 0:08.74 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26838 - SJ 0:03.16 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26839 - SJ 0:07.07 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26840 - SJ 0:08.12 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26841 - SJ 0:09.07 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26842 - SJ 0:07.45 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26843 - IJ 0:00.95 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26844 - SJ 0:07.27 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26845 - SJ 0:07.69 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26859 - IJ 0:01.01 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 26860 - IJ 0:05.75 /usr/local/bin/python3.7 /usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailma 50153 - IsJ 0:00.16 /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini 50481 2 S+J 0:00.00 grep mailman 26808 1 SJ 0:02.09 /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini 26832 1 IJ 0:00.00 /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini > Are you able to run `mailman members` command to list the members of a list? Yes. All the commands are working as expected. > Also, how did you actually install Mailman? Using pip. Here is a detailled post of how I did put all together: https://forums.FreeBSD.org/threads/mailman-3.61050/post-488128 Thanks for your support > > Abhilash. > >> TIA. >> >> >> >> >>> It should ideally return an output that looks something like shown >>> here[1]. You >>> can put the username/password of Core's API server in the above command. >>> [1]: >>> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… >>> >>> Abhilash >>>> I'm using sqlite as django database and mysql for mailman. >>>> >>>> ERROR 2021-02-06 11:47:49,015 26798 django.request Internal >>>> Server Error: >>>> /mailman3/mailman3/lists/name_and_domain.of.the.list >>>> Traceback (most recent call last): File >>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>>> line 119, in __getattr__ return self._get(name) File >>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>>> line 86, in _get raise KeyError(key) KeyError: >>>> 'subscription_mode' During handling of the above exception, >>>> another exception occurred: Traceback (most recent call >>>> last): File >>>> "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py", >>>> line 34, in inner response = get_response(request) File >>>> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", >>>> line 115, in _get_response response = >>>> self.process_exception_by_middleware(e, request) File >>>> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", >>>> line 113, in _get_response response = >>>> wrapped_callback(request, *callback_args, **callback_kwargs) >>>> File >>>> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", >>>> line 71, in view return self.dispatch(request, *args, >>>> **kwargs) File >>>> "/usr/local/lib/python3.7/site-packages/postorius/views/generic.py", >>>> line 74, in dispatch return super(MailingListView, >>>> self).dispatch(request, *args, **kwargs) File >>>> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", >>>> line 97, in dispatch return handler(request, *args, >>>> **kwargs) File >>>> "/usr/local/lib/python3.7/site-packages/postorius/views/list.py", >>>> line 295, in get member.subscription_mode == File >>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>>> line 124, in __getattr__ self.__class__.__name__, name)) >>>> AttributeError: 'Member' object has no attribute >>>> 'subscription_mode' *********************** some info about >>>> the installed versions via pip list: pip list | grep django >>>> django-allauth 0.44.0 >>>> django-appconf 1.0.4 >>>> django-compressor 2.4 >>>> django-extensions 3.1.0 >>>> django-gravatar2 1.4.4 >>>> django-haystack 3.0 >>>> django-mailman3 1.3.5 >>>> django-picklefield 3.0.1 >>>> django-q 1.3.4 >>>> djangorestframework 3.12.2 pip list | grep mailman >>>> django-mailman3 1.3.5 >>>> mailman 3.3.3 >>>> mailman-hyperkitty 1.1.0 >>>> mailmanclient 3.3.2 pip list | grep postorius >>>> postorius 1.3.4 On 6/2/21 11:12, >>>> Guillermo Hernandez (Oldno7) via Mailman-users wrote: >>>> >>>> I've just upgrade mailman 3 installation following Mr. >>>> Sapiro advice: did a pip install --upgrade >>>> django-mailman3 hyperkitty mailman mailmanclient >>>> mailman-hyperkitty postorius I did a "python3 manage.py >>>> migrate" after, too. And all seemed to run well. All the >>>> lists showed in postorius via web, but when I try to >>>> accesss into one of them the browser shows an error. In >>>> the log you can see: *-*-*-*-*-*-* Traceback (most recent >>>> call last): File >>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>>> line 119, in __getattr__ return self._get(name) >>>> File >>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>>> line 86, in _get raise KeyError(key) KeyError: >>>> 'get_requests_count' .. (And after all the traceback >>>> lines) AttributeError: 'MailingList' object has no >>>> attribute 'get_requests_count' *-*-*-*-*-*-*-* The lists >>>> seem to be distributing messeages well.. but I cannot >>>> acces via web administration (django/postorius) Can >>>> anyone point me in the right direction to solve this, >>>> please? _______________________________________________ >>>> Mailman-users mailing list -- mailman-users(a)mailman3.org >>>> <mailto:mailman-users@mailman3.org> To unsubscribe send >>>> an email to mailman-users-leave(a)mailman3.org >>>> <mailto:mailman-users-leave@mailman3.org> >>>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >>>> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/> >>>> >>>> >>>> _______________________________________________ Mailman-users >>>> mailing list -- mailman-users(a)mailman3.org >>>> <mailto:mailman-users@mailman3.org> To unsubscribe send an >>>> email to mailman-users-leave(a)mailman3.org >>>> <mailto:mailman-users-leave@mailman3.org> >>>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >>>> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/> >>>> >>>> >>>> _______________________________________________ Mailman-users mailing >>>> list -- mailman-users(a)mailman3.org >>>> <mailto:mailman-users@mailman3.org> To unsubscribe send an email to >>>> mailman-users-leave(a)mailman3.org >>>> <mailto:mailman-users-leave@mailman3.org> >>>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >>>> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/> >> >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >>

4 years, 2 months

[MM3-users] Re: Language confusion in held mail notifications

by Mark Sapiro

On 9/27/21 4:04 AM, Henrik Rasmussen wrote: >> Thanks for the hint Steve. There is a Spanish message catalog as >> evidenced by the fact that the reason was translated to Spanish, but the >> issue is almost certainly that there is no >> mailman/templates/es/list:user:notice:post.txt template so we fall back >> to the one for the list's language. > > I should note that my tests on same list with same language setup did not mix languages, for some reason and I can't replicate the problem. I wonder if it could have been a timing issue or the order that I changed languages on list language and user preference. I really think it has to do with two conditions: 1) the user's preferred language is Spanish 2) there was no mailman/templates/es/list:user:notice:post.txt template There were Spanish templates in Mailman core 3.3.4, but they were misnamed, e.g. list_user_notice_post.txt instead of list:user:notice:post.txt. Did you somehow add a mailman/templates/es/list:user:notice:post.txt template after the initial test? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Welcome message template errors

by Mark

On 2024-04-23 11:33, Mark Sapiro wrote: > On 4/22/24 17:06, Mark wrote: >> >> There was no line POSTORIUS_TEMPLATE_BASE_URL in >> /etc/mailman3/settings.py > So presumably you were getting the default > > POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' > > from mailman-web/settings/mailman.py because of > from mailman_web.settings.mailman import * > in your settings.py. Yes. # Mailman Web configuration file. # /etc/mailman3/settings.py # Get the default settings. from mailman_web.settings.base import * from mailman_web.settings.mailman import * ... > >> Then, as site-owner, creating a new custom Welcome template (again via >> the WebUI) I can see it correctly added to the database in >> mailman.template.uri >> >> - >> https://lists.mydomain.com/mailman3/api/templates/list/lists.mydomain.com/l… That URI should have been; https://lists.mydomain.com/mailman3/api/templates/list/mytestlist.lists.myd… If I go to the above URL, the text of the list's Custom welcome message displays on an otherwise empty webpage. > > > And what happens if you go to that URL in a web browser? Also what do > you get when going to https://lists.mydomain.com/mailman3? I get the Postorius page "Mailing Lists" that displays the table of lists.

1 year

[MM3-users] Re: Pre-approved howto

by Thor Atle Rustad

2018-07-09 10:49 GMT+02:00 Thor Atle Rustad <thor.rustad(a)gmail.com>: > >> >> > $ mailman shell -l junk(a)msapiro.net >> > Welcome to the GNU Mailman shell >> > The variable 'm' is the junk(a)msapiro.net mailing list >> >>>> m.moderator_password >> >>>> from mailman.config import config >> >>>> m.moderator_password = config.password_context.encryp >> t('xxx123').encode('us-ascii') >> >>>> m.moderator_password >> > b'$6$rounds=656000$SKMqTlPybIZSBjYB$wCga5qALCv8oobp4cDql2iKE >> g8T6qIgk8XEKYbkk9QXENeFQDHZ1M4AtmqfureYQDB5g.Az.nZPrWAr9N9g1N0' >> >>>> commit() >> > > Thank you, this worked permanently. Now, how can I loop through all 700 > lists and change the list password on all of them? > > Thor > I think I can answer this myself. I found inspiration here: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… and was able to do the following to change the moderator password on all lists: '>>> from zope.component import getUtility '>>> from mailman.interfaces.listmanager import IListManager '>>> listmanager = getUtility(IListManager) '>>> for mlist in listmanager.mailing_lists: '... mlist.moderator_password = config.password_context.encrypt('secret_pa$$word').encode('us-ascii') '... commit() '... print(mlist.list_name) Seems to work :-)

6 years, 9 months

[MM3-users] Re: outgoing.py mailman@example.com issue

by Mark Sapiro

On 11/8/21 11:10 AM, dancab(a)caltech.edu wrote: > > We do have mailman(a)caltech.edu configured with valid members/owners. > We're using Postfix for the MTA. Is it possible there's a misconfiguration there? > > We've been testing the system with a handful of lists for months. The bounce you saw From: Mailman mailman(a)example.com To: Mailman Bounces mailman-bounces(a)example.com Subject: SMTP Delivery Failure may have sent because you have VERP probes enabled (verp_probes: yes in the mta section of mailman.cfg) and a user on some list reached the bounce score threshold and a Mailman attempted to send a probe and the MTA refused the message, or it may have been sent because Mailman attempted to send a message to the user and the MTA refused it. In either case, the bounce message (fake DSN) should have contained a message body like Mail to user(a)example.com failed at outgoing SMTP with the actual user's address. These fake DSNs are sent in the case where the outgoing MTA refuses a message from Mailman so there is no actual failure DSN. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: EMWD Mailing Lists Down

by Mark Sapiro

On 1/15/22 5:49 PM, Sherry Xie wrote: > Hi all, > > I am an EMWD Mailman 3 customer, and I recently realized my mailing lists > are no longer working (the last email that went through was sent on > December 25, 2021). Emails I send to the lists do not show up in archives > or reach subscribers. It seems like others have had this issue before > since ownership of the company was transferred following Brian Carpenter's > passing – has anyone been able to get in touch with support or get their > issues resolved? > > I've submitted a support ticket but have no idea if this is being > monitored. I also have no way to contact the current management team, as > only their names were announced in the November 5, 2021 email from Barbara > Carpenter. Any help would be greatly appreciated – thanks in advance! There is a recent thread on this started at https://mail.python.org/archives/list/mailman-users@python.org/thread/N7NJL… and continued at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… You might find something helpful there. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Mailman3 without Hyperkitty in docker

by Danil Smirnov

Hi Mark, Actually all this stuff happens inside the container after it's started and initialized without errors. I didn't amend the image anyhow. Also I have the configuration based on docker-compose.yaml provided in the repository which works just fine for mailman-web image. The very same config with postorius image (+ UWSGI_STATIC_MAP param) fails with 500 error... Now answering your questions: ср, 27 февр. 2019 г., 22:56 Mark Sapiro <mark(a)msapiro.net>: > do you have django-q in INSTALLED_APPS in your Django settings and what > is set for Q_CLUSTER? > I've checked settings.py inside the container and I haven't found any of the mentioned configurations there. Does the manage.py that's being run here point to the right settings.py? > No clue. Also I wonder why we have some Hyperkitty-related cronjobs in non-HK configured image? https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web… Danil > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

6 years, 1 month

[MM3-users] Re: Welcome Message

by brian＠emwd.com

Abhilash Raj wrote: > If the URL for template is wrong, or Postorius is down for whatever reason, > the subscription will fail with the error that you saw before. Explain URL for template. You mean "POSTORIUS_TEMPLATE_BASE_URL"? That is not wrong. I am confident of that. It is back to "http://mailman-web:8000". I can successfully ping mailman-web:8000 from bash. > > I logged out of Postorious and subscribed using the > > subscribe form on > > the info page and the change to the welcome template showed up. So it > > looks like being logged in as admin while trying to subscribe someone > > was what was causing the problem. Is that a bug I discovered? > I suspect stopping-restarting and re-creating the template (idk, if you > really did that) might have something to do with it. I am not sure if this > is a bug unless you can reliably reproduce this. This error is absolutely reproducible. It even impacts other list admins who are trying to use a custom welcome message and subscribing a member while logged into Postorious. Everything else is working fine on this server and I followed your directions precisely when I set this server up. Please help. Thanks, Brian

6 years

[MM3-users] Re: OS upgrade - anything to take care of?

by Mark Sapiro

On 5/13/21 1:58 PM, Ruth Ivimey-Cook wrote: > > Sadly they aren't - they link to python3.6 or whatever... and even if > not, the /lib/ naming gets you as well. > > And even if that can be worked around (eg by renaming the mailman > /lib/python3.6 folder to /lib/python3.8), the python .pyc files are > /also/ versioned, so you then have to find & delete them all to force > the new interpreter to rebuild them or python falls down in a heap. Maybe I'm missing something, but it seems to me that if /usr/lib/python3.6 and /user/bin/python3.6 are gone, just creating symlinks from /usr/lib/python3.6 and /user/bin/python3.6 to the corresponding python3.8 directories would work. The .pyc files in __pycache__ should not be an issue. They are versioned and placed in a __pycache__ directory specifically so multiple python versions can coexist. See <https://www.python.org/dev/peps/pep-3147/>. Python3.8 will just make new ones. If there is some issue with this, one can always do ``` find /path/to/venv -name '*.pyc' -delete ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Mark Sapiro

On 10/22/22 13:07, Onyeibo Oku wrote: > On Sat Oct 22, 2022 at 7:44 PM WAT, Mark Sapiro wrote: >> The specific error you reported refers tp >> /opt/mailman/venv/lib/python3.10/site-packages/zope.i18nmessageid-5.0.1-py3.10.egg-info/PKG-INFO >> >> what does >> ``` >> ls -l >> /opt/mailman/venv/lib/python3.10/site-packages/zope.i18nmessageid-5.0.1-py3.10.egg-info/PKG-INFO >> ``` >> show? >> > > See below: > > command: > ls -lh /opt/mailman/venv/lib/python3.10/site-packages/zope.i18nmessageid-5.0.1-py3.10.egg-info/PKG-INFO > > output: > -rw-r--r--. 1 mailman mailman 7.8K Oct 19 18:31 /opt/mailman/venv/lib/python3.10/site-packages/zope.i18nmessageid-5.0.1-py3.10.egg-info/PKG-INFO This is actually strange. What does `pip --version` in your venv show? Did you do anything to install mailman and other packages in your venv other than `pip install`. I ask because I don't think there should be *egg-info directories in /opt/mailman/venv/lib/python3.10/site-packages/ at all. In particular, in addition to the actual code directories, I only see files and directories with names ending in nspkg.pth and dist-info. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: E-mail every minute: "Cron <www-data@sharky5> ..."

by Odhiambo Washington

On Sun, Jul 7, 2024 at 8:43 PM Robert Heller <heller(a)deepsoft.com> wrote: > At Sun, 7 Jul 2024 19:48:02 +0300 Odhiambo Washington <odhiambo(a)gmail.com> > wrote: > > > > > On Sun, Jul 7, 2024 at 7:16Ã¢Â€Â¯PM Robert Heller <heller(a)deepsoft.com> > wrote: > > > > > At Sun, 7 Jul 2024 18:52:05 +0300 Odhiambo Washington < > odhiambo(a)gmail.com> > > > wrote: > > > > > > > > > > > On Sun, Jul 7, 2024 at 4:12ÃƒÂƒÃ‚Â¢ÃƒÂ‚Ã¢Â‚Â¬ÃƒÂ‚Ã‚Â¯PM Robert > Heller <heller(a)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. > 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]

9 months, 2 weeks

[MM3-users] My list has been switched from public to private archives, but they are still visible

by Stephen J. Turnbull

Paul Arenson writes: > I set my list to private archives today. Up until then, it was > pubic. And yet, if you go to the list page, you will see that if > you click archives (top left), you can see them. (Filled with a > bunch of tests posts for now) Yes, I can see it, and the posts. I think there was a bug that you can see that private lists are present even if you are not a subscriber. However the posts themselves were private. This is not that bug, it's something else. > Am I misunderstanding what a private archive is? No (except for the bug mentioned above, which probably will be fixed -- the logic is nontrivial, since admins need access to the list of lists, but maybe not private lists they're not owners of, even if they're not subscribers). > Is something wrong with my setup (which is hosted)? Don't know yet. Some configuration changes require a server restart. I don't know offhand if this is one. It's worth a try if you can do that.

5 years, 7 months

[MM3-users] Re: Monthly mailman-web job using a lot of memory

by Mark Sapiro

On 7/2/22 12:04 PM, Andy Smith wrote: > > For ~6k messages it still took approx 16 hours to run that monthly > job, and during that time spewed out thousands of these errors: > > Failed to remove document 'hyperkitty.email.29351' from Whoosh: > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/haystack/backends/whoosh_backend.py", line 309, in remove > self.index.delete_by_query(q=self.parser.parse('%s:"%s"' % (ID, whoosh_id))) > File "/usr/lib/python3/dist-packages/whoosh/index.py", line 365, in delete_by_query > w = self.writer() > File "/usr/lib/python3/dist-packages/whoosh/index.py", line 464, in writer > return SegmentWriter(self, **kwargs) > File "/usr/lib/python3/dist-packages/whoosh/writing.py", line 515, in __init__ > raise LockError > whoosh.index.LockError > > …so I'm not even sure if it worked. I think the warnings come from the hourly update_index job which can't obtain a lock on the index because the update_and_clean_index job already has it locked. Once the update_and_clean_index job finishes the update_index job should run and do the right thing. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: Again, after systemupgrade the log file in /var/log/mailman was owned by list:list instead of mailman:mailman and starting failed for this reason [support request]

by Wikinaut

This is in /opt/mailman/web/logs# dir total 3164 276 -rw-r--r-- 1 mailman mailman 274457 Dec 24 09:05 mailmanweb.log 2056 -rw-r----- 1 mailman mailman 2100388 Dec 24 09:05 uwsgi-error.log 832 -rw-r----- 1 mailman mailman 846536 Dec 24 09:10 uwsgi.log Looks okay. This is my /etc/systemd/system/mailman3.service: Unit] Description=GNU Mailing List Manager After=syslog.target network.target mysql.service [Service] Type=forking User=mailman Group=mailman PIDFile=/opt/mailman/venv/bin/master.pid ExecStart=/opt/mailman/venv/bin/mailman start --force ExecReload=/opt/mailman/venv/bin/mailman restart --force ExecStop=/opt/mailman/venv/bin/mailman stop [Install] WantedBy=multi-user.target This mailman3web.service: [Unit] Description=GNU Mailman Web UI After=syslog.target network.target mysql.service mailman3.service [Service] Environment="PYTHONPATH=/etc/mailman3/" User=mailman Group=mailman ExecStart=/opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini KillSignal=SIGINT [Install] WantedBy=multi-user.target I do use the venv method, but the other issue may be a relict from former setup, as I said, and difficult to find. It so very strange, that the log-permisison issue stems from → systemctl start mailman3.

1 year, 3 months

[MM3-users] Re: Owner's or Moderator's Lists

by Mark Sapiro

On 7/31/20 11:09 AM, Johnny Cison wrote: > > It's 1.1.2, which is the python3-django-postorius version included with the > package manager on Ubuntu 18.04. > > Is there by chance a mechanism for viewing that information in 1.1.2? You have several choices. 1) Do nothing and wait for Debian/Ubuntu to upgrade the package and backport it. 2) Try upgrading Postorius from source or with pip. This will probably result in disaster, and even if it doesn't, will probably also require upgrading django-mailman3, mailmanclient and mailman core to support new features in Postorius. 3) See the merge requests at <https://gitlab.com/mailman/postorius/-/merge_requests/349>, and if you have >50 lists, <https://gitlab.com/mailman/postorius/-/merge_requests/437> and try patching installing those changes as patches. Note that!349 patches 15 files, but one of them is the change log and 12 are related to tests. The only ones you need to patch are postorius/templates/postorius/index.html and postorius/views/list.py. Likewise, these two are all you need from !437. 4) Abandon the Debian/Ubunto package and install the whole suite from source or with pip. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: So, why are css & js files only served with "DEBUG = yes" ?

by Odin Hørthe Omdal

> js and css files are static and should be served by your web server of choice. Actually, Python is able to do this very nicely and quickly these days. I've started using WhiteNoise (added as a django staticfiles provider) which does all the right things for you directly (uses sendfile, sets cache headers, does compression correct, all real work done at initialization time, if you best speed just add CDN, etc etc). It might be something to make MM3 setup a bit nicer and quicker (note, I still haven't migrated to MM3 so don't know much about it); http://whitenoise.evans.io/ A point against it is an extra dependency ofc. Odin 2017-05-07 15:12 GMT+01:00 Simon HANNA <simon.hanna(a)serve-me.info>: > js and css files are static and should be served by your web server of > choice. In a development environment you usually don't have a web server > running, so django serves the files itself. > > Your webserver can serve these static files much faster than django can, > so django doesn't serve them in production by default. You can find > instructions on how to do so online (Google is your friend) but since > that's not incouraged there is no point in including these in the repos. > > Simon > > Am 7. Mai 2017 16:06:17 MESZ schrieb Simon Liebold via Mailman-users < > mailman-users(a)mailman3.org>: > >Hello List, > > > >I did see this discussed in #180 > ><https://gitlab.com/mailman/postorius/issues/180>, but I didn't quite > >understand if this is an issue or not. > > > >Why is it that I can run the development server just fine. > > > > [07/May/2017 13:23:47] "GET > > /static/postorius/libs/bootstrap/css/bootstrap.min.css HTTP/1.1" 304 0 > > [07/May/2017 13:23:47] "GET /static/postorius/css/style.css > > HTTP/1.1" 304 0 > > [07/May/2017 13:23:47] "GET > > /static/postorius/libs/bootstrap/js/bootstrap.min.js HTTP/1.1" 304 0 > > [07/May/2017 13:23:47] "GET /static/django-mailman3/js/main.js > > HTTP/1.1" 304 0 > > [07/May/2017 13:23:47] "GET > > /static/postorius/libs/jquery/jquery-1.11.3.min.js HTTP/1.1" 304 0 > > [07/May/2017 13:23:47] "GET /static/django-mailman3/css/main.css > > HTTP/1.1" 304 0 > > [07/May/2017 13:23:47] "GET /static/postorius/js/script.js HTTP/1.1" > > 304 0 > > [07/May/2017 13:23:47] "GET > > /static/postorius/img/mailman_logo_small_trans.png HTTP/1.1" 304 0 > > > >And as soon as I comment out > > > > # SECURITY WARNING: don't run with debug turned on in production! > > # DEBUG = True > > > >in mailman-suite/mailman-suite_project/settings.py and restart it 404s > >on me. > > > > [07/May/2017 13:41:36] "GET > >/static/postorius/libs/bootstrap/css/bootstrap.min.css HTTP/1.1" 404 > >127 > > [07/May/2017 13:41:36] "GET /static/django-mailman3/css/main.css > > HTTP/1.1" 404 109 > > [07/May/2017 13:41:36] "GET /static/postorius/css/style.css > > HTTP/1.1" 404 104 > > [07/May/2017 13:41:36] "GET /static/django-mailman3/js/main.js > > HTTP/1.1" 404 107 > > [07/May/2017 13:41:36] "GET > > /static/postorius/libs/bootstrap/js/bootstrap.min.js HTTP/1.1" 404 125 > > [07/May/2017 13:41:36] "GET > > /static/postorius/libs/jquery/jquery-1.11.3.min.js HTTP/1.1" 404 123 > > [07/May/2017 13:41:36] "GET /static/postorius/js/script.js HTTP/1.1" > > 404 103 > > [07/May/2017 13:41:36] "GET > > /static/postorius/img/mailman_logo_small_trans.png HTTP/1.1" 404 123 > > > > > >So the choice is insecure vs. ugly? Neither of those sounds very > >tempting. > > > >I guess, I am missing something, or no? > > > >Simon > > > >_______________________________________________ > >Mailman-users mailing list > >mailman-users(a)mailman3.org > >https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Beste helsing, Odin Hørthe Omdal <odin.omdal(a)gmail.com> English, technical: http://tech.velmont.net Norsk, personleg: http://velmont.no

7 years, 11 months

[MM3-users] Re: "Private archives" aren't private

by Simon Liebold

Am 04.06.2017 um 15:55 schrieb Simon Hanna: > > Where are you seeing this behaviour? In my test archive: https://lists.simonliebold.de/hyperkitty/list/simsimmer@lists.simonliebold.… > > What version of Hyperkitty are you using? Master, commit 4c5eaead. > > Can you check what is stored in the database of Hyperkitty? > > ``` > > python manage.py shell > > from hyperkitty.models.mailinglist import MailingList > > MailingList.objects.all().values_list('name', 'archive_policy') > > ``` > > If the value for your list is 1 then we have a problem. 2 is for public > archives and 0 should never be archived. OK, no problem there: <QuerySet [(u'simsimmer(a)lists.simonliebold.de', 2L)]> > > It's possible that you changed the archive_policy of a list and the > change wasn't reflected in Hyperkitty. Postorius is showing the list's settings as "Private archives" (see screenshot). But apparently this setting doesn't do anything when switching it to "public" and back to "private". It always returns '2L'. Don't know if this is expected. Postorius is on 52c9c3a5. > > For such a possibly sensitive issue, you should open a hidden issue in > Gitlab ;-) > The issue is probably my setup. Simon

7 years, 10 months

[MM3-users] Re: not correct language in subject(s)

by Mark Sapiro

On 5/23/23 08:19, Mark Sapiro wrote: > On 5/23/23 06:24, Jens Günther wrote: >> >> But also other examples: >> - bounce-mail for the user that moderator approval is necessary (there >> the text is in german, but the reason is in english) >> - approval-mail for moderator (also text is in german, but subject and >> reason in english) > > > I'll look into these. If you don't have the > mailman/messages/de/LC_MESSAGES/mailman.mo file, this could be the > reason, but there may be a bug. I just tested, and the notice to the moderator of a held message is in the list's preferred language including the Subject: and the moderation reason, and the notice to the user sending a held message is in the User's preferred language for that list including the Subject: and the moderation reason. I suspect your issue is you don't have the compiled mailman.mo German message catalog. The text is in German because it comes from templates and you presumably do have German language templates. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: hyperkitty won't list more than 5 posts and shows empty grey Activity Summary box

by Barry Warsaw

On Aug 9, 2017, at 15:45, Mark Sapiro <mark(a)msapiro.net> wrote: > However, the sending of periodic digests depends on cron running > something periodically to actually trigger the sending. Right. There will eventually be additional recurring tasks for Core too though, such as processing the bounce database for disables and unsubs, pulling messages from NNTP, and possibly others as time goes on. I’ve always thought about handling these as commands that cron would run, much as in Mailman 2, but it would also be possible to implement a runner, or runners, to do those jobs. I can see advantages and disadvantages with either approach. > Note: I've just looked at the code and there seems to be an issue with > using 'mailman digests --send' to send the periodic digests. It appears > that if a list's digest mbox has any messages, 'mailman digests --send' > will send a digest even if digest_send_periodic is false. I've just > reported <https://gitlab.com/mailman/mailman/issues/384> for this issue. Yep, thanks for the bug report. `mailman digests —periodic` seems like the right approach. Cheers, -Barry

7 years, 8 months

[MM3-users] Internal server error

by Stephen J. Turnbull

Andrew Bernard writes: > My mailbox is filling up with dozens of notification of an internal > server error. i wont post the whole mail as it is long, but here is > the top: > > Internal Server Error: > /archives/list/jackrail-meta(a)jackrail.org/recent-threads > > TypeError at /archives/list/jackrail-meta(a)jackrail.org/recent-threads > 'datetime.date' object is not iterable This is not your error, this a bug in Mailman (unlikely), Django (plausible), or some library Django uses. It could be a broken email, but that's still a validation bug somewhere in the Mailman stack. Googling "'datetime.date' object is not iterable django" suggests there may have been a Django or library bug in 2016 or so (I did *not* go past the blurbs Google returns). Without a backtrace, I can't identify this. If the "long" email is long because of the backtrace, please do post it. If not, set DEBUG=True in your config, restart Mailman long enough to get the message, find the backtrace in the message or log, and post that. If you're shy about posting long texts of uncertain value to the -users list (I understand the feeling), feel free to post to the GitLab issue tracker or mailman-developers(a)python.org. Steve

5 years, 8 months

[MM3-users] Re: Hyperkitty Error Curiosity

by Brian Carpenter

On 11/11/20 7:40 PM, Mark Sapiro wrote: > On 11/11/20 4:18 PM, Brian Carpenter wrote: >> Some sort of auto-discard procedure after a number of retries? Is it >> possible to detect a message with a null characters and automatically >> discard them? Do such messages make it into the thread table? > > The message has been delivered to the list, but it is not archived. The > list post has an Archived-At: header with a URL, but the message isn't > there at all. The only way to get it archived is to correct the message > defect. Does the problematic message (null character) make it to the hyperkitty_thread table? > Thus, I don't think it's good to just discard the message at that point. > I'm fine with moving out of or not queueing it in the first place in > var/archives/hyperkitty/spool, but I think it should be preserved > somewhere, say in var/archives/hyperkitty/bad, and along with that, some > kind of notice sent to the site admin so bad messages don't just > accumulate without being seen. > Can a message with a null character be repaired with an automatic process? -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 5 months

[MM3-users] Re: Issues encountered while upgrading to 3.3.7

by Odhiambo Washington

On Mon, Dec 5, 2022 at 8:54 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/5/22 02:37, Odhiambo Washington wrote: > > > > Here again, Google-fu came to the rescue. I added the following line to > > settings_local.py and the warnings were suppressed. > > DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' > > I need to understand how this affects everything and how this is likely > to > > impact the functionality of MM3. What is the proper solution for this? > > And should it be django.db.models.BigAutoField or > > django.db.models.AutoField? Which is which? > > > Prior to Django 3.2 Django set default primary keys to 32 bit integers. > In 3.2 Django introduced the possibility to set default primary keys to > 64 bit integers by setting the type to django.db.models.BigAutoField. > > Thus, putting > ``` > DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' > ``` > in your settings will maintain compatibility with pre 3.2 versions and > existing tables and this is the correct thing to do. > Thank you very much for the clarification. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 4 months

[MM3-users] Re: using SSH/TLS with external MTA

by Mark Sapiro

On 7/28/24 09:54, Roland Giesler via Mailman-users wrote: > > These settings from the Django docs look like the ones in mailman.cfg. > Do I have to set them somewhere else too? Yes. The settings in mailman.cfg only affect mail from Mailman. For mail from Django, you have to set things like EMAIL_HOST = 'box2.gtahardware.co.za' EMAIL_PORT = 465 EMAIL_HOST_USER = 'roland(a)giesler.za.net' EMAIL_HOST_PASSWORD = '...' and possibly others as desired, See the links to the Django docs for these. > * |use_tls|:|EMAIL_USE_TLS| > > <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_USE_T…> > * |use_ssl|:|EMAIL_USE_SSL| > > <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_USE_S…> > * |timeout|:|EMAIL_TIMEOUT| > > <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_TIMEO…> > * |ssl_keyfile|:|EMAIL_SSL_KEYFILE| > > <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_SSL_K…> > * |ssl_certfile|:|EMAIL_SSL_CERTFILE| > > <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_SSL_C…> This all goes in your Django settings which from other posts I gather is /etc/mailman3/mailman3-web.py. I'm guessing you are using the Debian packages and that's where the package puts the Django settings. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 3 weeks

[MM3-users] Re: Can't deliver mails in queue

by Mark Sapiro

On 5/20/21 4:01 AM, Nathanael Schneider wrote: > > It would have been nice though to have a more refined error to figure > this out. But its solved now and hopefully this will help someone else > as well. I'm glad you resolved it, and I'm sorry I didn't consider the template issue myself. You actually had two separate template issues. If you created templates in Postorius, they were inaccessible because of the POSTORIUS_TEMPLATE_BASE_URL issue, but your initial problem with imported lists is different. It probably resulted from running the `mailman import21` command as root which you should never do. You should always run `mailman` commands as the Mailman user. This is mentioned at https://docs.mailman3.org/en/latest/migration.html#id1 The `mailman import21` command can create list specific templates in Mailman's var/templates/lists/LIST_ID/LC/ directory and if run as root these will be user:group root:root and not world readable and therefore can't be read by Mailman. Also, deleting and recreating the list with the same LIST_ID doesn't remove those templates, so the list still doesn't work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] New Mailman Releases

by Abhilash Raj

Hi, I am pleased to announce several new releases for GNU Mailman project. 1. Mailman Core 3.3.6 [1] 2. Postorius 1.3.7 [2] 3. Hyperkitty 1.3.6 [3] 4. Mailmanclient 3.3.4 [4] 5. Django-mailman3 1.3.8 [5] All the releases are published to PyPI and you can find links to all the PyPI projects: https://docs.mailman3.org/en/latest/ A full list of changelogs are available below: [1]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… [2]: https://docs.mailman3.org/projects/postorius/en/latest/news.html#section-2 -- Something weird is going on with the page missing the bullets. [3]: https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-6 [4]: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… [5]: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst Finally, the minimum Python version required is 3.7 although, 3.9 is recommended if you are doing a new install for longest support. 3.10 is supported for Django apps, but Mailman Core is missing that due to one of the core dependencies not support 3.10 yet (aiosmtpd). Thanks to all the contributors for making this release possible and apologies on my end for delayed releases. If you find any issues, you can report them at the respective bug tracker for the projects. The links to issue trackers are available here: https://docs.mailman3.org/en/latest/ -- thanks, Abhilash Raj (maxking)

2 years, 5 months

[MM3-users] Re: Mailman REST API not available. Please start Mailman core.

by Mark Sapiro

On 2/12/25 09:24, Christian via Mailman-users wrote: > Running Debian 4.19.316-1 > Python 3.7.3 > > I am unable to start mailman core > > > mailman@lists:~$ /opt/mailman/mm/bin/mailman start > Usage: mailman start [OPTIONS] > Try 'mailman start -h' for help. > > Error: A previous run of GNU Mailman did not exit cleanly (stale_lock). Try > using --force > mailman@lists:~$ > > > I try using --force and it did not work. So how do I start it? In Mailman's var/locks directory (maybe /opt/mailman/mm/var/locks/) you will see at least two files. The ones of interest are: ``` master.lck master.lck|<host_name>|<pid>|<random_integer> ``` First verify that pid is not running or if it is, that it's not Mailman's `master` process. Then remove all the files from the var/locks/ directory and Mailman should start. > Bottom line: I would like for Mailman core to start when I reboot the > server. How can this be achieved please? See https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailma… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months, 1 week

[MM3-users] We're in Season of Docs!

by Stephen J. Turnbull

So, we're in Season of Docs! Currently, Abhilash and I are registered as mentor/admins. I don't think we need more admins, but more mentors is always a good thing. Hey, users! You don't need to be a programmer to mentor docs, of course, and it may be a *good* thing to *not* be a programmer and even *not* a Mailman developer. :-) Suggestions as to doc projects we *really oughtta do!* are very welcome. (I can't believe we got in with the thin doc proposal I put together literally at the last minute, but here we are. ;-) Feel free to get in touch with us on mailman-developers (reply-to set; please respect) if you're interested in mentoring. Or if you prefer you can contact me or Abhilash directly. We can presumably add mentors up to July 23 (deadline for technical writer selection by orgs). For more information: https://wiki.list.org/DEV/SeasonOfDocs2019 https://developers.google.com/season-of-docs/ https://developers.google.com/season-of-docs/docs/participants/ https://developers.google.com/season-of-docs/docs/timeline Regards, Steve -- Associate Professor Division of Policy and Planning Science http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN

5 years, 11 months

[MM3-users] Re: Recommended way to backup a mailman3 instance

by Gilles Filippini

Abhilash Raj a écrit le 12/04/2020 à 19:34 : > > > On Sun, Apr 12, 2020, at 7:23 AM, Gilles Filippini wrote: >> Gilles Filippini a écrit le 10/04/2020 à 10:39 : >>> Hi, >>> >>> I'd like to schedule periodic backup for our mailman3 instance. Are >>> there recommended ways for doing this without down times? >> >> I should have precised that our mailman3 instance is dockerized. Then, >> as I understand it, these backups should be sufficient: >> * MailmanCore's volume (/opt/mailman/var folder) > > /opt/mailman/core/var > >> * Database dump >> >> Anything else? > > No, that should be enough. Mailman-web is fairly stateless and stores everything except the settings and logs in the database. If you have settings version controlled then you don't need anything else. There is also fulltext_index, but that doesn't need to be backed up because it can be easy re-generated with a single django-admin command. I don't know django. Would you mind giving some pointers about this django-admin command to re-regenerate fulltext_index? > Mailman core's entire state is in the var/ directory above. Ack. Thanks, _g,

5 years

[MM3-users] Rich Text support in Hyperkitty

by Abhilash Raj

Hi All, I have been recently working on adding rich text support through markdown in Hyperkitty so that emails can be made easier to read. The core design idea in my mind when working on this was building something that doesn't bother writers of plain text emails too much, but allows people to write emails in markdown. The supported syntax is limited Markdown, for example: Hyperkitty's Markdown Syntax ============================ - List items are supported - Even nested ones - Headers with `#` aren't supported, mostly due to their widespread use as comments in code shared on mailing lists. - You can **emphasize** text and _itcalize_ them too - Block code and `inline code` works. - URLs work like they usually do. - Images _do work_, but are disabled by default because of their potential for tracking users. They need to be enabled by administrators through a configuration flag. ``` def sample(): return "yay" ``` While text intentionally written for Markdown rending looks pretty good, plain text sometimes isn't as good. I have applied my branch[1] on both the Mailman installations for these two lists (mail.python.org & lists.mailman3.org) Any feedback or bug reports on weird looking stuff is welcome here or directly [on my PR][1] [1]: https://gitlab.com/mailman/hyperkitty/merge_requests/160 -- thanks, Abhilash Raj (maxking)

5 years, 10 months

[MM3-users] Re: Need help setting up mailman3 on ubuntu 20.04...

by Odhiambo Washington

On Mon, Mar 20, 2023 at 9:43 AM Marisa Giancarla via Mailman-users < mailman-users(a)mailman3.org> wrote: > I'm trying to get mailman3 up on ubuntu using the debian package. I did > the "apt install mailman3-full" and it does seem to have installed as > both the mailman3 & mailman3-web processes are running. I can use > "mailman create" in the command-line and "mailman lists" displays the > lists I created. > > > What I am having issues with is I don't see any entries in/etc/aliases, > and I don't know how to access the web interface (as either admin or > user). Can someone point me to what I need to do to finish it? > Thanks, > Marisa > Hi Maria, You will probably have to follow this old documentation to finish it: ``` https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan… ``` However, the latest supported installation method for _any_ platform is at: ``` https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… ``` It is a very straightforward method and the recommended one, supported by the developers. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 1 month

[MM3-users] Re: configuring moderators per list

by Dmitry Makovey

On 11/06/2017 03:17 PM, Abhilash Raj wrote: > Hi, > > > On Mon, Nov 6, 2017, at 02:33 PM, Dmitry Makovey wrote: >> We're trying to configure moderator per list and so far we were only >> able to add "superuser" accounts that can handle "Held messages", >> "Members", "Banned addresses" etc. >> >> Is there a way to create special account per-list to manage some of the >> aspects of particular ML without giving them all the permissions that >> Superuser comes along with? > > There are moderators and list owners in Mailman 3 too. Superusers can > add them under 'Members' tab in settings. > '/lists/<list_id>/members/moderator/' the the relative URL to add > moderators. > thanks. I do realize that this is a better security than MM2 approach, but we're trying to make MM3 a drop-in for existing MM2 and old behavior was that there was a single password for the moderator of ML which was not associated with user accounts really. That was the kind of thing we were thinking of. I'm guessing this is not a possibility in MM3 (and perhaps for the best)... -- Sr System and DevOps Engineer SoM IRT

7 years, 5 months

[MM3-users] Re: PSA: Avoiding spam-scanning outgoing mailman3 mail

by Mark Sapiro

On 5/8/20 2:11 PM, Mark Dadgar wrote: > > The easy fix was to edit the [mta] setting in mailman.cfg to deliver email via the submit port instead, which has no filtering applied to it: > > smtp_host: localhost > # using the submit port bypasses spamassassin filtering on outgoing list email > smtp_port: 587 > smtp_user: mm3send <— I created this user for this purpose > smtp_pass: <password-for-mm3send-user> > > This works great and can be applied to any email filtering. We tend to do this differently. For example, on mail.python.org which currently has 261 Mailman 2.1 lists and 134 Mailman 3 lists and sends about 135,000 individual messages per day from the two Mailman instances, we define in /etc/postfix/master.cf 127.0.0.1:8026 inet n - - - - smtpd -o smtpd_authorized_xforward_hosts=127.0.0.0/8 -o mynetworks=127.0.0.0/8 -o smtpd_recipient_restrictions=permit_mynetworks,reject -o smtpd_client_restrictions= -o smtpd_helo_restrictions= -o smtpd_sender_restrictions= -o smtpd_data_restrictions= -o receive_override_options=no_unknown_recipient_checks -o smtpd_milters=inet:127.0.0.1:8891 Then port 8026 only accepts locally generated mail and only does dkim signing (milter on port 8891) and essentially no other checks. Then in the [mta] section in mailman.cfg we only need smtp_port: 8026 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: Python 3.5 support?

by Abhilash Raj

On Wed, Jul 22, 2020, at 2:10 PM, Joel Lord wrote: > I'm looking through the recent changes to Core and Postorius and I keep > spotting what looks like removal of the test cases for Python 3.5. Is > the next release going to be dropping support for 3.5? Is this because > 3.5 is going EOL shortly or because there are changes in the upcoming > release that actively will not work on 3.5? I've tried to hold off on dropping support for 3.5 for as long as I can, the last release even though supported 3.5 in Core, didn't in Django apps(specifically, Hyperkitty). The main reason to drop support is that our dependencies have started dropping off support. For now, there is nothing in the Mailman source code that blocks 3.5, but that could change soon since I've really been waiting to use f'strings and other exciting features. Also, Debian and Fedora do have 3.7 or 3.8 in them at this point, so I am hoping this won't be a huge issue. > > -- > Joel Lord > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

4 years, 9 months

[MM3-users] Re: Migrating from old V2 server to new V3 server. Questions.

by Mark Sapiro

On 10/10/24 1:55 PM, jkoral(a)luc.edu wrote: > The old server is trying to send, but I end up getting an undeliverable message saying no connection could be made. I know port 25 is open because I can telnet to it. I'm wondering if I'm missing something in my configuration. Can you take a look? Thank you. > > Here are the active settings in /etc/postfix/master.cf: ... > smtp inet n - y - - smtpd This says port 25 is for smtpd and that's good. > And here are the setting I have in /etc/mailman3/mailman.cfg > # /etc/mailman3/mailman.cfg This is irrelevant as the message never gets to Mailman. On 10/10/24 1:58 PM, jkoral(a)luc.edu wrote: > Here are the results from netstat: > > tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 3876896/master And Postfix master process is listening on port 25. You say you can telnet to port 25. Can you do that from the old MM 2.1 server? Can you connect and receive the greeting and send `EHLO hostname` and get a good response? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 1 week

[MM3-users] Re: Please help - Held message is crashing mailman.

by Mark Sapiro

On 4/5/19 10:27 PM, Alex King via Mailman-users wrote: > Hi, > > I've used mailman a lot in the past, and decided to install mailman3 in > a recent install. I'm unimpressed so far, it seems buggy. > > Running on Ubuntu 18.04.2 LTS from packages, mailman3 3.1.1-9, > mailman3-web 0+20170523-14, python-django-postorius 1.1.2-3. > > After a few messages, I now can't go to the "Held Messages" in > postorius, I get a 500 error. > > I tried to interact on the command line, but could not work out how. > Reading > https://mailman.readthedocs.io/en/latest/src/mailman/docs/install.html > and > https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/shell.ht…, > I tried: > > # mailman shell > Welcome to the GNU Mailman shell > >>>> command = cli('mailman.commands.cli_withlist.shell') > Traceback (most recent call last): > File "/usr/lib/python3.6/code.py", line 91, in runcode > exec(code, self.locals) > File "<console>", line 1, in <module> > NameError: name 'cli' is not defined > > I did a lot of reading of the manual and googled, but I have no idea > where the cli object is supposed to come from.....? The documentation > is confusing. The line command = cli('mailman.commands.cli_withlist.shell') in <https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/shell.ht…> is dependent upon some behind the scenes setup to make the doctests work. Granted this is confusing, but basically all that does is set things up for the doctests to run the 'mailman shell' command. It is not intended to be run from within 'mailman shell'. > Anyway, after some trial and error, i found: > > # mailman shell > Welcome to the GNU Mailman shell >>>> list_manager = getUtility(IListManager) >>>> m=list_manager.get("committee(a)[redacted].org") >>>> from mailman.interfaces.requests import IListRequests >>>> requests = IListRequests(m) >>>> [x for x in requests.held_requests][0].id > 8 >>>> requests.get_request(8) > Traceback (most recent call last): > File "/usr/lib/python3.6/code.py", line 91, in runcode > exec(code, self.locals) > File "<console>", line 1, in <module> > File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", > line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File "/usr/lib/python3/dist-packages/mailman/model/requests.py", line > 120, in get_request > result.data_hash, expunge=False) > File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", > line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File "/usr/lib/python3/dist-packages/mailman/model/pending.py", line > 138, in confirm > value = json.loads(keyvalue.value) > File "/usr/lib/python3.6/json/__init__.py", line 354, in loads > return _default_decoder.decode(s) > File "/usr/lib/python3.6/json/decoder.py", line 339, in decode > obj, end = self.raw_decode(s, idx=_w(s, 0).end()) > File "/usr/lib/python3.6/json/decoder.py", line 355, in raw_decode > obj, end = self.scan_once(s, idx) > json.decoder.JSONDecodeError: Unterminated string starting at: line 1 > column 1 (char 0) > > It seems something was written out to disk that can't be read in for > some reason (assuming a json object on disk?) This is <https://gitlab.com/mailman/mailman/issues/385> which should be fixed by <https://gitlab.com/mailman/mailman/merge_requests/333>. The fix in in Mailman core version 3.2.0 > How do I debug this further? How do I find the json being decoded? Any > help would be appreciated. (I found mailman2 just worked, I was happy > with that.) The issue is in storing a pickled representation of the json encoding of 'rule_misses'. This gets very long if you have lots of header filters, and with at least the mysql backend gets truncated in the database which causes the Unterminated string error. I'm not sure what your options are for upgrading. The current Debian packages are all >= 3.2.0 [1], but Ubuntu doesn't get 3.2.0 until cosmic (18.10) [2]. [1] https://packages.debian.org/search?keywords=mailman3 [2] https://packages.ubuntu.com/search?keywords=mailman3 > (My colleague posted a bug about this I believe but I don't have the > link to that.) I haven't seen it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header.

by Mark Sapiro

On 10/22/21 8:51 AM, Marco Marinello wrote: > Hi everybody, > > as per subject, I'm getting this error in the hyperkitty log when mailman daemon tries to archive a mail. > I've setup the hyperkitty.cfg file with api_key = MAILMAN_ARCHIVER_KEY in settings_local.py but still nothing. > I've seen here and in GitLab issues some errors concerning a wrong api key but here it says that it wasn't sent at all. > All packages installed via pip install + latest .zip release, including mailman-hyperkitty. Currently running on apache with mod_wsgi_py3 without https. The following combinations should work: mailman-hyperkitty 1.2.0 with HyperKitty 1.3.5 mailman-hyperkitty <1.2.0 with HyperKitty <1.3.5 The following will not work: mailman-hyperkitty 1.2.0 with HyperKitty <1.3.5 mailman-hyperkitty <1.2.0 with HyperKitty 1.3.5 Do you see a message like 'The MAILMAN_ARCHIVER_KEY is now required to be sent over the Authorization HTTP header, you need to upgrade the mailman-hyperkitty package to 1.2.0 or newer.' In your Django log and/or your mailman.log? These will only be logged with HyperKitty 1.3.5 and mailman-hyperkitty < 1.2.0 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Mailing Lists

by David Newman

On 12/23/21 3:09 PM, John McDonald via Mailman-users wrote: > I am responsible for the mailing list of a local church. Recently the church was moved to using Mailman for this. When a simple message is created and sent to the mailing list most email addresses received it correctly but those with an Outlook or Hotmail account received attachments and not the message. There are three attachments and one of them has to be opened to view the message. > > Am I missing some setting? This is possibly unrelated to Mailman, and possibly happening because Outlook.com and Hotmail are both owned by Microsoft, and both are flagging your server as a spam source. You can verify this by checking your mail server's logs. Usually a big service like Hotmail or Gmail will embed a URL in the error message where you can go to apply to be whitelisted. If this is the problem, you may need to take additional steps (again outside of Mailman3) to be a good email server citizen, such as adding DKIM and SPF records in your domain's DNS. Unless you have both, Microsoft or Google may block your server. It might also be a Mailman problem, but since some subscribers do get postings, I'd start with this first. dn

3 years, 4 months

[MM3-users] Re: Problems getting MM3 to work

by Mark Sapiro

On 4/24/23 4:53 PM, Mark London wrote: > > Mark - I encountered the same problem and it wasn't clear from the > documentation what to do about it. > > So I eventually changed the name from example.com using the /admin link. > > But if I now set SITE_ID = 0, and restart the server, it is not happy > and tells me it encountered an error. > > raise > self.model.DoesNotExist(django.contrib.sites.models.Site.DoesNotExist: > Site matching query does not exist. I'm not sure about this. It may only work if there is more than one site. On the other hand, it requires that the requesting domain match a site. I.e., I think if the site's domain is example.com, but the request is from www.example.com, that could cause it to fail. Also, if proxying to a wsgi server, the web server has to pass the host. I.e., for nginx, proxy_set_header Host $host and for Apache ProxyPreserveHost On > I guess I should just let it be set to 1 and be done with it? - Mark Yes, I think so. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: Configuring sendmail without virtualtable? Is this possible?

by Andreas Schamanek

On Tue, 25 Apr 2023, at 11:01, Odhiambo Washington wrote: > On Tue, Apr 25, 2023 at 4:30 AM Mark London <mrl(a)psfc.mit.edu> wrote: >> https://gist.github.com/Maeglin73/72eb5b1e4ee66a383c2aa454726be9a5 > https://gitlab.com/mailman/mailman/-/issues/307#note_632495542 > You will have your solution - or not. I had to come up with a solution a year ago or so, and for reasons I unfortunately do not remember, suggestions from issue #307 did not work out for our sendmail. I ended up writing a Python script which accepts a message at stdin and hands it over to Mailman's LMTP. As such, it works almost like an in-place replacement for the MM2 /etc/mail/smrsh/mailman. I copied my script to /etc/mail/smrsh/mailman3 and changed aliases from e.g. mylist: "|mailman post mylist" to mylist: "|mailman3 post mylist" for any list that I migrated (while keeping MM2 running for old ones). I am not a programmer and I don't know Python. So, I won't share my script publicly for now, but it works for me, and anyone interested I am sure will find a way to contact me off-list. It's only my 2nd non-trivial Python script so far, so, no promises whatsoever ;) -- -- Andreas :-)

1 year, 11 months

[MM3-users] A few more MM3 questions

by Marc SCHAEFER

Hello, My migration from MM2 to MM3 seems near completion: I will do a few more tests and then tell the list admins to start testing. I have a few questions: 1) persistence: as I can regenerate the configuration files (mailman, mailman-web, hyperkitty), is all what's useful in the DB, or are some things in /var/lib/mailman3 worth saving? obviously messages to be moderated, hyperkitty failed messages, etc are stored there, but shall I assume that all mailing-lists configuration, all users configuration and all archives are in the DB? 2) I imported a list and all messages get a footer of: %(web_page_url)slistinfo/%(_internal_name)s which I guess changed between MM2 and MM3; however when I look at that list configuration in the web interface of MM3, I see no templates defined, nor any clue where this is configured: where may I change this? 3) is there a configuration somewhere that can allow someone to create a mailman web account ONLY if he is already referenced somewhere in a mailing-list, and not otherwise? (or to create accounts that need approvals from an admin before being usable?) also, can a non-yet-referenced e-mail From: still subscribe to a private list (confirm+moderate) via e-mail regardless of the above? Thank you for any pointers!

10 months, 3 weeks

[MM3-users] Re: using SSH/TLS with external MTA

by Roland Giesler

On 2024/07/28 17:06, Mark Sapiro wrote: > On 7/28/24 06:26, Roland Giesler via Mailman-users wrote: >> On 2024/07/28 00:39, Mark Sapiro wrote: >>> >>> What do you see in Mailman's smtp.log and in the mail.log on the >>> mail server? >> >> The smtp log is in syslog... > > The smtp.log I refer to is Mailman's smtp.log which is in Mailman's > var/logs/ directory. There are no entries in the /var/log/mailman3/smtp.log that get created when I try to log in (and authenticate) in Postorius. Jul 28 15:30:18 2024 (516) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Jul 28 15:30:18 2024 (516) Peer: ('192.168.161.103', 54464) Jul 28 15:30:18 2024 (516) ('192.168.161.103', 54464) handling connection Jul 28 15:30:18 2024 (516) ('192.168.161.103', 54464) EOF received Jul 28 15:30:18 2024 (516) ('192.168.161.103', 54464) Connection lost during _handle_client() Jul 28 15:30:18 2024 (516) ('192.168.161.103', 54464) connection lost Jul 28 15:50:22 2024 (1059) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Jul 28 15:50:22 2024 (1059) Peer: ('192.168.161.103', 34814) Jul 28 15:50:22 2024 (1059) ('192.168.161.103', 34814) handling connection Jul 28 15:50:22 2024 (1059) ('192.168.161.103', 34814) EOF received Jul 28 15:50:22 2024 (1059) ('192.168.161.103', 34814) Connection lost during _handle_client() The recent attempts I made where after 18:00.

8 months, 3 weeks

[MM3-users] Re: Congrats on the instructions for installation on ubuntu, what about migration?

by Mark Sapiro

On 10/8/24 5:45 PM, Bill Oliver wrote: > > Is there a tutorial/instructions on migrating data from an old system > to a new one? It's actually not the end of the world if I don't get > all the old emails transferred, but I'd like to get the email addresses > of the participants moved over easily... I believe that I set it up > in 2020, but did not do any version upgrades since then... There's no explicit doc, but there are some posts in the archives of this list, e.g. <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. The easiest scenario is if you want to migrate everything. You just dump the database on the old server and load it on the new one using the database manager's tools. If you only want to move some, but not all lists, it's more complicated, but possibly the easiest thing is to migrate everything and then delete the unwanted lists and their archives from Postorius and HyperKitty. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 2 weeks

[MM3-users] Re: confirm mail rejected

by Mark Sapiro

On 10/02/2017 05:21 AM, Marc Sluiter wrote: > > In the logs I see that postfix is trying both "liste-confirm+extension@domain" and "liste-confirm@domain" for another lookup map of type mysql (so "recipient_delimiter" is working), but not for the mailman map of type regexp. > Just a wild guess, I didn't find anything about it: can it be that “recipient_delimiter" doesn't work for “regexp" maps? I think so. See the note I just added at <https://gitlab.com/mailman/mailman/issues/401#note_42163915>. > For now I worked around this issue by manually modifying the confirm regex in "postfix_lmtp” to /^liste-confirm\+.*(a)domain\.tld$/ > > Does anyone have an idea why the regexp map isn’t working for me and at least 1 other user (see https://gitlab.com/mailman/mailman/issues/401)? > Would my workaround be a long term solution which could be implemented in mailman? That would mean that mailman could work independent of the “recipient_delimiter” setting (or do I oversee something?) I'll be working on a fix. My inclination is to change all the regexp -confirm and -bounces table entries from, e.g., /^list-bounces(a)example\.com$/ to /^list-bounces(+.*)?(a)example\.com$/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 6 months

[MM3-users] Re: Dealing with hyperkitty spool files (was Re: Re: Fwd: [Django] ...)

by Mark Sapiro

On 3/2/21 11:33 PM, David Partain via Mailman-users wrote: > > In this regard, I have three questions: > > 1. Am I correct in assuming that I can just use my favorite editor (vi) > to remove the offending characters from the file? No. The file is a Python pickle and you can't edit it. You would need to get the message and the metadata from the pickle (you could at least view it with the `mailman qfile` command), edit the message and then re-pickle the message and metadata. > 2. If I cannot find the offending character, is it safe to just remove > the file so that subsequent archiving can proceed? Yes. > 3. Can I do something to make hyperkitty go through the spool? I don't know what you mean. Every time there is a new post to any list, Mailman core invokes the mailman_hyperkitty process to archive the message and the forst thing that process does is attempt to reprocess all the messages in the spool which fails because of the utf8mb4 issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: Broken web interface Ubuntu 20.04

by tim＠thecutts.org

Mine is doing the same thing. It happened yesterday morning, when some packages were upgraded by the system. I'm glad it's not just me this has happened to. It looks like someone pushed an apache2 package which broke things on the 28th September, and another has been pushed yesterday, but it's still broken. From my logs, these packages got updated the first time: Start-Date: 2021-09-29 06:38:15 Commandline: /usr/bin/unattended-upgrade Upgrade: libapache2-mod-proxy-uwsgi:amd64 (2.4.41-4ubuntu3.4, 2.4.41-4ubuntu3.5), apache2-data:amd64 (2.4.41-4ubuntu3.4, 2.4.41-4ubuntu3.5), apache2-bin:amd64 (2.4.41-4ubuntu3.4, 2.4.41-4ubuntu3.5), apache2:amd64 (2.4.41-4ubuntu3.4, 2.4.41-4ubuntu3.5), apache2-utils:amd64 (2.4.41-4ubuntu3.4, 2.4.41-4ubuntu3.5) End-Date: 2021-09-29 06:38:52 and then the next day: Start-Date: 2021-09-30 06:33:46 Commandline: /usr/bin/unattended-upgrade Upgrade: libapache2-mod-proxy-uwsgi:amd64 (2.4.41-4ubuntu3.5, 2.4.41-4ubuntu3.6), apache2-data:amd64 (2.4.41-4ubuntu3.5, 2.4.41-4ubuntu3.6), apache2-bin:amd64 (2.4.41-4ubuntu3.5, 2.4.41-4ubuntu3.6), apache2:amd64 (2.4.41-4ubuntu3.5, 2.4.41-4ubuntu3.6), apache2-utils:amd64 (2.4.41-4ubuntu3.5, 2.4.41-4ubuntu3.6) End-Date: 2021-09-30 06:34:32 So clearly something's gone wrong with Ubuntu's apache2 packages, and it's broken something quite badly for Django and/or Postorious. But I don't know enough about how Django or WSGI work to be able to debug this. When I look at the mailman-web-logs, the urls that postorious puts into the page don't honour the POSTORIOUS_TEMPLATE_BASE_URL variable in the mailman-web.py file any more. Tim

3 years, 6 months

[MM3-users] Re: Editing "automatic responses" tab i Postorius does not work

by David Krantz

But this one is already exposed. But I cannot change it anyway as the tab requires URIs for the different templates to allow saving. I do not use those URIs as I have configured the defaults as I like them. I tried once and it failed so I decided to set the defaults instead. cheers. // David On Sun, May 21, 2017 at 3:48 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/21/17 5:22 AM, David Krantz wrote: >> >> I am trying to change e.g. the value of "notify admin on membership >> changes" through postorius. > > > There are still many settings not yet exposed in Postorius. We are > painfully aware of this and will probably be working on some of this at > the PyCon sprints starting tomorrow. > > Until we get more of these addressed, you will need to use tools like > "mailman withlist" to set these things. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

7 years, 11 months

[MM3-users] so many instances of mailman.cfg

by Christian Stalberg

Question: I've five copies of mailman.cfg on my box. How can I tell which one is actually being used please? -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, November 26, 2021 11:06 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: mass subscribers disablement!? On 11/26/21 9:39 AM, Christian Stalberg via Mailman-users wrote: > After the first time where users were unsubscribed automatically, I > added back one at a time all the subscribers who were unsubscribed. > Now they have all been unsubscribed again automatically. They are > valid working email addresses. How can I stop this behavior from occurring please? Do you have the bounce processing notifications `Notify owner on disable` and `Notify owner on removal` set to `Yes`. If not, set them. Then, what's in the notices you receive? You might also consider setting `verp_probes: yes` in the `[mta]` section of mailman.cfg. This will avoid some issues with users being disabled/unsubscribed due to list posts being rejected as spam. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 4 months

[MM3-users] Re: Mailman3 / Exim4: Router fails

by ceo＠sartrack.nz

Hi Mark. I have no idea if that file exists. As far as I can see, it cannot exist. It must be some virtual file. And it would have to be created by Mailman3 just for a short moment, for Exim to pick it up. It looks very weird to me, but the old Mailman 2.1 worked in the same way.... and I can no longer see how that would have worked as it has been wiped out by the OS upgrade. And yes, I generated the mailing list as (from memory) : mailman3 create templist(a)sartrack.nz templist.lists.sartrack.nz (?) I tried to create it as: create templist(a)sartrack.nz templist(a)sartrack.nz but it would not accept that. This all was done while I war trying to *import* the existing list, but this keeps failing with a 'mailing list does not exist' until I after much Googling found a comment somewhere that I first has to Create a list (not to be found in any documentation). Somehow Mailman must create this weird file for Exit to be able to read it, and then it would have to dissapear, because it makes no sence if that file would be sitting in the mail 'lists' directory. I do not understand this system at all.

1 year, 11 months

[MM3-users] Re: Set domain inactive / archive import from other domain.

by Mark Sapiro

On 09/18/2018 07:14 PM, Johannes Winter wrote: > Am Sat, 15 Sep 2018 09:31:53 -0700 > schrieb Mark Sapiro <mark(a)msapiro.net>: >> >> Why do you think the domain name is an issue? Perhaps the issue is >> there is already one or more messages in the archive and the messages >> you are importing are older. If you don't specify --since to >> hyperkitty_import it won't import messages older than the newest >> message in the existing archive. > > > Thanks a lot for your excellent and fast support! That was the problem. > Maybe it would be wise to include that into the help of the > hyperkitty_import command? > > Although this command successfully imported 3/4 of the huge (1.7GB) > mbox, it stumbled upon an error after some minutes: > https://gitlab.com/mailman/hyperkitty/issues/200 I have added a comment there which see. I'll "fix" this and I'll update the help to note that if not specified, --since defaults to the date of the newest existing message in the archive. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

[MM3-users] Re: The message is larger than the 40 KB maximum size

by Mark Sapiro

On 9/21/20 3:01 PM, Mohsen Masoudfar wrote: > It seems something is fundamentally wrong with Hyperkitty: > >>From /var/log/mailman3/mailman.log > > --- > 49 Sep 21 21:49:25 2020 (24925) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> > 50 <h1>Authorization Required</h1></body></html> (401) > 51 Sep 21 21:49:25 2020 (24925) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> > 52 <h1>Authorization Required</h1></body></html> (401) > 53 Sep 21 21:49:25 2020 (24925) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> > 54 <h1>Authorization Required</h1></body></html> (401) > 55 Sep 21 21:49:26 2020 (24918) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/archive: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2. 0//EN"> ... I doubt this has anything to do with the missing approved message, but what's in you mailman-hyperkitty.cfg file for api_key and does that match your settings_local.py setting for MAILMAN_ARCHIVER_KEY except for being quoted in settings_local.py and not in mailman-hyperkitty.cfg. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Onyeibo Oku

On Tue, 25 Oct 2022 14:46:06 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/25/22 12:56, Onyeibo Oku wrote: > > > > I must be missing necessary policy modules for mailman or I am > > missing relevant parts of the tutorial that deals with SELinux. > > Where do I go from here? > > > Create the necessary SELinux rules to allow `mailman` to access what > it needs to. Roger that. There is progress beyond the previous report (after setting mailman_lock_t on '/opt/mailman/mm/var/locks'. Systemd fails again on '/opt/mailman/mm/var/logs/mailman.log' I applied mailman_log_t SELinux policy to that folder. Unlike the previous AVC, that didn't fix it. PermissionError: [Errno 13] Permission denied: '/opt/mailman/mm/var/logs/mailman.log' AVC avc: denied { append } for pid=774 comm="mailman" name="mailman.log" dev="sda" ino=2070696 scontext=system_u:system_r:init_t:s0 tcontext=unconfined_u:object_r:mailman_log_t:s0 tclass=file permissive=0 > > I don't know if anyone on this list can help you with that. > > Note that if `mailman` is currently a `normal user` as opposed to a > `system user` making it a system user might help. See `man usermod` > Mailman user is a System User here. Regards Onyeibo

2 years, 5 months

[MM3-users] Re: (Custom) Plugins: Proper file path(s) for adding a handler?

by Abhilash Raj

On Wed, 25 Oct 2023, at 11:23 PM, Abhilash Raj wrote: > On 10/25/23 01:04, Thomas Ward via Mailman-users wrote: >> Running into some nasty issues. >> >> I have a structure like this, installed as a package in the workspace >> once installed by pip in the venv: >> >> mailman_customizations/ >> __init__.py >> hooks.py <-- plugin definition in here as MailmanCustomizations >> for class name >> handlers/ >> __init__.py >> handlers.py <-- custom handler in here >> pipelines/ >> __init__.py >> pipelines.py <-- custom pipelines which implement the handlers >> here. >> >> However, whenever I specify this in config with this clause: >> >> [plugin.MailmanCustomizations] >> class: mailman_customizations.hooks.MailmanCustomizations >> enabled: no >> > > Change this to > > [plugin.mailman_customizations] > class: mailman_customizations.hooks.MailmanCustomizations > enabled: yes FWIW You can also do: ``` [plugin.MailmanCustomizations] class: mailman_customizations.hooks.MailmanCustomizations enabled: no component_package: mailman_customizations ``` In ^ case, the "name" of the plugin, "MailmanCustomizations" in this case, doesn't matter and can be anything and mailman will use "component_package" as the base module to look for components. -- thanks, Abhilash Raj (maxking)

1 year, 5 months

[MM3-users] HyperKitty: discussions not updating, misreporting stats

by Cameron Smith

These are a couple of HyperKitty issues that I have talked about in August [1]. I’ve been doing a bit more experimentation in the last few days and am reporting my findings. The two issues are: — Missing messages: HyperKitty doesn’t show all of the messages in a discussion - Misreporting of discussion statistics: HyperKitty doesn’t update the number of participants and comments in a discussion I’m using the latest Docker setup. Neither of these issues are solved by updating or rebuilding indexes: sudo docker exec mailman-web ./manage.py update_index sudo docker exec mailman-web ./manage.py rebuild_index However, if I stop and then restart the containers (sudo docker-compose down; sudo docker-compose up -d), the discussion statistics are updated and properly display the number of participants and comments in all discussions. This does not, however, solve the problem of missing messages. I have discovered two methods of displaying the missing discussion messages: add a new message to the thread in HyperKitty; I’m not convinced that this works *every* time, but it at least works *most* times run the yearly cron job; this seems to work *every* time: sudo docker exec mailman-web ./manage.py runjobs yearly [1]: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Cameron Smith

7 years, 5 months

[MM3-users] Re: Digest Formatting

by Stephen J. Turnbull

mailman(a)manygoodideas.com writes: > 1) Is there a way to trigger a digest for a user (for testing > purposes)? Specifically, is there a function that can be > revealed via the REST api to an interface like Postorius and > Affinity? You can't trigger a digest to an individual member (unless they're the only active digest subscriber to the list, of course, so you can experiment on a test list if it's not specific to a particular list). I thought there was a way to trigger immediate distribution of a digest immediately, but I guess I'm remembering that from Mailman 2. Neither the Postorius management interface nor the core documentation suggests there's such a trigger in Mailman 3. > > 2) I have customized list:member:digest:header, but am not seeing > the custom text where I thought it should be. The documentation > seems to imply that both list:member:digest:header and > list:member:digest:footer surround each message in the digest Which documentation do you mean? As far as I know (Mark will have authoritative information if I'm wrong), the digest header and footer appear at the top and bottom of the *whole* digest message (ie, once each per digest), not surrounding or in the bodies of the component messages.

4 years, 5 months

[MM3-users] Weblate spanish translation of templates (was: Re: spanish localization)

by Guillermo Hernandez (Oldno7)

On 14/2/21 2:42, Abhilash Raj wrote: > You can actually translate the templates in Weblate too. That is > actually the whole > reason to go with monolingual template format in Mailman Core. > > Mailman uses the template file's name as the msgid for translations > and all in-tree > templates are copied into English's .po file when we re-generate them. > > For example in here: > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/messages/es/LC… > > > The english .po file is considered as reference in Weblate and used > for source string. I want to contribute making it via Weblate, since it is already done via gitlab repository (thanks to Mark Sapiro for approving the merge requests), making a revision and editing them if needed, but I cannot see how to make it in a consistent way, as I cannot determine how to edit each template in the Weblate UI. I've tried to access via the file name (accessing via msgid as for your example) of the template... but I cannot access them by this way, or I'm missing something. Can you, please, point me in the right direction on how to do it?

4 years, 2 months

[MM3-users] Re: Lost in default style creation

by Mark Sapiro

On 6/2/22 02:44, kenneth.karlsson(a)eco.cept.org wrote: > > It shows me its there, then i proceed to quit() and go back in to the shell, and do this: >>>> quit() > ecoadmin@list01:/etc/mailman3$ sudo mailman shell > Welcome to the GNU Mailman shell > >>>> from zope.component import getUtility ... More recent versions of mailman shell will tell you what the problem is. ``` $ ./mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> ``` You need to exit the shell with control-D or issue a commit() before you exit. Also, NEVER run any `mailman` commands as root. Always run `mailman` as the Mailman user. Running `mailman` as root can create files owned by root that can't be read/modified by the Mailman user. More recent versions will tell you ``` $ sudo ./mailman Usage: mailman [OPTIONS] COMMAND [ARGS]... Try 'mailman -h' for help. Error: If you are sure you want to run as root, specify --run-as-root. ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: Postfix-Fehler mit mailman-web

by Jens Günther

Thank you Abhilash, probably it's hard to tell, but somehow the container started with a different IP now. Do you have any clew, how this can happen? The network part is as follows: networks: mailman: ipv4_address: 172.22.0.4 -> but it has 192.168.176.6 Thank you in advance. Am 28.08.23 um 14:11 schrieb Abhilash Raj: > On 8/28/23 13:51, Stephen J. Turnbull wrote: >> Jens Günther writes: >> >> > 2023-08-26T08:21:59.522238+02:00 postfix/smtpd[2843414]: NOQUEUE: >> > reject: RCPT from unknown[192.168.176.6]: 450 4.7.25 Client host >> > rejected: cannot find your hostname, [192.168.176.6]; >> > from=<$admin(a)mydomain.de> to=<$recipient> proto=ESMTP >> helo=<mailman-web> >> >> There are a bunch of $myxxxx variables in Postfix, I think $myhosts >> might be the right one. > > It should be under $mynetworks as per documentation: > > https://asynchronous.in/docker-mailman/#postfix > > Also, official postfix docs says the same: > > https://www.postfix.org/BASIC_CONFIGURATION_README.html > > > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to jens.guenther(a)posteo.de

1 year, 7 months

[MM3-users] Re: Two trivial questons:

by Bill Oliver

Whoops, and now that I'm in, I see where the SITE_ID stuff comes in. I just created the doman, and it works. So.. sorry to bother you. I seem to be good to go... billo On Wed, 2024-10-09 at 20:03 -0400, Bill Oliver wrote: > > I take that back again. I found the error. I had nothing listed in > CSRF_TRUSTED_ORIGINS. I filled that in and it ran like a charm. > > So, now it's just the SITE_ID thing... > > billo > > > On Wed, 2024-10-09 at 19:22 -0400, Bill Oliver wrote: > > > > I take that back. I went back and made another superuser using > > mailman-web create superuser. But... I still get bounced with the > > error: > > > > > > Forbidden (403) > > CSRF verification failed. Request aborted. > > > > More information is available with DEBUG=True. > > > > > > > > my uwsgi.log generates: > > > > [pid: 1385|app: 0|req: 14/22] 127.0.0.1 () {52 vars in 1078 bytes} > > [Wed > > Oct 9 23:15:17 2024] GET /accounts/login/?next=/mailman3/lists/ => > > generated 8204 bytes in 33 msecs (HTTP/1.0 200) 11 headers in 509 > > bytes > > (1 switches on core 1) > > [pid: 1385|app: 0|req: 15/23] 127.0.0.1 () {62 vars in 1230 bytes} > > [Wed > > Oct 9 23:15:27 2024] POST /accounts/login/ => generated 1019 bytes > > in > > 2 msecs (HTTP/1.0 403) 8 headers in 268 bytes (1 switches on core > > 0) > > > > So it wasn't that I forgot the superuser name. It's getting > > denied. > > That's all I got. > > > > Any help would be appreciated... > > > > billo > > > > > > On Wed, 2024-10-09 at 19:04 -0400, Bill Oliver wrote: > > > First: > > > > > > Last night I got everything installed and, I think, working. > > > Unfortunately, I forgot to write down the name and password of > > > the > > > superuser I created. I know what I put in as password, but I > > > cant' > > > remamber the name of the superuser. > > > > > > I know I could just create another superuser with "mailmanweb > > > createsuperuser" but I was wondering if there was a "mailmanweb" > > > command for *listing* superusers. > > > > > > If not, I'll just make another superuser... > > > > > > Second: > > > > > > I have the "example.com" error in the login screen. The > > > instructions > > > state that this is a problem with making SITE_ID=1. Okay, but I > > > don't > > > know what to change it to. I tried SITE_ID=2 on a lark and > > > everything > > > broke, and the instruction say not to do SITE_ID=0. Apparently > > > it > > > has > > > to be an integer (I also tried putting in site name and got that > > > error). So... where do I change it? > > > > > > Thanks! > > > > > > billo > > > _______________________________________________ > > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > Archived at: > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > > > > This message sent to billo(a)billoblog.com > > > > _______________________________________________ > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > Archived at: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > > This message sent to billo(a)billoblog.com > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to billo(a)billoblog.com

6 months, 2 weeks

[MM3-users] after upgrade: OperationalError: no such column: hyperkitty_mailinglist.archive_rendering_mode

by Hans Mayer

Dear All, recently I did a system os upgrade debian 11.8 -> 12.4 / bullseye -> bookworm This did also upgrade Mailman3 version 3.3.3 -> 3.3.8 as a used the packages which came with Debian OS. Initially after the upgrade I had some troubles with the MM3 services to start, but I fixed this. Now almost everything is running. Only the Archives are not working. The browser shows a server error, when I look at the mailman-web.log I see ERROR 2024-01-31 15:14:14,403 2699563 django.request Internal Server Error: /mailman3/hyperkitty/ Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 423, in execute return Database.Cursor.execute(self, query, params) sqlite3.OperationalError: no such column: hyperkitty_mailinglist.archive_rendering_mode When I check the schema I find such a column in table "mailinglist" I assume there is only one solution, to uninstall and delete everything and start from scratch. Or is there a way the check all tables with a script and do an table update for missing columns ? Or a partial installation of hyperkitty, as I don't care about the archives. I am using sqlite3 as DB backend. Kind regards Hans --

1 year, 2 months

[MM3-users] Re: adding imprint / private policy link to postorius

by Thomas Stein

Thanks Abhilash. Will have a look. On 2020-09-03 07:09, Abhilash Raj wrote: > On Tue, Sep 1, 2020, at 11:17 PM, Thomas Stein wrote: >> >> Hello one and all. >> >> Is it possible to add an imprint link to the postorius start page? I >> guess it is, but it would be >> nice if someone could me point to the right direction / documentation. >> Something like they have: >> >> https://lists.openrailwaymap.org/mailman3/postorius/lists/ >> > > There isn't an official way to do that, but you can patch your > installation to update the footer. > > This[1] is the location and file you want to update and you can insert > simple HTML there. If you are using system packages it should be > somewhere in the `/usr/lib/python3/dist-packages` directory and > in `lib/site-packages` if you are using a virtualenv based > installation. > > > https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/templates/… > >> cheers, t. >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >>

4 years, 7 months

[MM3-users] Re: is there a mailman command/setting to periodically clean archives?

by Mark Sapiro

On 1/4/22 2:59 PM, David Newman wrote: > > As a followup: Is there any need or advantage to running both the > prototype and hyperkitty archivers? Only if you want to keep all the raw messages. HyperKitty only stores the message_id, subject, date, in_reply_to and sender information. Other header information is not stored in HyperKitty. The prototype archiver is intended to store messages to be delivered to some other third party archiver. > I did an installation following the venv directions, and it looks as > though the system now uses both archivers. > > If this is a duplication of effort and storage, is it safe to disable > the prototype archiver like this: > > # /etc/mailman3/mailman.cfg > .. > [archiver.prototype] > enable: no > > and then delete anything under here? > > /opt/mailman/mm/var/archives/prototype/ Yes, but you also have to go through all the lists Settings -> Archiving pages and uncheck prototype under Active archivers. You could also do this with a database query like UPDATE listarchiver SET _is_enabled = 'f' WHERE name = 'prototype'; -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Managing users in postorius

by Mark Sapiro

On 9/25/24 11:08, Lieuallen, Thomas Otis wrote: > I don’t seem to have very much control with the site admin account. I’d like the ability to add a secondary address for a user instead of talking them through the process of doing it themselves. Is there a way that I’m not aware of? In the Django admin web UI under Email addresses, you can add an address and associate it with an existing user. > Additionally, when I look up users and choose ‘manage’, it only lists a person’s member roles. It doesn’t list any other roles (owner/admin, moderator, etc). Any way to fix that? It should list both member and nonmember rolls. If you scroll down past Subscriptions to Ownerships, it lists owner and moderator rolls. > I’m also curious what the process would be for merging two postorius accounts into one? My thought process was that I should remove one and then have the user add that email address to the other account. But, if you delete the account, it will unsubscribe the user. In the Django admin UI, you can edit the user associated with an email address under Email addresses -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 4 weeks

[MM3-users] Good MM hosts for customized code?

by Steven Clift

E-Democracy.org is plotting a test move from GroupServer.org (end of life coming) to MM3. We have certain technologies we've embedded into GroupServer, like volume based posting limits on our political forums (no more than X posts in y hours per member ... typically 2 or 3 posts in 24 hours), inserting standard "who made this post" in the email footer with links to the user profile for context assuming email is forwarded as well as the web archive url to that post. We know that we do not want to be in charge of email deliverability and we don't yet have an Mailman aficionado in our volunteer team. So ideally, we'd find the right Mailman host where we can use our own selected domain (@opengroups.org perhaps) and whether we hire coders to help out with custom tech OR have volunteer coders (interested in local online communities? AKA hate that Facebook and NextDoor host most of these, let me know :-) ), we'd like to have the right set up to allow us to experiment. Advice? Thoughts? Thanks, Steve Steven Clift <http://stevenclift.com> - Founder and Volunteer, E-Democracy.org clift(a)e-democracy.org - +1 612 234 7072 @Democracy <http://twitter.com/democracy> - Facebook <https://www.facebook.com/stevenlclift> - LinkedIn <http://linkedin.com/in/netclift>

4 years, 1 month

[MM3-users] Re: Any known limit of number of lists that one can be owner/member of?

by Mark Sapiro

On 5/8/19 3:33 AM, Alan So wrote: > We have just migrated hundreds of lists from Mailman 2 to Mailman 3. It was smooth in most of the cases. However, we just notice that there are some abnormal behaviour of Postorius for particular users who are owner/member of a large number of lists. We further look into a particular user who is owner of 84 lists. When the user login Postorius, only 50 lists are displayed no matter what the number of "Results per page" is chosen. Prev/Next page cannot be clicked as there is only 1 page. See <https://gitlab.com/mailman/postorius/issues/335> > When I use the following mailman client snippet, it also displays the same 50 lists: > > lists = client.find_lists('xxx(a)yyy.com', 'owner') > for m_list in lists: > print(m_list.fqdn_listname) > > Did we hit any limit of find_lists? Is it a bug or are something wrong during the migration? find_lists defaults to count=50. What happens if you do lists = client.find_lists('xxx(a)yyy.com', 'owner', count=100) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

[MM3-users] Re: Documentation for transferiering a list between mm3 and mm3

by Mark Sapiro

On 2/26/21 10:09 AM, Brian Carpenter wrote: > On 2/26/21 11:50 AM, Johannes Winter wrote: >> I didn't find any documentation on how to export list data from mm3 and >> import it into another mm3 instance. Have I missed something, or is it >> yet nonexistant? > > If you are referring to List Settings, then I don't think you can. As > Peter pointed out, you can export/import your list roster but I don't > believe that includes moderators/owners which is problematic. If you > wanted to migrate archives, then you can download an entire archive via > Hyperkitty which is exported in mbox format. You can then import that > mbox file into your new Mailman 3 list. Brian is correct. Essentially, you would need to run database queries to get all the relevant data from the database and then add it to the database of the new instance. A tool could be created to do the export and import, but it doesn't currently exist unless some user has developed one and not reported it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: Changing subscription address

by Stephen J. Turnbull

Abhilash Raj writes: > The existing subscription workflow is a multi-step process that can be > paused and resumed. We pause when we send out a confirmation > email and then resume when that confirmation token is somehow > processed via email or API. So, post receiving the confirmation and > before actually subscribing, we can se the address as primary if the > user doesn’t have one and subscribe user as inhert. We don’t do any > of that if user already has chosen a primary address and it doesn’t > match the current address. OK, it sounds like we're thinking basically the same process, just using slightly different words to describe it (and mine have definitely been inaccurate about current logic at points, adding to the confusion :-P ). > Also, mass-subscribe and import does allow you to verify an address by > clicking this “Pre-verified” checkbox, which can be useful if you are > migrating from a different service or you exported a list of users from > somewhere you know to be valid. I wasn't aware of that. I haven't yet done a mass-subscribe from Postorius (I have a bunch of scripts for generating mailing lists from student rosters and just retargeted them to the REST API :-). Steve

4 years, 1 month

[MM3-users] Re: Installation -- error on mailman-web migrate

by Mark Dale

An update. More on following the installation instructions at: https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… ========== I found the mailmanweb.log at "/opt/mailman/mm/var/logs" rather than "/opt/mailman/web/logs". So I edited the file -- /etc/mailman3/settings.py ... #STATIC_ROOT = '/opt/mailman/web/static' STATIC_ROOT = '/opt/mailman/mm/var/static' #LOGGING['handlers']['file']['filename'] = '/opt/mailman/web/logs/mailmanweb.log' LOGGING['handlers']['file']['filename'] = '/opt/mailman/mm/var/logs/mailmanweb.log' ... and re-ran the "mailman-web migrate" ... root@mx:~# su mailman (venv) mailman@mx:/root$ mailman-web migrate ... and then at the beginning of many errors printed to screen I now have... /opt/mailman/venv/lib/python3.9/site-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. Completely not comprehending the above doc (and being absolutely clueless about django), I blindly added "retry: 30" ... root@mx:~# nano -c /opt/mailman/venv/lib/python3.9/site-packages/django_q/tests/settings.py # Django Q specific Q_CLUSTER = { "name": "django_q_test", "cpu_affinity": 1, "testing": True, "log_level": "DEBUG", "django_redis": "default", "retry": 30, } ... but no joy. Is it me or are there some pieces missing from the documentation?

3 years, 7 months

[MM3-users] Re: username

by bryan.kartzman＠yu.edu

Thank you Steve for your reply. I have created from scratch in mailman 3 all the lists that were on the old mailman 2 server. So now I would like to pre-populate Django users for all the moderators and owners by creating accounts using their University NET account name and linking them to their University email address (what I used for their owner/moderator address). Unfortunately, its not simple because their NET username is a short, up to 8 character, username whereas their email address is first.last(a)yu.edu. I have access to the university database which correlates both so I will be able to feed both to whatever script will do this. The university does use SSO for many applications and I was asked by upper management of the IT department to try and implement it here. I'm still trying to understand your reply to my SSO question from last week (my SSO knowledge is limited and I'll have to read up on Shibboleth, SAML, as well as Django) so for now I'm thinking to not use SSO so that I can get things started and then transition to SSO later. If you have any pointers as to where to read up on SSO, SAML, Shibboleth and also on Django please point me in the right direction.

1 year, 10 months

[MM3-users] Automatic migration from Mailman 2.1 (Debian buster) to Mailman 3 (Debian bookworm)

by schaefer＠alphanet.ch

Hello, I already have some success in auto-migration from Mailman 2.1 (Debian buster) to Mailman 3 (Debian bookworm), using a new container (not upgrading the existing installation, which is obsolete e.g. 32 bit x86). I am doing this using custom scripts. The idea being to be able to import most of the existing configuration and archives, let the list administrators test the new system, and progressively advertise this to users. Then, the old container will be disabled. The basic stuff works (From: domain is OK, HTTP transport works, mail go out, etc) I however bumped into the following problem: How may I automatically (from the command line) replace the example.com which is displayed in the web interface and in the From: comment field of the e-mails (the address itself is OK) -- I only found documentation about changing through the GUI so far. Any pointer? Also, I have a question: if I import my 2.1 config for each ml, will DKIM work-arounds work (e.g. replace This User <user@domain> by This User user@domain <the-mailing-list>) ? Will Mailman 2.1 it required some config changes and also I had to modify mailman using a Debian diversion, AFAIR. Thank you for any input.

10 months, 4 weeks

[MM3-users] Re: Avoiding non-members to be saved.

by Guillermo Hernandez (Oldno7)

On 8/8/21 11:51, Stephen J. Turnbull wrote: > Guillermo Hernandez (Oldno7) via Mailman-users writes: > > > I find it very convenient too, but it concerns me that spammers, > > really "profesional" spammers and senders of phising mail change > > the forged address and sender domain too rapidly to track them. As > > of it, the non-member database is growing more and more. It could > > be a "monster" in two or three years... > > Well, let's think that out. I think we allocate a 255-byte text field > for email addresses, another 255 bytes for display names, and I can't > imagine that including the rest of the data fills as much as 1k, even > including indicies and other database optimization overhead. So if > you get a million spam messages to your lists, each from a unique > address, that's only one gigabyte. To get a million spam messages in > three years, you'd need to get almost a thousand per day that get > through your MTA's filters to Mailman's moderation queue, which is the > only place this automatic construction of nonmembers takes place. I > think your moderators would let you know about that long before your > disk fills up. You are absolutely right. I am the problem... well, my background of developing from the eighties of the last century, when 1k (no mistake here) meaned a difference. > > I'm not making fun of you, Never thought that. > I'm explaining why I don't think this is a > high priority for us, and why you don't need to worry about monster > databases, either: the human resources just for looking at the queue, > let alone taking action, will be a constraint long before the disk or > CPU consumption for the address database is. If there's something > wrong with my analysis, let me know, but as far as I can see, if the > spam flood to your lists gets to that scale, the first worries are > denial of service and admin exhaustion. As usual, the best answer is > to stop the barbarians at the gate (ie, the MTA). Yes... that's the point where I expurge most of that (discarding completely email from domains that will never send a legitimate email to our lists, and in a few cases entire .XXX areas) to "normal" addresses. But I have to confess that I relayed in the mailman control of subscriptions for that in the lists. And it all went well until I made a security hole with one non-member address > > I guess if the list is configured to automatically discard all posts > from non-members, we could optimize away the non-member creation. But > this seems like a relatively rare case, and if there were non-local > bans on addresses, it might not be a good idea anyway. And that's exactly the case of the list where a malicious mail get into: it's a private list with "discard all non subscribers addresses", but there was a legacy address imported from mailman 2 that had permission to send mails (and I was not aware)... and a bastard spammer forged it (well, it was one of many tries with different origin addresses). My fault completely. But this is a unique case in now more than 8 months using mailman3 (and more than 12 years using mailman). Being that list private and non publicily available, I suspect that one subscriber address book has been hijacked, and I can expect some crap from a forged subscriber address. But that is another story... Thanks a lot, again, for all your explanations and good work. I'm always grateful to all of you. > > In theory, we could even arrange to do the lookup at moderation time, > although we currently do it at mail receipt time. That would allow a > moderator to ban the addressee on list A and then not even see the > post when they go to check on list B. I suspect even professional > spammers don't bother to create a unique sender address for each > recipient! Obviously, this kind of service would require putting the > nonmember addresses in the database, at least temporarily. > > Steve > --

3 years, 8 months

[MM3-users] [Mailman-Users] Listservers currently hosted with EMWD - urgent request for assistance

by Stephen J. Turnbull

Note: Reply-To set to mailman-users(a)mailman3.org. Please check that any replies are addressed to that list, and not mailman-users(a)python.org. Jonathan, FWIW, I haven't heard anything. I have 3 students submitting MS/PhD theses in less than (checks watch) 18 hours, but after that I'll see if I can find out anything. I wouldn't bet on it, though, as I don't think anyone here has a connection to the Carpenter family or whoever is left of the EMWD staff. I assume you have checked the emwd.com website? > We have our listservers hosted with EMWD which stopped working on > 23 December. What does "stopped working" mean? I assume that list traffic is no longer being forwarded to subscribers, but perhaps other services are working. It may help if you can answer the following questions. 1. Are you using the GNU Mailman-supplied Postorius/HyperKitty combination for administration and archiving, or EMWD's proprietary "Harmony" (Affinity/Empathy) platform? 2. Can you see archives (if any)? 3. Can you log in to the administrative interface? 4. Is mail to the lists being returned to sender, or just disappearing into the void? 5. You mention an automated response in a later message. Is that to an email you sent, or from a web-based issue-tracking system? What does it say about the current status of EMWD services, if anything? Regards, Steve > We have since found out the devastating news that > Brian Carpenter passed away last year. Brian was really helpful > when we moved our listservers from a legacy system to hosting on > the EMWD platform. My sincere condolences to his family and > friends. > > As we can no longer get a response from EMWD about our listserver issue I was wondering if any one else in this community could help. > > Many thanks. > > Jonathan > > Jonathan Ashby > ICT Strategic Communications Project Manager > Londonwide LMCs and Londonwide Enterprise Ltd > Working days: Tuesday and Wednesday > Direct dial: 020 3818 6228 > Mobile: 07768 109601 > Fax: 020 7383 7442 > Email: jonathan.ashby(a)lmc.org.uk > Web: www.lmc.org.uk > Twitter: @LondonwideLMCs > > > > ---------------------------- > Visit www.lmc.org.uk/coronavirus-covid-19 for the latest official resources and guidance on covid-19. > > Remember that you can use WhatsApp and FaceTime for online consultations as well as the usual online tools. > 🌲 Think of the environment. Do you really need to print this email? > This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please accept our apologies and notify the sender. > > The registered and office address for Londonwide Local Medical Committees Limited is: Tavistock House South, Tavistock Square, London WC1H 9LG. Registered in England No: 6391298. > > Londonwide Enterprise Limited is a wholly owned subsidiary of Londonwide Local Medical Committees Limited. Londonwide Enterprise Limited is registered at: Tavistock House South, Tavistock Square, London WC1H 9LG. Registered in England No. 6990874. Londonwide Enterprise Limited is registered as a Company Limited by Shares. VAT no: 130 1454 66. > > Londonwide Local Medical Committees Limited and Londonwide Enterprise Limited do not provide legal or financial advice and thereby excludes all liability howsoever arising in circumstances where any individual, person or entity has suffered any loss or damage arising from the use of information provided by Londonwide Local Medical Committees Limited and Londonwide Enterprise Limited in circumstances where professional legal or financial advice ought reasonably to have been obtained. > > Londonwide Local Medical Committees Limited and Londonwide Enterprise Limited provide guidance and support to GPs and practice teams in the Londonwide area. Additionally Londonwide Local Medical Committees Limited provides representation to GPs and practice teams in the Londonwide area. Londonwide Local Medical Committees Limited and Londonwide Enterprise Limited strongly advises individuals or practices to obtain independent legal or financial advice. > > ------------------------------------------------------ > Mailman-Users mailing list -- mailman-users(a)python.org > To unsubscribe send an email to mailman-users-leave(a)python.org > https://mail.python.org/mailman3/lists/mailman-users.python.org/ > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ > https://mail.python.org/archives/list/mailman-users@python.org/

3 years, 3 months

[MM3-users] Filter who can send on mailman3 list?

by marcus.granath＠gmail.com

Hi! I have a mailman3 mailing list which I admin, and I would like setup the following rule. Me and 3 of my team mates (who are part of the mailman3 list) should be able to send on the list as well as an "no-reply" user, others on the mailman3 list should only be able to receive the e-mails (and of course be able to unsubscribe themself). Both the: "Default action to take when a non-member posts to thelist" and the "Default action to take when a member posts to the list" is set to "Default processing", and I tried to setup actions in the "Header Filters" - but no really success.. :-( So what I basically try do achieve is to have only the following addresses to be allowed to send announcements (e-mails) on the mailman3 list, and all others that are member of the mailman3 list will just receive the e-mails. The usual "announcements" are sent out as the "no-reply" address (that actually are not really part of the mailman3 list) ;-) no-reply(a)abc.com ("fake address" that actually are not really part of the mailing-list) peter(a)abc.com david(a)abc.com marcus(a)abc.com How to achieve this kind of filter with mailman3?

4 years

[MM3-users] Re: Filter who can send on mailman3 list?

by Marcus Granath

It seems like the version used is: Postorius Version 1.1.2 The menus I can see are the following: Info Subscription requests Held messages Members Settings Mass operations Banned addresses Header filters Delete list And from the "Members" I can select "Subscribers", "Moderators", "Owners" - so I can manage to delete "subscribers" and add somebody as Moderator or Owner for my list. But I cannot find anywhere to set or add something like "non-member". What I basically want to achieve is that my "sendmail" script (executed from linux) will send announce-mails to this mailing list - and will set an "pseudo-address" (not my own name and address) as sender of this e-mail, i.e "ABC Announcement <no-reply(a)abc.com>" - and to get this "pseudo-mail" to be one of the accepted users (together with me and some team mates with real addresses) to send on the list - one option I understood was to use the "non-member" user for this "ABC Announcement <no-reply(a)abc.com>". But in my web-interface (as described above), I cannot find where to add and manage such user (non-member). Or can I use some other API (then the web-page) to do that kind of operation? ;-)

4 years

[MM3-users] Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by Mark Sapiro

On 2/4/22 14:54, gordon(a)dickens.com wrote: > Hi Mark, > > Thanks very much for your prompt and helpful reply! > > I made the change to the mailman3 configuration for Apache that you recommended since I am using uwsgi. Now, I am able to start/status/stop the mailman3-web service without errors. However, now, when I then attempt to access the mailman installation on my server with my browser, I get the following message in the browser window: > > Internal Server Error > > I am unable to find any errors in the mailman3 logs or in the Apache error logs. However the Apache access logs have the following: > > 173.165.166.34 - - [04/Feb/2022:17:06:20 -0500] "GET /mailman3 HTTP/1.1" 500 21 > > Do you have any idea as to what is going on now? Any suggestions for troubleshooting this? Without more log info, I don't know what the issue is. Have you looked in /var/log/mailman3/mailman.log and /var/log/mailman3/web/mailman-web.log? Possibly there is a uwsgi log somewhere in /var/log that might have something relevant. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: (Custom) Plugins: Proper file path(s) for adding a handler?

by Thomas Ward

On 10/24/23 18:53, Mark Sapiro wrote: > On October 24, 2023 3:47:10 PM PDT, Thomas Ward via Mailman-users <mailman-users(a)mailman3.org> wrote: >> On 10/24/23 18:29, Mark Sapiro wrote: >>> What if you try this with `mailman-web shell`? >>> >> Doesn't error on load, but can't access configs in order to see if my custom handler is present. Which Abhilash said has to be done in the mailman shell - as does the documentation. Mailman can't even start with this added. Which is a problem. > > I was confused. I should have said ` mailman shell`, not `mailman-web shell`. Insert "circular problem" here. When I DO NOT have the module loaded in the configuration, `mailman shell` works. Since that was functional, I went into the shell and executed this: > from mailman_customizations.hooks import MailmanCustomizations This worked fine, but obviously importing the class doesn't necessarily *activate* the class. So something is up with how I'm *supposed* to activate the plugin in the config, and we know that it's visible to Mailman in its shell, but it can't autoload it. So, again, not sure where to look next for debugging. Thomas

1 year, 5 months

[MM3-users] Re: Welcome message template errors

by Mark Sapiro

On 4/26/24 17:04, Mark Sapiro wrote: > Mark Sapiro wrote: >> I just did a test on my development system and I see the same timeout >> error, so it's not just you. I'll work on this. ... > I also note that this timeout only occurs when it is a subscription via > REST. I.e. subscription via email or `mailman addmembers` sends the > proper welcome message. > > So it has something to do with the retrieval being done by a rest > runner, but I still don't know what the underlying issue is. More strangeness. I've now done a test on one of the production servers I manage, and there is no error. Both the production server and the development server are running the identical Mailman code installed in a venv, they both have the same version of urllib3 and similar Python versions, 3.9.16 on the development server and 3.9.10 on the production server. Both servers are running under Ubuntu 20.04.6. The only other difference I see is on the production server everything runs as user mailman and on the development server everything runs as user mark. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 3 weeks

[MM3-users] Re: Trying to understand the mailman.cfg from the virtualenv installation guide

by Mark Sapiro

On 9/8/24 01:04, unite42--- via Mailman-users wrote: > Hello, > > I'm trying to install Mailman3 following the Virtualenv Installation guide. I would like to understand why the configurations in the displayed mailman.cfg are recommended. > > Especially the following two: > > [archiver.prototype] > enable: yes > > "The prototype archiver stores messages individually in > var/archives/prototype/LIST_NAME/." > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > Do I need this, when using hyperkitty? Is this a fail-safe recommendation? The prototype archiver is separate from and independent of HyperKitty. If you are using HyperKitty as an archiver, you don't need the prototype archiver. Note however that if the prototype archiver is not enabled, it can't be used at all, but if it is enabled, it can still be enabled or disabled on a per-list basis. > [mta] > verp_confirmations: yes > verp_personalized_deliveries: yes > verp_delivery_interval: 1 > > What is the background of these recommendations? These settings enable VERP for all list messages. This results in more reliable bounce processing. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 1 week

[MM3-users] Re: My Server is unable to connect to Mailman REST API few times

by Shashikanth Komandoor

Dear Mark, As I already said, your suggestion worked well on one list. But when I tried to implement the same trick on another list, I found the below error messages in the mailman.log. > * Sep 23 18:31:31 2020 (22951) Uncaught runner exception: [Errno > 2] No such file or directory: > '/var/lib/mailman/mailman/var/lists/press.dpr-pb.lsmgr.nic.in/digest.mmdf > <http://press.dpr-pb.lsmgr.nic.in/digest.mmdf>'* > > > *Sep 23 18:31:31 2020 (22951) Traceback (most recent call last):* > * File "/usr/lib64/python3.6/mailbox.py", line 581, in __init__* > * f = open(self._path, 'rb+')* > *FileNotFoundError: [Errno 2] No such file or directory: > '/var/lib/mailman/mailman/var/lists/press.dpr-pb.lsmgr.nic.in/digest.mmdf > <http://press.dpr-pb.lsmgr.nic.in/digest.mmdf>'* > *During handling of the above exception, another exception occurred:* > *Traceback (most recent call last):* > * File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 173, > in _one_iteration* > * self._process_one_file(msg, msgdata)* > * File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 266, > in _process_one_file* > * keepqueued = self._dispose(mlist, msg, msgdata)* > * File "/var/lib/mailman/mailman/src/mailman/runners/pipeline.py", line > 37, in _dispose* > * process(mlist, msg, msgdata, pipeline)* > * File "/var/lib/mailman/mailman/src/mailman/core/pipelines.py", line 50, > in process* > * handler.process(mlist, msg, msgdata)* > * File "/var/lib/mailman/mailman/src/mailman/handlers/to_digest.py", line > 47, in process* > * with Mailbox(mailbox_path, create=True) as mbox:* > * File "/usr/lib64/python3.6/mailbox.py", line 893, in __init__* > * _mboxMMDF.__init__(self, path, factory, create)* > * File "/usr/lib64/python3.6/mailbox.py", line 585, in __init__* > * f = open(self._path, 'wb+')**FileNotFoundError: [Errno 2] No such > file or directory: > '/var/lib/mailman/mailman/var/lists/press.dpr-pb.lsmgr.nic.in/digest.mmdf > <http://press.dpr-pb.lsmgr.nic.in/digest.mmdf>'* > > I ran in both the ways you suggested i.e. through "mailman shell" and "mailman remove". But no luck. Could you please suggest me at this point ? <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Tue, Sep 22, 2020 at 10:29 PM Shashikanth Komandoor < shashikanth.komandoor(a)gmail.com> wrote: > > Thank you Mark a lot. > > It worked awesome. You don't know how much you helped me. > > Thank you once again. > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > <#m_8502129290396208734_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > On Sat, Sep 19, 2020 at 8:56 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 9/19/20 4:32 AM, Shashikanth Komandoor wrote: >> > >> > But I am trying to delete a list on an urgent basis. Because of which I >> am >> > getting the above said errors. I tried to delete >> > through the interface, through curl command and through "mailman shell" >> but >> > nothing led me to a >> > positive result. Is there any work around to delete the list ? >> >> What have you tried in Mailman shell? This should do it. >> >> $ mailman shell -l list.example.com >> Welcome to the GNU Mailman shell >> Use commit() to commit changes. >> Use abort() to discard changes since the last commit. >> Exit with ctrl+D does an implicit commit() but exit() does not. >> The variable 'm' is the list.example.com mailing list >> >>> getUtility(IListManager).delete(m) >> >>> commit() >> >> So should just >> >> $ mailman remove list.example.com >> >> What happens if you do those? >> >> -- >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > > > -- > Thanks & Regards, > Shashi Kanth.K > 9052671936 > > > > -- Thanks & Regards, Shashi Kanth.K 9052671936

4 years, 7 months

[MM3-users] Re: setup of URLs

by pmlists＠free.fr

> On Sun, Jan 28, 2018, at 12:24 PM, Peter Münster wrote: > This patch should do what you want: > > ``` > index a5ea108..bff54f3 100644 > --- a/example_project/urls.py > +++ b/example_project/urls.py > @@ -25,11 +25,10 @@ try: > except ImportError: > from django.urls import reverse_lazy > from django.views.generic import RedirectView > +from postorius.views.list import list_index > > urlpatterns = [ > - url(r'^$', RedirectView.as_view( > - url=reverse_lazy('list_index'), > - permanent=True)), > + url(r'^$', list_index), > url(r'^postorius/', include('postorius.urls')), Thank you. I've modified the patterns a bit, so that links to the list index, point also to "/": urlpatterns = [ url(r'^postorius/', include('postorius.urls')), url(r'^archive/', include('hyperkitty.urls')), url(r'', include('django_mailman3.urls')), url(r'^accounts/', include('allauth.urls')), url(r'^admin/', include(admin.site.urls)), url(r'^$', list_index, name='list_index'), ] > Just as an FYI, my browser would always re-direct me to /posotrius/lists, even after I > applied this patch, not sure if it was some sort of caching or something else. If it's Firefox, then you can right-click on the site in the history window, and select "Forget about this site". (Strange: I did not get your message by email. For this reply I use the web-interface.) -- Peter

7 years, 2 months

[MM3-users] Re: mailman3 postorius cannot retrieve template

by Mark Sapiro

On 11/2/21 3:28 PM, Wolfgang Bock via Mailman-users wrote: > > I get an db-entry in the mailman3 table template which doesnt lead to a > suitable link: > https://localhost/postorius/api/templates/list/testliste01.mydomain.de/list: > member:regular:footer > > In the next stept it leads to a flood of entries in my syslog because django > is asking for a certificate match for "localhost": > Nov 2 11:47:49 myserver mailman3[175334]: Nov 02 11:47:49 2021 (175334) > Certificate did not match expected hostname: localhost. Certificate: ... > > Letsencrypt cannot deliver this match for "localhost", it is impossible to > configurate letsencrypt to do so. > > The running script must create a postgres INSERT database command which > includes the correct domain-name including the correct path > .../mailman3/api/templates .... and not ... postorius/api/.... > > I dont know, where is the place to correct this. > - in mailman-web.py ?? > ... > ALLOWED_HOSTS ... '*' > or > MAILMAN_REST_API_URL = 'http://localhost:8001' > or > POSTORIUS_TEMPLATE_BASE_URL = 'https://localhost/mailman3/' If you normally access Postorius on your site at something like https://www.example.com/postorius, than set that as POSTORIUS_TEMPLATE_BASE_URL -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Postorius with screen readers

by Stephen J. Turnbull

Andrew Hodgson writes: > Just wanting to let people know that since bumping to Postorius > 1.3.3 I am seeing a real improvement in access to the Mailman > settings and tabs using a screen reader with Chrome. Thanks for telling us! > When navigating through the tabs you are hearing two iterations of > the tab, the first for example saying "Held Messages 0 tab" which > is not a link, but then if you arrow down past that you hear "Held > Messages 0" which is advertised as a link and if you hit enter on > those it changes the page to the requested view. I don't think we have accessibility specialists among the developers, although several of us care deeply about it. So I'd like to confirm: the two iterations, one telling you you are on a tab, the other telling you you have a link, is a good thing? Would it be better if you got one notification that there is a tab with a link on it? I don't know if there is anything we can do about that, since our accessibility features come from the Django framework. But I'd like to improve my awareness and knowledge of how these features work for our users in Mailman. Steve

4 years, 10 months

[MM3-users] Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Sun, Dec 25, 2022 at 5:13 PM Stephen J. Turnbull < stephenjturnbull(a)gmail.com> wrote: > Odhiambo Washington writes: > > > > Besides mod_wsgi as Mark suggests and the uwsgi configuration, the > > > only thing I can think of is an Apache rewrite rule. It's not in the > > > Postorius and HyperKitty templates. > > > > And I do not have any rewrite rules in my VHOST config: > > > > https://pastebin.ubuntu.com/p/9MRMJST9zZ/ > > Is there a mod_wsgi.conf file? I've never seen this "mysterious" > insertion of "/mailman3" in URLs. I'm trying to imagine where > mod_wsgi would get it from, and just can't think of why that would be > in mod_wsgi or its .load or .conf files in the Apache config. The > maintainable place for URL configuration is the main apache.conf or a > site-specific include file such as sites-available/mailman.conf. I > guess it could be in an instance-specific configuration file or stanza > of uwsgi to create a namespace. > > Steve > There is none that is in use anywhere. Only /etc/mailman3/uwsgi.ini -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 3 months

[MM3-users] Re: Set member.moderation_action via REST API as part of message approval?

by Andy Matthews

After reading Mark's comments it seems like a good approach, knowing that a moderator has explicitly chosen to "always accept" a post from a user, would be to first create that user record (including setting the `moderation_action` property to `defer`—as Mark indicates) , before approving their email. That way when the message itself is approved the user record is already included. And then we don't have any need to explicitly update the list's `accept_these_nonmembers` property because we've already set the `moderation_action` on the user. Does that sound like an acceptable approach? And a follow up question: at the moment we don't explicitly create users, we simply subscribe them to a list, and allow the implicit processes to do their magic. However if I wanted to manually create a nonmember, would I "create a user" or would I "subscribe a user to a list" with a role of `nonmember`? Which brings up an additional question. Is the `moderation_action` list-specific or does it apply to all lists from the same domain? To be clear, if abc(a)123.com's `moderation_action` is set to "defer" for **open-list(a)foo.bar** would that setting also apply to **another-open-list(a)foo.bar**?

1 month, 2 weeks

[MM3-users] Re: Digests not working correctly

by Joel Lord

Now I'm on one of the lists in digest mode and I can see that it's a mess. Periodic digests are definitely NOT working, so I'll lay that out here. root@host2:/# cat /etc/cron.d/mailman # This goes in /etc/cron.d/mailman # Replace "apache" by your webserver user ("www-data" on Debian systems) and # set the path to the Django project directory 0 23 * * * lists /usr/local/bin/mailman digests --periodic 0 23 * * * lists /usr/local/bin/mailman notify root@host2:/# grep digests /var/log/cron.log Jun 11 23:00:01 host2 CRON[1632765]: (lists) CMD (/usr/local/bin/mailman digests --periodic) Jun 12 23:00:01 host2 CRON[2177286]: (lists) CMD (/usr/local/bin/mailman digests --periodic) root@host2:/home/members/directory# su - lists lists@host2:~$ /usr/local/bin/mailman digests --periodic lists@host2:~$ ls var/lists/<list>/ digest.mmdf In this case I've got /usr/local/bin/mailman as a symlink to the mailman binary inside the venv's bin directory, just for simplicity. That digest.mmdf file is dated June 9th and clearly ought to have been cleared out on any of the nightly runs between then and today but has not. There are no errors anywhere I can find. How can I try and track this down? -Joel On 6/4/2023 10:15 PM, Joel Lord wrote: > The May 4th digest that went out was _also_ size-triggered, so this may > have nothing to do with periodic digests at all, and possibly my > periodic digests aren't working. I'm not on any of my own lists in > digest mode, I'm slowly extracting diagnostic information out of people > who are. Also, since this is a ~2 month cycle, it's really difficult to > get data points to work with. I'll need to remember to go in and look > when this settles down again (new cycle of activity started last night) > to see if there's anything left pending. > > (venv) root@host2:/home/lists/mailman/venv/bin# pip freeze | grep -i hyper > HyperKitty==1.3.7 > > On 6/4/2023 10:05 PM, Mark Sapiro wrote: >> On 6/4/23 18:35, Joel Lord wrote: >>> >>> The periodic digests do seem to be coming out. I also now have >>> confirmation that the one message in this morning's digest that was >>> from May 4th was also included in the last digest back on May 4th, so >>> it seems that the one message was left behind in the digest queue >>> when the periodic digest was sent. >> >> I don't see how that can happen. The process that sends a digest >> renames the var/lists/<list-id>/digest.mmdf mailbox file in which the >> messages are accumulated to >> var/lists/<list-id>/digest.<volume>.<issue>.mmdf, where <volume> and >> <issue> are the volume and issue numbers of that digest, and then >> queues a message in the `digest` queue to tell the digest runner to >> create the digest from the messages in that mbox and send it. Thus, it >> leaves no var/lists/<list-id>/digest.mmdf mailbox file behind and that >> is created anew when the next post arrives. Further, if there is a >> non-empty digest.mmdf file, its messages should be sent no later than >> the next 11 PM `cron digests`. >> >> >>> There was one earlier message to the list back on May 4th, before the >>> one that got duplicated, but I can't tell if that triggered a >>> size-based digest to be sent: the logs aren't clear enough on that >>> detail for me to tell > >> >> OK >> >> >>> Just to inform things: >>> >>> (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep mailman >>> django-mailman3==1.3.9 >>> mailman==3.3.8 >>> mailman-hyperkitty==1.2.1 >>> mailman-web==0.0.6 >>> mailmanclient==3.3.5 >>> (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep hyper >>> mailman-hyperkitty==1.2.1 >> >> Actually, it's HyperKitty, not hyperkitty, but I assume HyperKitty is >> up to date as are the others. >> >>> (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep post >>> postorius==1.3.8 >>> >>> >> > -- Joel Lord

1 year, 10 months

[MM3-users] Re: Which documentation to follow for installation

by Abhilash Raj

On Fri, 18 Aug 2017 09:40:37 -0000 ribanez(a)sciops.esa.int wrote: > Hi everyone, > > I'm trying to deploy Mailman 3.1, but it seems there isn't a clear place to > look for documentation. I found two different sites: > > https://mailman.readthedocs.io/en/latest/ > http://docs.mailman3.org/en/latest/ Both of the above are actually latest documentation, docs.mailman3.org should be the one to look for installations guidelines for the entire Mailman 3.x Suite, mailman.readthedocs.io is the documentation of Mailman 3 Core, which handles the mail. http://docs.mailman3.org/en/latest/prodsetup.html This should be the best place to start, be sure to look at the Pre-Installation Guide if you are new to the Python ecosystem. > > Do you know which one should be followed? Both at the same time? I find it > quite unclear... and this installation will be for an operational environment. > > Also, there are some (official?...) docker images, but all images are for > mailman 3.0 but not mailman 3.1, and of course updates are not guaranteed. It is meant for Mailman 3.X series and is maintained by me. It currently includes the latest releases for all the Mailman's sub-projects, also Mailman 3.1. Hope that helps! -- thanks, Abhilash Raj

7 years, 8 months

[MM3-users] Re: Exception in the HyperKitty archiver: 'utf-8' codec can't encode characters

by Gilles Filippini

Mark Sapiro a écrit le 15/06/2020 à 21:58 : > On 6/15/20 12:37 PM, Gilles Filippini wrote: >> >> There are 4 emails stored into this folder. 3 of them are spam, and the >> last one is a legitimate email. This is annoying that such emails could >> accumulate and stay into var/archives/hyperkitty/spool/ forever, causing >> more and more hyperkitty errors. >> >> Any idea how to make their processing more error proof? > > > Change the offending .encode() method to add errors='replace'. > > The traceback from the error should tell you where it is. > > You could also open an issue at > <https://gitlab.com/mailman/hyperkitty/-/issues> for us to look at. If > you do that, please include an error traceback if possible. If there is > not a traceback in mailman.log associated with the error, there might be > one in HyperKitty's log (configured in Django's settings). Also, > including enough of a message to duplicate the issue is very helpful. I've now deleted the offending messages. Will open an issue with related details the next time this error occurs. Thanks a lot, _g.

4 years, 10 months

[MM3-users] Re: How to import mailman2 into mailman3 in Docker, getting error with archives.

by Jens Günther

For importing the archives, it's the mailman-web container. For me it was like: python manage.py hyperkitty_import -l listxy(a)somedomain.org /opt/mailman-web-data/listxy.mbox Before I connected into container as the user mailman! Hope this helps. Am 15.09.21 um 19:36 schrieb bob B: > I know you can't run mailman commands in the docker images and I have to copy the data to an area where he docker images can access it, but in looking that the commands I got the list settings to import > > docker exec -it mailman-core mailman import21 [REDACTED](a)REDACTED].REDACTED].org /opt/mailman/migration/config.pck *** this worked > > > But having issues importing the archives? do i run this on mailman-core OR mailman-web? I tried both but it does not like python? > > docker exec -it mailman-core python manage.py hyperkitty_import -l [REDACTED](a)REDACTED].REDACTED].org /opt/mailman/migration/[REDACTED].mbox > OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "python": executable file not found in $PATH: unknown > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 7 months

[MM3-users] Re: Moderation request email from a non existing user

by Mark Sapiro

On 6/1/22 00:45, David Lopez via Mailman-users wrote: > I'm on postorius 1.3.4 so I tried to do via shell but after logging it shows a syntax error. > > mailman shell -l mylist@mydomain(dot)com > pendingsdb = getUtility(IPendings) >>>> for token, data in pendingsdb.find(m, pend_type='unsubscription'): > ... ... if data['token_owner'] == 'moderator': > File "<console>", line 2 > ... if data['token_owner'] == 'moderator': > ^ > IndentationError: expected an indented block >>>> ... pendingsdb.confirm(token) > File "<console>", line 1 > ... pendingsdb.confirm(token) You are entering the `... ` prompts that I showed in my example. You show ``` ... ... if data['token_owner'] == 'moderator': ``` the first `... ` is the actual prompt from mailman shell. The second `... ` is the prompt from my example which you shouldn't enter. You should only be entering ``` pendingsdb = getUtility(IPendings) for token, data in pendingsdb.find(m, pend_type='unsubscription'): if data['token_owner'] == 'moderator': pendingsdb.confirm(token) commit() ``` Indentation is important. After `pendingsdb.confirm(token)` enter an empty line at the last `... ` prompt. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] How to enable VERP?

by Andy Smith

Hi, I'm a little confused as to how to enable VERP. mailman3 Debian package, version 3.3.3-1, using Exim 4 MTA. In /etc/mailman3/mailman.cfg I added: [mailman] … verp_delivery_interval: 1 verp_probes: yes and restarted mailman3.service. The list's "Alter Messages / Personalize" setting is "Individual" (but I tried "Full" as well and saw no difference in VERP behaviour). I can see the MTA is doing an individual delivery for each recipient, and the list's custom footer tells the recipient which address they are subscribed under, so I know that part is working. With VERP enabled I was expecting the Return-Path header in the delivered list mail to include a cookie to identify the individual subscriber, but instead it is "listname-bounces(a)example.com" like always. In mailman.cfg my MTA-related settings are: [mta] incoming: mailman.mta.exim4.LMTP outgoing: mailman.mta.deliver.deliver smtp_host: localhost smtp_port: 25 configuration: python:mailman.config.exim4 And the Exim configuration itself has ther macros, router and transport files from the "Exim" section of here: https://docs.mailman3.org/en/latest/config-core.html#configuring-mta edited only for correct paths. That's been working for months for delivering list email in and out, but I'm just now trying to enable VERP and it's not happening. Is there something I'm missing? Thanks, Andy

2 years, 6 months

[MM3-users] Re: mailman3 3.2.2 python3.8 problem on focal

by Thomas Stein

Answering my own post for now. Replacing time.clock() with time.process_time() in /usr/lib/python3/dist-packages/mailman/utilities/uid.py seems to fix the current issue for me. Don't know what else I broke with it though. :) cheers! t. Am 2024-03-20 12:54, schrieb Thomas Stein: > Hello list! > > I saw a few posts regarding the "Uncaught runner exception: module > 'time' has no attribute 'clock'" problem but no solution to that. It > seems this issue sneaked in at some point. I was getting aware of it > when suddenly notifications to non-member posts did not work anymore. > Everything else seems still to work. > > So, what is the prefered solution here? Is it possible to "repair" > focal? There is python2.7, python3.6 and python3.8 installed currently. > Or do I need to switch to a supported distribution like debian > something? Wait for ubuntu 24.04? > > Any hints are really appreciated. > cheers! t. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to himbeere(a)meine-oma.de

1 year, 1 month

[MM3-users] Re: Welcome message template errors

by Mark

>> On 2024-04-23 11:33, Mark Sapiro wrote: >> That URI should have been; >> >> https://lists.mydomain.com/mailman3/api/templates/list/mytestlist.lists.myd… > I think you are saying the what you reported originally was not > correct and the URL in the template table was in fact the latter URL. I meant when I typed the URL in my first email I had unintentionally omitted the name of the list (mytestlist) when I redacted the real domain name to 'lists.mydomain.com'. ...emplates/list/lists.mydomain.com/list:user:noti... I should have written ...emplates/list/mytestlist.lists.mydomain.com/list:user:noti... >> If I go to the above URL, the text of the list's Custom welcome >> message displays on an otherwise empty webpage. > > > And that's what is expected. So you can go to that URL and get the > template, but when Mailman Core tries to do the same thing, it gets a > timeout. Is there some firewall or other security software blocking > this access? #ufw disable Firewall stopped and disabled on system startup Then restarted everything... # ufw status verbose Status: inactive And still getting the error in the Postorius webpage ... HTTP Error 400: HTTPSConnectionPool(host='lists.mydomain.com', port=443): Read timed out. (read timeout=5)

1 year

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 10/19/20 11:32 PM, Mark Sapiro wrote: > On 10/19/20 7:42 PM, Brian Carpenter wrote: >> On 10/19/20 10:23 PM, Mark Sapiro wrote: >>> And the import21 created the user and address records for this user. >> Does the same thing for a new subscriber as well. So there is no pathway >> to change a real name that is associated with an email address. None. >> Zilch. Mailman 2 made this so easy and Mailman 3 made it impossible. I >> will let someone else file the bug report. You don't really think that >> this is an issue which means it will be years before it is addressed. So >> I will save me some time. I will learn to live with it. > > I didn't say I didn't think it was a real issue. I mostly questioned > whether a new subscription should change an existing display_name. I > agree that there should be a way for a user to change the display_name > associated with her address. I'm not so sure about a list admin. Respectively, I think you are asking the wrong question here. The real question is why isn't a display_name being removed when a list subscriber is unsubscribed. Also list members being forced into a powerless role by Mailman 3's architecture have no way of changing a name except through a list owner unless they register an account but then again, *even that doesn't allow them to change their display name*. There are also other use cases in which a list owner will want to identify portions of their membership roster through the use of the display_name. Most list members interact with a Mailing list program via email. I know you understand that. However it is List owners that are the "real" power users of Mailman and so the admin interface should be designed in such a way that empowers List owners. Taking the ability away from List owners (and List members to make), what should be a simple name change, weakens them. > And in any case, I'm only one person. I'm not the only one deciding > what's important and what's not. I only decide what I want to work on, > not what anyone else thinks is important or wants to work on, so even if > I think something is not worth doing, that doesn't mean it won't get > done, and once again for emphasis, I do thing a user should be able to > change the display name associated with her address(es). Again I think we are missing something here from this conversation: data is not being removed. A list subscriber being removed (unsubscribed) should have their information totally removed. It is not. I now have one list owner who realizes this and it is not good. How does this not violate GDPR? This is why I think all the mailman developers ought to make this issue a high priority. It is creepy to see a name returned out of nowhere when someone resubscribes to a list without associating a name with a second resubscribing. I think this puts List owners at a disadvantage. > > Mailman 3 is totally different from Mailman 2.1 in this respect. Mailman > 2.1 had no concept of user. All it knew was addresses subscribed to > lists and an address subscribed to one list had no connection to the > same address subscribed to another list or being an owner or moderator > of a list. I think this should still be the case for non-registered list members. List owners/moderators are different. They HAVE to be registered users of Postorius/Affinity in order to manage/moderate a list. I wonder what the majority of list members' scenarios are. Is the majority scenario in play today the one where most list members are only subscribed to a single list on a single mailman instance? Or is it the scenario that is in majority use the one where a single list member is subscribed to multiple lists? I think that it is important to find out because it should govern the development process to a certain degree. This single approach of having registered user account with multiple associated email accounts elevates one scenario at the expense of the other. It also assumes/requires that list members have a registered user account and I can tell you from my experience that is not going to happen. The majority of mailman 2 users will not registered with a Mailman 3 admin interface. Some will of course, the majority will not. Maybe the behavior should and will change but it will take years for that to happen. So what I am challenging and questioning here is the approach where such assumptions are being made already that results in the weakening of list owners. > > Mailman 3 does have a concept of user and addresses belonging to a user. > This complicates things in some ways. In Mailman 2.1 we could have "The > Boss <user(a)example.com" as a member of one list and "Just a Peon > <user(a)example.com>" as a member of another list. In Mailman 3 that is > not possible unless the addresses are tweaked in some way to make them > different. Perhaps there is a better approach here to handle single member w/multiple subscriptions that doesn't hurt the ability of List owners to serve the needs of list members who do not have a registered user account and prevents the removal of data when a SINGLE user unsubscribes from a list. > > You don't seem to be concerned about the case where I subscribe to a > second list with a different display name and am surprised to find my > display name changed on the first list, but it's something that I have > to consider. I am not concerned because I think such cases are in the extreme minority. Are you saying that people are now going to be using different real names associated with their other subscriptions as well and that is going to be so needed it warrants this complex system that you have come up with? If someone whats to have a different name associated with a different subscription/email address then I am going to tell them create a new user account and use a good password management program to keep track of their logins. Right now I think this minority use case scenario is negatively impacting other administrative tasks of Mailman, particularly in the removal of user data when someone unsubscribes from a list. Its the use of a square peg being forced into a round hole. Except in this case most of the holes are round but by golly, we are going to use that square peg regardless! > > As far as filing or not filing an issue, issues in the GitLab trackers > are how we track these things. Threads on mailing lists are appropriate > for discussion of issues, but if something is going to get changed or > fixed, an issue in the tracker is the way to ensure it doesn't get put > aside and forgotten. If this is as important to you as it seems to be, > please file the issue. I will but what is disturbing is that you don't think that the non-removal of user data in cases of unsubscribing is not important or even an issue. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 6 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Nice you opened a new issue, ok then... About this: Ideally, you want to use paths.fhs which is based on Filesystem Hierarchy Standard . To use this add the following to your configuration: [mailman] layout: fhs Should I do it???? is that for production?? Sometimes I wish the install process was easier, sorry for disturbing you guys but believe me I've been more than 2 weeks trying and it's been difficult El vie., 21 jul. 2017 a las 13:02, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 10:29 AM, Rafael Mora wrote: > > Can we modify the docs? > > > > El vie., 21 jul. 2017 a las 12:25, Mark Sapiro (<mark(a)msapiro.net>) > > escribió: > >> > >> However, that said, the doc is wrong. The lines should be added to > >> main.cf, not master.cf. See > >> <https://gitlab.com/mailman/mailman-suite-doc/issues/14>. > > > That's what the above issue and associated MR are for. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 9 months

[MM3-users] Change settings via mailman shell

by kk＠eco.cept.org

I am trying to find a way to set some parameters on the lists from a shell script. One specific parameter - max_message_size is not presented through the REST interface apparantly, and i found a way to set this with mailman shell command. Continuing this path i seem not to be able to set any other parameters like this: m.archive_policy = 'never' m.subject_prefix = '' m.dmarc_mitigate_action = 'munge_from' m.dmarc_mitigate_unconditionally = True commit() However i end up with this error: sqlalchemy.exc.StatementError: (builtins.AttributeError) 'str' object has no attribute 'value' [SQL: 'UPDATE mailinglist SET archive_policy=?, dmarc_mitigate_action=?, dmarc_mitigate_unconditionally=?, subject_prefix=? WHERE mailinglist.id = ?'] [parameters: [{'dmarc_mitigate_unconditionally': 'True', 'dmarc_mitigate_action': 'munge_from', 'subject_prefix': '', 'archive_policy': 'never', 'mailinglist_id': 65}]] Not sure what to make of it, but it seems like the fields are not there. I then proceed to get a list of all parameters with information found here: http://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclient… and the parameters seems to exist - however this list is made with the REST interface - so my question are - are there a difference in parameters in "mailman shell" command and REST interface - and how do i then get a list of parameter and possible settings in the "mailman shell" command ? Thanks in advance Kenneth Denmark

6 years, 1 month

[MM3-users] Current status and issue deleting Archives in Mailman3

by bob B

So just want to make sure I have the latest information after searching this list and googling or have I missed something? It appears there is no way in mailman3 to delete archives. There has been discussion on implementing this, but it has not been developed? is that correct? I saw references to: >>> from hyperkitty.models import MailingList >>> ml = MailingList.objects.get(name="test2(a)freeculture.org") >>> ml.delete() But how do I run this? I believe it is run in mailman-core (I am in a docker environment but that should not matter). I can get into the mailman shell, but that command does not work I did the following: bash-5.0# mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> from hyperkitty.models import MailingList Traceback (most recent call last): File "<console>", line 1, in <module> ModuleNotFoundError: No module named 'hyperkitty' >>> What am I missing? ************** Question 2 What about pruning archives? I use to run a script for mailman2 to prune archives of messages older than X days for a list, Is that possible in mailman3

3 years, 5 months

[MM3-users] Re: Mailman3 on FreeBSD

by Barry Warsaw

Thanks for the reference John, > On Aug 13, 2017, at 06:52, John Poltorak <karotlopj(a)gmail.com> wrote: > > Regarding location of mailman.cfg...FreeBSD adopt a strict directory > hierachy > > https://www.freebsd.org/cgi/man.cgi?hier(7) > > Anything installed outside the base OS belongs in /usr/local I looked over that page. Does this mean that even if you were to install Mailman 3 via the FreeBSD package manager (i.e. ports), you’d still want mailman.cfg in /usr/local/etc instead of /etc? That would differ from most Linux distributions where package manager installed packages would have their configuration files in /etc, and where “third party” packages would have them in /usr/local/etc. > I guess that issue is something for the FreeBSD porters of Mailman3… I think so. I think for now I don’t want to support /usr/local/etc/mailman.cfg out of the box, although I’m open to persuasion if there are some more generic use cases. OTOH, the internal function that calculates the search paths could be refactored to make it easy for distributions to carry small deltas to add that as a search path (it really wouldn’t be that hard to do now, but it’s a little icky). Of course, you can’t add a configuration file to find a configuration file. :) Cheers, -Barry

7 years, 8 months

[MM3-users] Re: Postorius performance with over 1000 pending users

by Nick W

On 06/08/19 at 12:13, Nick W <mail(a)nickwynja.com> wrote: > Could it be that these requests are being submitted through Postorius? I'd > assume there would be some sort of honeypot input to prevent abuse. I'll > continue investigating and follow up with any insight I can on the cause of The > Problem. Some follow up here: cat /var/log/nginx/access.log | grep "POST /postorius/lists/mylist.exmple.com/" shows only a recent manual attempt I made to subscribe but not much else, which leads me to believe these requests aren't coming through Postorius. Now the more embarrassing part. The likely culprit is my stupidity. In an attempt to have subscription forms embedded on my static websites, I created this flask app to handle POSTs and subscribe people the the specified lists. https://github.com/nickwynja/fmmss/ I included a menial honeypot feature to handle spam requests, which I thought was working. It must not be but it appeared like it was, likely because I made the honeypot for my app at the same time I changed the subscription policy to 'confirm' and upgraded from Postorius 1.2.3 (when pending user subscriptions were no longer shown). Seems like I have some homework to do to prevent spam subscriptions through my app.

5 years, 10 months

[MM3-users] Re: Gmail problems?

by Odhiambo Washington

On Sat, Apr 22, 2023 at 6:03 PM Stephen Daniel <swd(a)pobox.com> wrote: > Mailman Gurus -- > > I run a number of small lists for my neighborhood association. The largest > of these is ~120 users. Typical volumes are about 2 messages/day. > > In the past week or so a number of users who use gmail as their email > client have complained that list emails have been going to spam or > "promotions" folders. I've always had 1 or 2 users who had trouble > receiving mails, but this seems to be a significant percentage of all gmail > users. > > I have DMARC mitigation set to unconditional, and the DMARC action set to > "Replace From: with list address". > > My emails are sent using google workspace as my SMTP relay. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Does the above mean that your MM3 instance uses Google Workspace to relay the e-mails to subscribers? If that is the case, then I do not see how Gmail would put perfectly authenticated email in spam/promotion folders, unless something is not quite right with the content of those emails. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years

[MM3-users] How to fix: [Django] ERROR (EXTERNAL IP)

by Jigme Datse

This feels like something that I should have working. I know I've not been attending to things all that well, so the thing that has happened, that's got us from, "possibly doing nothing," to throwing this error is that I went to update my mail server, and in the update, Mailman3 stopped working entirely (it was a variety of things), but now it's launching, and will load the main web interface... but Going to any of the list pages, gives the above Error. Well, not exactly the above error, Django is in square brackets. OK, that will work better for me with the how to fix. How to fix, probably isn't quite what I'm looking for, it's how to diagnose. The error tells me that the IP address is 127.0.0.1 and that 127.0.0.1 is in the ALLOWED_HOSTS. I *mostly* see this coming from Google, but when I go and look at the webpage, I get: normal page at /mailman3/lists/ But my lists, all give me... Something went wrong HTTP error 500: {"title": "500 Internal Server Error"} I've tried to figure out where to go from here, and right now I'm not making any progress, so I thought I'd ask here.

5 months, 3 weeks

[MM3-users] OS update 18.04 -> 20.04 with Python 3.6 -> 3.8

by Torge Riedel

Hi, just want to report that updating my server's OS from Ubuntu 18.04 to 20.04 including an upgrade from Python 3.6 to 3.8 worked 75% on the mailman3 installation. Stopping and disabling the service before prevented most of the problems, but I forget to disable the cron jobs. **sigh** So whenever you have to upgrade your OS including python, don't forget the cron jobs. After OS upgrade I renamed both "venv" directories and rebuild them from my notes. Worked. Starting up mailman-core was easy. Getting mailman-web back to work was a little tricky: 1. After rebuild I forgot to run the post-update script, overseen that in my notes. **sigh #2** 2. My uwsgi-emperor was totally confused and needed some guidance and manual remove of .sock file 3. Finally I got this in the logs: /opt/mailman/web/venv/lib/python3.8/site-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. Seehttps://django-q.readthedocs.io/en/latest/configure.html#retry for details. warn( I checked the reference file from here: |https://gitlab.com/mailman/mailman-suite/raw/master/mailman-suite_project/settings.py?inline=false| and it misses the "retry" value. After adding it to Q_CLUSTER everything works fine. Kind regards Torge

3 years, 10 months

[MM3-users] Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by Mark Sapiro

On 2/18/22 08:43, gordon(a)dickens.com wrote: > > My only remaining problem is that I cannot access the individual mailing lists. That is, when I navigate a list and click on the list name then my browser displays: > > "Server error > An error occurred while processing your request." > > Concurrent with the above browser display, mailman3 sends an email to the system admin with the subject: > > "[Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/lists/list_local_name.domain.tld" > > This email and my logs now complain about: > > "Internal Server Error: /mailman3/lists/list_local_name.domain.tld/ > MultipleObjectsReturned at /mailman3/lists/list_local_name.domain.tld/ > get() returned more than one EmailAddress -- it returned 3!" > > Also, I get the same errors after I create a new mailing list as well. > > I hope that Mark and/or somebody here can offer up suggestions on what I need to do to fix this. Any suggestions would be very much appreciated! It seems like a database issue. I would like to help. What is the Traceback from that error? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: Welcome message template errors

by Mark Sapiro

On 4/23/24 14:59, Mark wrote: > > The welcome message is returned. > > root@hel:~# sudo -u mailman curl > https://LISTS.MYDOMAIN.COM/mailman3/api/templates/list/MYTESTLIST.LISTS.MYD… > Test Welcome message for new subscribers.root@hel:~# I don't know what the issue is. curl, running as user mailman, is able to get the url, but Mailman core, presumably running as user mailman, times out trying to get the url. I can't explain why. Try the following in `mailman shell` running as user mailman ``` (venv) $ mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> import requests >>> r = requests.get( ... 'https://LISTS.MYDOMAIN.COM/mailman3/api/templates/list/MYTESTLIST.LISTS.MYD…', ... timeout=5) >>> t.text ``` Note the URL above is all on one line. This is exactly what Mailman core is doing to get the template assuming the `uri` in the template` table entry is the argument of the requests.get(). If this times out, try increasing the timeout= value. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: [Mailman-Developers] Mailman 3.1 beta coming soon

by Stephen J. Turnbull

Barry Warsaw writes: > >I can also work on Postorius. Also in this vein I have a question. > >Should the DMARC settings be added to the Alter Messages tab in the List > >Settings view or would it be better to have a separate DMARC Mitigations > >tab. > > My gut reaction is to add a separate DMARC Mitigations tab, but Florian and > Terri have final say I think. I would find it more natural to have "Posting Policy" (which would include posting filters on size and list membership, as well as message alterations such as removing .exe files and enforcing plain text by removing or rendering HTML parts), and "Malware Mitigation", which would include IP, domain, and mailbox filters as well as DMARC. I think DMARC mitigation is probably too special to deserve its own tab. Probably this is way too much reorganization to do at this point, but I'd like to keep this point in mind. We are already getting reports that configuration options are hard to find just because it's different from Mailman 2. I suspect that the REST API is sufficiently flexible and regular that we'll be tempted to proliferate options, so let's try to keep them organized. Steve

8 years, 4 months

[MM3-users] Re: mailman-web: ResponseNotReady

by Dmitry Makovey

On 10/18/2017 01:41 PM, Abhilash Raj wrote: > Hi, > > $ docker-compose rm -f mailman-web > $ docker-compose up -d mailman-web > > This will basically create a new container for Mailman-web, but, since > the state of mailman-web is stored completely in database (database > container), I am not sure how to reset *just* mailman-web without > dropping mailman-core related tables too (they share the same database > but have their own separate tables). The above command will get you a > fresh copy of code running. > > You can potentially get the list of tables and drop them, or maybe > Diango has some way to reset it's state from Django shell (python > manage.py <http://manage.py> shell, from inside mailman-web will get you > shell). I may have to look it up. > > Also, just by looking at the traceback, I am not sure about the exact > error. I may have to debug more to arrive at a better conclusion, which > I won't able to do until after this weekend. thanks for the suggestions. I'll try to dig in direction outlined by you, may end up producing some code to automate such task in the future :) -- Sr System and DevOps Engineer SoM IRT

7 years, 6 months

[MM3-users] Re: django-mailman3 update causing errors

by Darren Smith

So we have pulled all fresh versions of these projects from gitlab as of last Friday: postorius hyperkitty django-mailman3 mailmanclient Django is version 1.11 When we installed, each of these were placed in a conda virtual environment. Postorius, Hyperkitty, and django-mailman3 are all still under a python 2.7 environment. Is that our problem here? Do they need to be in python 3 now? -Darren On Tue, May 1, 2018 at 3:47 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 05/01/2018 01:35 PM, Darren Smith wrote: > > Hello, > > > > In attempting to update our mailman3/postorius/hyperkitty installation, I > > have run into an error after upgrading the django-mailman3 project. > ... > > Any thoughts on why updating django-mailman3 would cause this? > > > To what version did you update? any 1.2 version is part of the migration > of Postorius/HyperKitty to Python 3 and requires > > postorius>=1.2.0b1 > hyperkitty>=1.2.0a1 > Django>=1.11 > django-mailman3>=1.2.0a2 > mailmanclient>=3.2.0b1 > > and is all Python 3 > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

6 years, 11 months

[MM3-users] Re: Chinese characters in list name shows question mark (?)

by Mark Sapiro

On 10/24/19 4:53 AM, Franklin Weng wrote: > > Thanks for your help. I did what you said above, but then I still got the > same result even after restarting mailman3 services. > > ~# mailman shell -l zh-l10n.lists.linux.org.tw > Welcome to the GNU Mailman shell > The variable 'm' is the zh-l10n.lists.linux.org.tw mailing list >>>> m.preferred_language > <Language [zh_TW] Chinese (Taiwan)> >>>> quit() The issue is the list welcome message is sent in the character set of the new member's preferred language and if that is not set in the subscription request, and it's not possible to do that in Postorius, it defaults to the installation's preferred language. It should probably default to the list's preferred language. See <https://gitlab.com/mailman/mailman/issues/608> You have two choices: You can set the installation's default language by putting [mailman] default_language: zh_TW in your mailman.cfg, or you can leave the default language English and set the character set for English to utf-8 by putting [language.en] charset: utf-8 in your mailman.cfg. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Request for help with configuring "from" headers in mailman3 list

by Stephen Daniel

Mailman3 users -- I am in the process of migrating a set of mailing lists from a very old privately operated server running mailman2 to a VM in Google's cloud (GCP) running mailman3. I have mailman3 up and running in GCP. However, VM's in GCP are not permitted to send emails. To work around this I configured postfix relay SMTP traffic through sendgrid.com. I chose Sendgrid because they offer a free service for low volume users. This works well for emails generated by the mailman3 system. However, it does not work for the list traffic itself. Sendgrid requires that the "From:" address on any email reference an authenticated domain. In the old mailman2 implementation, emails sent by mailman are listed as From: <human name via LISTNAME> LISTNAME(a)LISTDOMAIN.org Reply-to: <human name> sender(a)senderdomain.com (the original email's sender) Sendgrid would be happy with this, because LISTDOMAIN.org is a validated domain. However, in my mailman3 implementation, the From: header lists the original email's sender. Sendgrid rejects this because the original email's sender's address is not one of the validated domains. How do I configure mailman3 to generate headers in the same style as the old mailman2 implementation? Thanks! -- Stephen Daniel

3 years, 3 months

[MM3-users] Re: MAILMAN_ARCHIVER_KEY - 401 error

by Mark Sapiro

On 4/12/22 03:33, Torsten R. wrote: > > But when I try to send a message (as a member of a list) to a list I always get a 401 in mailman.log and the message that I should check if I provided MAILMAN_ARCHIVER_KEY and if it is correct. > So far, I can say that the key is the same in mailman-web.py (with single quotes) and mailman-hyperkitty.cfg (without quotes). > in mailman-web.py I have: > MAILMAN_ARCHIVER_KEY = 'somesecretkeywithlotsofcharacters' > and in mailman-hyperkitty I have this: > api_key: somesecretkeywithlotsofcharacters > > I have some messages in $var_dir/archives/hyperkitty/spool but mailman qfile <messagefile> doesn't show anything that would catch my eye. The issue is not related to message content. One possibility is that there is an incompatibility between mailman-hyperkitty >= 1.2.0 and HyperKitty <= 1.3.4. that could cause this. What are your versions? What is your setting in mailman-hyperkitty.cfg for base_url: if you append `api/` to that and do something like curl base_url/api/ it should return a page of documentation of the API. If that is the case, the issue is almost certainly communicating the api key between mailman-hyperkitty and HyperKitty -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users] changeaddress command and nonmembers

by Mike Wertheim

I recently upgraded a Mailman 2 installation (which included a number of email lists) to Mailman 3.3.3. There is one human user who in the past has used two different email addresses. Let's call them oldaddress(a)hotmail.com and newaddress(a)gmail.com. This person used to participate on an email list using oldaddress(a)hotmail.com (both posting and receiving). He then unsubscribed oldaddress(a)hotmail.com from the list and then subscribed to the email list as newaddress(a)gmail.com. All of this happened while using Mailman 2. Now that we're on Mailman 3 and the email list was migrated from MM2 to MM3, we see that newaddress(a)gmail.com is a Member of the list, and we see that oldaddress(a)hotmail.com is a NonMember of the list. That all makes sense. But now, this person has decided that they actually want to go back to using the old address. So I ran the command "mailman changeaddress newaddress(a)gmail.com oldaddress(a)hotmail.com". But that gave me this output: Usage: mailman changeaddress [OPTIONS] OLD_ADDRESS NEW_ADDRESS Try 'mailman changeaddress -h' for help. Error: Address oldaddress(a)hotmail.com already exists; can't change. Can anyone explain how I can do what I'm trying to accomplish? (Also, why is this error displaying the usage message? That seems odd, since the number and type of arguments was correct.)

2 years, 2 months

[MM3-users] Re: MM3 Docker

by Odhiambo Washington

On Wed, 9 Jan 2019 at 19:25, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/8/19 10:50 PM, Odhiambo Washington wrote: > > > Now that has clarified the matter for me. That even when I am logged out, > > the scripts do the neccessary > > to activate the venv to run things. > > > As mentioned before, a virtualenv is not like a container. It is only a > directory that contains among other things a bin/ directory with > activate scripts and easy_install, python, pip and wheel commands. > > When you activate a virtualenv in your shell, all it really does is add > a deactivate command, modify the command prompt and insert its bin/ > directory at the beginning of its PATH. > > What this means is whether or not a virtualenv is "active", running a > command from the bin/ directory in the virtualenv is using the virtualenv. > Thank you very much for the elaboration. What used to confuse me was the early stage documents which detailed how to run MM3 in a virtual environment - I am talking about the BETA days. I think from this point onward, I have the complete foundation information to move forward. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

6 years, 3 months

[MM3-users] Re: Weird hourly indexing error

by Mark Sapiro

On 5/12/20 3:02 PM, Mark Dadgar wrote: > > The second patch did not work either. Ahh, well. I think you need to do something like this: $ mm/bin/django-admin shell Python 3.7.1 (default, Dec 14 2018, 13:17:01) [GCC 5.4.0 20160609] on linux Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> from hyperkitty.models import Email >>> emails = Email.objects.all() >>> for email in emails: ... if email.content.find('\u200b'*5) >= 0: ... print('Found in ml {}, hash {}'.format( ... email.mailinglist.name, ... email.message_id_hash)) ... >>> _NAME/message/HASH/ This will print the mailing list and message id hash for messages found that contain at least 5 U+200B Unicodes in a row. You may need to adjust the '\u200b'*5 if it doesn't find anything. Once you know the list and hash you can go to something like https://example.com/hyperkitty/lists/LIST_NAME/message/HASH/ to see the message in the archive and delete it. Before deleting it, you might want to 'download' it. I'd be interested in seeing that to see if I can understand the issue better and why the patches don't work to solve it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: Topics - Tags

by Mark

On 2024-03-23 23:21, Stephen J. Turnbull wrote: > Mark writes: > > > >> In Mailman 2 there is an Admin web UI for "Topics". Is there > > >> such a web UI that can be enabled in Mailman 3 so that the list > > >> owners can create topics (tags) in their lists? > > Do you specifically want topics, that is, a way for users to select > subsets of the list posts based on themes set by the administrator? That's what I was referring to. One of the list admins was asking about it after I moved the list from Mailman 2 to Mailman 3. > There is (was?) an alternative specification implemented by the > Systers, which they call "dynamic sublists". > > If that sounds as good as Mailman-2-style topics to you, I can > add/emphasize it on our GSoC task list. Although that sounds good (and I don't think the use of email commands would be onerous to people who would value sublists), I am the wrong person to have an opinion on it as I haven't really used Topics in earnest and most likely would not use sublists. That said Steve, thank you for your considered reply. A font of useful (and much appreciated) information as always. Best, Mark

1 year

[MM3-users] Re: Mailman stops processing....... where to start looking for root cause?

by Stephen J. Turnbull

Mark Sapiro writes: > One of the runners has died, most likely the `out` runner, but > possibly another. The missing messages are stuck in a queue. Do ``` > ls -laR /opt/mailman/core/var/queue ``` to see in which queue the > messages are. The runner that processes that queue is gone or > possibly stuck. I have seen "stuck", in a multisite installation where Mailman's smarthost ended up being about 1000 miles from Mailman. I'm not sure what the issue is (we fixed the DNS, not Mailman :-), but every once in the while the connection would hang. In that case nothing showed up in the log. The only symptoms were the buildup in the out queue and a stale connection to port 25 on the smarthost. If your smarthost is not "network far" from the Mailman host, this is quite unlikely from my experience, although Mark may know better. In any case, I think the best way to start diagnosis is to check the Mailman and MTA queues for stuck messages. Of course in normal operation you will often see messages in the queue, but long queues or messages older than a minute are 99% a dead or stuck queue runner. Steve

1 year

[MM3-users] Re: hyperkitty won't list more than 5 posts and shows empty grey Activity Summary box

by Mark Sapiro

On 08/04/2017 02:54 AM, Cyprian Laskowski wrote: > Hi, > > On our new installation of Mailman 3, which seems to be otherwise working fine (thanks!), the "More..." link doesn't work, such that the list continues to only show 5 posts, even though it's clear that hyperkitty is aware of more (if I click on August, for example). This is <https://gitlab.com/mailman/hyperkitty/issues/134>. The fix is a one-liner at <https://gitlab.com/mailman/hyperkitty/commit/2034b937c438f66b465d86bebbbc12…> > Also, nothing is shown in the grey box under Activity Summary (the <svg class="chart-data"> element), although I'm not sure what's supposed to be shown there. The public archived list is here: http://seznami.cjvt.si/hyperkitty/list/test@seznami.cjvt.si/. I'd appreciate any pointers. The box is a bar graph of posts by day. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/> for what it should look like. I'm not sure why it's empty in your case. Do you have cron running all the Django minutely, quarter-hourly, ... tasks? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 8 months

[MM3-users] Re: Hyperkitty Archives - Sidebar years/months

by Mark Sapiro

On 11/7/18 4:18 PM, Enrique Terrazas wrote: > Thank you Mark > I don't think the periodic Django jobs are running. I do see the cron job executing the jobs as scheduled but I am seeing errors being sent to /var/spool/mail/mailman (thats the user that runs the MM3 application) that say: > /bin/sh: django-admin: command not found So whatever django-admin you are trying to run is not in the path of the cron job. Try an absolute path to django-admin instead. > If I run: > django-admin --help > > I get the following: > > Note that only Django core commands are listed as settings are not properly configured (error: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings.). I install Mailman in a virtualenv and the django-admin file I run contains #!/bin/bash . /opt/mailman/mm/venv/bin/activate cd /opt/mailman/mm export PYTHONPATH=/opt/mailman/mm export DJANGO_SETTINGS_MODULE=settings django-admin $@ The main things are the directory containing settings.py is /opt/mailman/mm and I export that as PYTHONPATH so my settings module can be found. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

[MM3-users] Re: Emergency Moderation

by Mark Sapiro

On 5/24/20 10:59 AM, Allan Hansen wrote: > In the MM3 settings there is an option to ‘Hold for moderation’ when members or non-members post to the list. > I use that for the same cases where in MM2 I switched a list to ‘Emergency Moderation.’ If you imported your MM 2.1 lists with `mailman import21`, `emergency` was set appropriately for the imported list and should be working to hold posts regardless of other settings. > My own current top-of-the-list issues: > > A bug: Moderators can’t see/edit the list of members even when allowed to by list setting. The visibility issue is <https://gitlab.com/mailman/postorius/-/issues/369>. Editing membership beyond what could be done via the admindb interface (i.e. clearing a moderated poster's mod flag) was never allowed for a moderator in MM 2.1. In MM 3, a moderator can set a member's moderation when handling a held post. Do you think a non-owner moderator should be able to make other changes to a member? > A feature request: Member changing email address on all lists he/she belongs to, without involving moderators. This is <https://gitlab.com/mailman/postorius/-/issues/399> and we're working on it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: Installing MM3 via pip fails…

by Patrick Ben Koetter

* Mark Sapiro <mark(a)msapiro.net>: > On 2/18/20 10:45 AM, Patrick Ben Koetter wrote: > > Has anyone managed to install MM3 recently using pip on Ubuntu 18? > > > > I followed the instructions at > > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…. > > As soon as I get to the Django part things get hairy. It seems Django requires > > something that was removed from it. > > > What exactly is the issue? I just tried following the doc starting at > <https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-setup> > and doing everything through > > (venv)$ python3 manage.py runserver > > and I encountered no issues. One possibility is the Ubuntu 18.04 box on > which I did this already had ruby-sass and python3-dev globally installed. > > sudo apt install ruby-sass > sudo apt install python3-dev > > Did you install these? Yes, I did. But to be sure I'll try on a vanilla VM and see how it goes if I install ruby-sass and python3-dev beforehand. p@rick -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein

5 years, 2 months

[MM3-users] Re: Backups & disaster recovery of mailman3

by Mark Sapiro

On 3/7/21 11:07 AM, David Partain via Mailman-users wrote: > Hi, > > So now I have a running mailman3 installation. Whew... > > Is there documentation of things like thorough backups and disaster recovery? I haven't yet found it. > > Backups: Obviously, I understand that I need to have datbase (mysql, in my case) dumps, and I'll have file system backups onto something that our IT folks will backup. Is there more I should think of? No, backing up the database with dumps and backing up Mailman's var/ directory and the various settings and mailman.cfg files should be sufficient. Backing up the entire Mailman installation might be useful should you need to restore it on a new server. > Disaster recovery: So, let's say my server (which is cloud-y) gets trashed and I need to get mailman back on a new server. Is this process described somewhere? I don't think so, but assuming you get all the Mailman pieces together on the new server, loading the database from a backup dump and restoring the var/ directory and the various settings and mailman.cfg files should do it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: Any possible way to reduce robot spam accounts?

by Franklin Weng

Hi Mark, Mark Sapiro 於 2023/7/21 12:01 寫道: > On 7/20/23 20:42, Franklin Weng wrote: >> >> Thank you. When I set it in my settings_local.py, I clicked register >> and got an error: >> >> ModuleNotFoundError at/accounts/signup/ >> No module named 'django_mailman3.views.user_adapter' >> >> (In the document the path is /etc/mailman3/settings.py but I >> installed it with Debian packages so I guess the path is somewhat >> different, and I thought setting in setting_local.py should work >> too. It seems work since it gave me the error above.) >> >> Do I have to install something else? Or disable some other options? > > > What is the version of django_mailman3 in your Debian package? As it > says in the FAQ article, "You would need django-mailman3 >= 1.3.6 for > these settings to work." > Debian Bullseye goes with 1.3.5, and Debian Bookworm goes with 1.3.9 but as I have said in another thread it has problems in django admin. So I downloaded the 1.3.9 source code, extracted it, and copied django-mailman3/views/user_adapter.py to /usr/lib/python3/dist-packages/django_mailman3/views. It worked! For a record here. Thanks for your help. Thanks, Franklin

1 year, 9 months

[MM3-users] Re: External MTA incoming mail: configuration

by Roland Giesler

On 2024/07/30 22:39, Mark Sapiro wrote: > It appears you have a situation where the MX for the Mailman domains > is not the Mailman server. You need to configure the MTA on > box2.gtahardware.co.za to relay Mailman's mail to the mailman server. > You can to this by configuring that MTA to use transport_maps, etc as > if it were the Mailman server. In order to get Mailman's generated > files on the other server, you need to create a process to do that. > When Mailman makes changes by adding or deleting lists or when it is > started, it updates the postfix_lmtp and postfix_domains files and > calls a command (normally postmap) to update the corresponding .db > files. The command can be set by setting `postmap_command` in the > `[postfix]` section in mailman.cfg. I'm not able to find any documentation about `postmap_command`, not even in the schema.cfg. If I have to provide method to update the postfix_lmtp and postfix_domains on another server, then it would have to something like sftp? mailman changes the files on the mailman server (in a location I set) and then postmap_command copies those files to the destination on the MTA server. Is that in principle what needs to be done? thanks again! Roland

8 months, 3 weeks

[MM3-users] Re: Installation Wooes

by Mark Sapiro

On 5/3/20 7:14 PM, Samir Faci wrote: > > Here's my next question. Hopefully this isn't off topic, but trying to get > postfix to work with mailman and I keep on getting relay denied issues. ... > These are the changes I have in postfix that seem relevant. > > /etc/postfix/master.cf > > mailman unix - n n - - pipe > flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py > ${nexthop} ${user} postfix-to-mailman.py is Mailman 2.1 only. It doesn't work with Mailman3. > /etc/postfix/main.cf > > compatibility_level = 2 > > recipient_delimiter = + > unknown_local_recipient_reject_code = 550 > owner_request_special = no > transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp > local_recipient_maps = $alias_maps hash:/var/lib/mailman3/data/postfix_lmtp > relay_domains = hash:/var/lib/mailman3/data/postfix_domains These mostly have to do with delivery of mail to Mailman rather than from Mailman. > smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated > defer_unauth_destination > myhostname = lists.domain.org > mydestination = $myhostname, localhost.localdomain, localhost, $mydomain, > lists.domain.org The entire output from `postconf -n` might be helpful. Also the postfix log messages for the the failed deliveries would be helpful. Can you send mail to csgeek(a)domain.com in other ways, e.g. mutt or mail or sendmail? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: [Django] ERROR (EXTERNAL IP): Internal Server Error: /accounts/login/

by Mark Sapiro

On 5/18/21 7:28 PM, Mark Dadgar wrote: > > I had actually done this but checked the Users section and had overlooked the Email Addresses section. It was as you suggested - duplicate emails differing only in case. > > Given that there was only one user account, how does this happen? List subscription without associated user account creation with slightly different case? First, the Django users are separate from Mailman core users and don't have anything directly to do with list subscriptions. As far as how there got to be one User in Django with two EmailAddresses differing only in case, that's probably a bug in Django allauth. The page at accounts/email/ doesn't allow adding an address that differs only in case from an existing address, but possibly adding via a social auth provider bypasses that check. I couldn't find an issue at https://github.com/pennersr/django-allauth/issues but that doesn't mean there isn't one. In case you haven't done it, I think just deleting one of the addresses (the non-primary one) in Django's Email Addresses section will solve your issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: Mailman3-Web lots of database queries

by Abhilash Raj

On Mon, Dec 3, 2018, at 11:44 AM, Stefan Tatschner wrote: > On Mon, 2018-12-03 at 10:01 -0800, Abhilash Raj wrote: > > So, if you are using Django's ORM to keep the task states in Django Q, this > > is bound to happen depending on how frequently do you run tasks. In Hyperkitty, > > we have some minutely tasks, which means the polling is going to be high. > > > > You can however, configure Django Q to store the tasks outside of database > > in a better high-speed in-memory database like Redis for example[1] for queuing > > the tasks. Other options like MongoDB, Amazon SQS is also available. > > Is it really necessary to have these high complexity? Reducing database > load by introducing another database seems wrong to me. Redis is not exactly a database, it is used as a message broker. The ORM backend in DjangoQ exists for low performance workloads where you can afford to poll the database that frequently and not have negative affects on rest of your system. It also lets you avoid installing a message broker like Redis. If your system does handle a ton of traffic, then it is recommended to use Redis or similar higher-performant systems. -- thanks, Abhilash Raj (maxking)

6 years, 4 months

[MM3-users] Re: Hyperkitty Error Curiosity

by Mark Sapiro

On 11/12/20 6:59 AM, Brian Carpenter wrote: > On 11/11/20 7:40 PM, Mark Sapiro wrote: >> >> The message has been delivered to the list, but it is not archived. The >> list post has an Archived-At: header with a URL, but the message isn't >> there at all. The only way to get it archived is to correct the message >> defect. > > Does the problematic message (null character) make it to the > hyperkitty_thread table? I thought that saying it is not archived would answer that, but no, nothing about that message is stored in any hyperkitty table. > Can a message with a null character be repaired with an automatic process? Probably, but I don't think HyperKitty should be in the business of attempting to repair message defects. This one issue of a null byte is arguably not a defective message, but rather an issue of storing a null byte in a database field, so maybe something could be done to `cleanse` that data before storing it. If I were going to look at doing that, I would need an example of a problem message, and ideally, an issue in the tracker. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: Hyperkitty 403 Forbidden Error

by Phil Thompson

On 07/08/2019 17:04, Abhilash Raj wrote: > On Wed, Aug 7, 2019, at 8:41 AM, Phil Thompson wrote: >> On 06/08/2019 09:48, Phil Thompson wrote: >> > On 06/08/2019 03:38, Abhilash Raj wrote: >> >> On Mon, Aug 5, 2019, at 10:06 AM, Phil Thompson wrote: >> >>> I'm in the process of setting up mailman3. The only problem I seem to >> >>> be >> >>> having is getting Hyperkitty to archive messages. Rather than the >> >>> authorisation problems people have previously asked about on the >> >>> list, I >> >>> am getting a 403 error... >> >>> >> >>> Aug 05 15:38:40 2019 (10229) HyperKitty failure on >> >>> http://localhost/mailman3/hyperkitty/api/mailman/urls: >> >>> <html><title>Forbidden</title><body> >> >>> <h1>Access is forbidden</h1></body></html> (403) >> >>> Aug 05 15:38:58 2019 (10222) HyperKitty failure on >> >>> http://localhost/mailman3/hyperkitty/api/mailman/archive: >> >>> <html><title>Forbidden</title><body> >> >>> <h1>Access is forbidden</h1></body></html> (403) >> >>> >> >>> Any suggestions would be appreciated. >> >> >> >> How did you install Hyperkitty? >> > >> > On Ubuntu... >> > >> > apt-get install mailman3-full >> > >> >> You probably need to the set the API key correctly in both Core and >> >> Hyperkitty. >> >> >> >> Have you looked at documentation here[1]? >> >> >> >> [1]: >> >> https://hyperkitty.readthedocs.io/en/latest/install.html#connecting-to-mail… >> >> >> >> Note that the MAILMAN_ARCHIVER_KEY = "value" (this value should be in >> >> quotes, single or double, doesn't matter) in your settings.py for Web >> >> (Django) should be same as the `api_key : value` (without quotes here >> >> in hyperkitty.cfg config file). >> > >> > That's all correct. I'm familiar with the authorisation issues that >> > other people have had. >> > >> > The only thing I'm doing differently (as far as I am aware) is that >> > I'm using a URL prefixed with /mailman3 which is stripped off in my >> > nginx configuration... >> > >> > # mailman3. >> > location /mailman3/ { >> > uwsgi_pass unix:/run/mailman3/web/uwsgi.sock; >> > include uwsgi_params; >> > uwsgi_param SERVER_ADDR $server_addr; >> > uwsgi_modifier1 30; >> > uwsgi_param SCRIPT_NAME /mailman3; >> > } >> > >> > location /mailman3/static { >> > alias /var/lib/mailman3/web/static; >> > } >> > >> > location /mailman3/static/favicon.ico { >> > alias /var/lib/mailman3/web/static/postorius/img/favicon.ico; >> > } >> > >> > ...but I don't see this affecting the mailman to Hyperkitty >> > communication. Posting to lists and the Postorius and Hyperkitty >> > frontends seem to work fine. >> >> I have now fixed the 403 error (by setting MAILMAN_ARCHIVER_FROM to my >> public IP address). However I now get a 400 Bad Request error. >> >> I have traced this to the archive() function in >> hyperkitty/views/mailman.py which is expect a POST but is actually >> getting a GET, specifically... >> >> GET '/mailman3/hyperkitty/api/mailman/archive?key=...' >> >> ...which seems to be a fairly fundamental problem. >> >> Again, any suggestions would be welcome. > > It should be sending POST request to archive emails[1]. How did you > grab the above request? Was it from logs? Yes, I added DEBUG=True in mailman-web.py and captured the HTML from mailman.log. > Do you have anything else in the logs? There should be something in > the Mailman Core or web logs should have something. There's nothing useful in the core log. There are 3 preceding entries in the web log... GET /mailman3/hyperkitty/api/mailman/urls?mlist=...&key=... GET /mailman3/hyperkitty/api/mailman/urls?mlist=...&msgid=...&key=... GET /mailman3/hyperkitty/api/mailman/urls?mlist=...&msgid=...&key=... There is one item in the spool directory. These were all (apparently) successful. It seems odd that the last two entries were identical. Phil

5 years, 8 months

[MM3-users] Re: HyperKitty failure: {"error": "'Thread' instance needs to have a primary key value before this relationship can be used."} (400)

by Stephen J. Turnbull

armin.schoeffmann(a)aegaeon.de writes: > > What version of Django is installed? > 4.1.2 If your main priority is to get mailman-web working, I suggest trying a downgrade of Django to 3.2.x. (Probably x=16 is current but any x in double digits should be OK). We just a couple weeks ago merged patches from a 3rd party to support Django 4. So quite a bit of risk here, I don't think any of the core devs are running Django 4 systems yet, and I know none of the production systems at python.org and mailman3.org do yet. If you're willing to help us get our code in shape for Django 4, of course we'd love to have a beta tester. :-) But to be honest, I have no idea what's going on with that error, and I don't know if either Abhilash or Mark would either. So it may take a while (or Mark could pop up in 10 minutes and wave his magic wand and all will be well -- that's life in the beta lane ;-). Steve

2 years, 6 months

[MM3-users] Re: Database problem after system upgrade

by Lars Bjørndal

I managed to upgrade the database. However, Mailman3 won't start: × mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: disabled) Drop-In: /usr/lib/systemd/system/service.d └─10-timeout-abort.conf Active: failed (Result: exit-code) since Wed 2023-11-15 06:49:38 CET; 44min ago Process: 28224 ExecStart=/opt/mailman3/venv/bin/mailman start (code=exited, status=1/FAILURE) CPU: 948ms nov. 15 06:49:38 dalen.lamasti.net mailman[28224]: return self.loaded_dbapi.connect(*cargs, **cparams) nov. 15 06:49:38 dalen.lamasti.net mailman[28224]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ nov. 15 06:49:38 dalen.lamasti.net mailman[28224]: File "/opt/mailman3/venv/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect nov. 15 06:49:38 dalen.lamasti.net mailman[28224]: conn = _connect(dsn, connection_factory=connection_factory, **kwasync) nov. 15 06:49:38 dalen.lamasti.net mailman[28224]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ nov. 15 06:49:38 dalen.lamasti.net mailman[28224]: sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "localhost" (::1), port 5432 failed: FATAL: Ident authentication failed for user "mailman" nov. 15 06:49:38 dalen.lamasti.net mailman[28224]: (Background on this error at: https://sqlalche.me/e/20/e3q8) nov. 15 06:49:38 dalen.lamasti.net systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE nov. 15 06:49:38 dalen.lamasti.net systemd[1]: mailman3.service: Failed with result 'exit-code'. nov. 15 06:49:38 dalen.lamasti.net systemd[1]: Failed to start mailman3.service - GNU Mailing List Manager. Mailman.log doesn't contain any info. How do I find the cause of this problem? Lars

1 year, 5 months

[MM3-users] Re: Bad Signature with Gmail

by Mark Sapiro

On 9/19/20 12:33 PM, Massimo Zappalà wrote: > Hi Mark, thanks for the reply. > > my /etc/opendkim.conf > AutoRestart Yes > AutoRestartRate 10/1h > UMask 002 > Syslog yes > SyslogSuccess Yes > LogWhy Yes > Canonicalization relaxed/simple > ExternalIgnoreList refile:/etc/opendkim/TrustedHosts > InternalHosts refile:/etc/opendkim/TrustedHosts > KeyTable refile:/etc/opendkim/KeyTable > SigningTable refile:/etc/opendkim/SigningTable > Mode sv > PidFile /var/run/opendkim/opendkim.pid > SignatureAlgorithm rsa-sha256 > UserID opendkim:opendkim > Socket inet:12301@localhost > > > my /etc/opendkim/SigningTable > *(a)catania.linux.it mailselector._domainkey.catania.linux.it Assuminng your list's domain is catania.linux.it, what you need to do to enable DKIM signing of this message is add SenderHeaders List-Post,Sender,From to /etc/opendkim.conf > full email django error > Internal Server Error: /hyperkitty/api/mailman/archive > > OperationalError at /hyperkitty/api/mailman/archive > (1366, "Incorrect string value: '\\xF0\\x9F\\x98\\xB1\\xF0\\x9F...' for column `mailman3web`.`hyperkitty_email`.`content` at row 1") Unfortunately, the rest of the detail doesn't help. What we need to see is the raw message. You should be able to find it in Mailman's var/archives/prototype/<list_address/new/ directory, perhaps by timestamp or something in the headers. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: Re-enable member after bouce processed disable

by Mark Sapiro

On 12/9/21 6:07 AM, Henrik Rasmussen wrote: > Recently I upgraded Mailman to GNU Mailman 3.3.4 (Tom Sawyer) (Postorius: 1.3.5 and HyperKitty: 1.3.4) which is now processing bounces. > > When a member have been disabled due to bounces, how is the member re-enabled? I would guess it would be under the "Users -> Members -> Member options -> Delivery status", but theses are both (Enabled and disabled) unchecked, not indicating whether or not the member is either or. You are looking at the user's list based preferences. If one of these is unset, it falls back to address based preferences and from there to the user's global preferences. You can see all of these for yourself at the Mailman settings choice in the dropdown at your user name, but for another list member you only see the list based preferences. > How do I or the list admins re-enable a bounce-disabled member? Just set the member's delivery status on the page you see to Enabled. Even though it was not previously shown as Disabled by Bounces, it will be enabled. Likewise the member can set her Delivery status to Enabled. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] nginx configuration on a multitasking server

by David Newman

Couple of questions about the sample nginx configuration given in the venv doc and the Mailman Mailman Suite Documentation v. 3.3 PDF: server { listen 443 ssl default_server; listen [::]:443 ssl default_server; server_name MY_SERVER_NAME; location /static/ { alias /opt/mailman/web/static/; } location / { proxy_pass 127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } ssl_certificate /path-to-ssl-certs/cert.pem; ssl_certificate_key /path-to-ssl-certs/privkey.pem; } 1. At least on my system, the proxy_pass statement will only run without errors if I change this to a fully formed URL, e.g., 'proxy_pass http://127.0.0.1:8000'. Is this a typo in the docs? 2. What document root(s) and alias(es) to use for Postorius and Hyperkitty and the Django admin on a server that also runs other services (e.g., Postfix for non-list mail and Roundcubemail)? With MM2, I use location statements with their own root and aliases: location /mailman { root /usr/lib/cgi-bin; fastcgi_split_path_info (^/mailman/[^/]+)(/.*)$; fastcgi_pass unix:///var/run/fcgiwrap.socket; include /etc/nginx/fastcgi_params; fastcgi_param SCRIPT_FILENAME \ $document_root$fastcgi_script_name; fastcgi_param PATH_INFO $fastcgi_path_info; } location /images/mailman { alias /var/lib/mailman/icons; } location /icons { alias /var/lib/mailman/icons; } location /pipermail { alias /var/lib/mailman/archives/public; autoindex on; } What is the MM3 equivalent way to do this? I think root would be somewhere under /opt/mailman but don't know exactly where, or which locations to point to. Many thanks! dn

3 years, 4 months

[MM3-users] Re: list footer questions

by Mark Sapiro

On 6/7/20 3:22 PM, kelly.close(a)lrewater.com wrote: > Well, Glory Be! My .cfg settings were fine but the public.template table was empty (I'm using PostgreSQL and accessing it with pgAdmin). I had not considered that there needed to be database content representing the template but it makes sense. Everything else is in there, which is the whole reason why we went with Mailman3 in the first place. > > After manually creating this record in the public.template table it WORKED!!! > name = list:member:regular:footer > context = f2p2-test.udfcd-lists.org > uri = file:////var/lib/mailman3/templates/lists/f2p2-test.udfcd-lists.org/en/list… > (username and password were left blank) username and password are only required for basic auth to the URI if needed so blank is correct. However, you shouldn't have needed to do that. I only mentioned it in case there was an entry for the name and context with a URI pointing elsewhere. The default if there is no entry is to use Mailman's normal search rules which include templates/lists/<list-id>/en/list:member:regular:footer.txt. So I have to think that without that entry, it was searching a different templates/ directory. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 10/29/20 11:26 AM, Mark Sapiro wrote: > On 10/29/20 5:17 AM, Brian Carpenter wrote: >> On 10/29/20 4:27 AM, Alex Schuilenburg via Mailman-users wrote: >>> On 29/10/2020 01:57, Brian Carpenter wrote: >>>> With Mailman 3, every list owner has the ability to remove a reply in >>>> a thread, a complete thread, and even the entire archives. That is a >>>> welcome difference from MM2 in my opinion. >>> A very welcome difference, only I don't see this option in the web >>> interface of my debian 3.2.1 installation. Is this a shell only >>> option, 3.3 feature or configuration option I have missed? >> It is not a shell option. It can be done via Hyperkitty but I am not >> sure when that feature showed up. > > Actually, with current HyperKitty, only site admins can remove messages > or threads or the archive. The ability for list owners to do it is > <https://gitlab.com/mailman/hyperkitty/-/issues/261>. Thanks Mark. To clarify more, we have this ability for List owners with our own custom admin interface (Affinity). I thought Postorius had that. When I checked out Postorius, I was indeed logged in as server owner. Sorry for the incorrect info. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 5 months

[MM3-users] Re: Splitting hosts: mta&core vs postorius

by samuel.d.darwin＠gmail.com

> the fourth paragraph: "Because the REST server has full administrative access, it should never be exposed to the public internet. By default it only listens to connections on localhost. Don’t change this unless you really know what you’re doing." Let's say that you are trying to embed Hyperkitty into a larger Django project that's horizontally deployed in an autoscaling group or K8S. The mailman-core component would be better served from a fixed IP address and a single server. In order for mailman-web to communicate with mailman-core, it needs to listen on a network interface, not localhost. So, you'd like to have a config field, and listen on a reachable interface and then configure the AWS Security Groups or Firewall to limit access. The proposed "listen" field is optional, and in its absence, it defaults to the current behavior, which is localhost. This scenario matches the "really know what you’re doing" case. You'd be facilitating a more advanced architecture, although not requiring it, and still default to localhost. However, again I say "theoretical", because we ran into other difficulties with embedding Hyperkitty in a larger Django project. It seems easier to break that into a bite sized pieces, and only address them one at a time.

1 year, 3 months

[MM3-users] Re: WEB UI fail to reply and create new thread

by Mark Sapiro

On 12/19/20 3:02 AM, Carlo Landmeter wrote: > We are not running in debug mode, we simply set the loggers to log DEBUG or else we don't see much info. > I also doubt the shown error is the problem as I see more template errors. > I have also tried to run the official docker images mailman-docker but im having the same issue. > > When I post via the online form, i can see uwsgi requests with http status 200 from the ajax call, so i would expect it to work, but it does not leave a message in hyperkitty nor sends an email. > > PS emails are send just fine via smtp posting. The error reported from hyperkitty/ajax/temp_message.html in the OP has nothing to do with the replies not being sent or archived. hyperkitty/templates/hyperkitty/ajax/temp_message.html is called to build the HTML response sent to the web browser after the reply has been sent to Mailman core. Abhilash's fix at <https://gitlab.com/mailman/hyperkitty/-/merge_requests/299> will get rid of that error, but I would be very surprised if it fixes the problem. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: is there a mailman command/setting to periodically clean archives?

by David Newman

On 12/29/21 4:11 PM, Mark Sapiro wrote: > On 12/29/21 3:58 PM, William Oliver wrote: >> >> I'd like to delete all my archives that are more than a certain age, >> e.g. more than a week old. I can easily do that with a cron job, >> deleting old files in >> >> >> /opt/mailman/mm/var/archives/prototype/testlist(a)example.com/* >> >> which is, as far as I can see the only place archive emails live. > > > Those are emails archived in the prototype archiver. That's all the > prototype archiver does - store the mail there. The HyperKitty archived > emails are stored in the mailmanweb database in the hyperkitty_email > table. Attachments are in the hyperkitty_attachment table and other > tables are also involved. As a followup: Is there any need or advantage to running both the prototype and hyperkitty archivers? I did an installation following the venv directions, and it looks as though the system now uses both archivers. If this is a duplication of effort and storage, is it safe to disable the prototype archiver like this: # /etc/mailman3/mailman.cfg .. [archiver.prototype] enable: no and then delete anything under here? /opt/mailman/mm/var/archives/prototype/ Thanks dn

3 years, 3 months

[MM3-users] Re: Finding a user to delete them

by Stephen J. Turnbull

Brian Carpenter writes: > I do think List Admins would want an interface to help "manage" a > user account on behalf of a user then what is currently available > in Postorius. Oh, no question about that whatsoever. I'm quite surprised that this facility isn't present yet. (I rarely make mistakes in mass subscribe and the defaults work fine for my subscribers -- or they make their own changes -- so I can't recall ever encountering this need.) I wonder if in Mailman 3 where user profiles exist and are clearly *not* subject to control by *list* admins in the same way that subscriptions are, and in this day of GDPR etc if maybe we need to restrict admin access to various user properties. This sounds like a rather difficult design problem. > I don't see this functionality built into Mailman 3 nowhere near > the extent that Mailman 2 has. Web interfaces are supposed :-( to be easy enough for Great-Grandma to use, so I imagine the designers didn't think much admin intervention would be needed. > My approach with Affinity is definite leaning very heavy on the > needs of list admins atm. Perhaps that's a good division of responsibility between Postorius and Affinity dev processes. Something to think about. Steve

5 years, 1 month

[MM3-users] Re: Problem with list creation

by Abhilash Raj

On Thu, Sep 17, 2020, at 4:17 AM, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > On 9/16/20 8:25 AM, Pawel Grzywaczewski wrote: > > > > We increased timeout in mailman.cfg > > This looks like the issue in Shashikanth's post, too: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > They are also creating more than 1000 lists. > > Do we know why these timeouts are happening? (Search for "list > creation times out" returns no results in either core or Postorius > issues.) This is the first time I am actually seeing this. I tried hammering a local server with default number of workers, 2, and created 5000 lists in a loop and went through pretty smooth. I am probably not replicating the exact situation, I am using the sqlite database (which I presumed would be slow and choke up faster but...it didn't). Creating list isn't one of the slow operations AFAIK, so I am actually surprised that it needs increasing timeout. It could be the interaction with database layer maybe, but I can't be sure without more debugging. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

4 years, 7 months

[MM3-users] Re: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Mark Sapiro

On 5/24/24 2:18 AM, marcus--- via Mailman-users wrote: > > The problem, however, is that it does not send out any mails, nor do they appear in the archive. > > When I look in the Mailman-Log I find: > > May 16 01:44:55 2024 (6833) Cannot connect to SMTP server localhost on port 25 This is a misleading error message. It can occur when Mailman's out runner can't read a template. You need to check ownership and permissions on mailman/templates in the code tree and Mailman's var/templates directory which probably has permissions errors from running inport21 as root. Also, if you've set any templates in Postorius, they may not be accessable if your setting for POSTORIUS_TEMPLATE_BASE_URL is not good. > May 16 01:48:15 2024 (61252) error opening connection to nntp_host: localhost > [Errno 111] Connection refused > May 16 01:48:15 2024 (61252) NNTP error for list vereinsmitglieder(a)ludothek.de: > [Errno 111] Connection refused Are you gating messages to/from usenet for this list? If so, you have to set host: and port: and maybe user: and password in the nntp section of mailman.cfg -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 4 weeks

[MM3-users] Re: Hyperkitty: Error when rebuilding Index

by Mark Sapiro

On 11/26/21 4:35 AM, M4tze wrote: > Dear list members, > > if there is any Hyperkitty expert here, I have issues in Hyperkitty > (just updated Maxkings Docker images) when rebuilding the Index. > > Unfortunately, there are more than 25,000 mails and I do not know which > one is/might be broken. Does the error mean that the rebuilding process > is incomplete or does it simply skip the erroneous message? It means the process is incomplete. > Traceback (most recent call last): ... > return self._result.fetch_row(size, self._fetch_type) > UnicodeDecodeError: 'utf-8' codec can't decode byte 0xed in position > 3209: invalid continuation byte I'm not sure what's going on here. I suspect the issue is withe the `content` of some message in the hyperkitty_email table in the database. You could try a database query like ``` SELECT * FROM hyperkitty_email WHERE LEN(content) >= 3209; ``` If you're lucky, that may just return a few messages and enable you to find the problem one. Otherwise, you could try first running `mailman-web clear_index` and then run `mailman-web update_index` with --start and --end options to specify a date range and zero in on the offending message. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Should I try to install mailman3 on Kubuntu 20.04?

by Sam Darwin

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 at 4:31 PM Bill Oliver <billo(a)billoblog.com> wrote: > > I have been a happy camper running mailman3 on a vps I rent from a > vendor, running CentOS 7. CentOS 7 is past end of life, so I moving > over to a new machine running Kubuntu 20.04 LTS. I have been searching > the intertubes and have seen a bunch of people having headaches trying > it. So... > > Is Ubuntu 20.04 cool with mailman3? Should I go ahead and give it a > shot or use a different distro? > > Should I do the apt install, the virtualenv install, or try the docker > install? > > thanks > > billo > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to samuel.d.darwin(a)gmail.com >

6 months, 2 weeks

[MM3-users] Re: Finding a mailman3 installation description that works

by Andrew Hodgson

Abhilash Raj wrote: >On Tue, Mar 31, 2020, at 11:28 AM, Andrew Hodgson wrote: >> ralf.wiegand(a)tena-sda.org wrote: >> >> >WE are currently using mailman2. I have the task to setup and install a maiman3 server. Postfix is installed and working. Can anybody point me to a link where the actual installation is described using RHEL 7 or RHEL 8. This will be a >hardened DISA compliant server, so I am trying to avoid installing compilers and tools that are not part of the standard RHEL 7 repos. > >> Have you looked at creating a development environment using a Python3 >> venv somewhere else (eg another server or container) then copying the >> venv out to the production server? >Python virtualenvs are really not movable because of the paths that are in there. It is tricky to get that working right, I would caution against doing that. Thanks for this, I actually did this work over the weekend to test a restore on a new server using the same paths because I was worried about this being an issue. It did work, but the paths were exactly the same. I may have to re-investigate quick restore options (probably writing a script to create the venv and re-constitute the packages). Andrew.

5 years

Search results for query "dO"