Search results for "2021" - Mailman-users

Re: Documentation for transferiering a list between mm3 and mm3

by Mark Sapiro

On 2/26/21 11:03 AM, Morris Jones wrote: > On 2/26/2021 10:55 AM, Mark Sapiro wrote: >> 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. > > Would it be unreasonable to do a database dump on the old instance and a > restore on the new one? The question is transferring a `list`. I took that to mean transferring one of multiple lists to another installation which may also have other lists. -- 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

Re: Current status and issue deleting Archives in Mailman3

by Mark Sapiro

On 11/2/21 11:50 AM, bob B wrote: > So I am teaching myself to fish, and see that it is actually django-admin, so that is in > mailman-web? (in docker) > > But i get this: > > $ docker exec -it mailman-web /bin/bash > bash-5.0# django-admin shell > Python 3.8.10 (default, May 6 2021, 06:30:44) > [GCC 9.3.0] on linux > Type "help", "copyright", "credits" or "license" for more information. > (InteractiveConsole) >>>> from hyperkitty.models import MailingList > Traceback (most recent call last): ... > raise ImproperlyConfigured( > django.core.exceptions.ImproperlyConfigured: 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. Do what it says. I.e. run DJANGO_SETTINGS_MODULE=path/to/settings; django-admin shell -- 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

Re: [SOLVED] Re: Re: Help with Newbie error -- I think I deleted my server

by William Oliver

On Sat, 2021-12-25 at 10:19 -0800, Mark Sapiro wrote: > On 12/25/21 7:13 AM, William Oliver wrote: > > > > Just out of curiosity, if I could not have guessed a valid ID > > number > > and did not have the admin interface, how could I have figured out > > what > > site IDs were available? > > > If Postorius is working, recent versions show the SITE_ID in the > domains > view. I.e. after you added your domain you could have noted the > SITE_ID > and made the change in settings before deleting the example.com > domain. > > In any case, the django_site table in Mailman's database has the > information. > Thanks. Yep, I peeked at the database and there it was. That would probably been more efficient than randomly choosing numbers... billo

3 years, 6 months

duplicate SITE_IDs and broken /postorius/lists/ display; Mailman Client

by Stanisław Findeisen

Hi I am having 4 different virtual domains (FILTER_VHOST = True). However on the domain list page in Postorius: https://.../postorius/domains/ I can see only 3 different SITE_IDs: 1,1,4,3. If I recall correctly, the "3" and "4" were created manually using the Postorius Web UI, whereas the two "1"s were created using the Mailman Client: client.create_domain(name) Is this a bug? Or did I mess something up? What significance do those SITE_IDs have? What I also noticed is that in the Postorius Web UI: https://.../postorius/lists/ both "1" domains display the lists contained in "3", whereas both "3" and "4" display correctly their lists. Except the "3", all domains are empty at the moment (no lists) (so "4" correctly displays no lists). Not sure if this is related?... Mailman Core Version GNU Mailman 3.3.3 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] Thanks! Stanisław

3 years, 3 months

Re: Mailman backend maintenance task

by Eugenio Jordan (external)

Dear Robert. Thanks so much for your prompt answer. I am afraid this is not feasible, as this MTA is also serving other purposes, hence impacting not only the messages addressed to distribution lists, but actually all of them. Besides, we would not like to resort to relaying in mail servers we do not control for retries, as they may have so heterogeneous behaviours regarding how the subsequent attempts are dealt. I would you to also please confirm whether there is a way to stop just Hyperkitty, or Django maintenance tasks. I would like you to please confirm whether the runners need the backend available just to deliver mails to the members of the distribution lists. Many thanks for your time once more. Best regards. -----"Robert Moody" <[1]robert(a)kneedrag.org> wrote: ----- To: [2]eugenio.jordan(a)esa.int From: "Robert Moody" <[3]robert(a)kneedrag.org> Date: 08/23/2021 06:09AM Cc: [4]mailman-users(a)mailman3.org Subject: Re: [MM3-users] Mailman backend maintenance task A simple solution would be to stop the MTA in front of mailman. That is assuming the MTA is only delivering to mailman and nothing else. This would force any mails being sent during the maintenance to queue up on the sending server and once the maintenance is done starting the MTA will allow mails that were queued on the sending MTAs to get delivered. Downside is mails will be delayed based on the sending servers retry settings. Get [5]BlueMail for Android On 23 Aug 2021, at 05:55, [6]eugenio.jordan(a)esa.int wrote: Dear all. My apologies if the answer to this question is obvious, but I am pretty newbie for 3 version, and to be very honest I haven't had enough time yet to have a deep look into the documentation. Our customer is currently using PostGRESQL as backend, and we would like to perform some maintenance tasks, namely running vacuum full, or at least trying to rebuild hyperkitty_email primary key related index. We have been asked on the real impact of putting in place such initiative. Though the latter is related to archiving, I haven't found a way to stop just Hyperkitty or Django related processes other than stopping Mailman's core, hence preventing mails addressed to distribution lists from being delivered, could you please confirm if I am correct? Regarding the former, as far as I have read, the "mappings" lists -> addresses are stored just in the database, so if we run some kind of procedure or task like vacuum which will lock exclusively tables, or want anyway to have the database stopped for a cold backup or whatever, Mailman willl not work, that is, again the mails addressed to the distribution lists will not be delivered. Will you please confirm this point, too? Really wish we had a testing environment to have been able to check this ourselves and not bothering others, but unfortunately we lack it, and we need to provide an answer as soon as possible. Thanks a lot for your time. Best regards. __________________________________________________________________ Mailman-users mailing list -- [7]mailman-users(a)mailman3.org To unsubscribe send an email to [8]mailman-users-leave(a)mailman3.org [9]https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org / This message is intended only for the recipient(s) named above. It may contain p roprietary information and/or protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received this e-mail in error, please notify the sender immediately. ESA applies appropri ate organisational measures to protect personal data, in case of data privacy queries, please contact the ESA Data Prot ection Officer (dpo(a)esa.int) References 1. mailto:robert@kneedrag.org 2. mailto:eugenio.jordan@esa.int 3. mailto:robert@kneedrag.org 4. mailto:mailman-users@mailman3.org 5. https://bluemail.me/ 6. mailto:eugenio.jordan@esa.int 7. mailto:mailman-users@mailman3.org 8. mailto:mailman-users-leave@mailman3.org 9. https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org

3 years, 10 months

Re: Mailman, etc. upgrade woes and persistent bugs

by Allan Hansen

Thank you, Mike. I will see how to get this across to my users. :-) With love, Allan > On Feb 12, 2021, at 11:55 , Mark Sapiro <mark(a)msapiro.net> wrote: > > On 2/12/21 10:27 AM, Allan Hansen wrote: >> They need to resubscribe to each list they want the new address to be used for. >> Subscriptions involves permissions from the moderators. It’s not a >> simple process, especially if you are on many lists. > > > Not true if they have a Django account. See my reply at > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. > > > -- > 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, 4 months

Re: Ann: Mailman Core 3.3.5 is out

by Eggert Ehmke

Should I upgrade my Mailman 3.3.3 installed from Debian Bullseye? I would have to bypass the Debian installer. Or will there be Debian packages available? Same question for Postorius 1.3.6 Am Mittwoch, 29. September 2021, 05:26:47 CEST schrieb Abhilash Raj: > Hey Everyone, > > I just tagged and uploaded Mailman Core 3.3.5 release. > > This release includes both bug fixes and some new features. A full list of > changes is available here: > > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS. > html#news-3-3-5 > > You can install this version using pip: > > $ pip install mailman==3.3.5 > > The release tarball is available on PyPI as well: > > https://pypi.org/project/mailman/3.3.5/#files > > Thanks to everyone who made this release possible! > > Abhilash > > > On Sep 19, 2021, at 11:02 AM, Abhilash Raj <maxking(a)asynchronous.in> > > wrote: > > > > Hey Everyone, > > > > I just tagged and released Mailman Core 3.3.5rc1 release. > > > > This is identical to 3.3.5b1 in code, the only changes that have been made > > are in utility scripts and testing configuration.> > > You can install this version using: > > $ pip install --pre mailman==3.3.5rc1 > > > > If you want to download a release tarball, you can do so from here: > > https://pypi.org/project/mailman/3.3.5rc1/#files > > > > This is the first (and only) planned release candidate for 3.3.5 release. > > The stable release is planned for next week. > > > > thanks, > > Abhilash > > > > On 9/7/21 12:39 AM, Abhilash Raj wrote: > >> Hello Everyone, > >> I am pleased to announce that Mailman Core 3.3.5b1 is now out. It is a > >> pre-release for 3.3.5, which is slated to come out in 3 weeks from now. > >> I am planning for a 2 week beta period, after which I'll release the > >> first RC and then stable a week after. Right now I am not planning to > >> release a second beta version, but if there are several changes in Core > >> in the next week or so, then I might. This release includes a lot of bug > >> fixes and some new features. It also includes a security enhancement > >> that improves the authentication of REST API by adding resistance to > >> some timing channel attacks. A full list of changes in this version can > >> be found here[1]. > >> [1]: > >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NE > >> WS.html#news-3-3-5 We have also made improvements in the i18n workflow > >> and now the email templates are updated from the translated messages in > >> the .po files that we get from Weblate. Documentation for translators is > >> available here[2] if you want to help translate Mailman into your native > >> language. [2]: https://docs.mailman3.org/en/latest/translation.html > >> > >> This is a pre-release version, if you want to test it with your setup, you can install it using: > >> $ pip install --pre mailman==3.3.5b1 > >> > >> If you want to download a release tarball, you can do so from here: > >> https://pypi.org/project/mailman/3.3.5b1/#files > >> > >> This release received a lot of contributions from community, which I am > >> really happy about! I'd like to thank everyone who made this release > >> possible!> > > -- > > thanks, > > Abhilash Raj (maxking) > > -- > thanks, > Abhilash Raj (maxking)

3 years, 9 months

Re: [EXTERNAL] Re: Database deadlock when trying to delete a member.

by Mark Sapiro

On 3/23/21 3:23 PM, Mark Sapiro wrote: > > Actually, that's a typo, but it's not an error. in Python, two strings > without an intervening operator are just concatenated, so > > "Interface for creating new databases.""" > > is just > > "Interface for creating new databases." concatenated with "" (the null > string). I looked and found a total of 3 which are being fixed by <https://gitlab.com/mailman/mailman/-/merge_requests/809> You can see these are really inconsequential with something like $ python3 Python 3.9.1 (default, Feb 6 2021, 11:54:30) [GCC 7.5.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> print("Interface for creating new databases.""") Interface for creating new databases. >>> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

Re: Mails for 1 specific mailinglist not being send and looping in out queue

by Eric Broens

Thank you very much Mark! I removed the footer and that solved the issue. It appears that there was one single quote in the footer. I didn't test, but I suspect that caused the problem. Best Regards,Eric On Thursday, January 14, 2021, 08:24:44 PM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 1/14/21 3:26 AM, Eric Broens via Mailman-users wrote: > These mails keep looping for days in the out queue and are never shunted. > Looks to me as a serious bug. > Is there anything that can be done for this? Is this possibly <https://gitlab.com/mailman/mailman/-/issues/745> -- 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

Re: new list not working

by Mark Sapiro

On 3/10/23 09:03, Christian via Mailman-users wrote: > > Again, that's only the post being delivered to Mailman. What comes after > that in the log? > > Mar 10 08:39:28 2023 (1005) Available AUTH mechanisms: LOGIN(builtin) > PLAIN(builtin) Mar 10 08:39:28 2023 (1005) Peer: ('127.0.0.1', 55662) Mar 10 > 08:39:28 2023 (1005) ('127.0.0.1', 55662) handling connection Mar 10 > 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'LHLO > zarathustra.ccalternatives.org' > Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'MAIL > FROM:<christian(a)naturalintelligence.us> SIZE=3498' > Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) sender: > christian(a)naturalintelligence.us Mar 10 08:39:28 2023 (1005) ('127.0.0.1', > 55662) >> b'RCPT TO:<redlatinleg(a)lists.ccalternatives.org>' > Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) recip: > redlatinleg(a)lists.ccalternatives.org > Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'DATA' > Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'QUIT' > Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) connection lost Mar 10 > 08:39:28 2023 (1005) ('127.0.0.1', 55662) Connection lost during > _handle_client() Mar 10 08:44:05 2023 (1005) Available AUTH mechanisms: > LOGIN(builtin) PLAIN(builtin) Mar 10 08:44:05 2023 (1005) Peer: > ('127.0.0.1', 54800) Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) > handling connection Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> > b'LHLO zarathustra.ccalternatives.org' > Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'MAIL FROM:<> > SIZE=1139191' > Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) sender: <> Mar 10 08:44:05 > 2023 (1005) ('127.0.0.1', 54800) >> b'RCPT > TO:<medialist-bounces+kkeys=courier-tribune.com(a)lists.ccalternatives.org>' > Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) recip: > medialist-bounces+kkeys=courier-tribune.com(a)lists.ccalternatives.org > Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'DATA' > Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'QUIT' > Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) connection lost Mar 10 > 08:44:05 2023 (1005) ('127.0.0.1', 54800) Connection lost during > _handle_client() Mar 10 08:45:15 2023 (1005) Available AUTH mechanisms: > LOGIN(builtin) PLAIN(builtin) Mar 10 08:45:15 2023 (1005) Peer: > ('127.0.0.1', 38820) Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) > handling connection Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> > b'LHLO zarathustra.ccalternatives.org' > Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'MAIL FROM:<> > SIZE=1155595' > Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) sender: <> Mar 10 08:45:15 > 2023 (1005) ('127.0.0.1', 38820) >> b'RCPT > TO:<medialist-bounces+john.harbin=blueridgenow.com(a)lists.ccalternatives.org> > ' > Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) recip: > medialist-bounces+john.harbin=blueridgenow.com(a)lists.ccalternatives.org > Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'DATA' > Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'QUIT' > Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) connection lost Mar 10 > 08:45:15 2023 (1005) ('127.0.0.1', 38820) Connection lost during > _handle_client() There are no messages from the out runner process. it isn't running or it's hung. > And have you checked if Mailman's out runner is running? Note that if it > died for some reason and wasn't restarted or used up its restarts, > restarting Mailman core won't start it. You need to stop Mailman core and > then start it. > > OK I DID THAT Did the mail start flowing? > Are there files in mailman's var/queue/out/ or var/queue/shunt/ directories? > > root@zarathustra:/opt/mailman/mm/var# ls -la queue/out total 4416 > drwxrwx--- 2 mailman mailman 4096 Mar 10 04:44 . > drwxr-xr-x 14 mailman mailman 4096 Mar 8 12:07 .. > -rw-rw---- 1 mailman mailman 1126829 Mar 10 04:39 > 1678316345.5510073+678e72d483278a233b12cc38ebc3786fbfd50a44.bak > -rw-rw---- 1 mailman mailman 1083682 Mar 8 20:00 > 1678334445.1113052+b43224b03f1ba2aa2610301331195b0cbaa151b7.pck > -rw-rw---- 1 mailman mailman 1083744 Mar 8 20:00 > 1678334445.1324928+10c5ec711b7a4364407685b7899a9e8ea25a1a8b.pck > -rw-rw---- 1 mailman mailman 1083680 Mar 8 20:00 > 1678334445.1501603+f2d2895ae7fa80ad387df77ffa17361294fe781c.pck > -rw-rw---- 1 mailman mailman 2922 Mar 9 07:49 > 1678376944.9032273+9923c3da8724cff6ff71b585d1971a90a0ae65cb.pck > -rw-rw---- 1 mailman mailman 2862 Mar 9 07:49 > 1678376944.9125621+2635b96fc6cd2ebb98a2c60a269d07517c1f5046.pck > -rw-rw---- 1 mailman mailman 2886 Mar 9 07:57 > 1678377458.4585488+73f68f6f05d6ee64020e05c8ba2569378e4238f0.pck > -rw-rw---- 1 mailman mailman 6600 Mar 9 07:59 > 1678377564.335885+63793d373c7668947ce4ef2c4a89644ba288d775.pck > -rw-rw---- 1 mailman mailman 8290 Mar 9 08:25 > 1678379122.8619912+bfba87ac1c5e97473ea9c9645a99719d11179308.pck > -rw-rw---- 1 mailman mailman 5966 Mar 9 08:48 > 1678380525.743866+d6f70271750015293a249f9ffae8200367eee509.pck > -rw-rw---- 1 mailman mailman 6124 Mar 9 13:01 > 1678395691.1910245+9e087862cd317d77af8586d5390d60d483af8123.pck > -rw-rw---- 1 mailman mailman 2789 Mar 9 13:31 > 1678397516.4386168+14bb385ad36166aef4a23e1d2b9dd92b50af254d.pck > -rw-rw---- 1 mailman mailman 2752 Mar 9 13:31 > 1678397516.4514658+00546161e5310c988ca3b4d0be4c4a96d3295969.pck > -rw-rw---- 1 mailman mailman 2321 Mar 9 13:58 > 1678399097.1614358+b7b3bfa9cdef9ada94045eed945862664aff065e.pck > -rw-rw---- 1 mailman mailman 2390 Mar 9 13:58 > 1678399097.172284+7188ab4729863b3781c0890ec3b1be7de642454a.pck > -rw-rw---- 1 mailman mailman 6031 Mar 9 14:07 > 1678399672.4968731+2caeb7c82672c9051be407b1cdb7a8b21a87d348.pck > -rw-rw---- 1 mailman mailman 2095 Mar 9 14:08 > 1678399689.8167183+199b2da6cd1f8a00d10c1cd79ccc6cbcb4bdd503.pck > -rw-rw---- 1 mailman mailman 7179 Mar 9 14:08 > 1678399689.8327854+a8d1dc73e5979bde43dccf48caa9bc58de575f41.pck > -rw-rw---- 1 mailman mailman 8357 Mar 9 14:19 > 1678400356.5360696+62b6dce2428e420d6cb53c337c61db69a6fe4d44.pck > -rw-rw---- 1 mailman mailman 5939 Mar 9 14:28 > 1678400903.3894706+d3f5dad6c67057edd0f2888e193dd71de14d2bf9.pck > -rw-rw---- 1 mailman mailman 2096 Mar 10 04:43 > 1678452191.4875023+2e00a89aa5454f965d35a7b8be6a4f620944b8a1.pck > -rw-rw---- 1 mailman mailman 7181 Mar 10 04:43 > 1678452191.4984088+1fd6f3aff9ef79aff269f4edc920f2424a8b35b7.pck > -rw-rw---- 1 mailman mailman 6036 Mar 10 04:44 > 1678452252.847286+552f758b7fca32c2f082bd922f68de1f850dec2d.pck Was this before or after you stopped and started Mailman core. If before, what is the situation now? Is mail being delivered? If after, is there still a 1678316345.5510073+678e72d483278a233b12cc38ebc3786fbfd50a44.bak file in que/out? If this file is still there, it is hanging the out runner. Stop Mailman, move this file aside and start Mailman and see if the rest of the messages are processed. If that fixes it, there is something in that one message causing this. You can examine it with `mailman qfile`. That message arrived at Wed Mar 8 14:59:05 2023 (1678316345.5510073 is a time stamp) and is apparently causing the problem. If moving it aside fixes things, you can send it to me off list and I will try to figure out what the issue is. > root@zarathustra:/opt/mailman/mm/var# ls -la queue/shunt total 12 > drwxrwx--- 2 mailman mailman 4096 Mar 8 12:07 . > drwxr-xr-x 14 mailman mailman 4096 Mar 8 12:07 .. > -rw-rw---- 1 mailman mailman 447 Apr 26 2021 > 1619433583.1513886+2626ca223f3fc4368f6cf90fecc1e0e50705c36a.pck This is an old shunted message. The exception that caused it and a traceback were written to mailman.log on April 26 2021. If you still have that log, the exception and traceback will show what happened. In any case, `mailman qfile queue/shunt/1619433583.1513886+2626ca223f3fc4368f6cf90fecc1e0e50705c36a.pck` will show the msg and its metadata. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

Mailman-users search results for query "2021"