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

[MM3-users] Re: Deleting A List

by Odhiambo Washington

On Fri, May 3, 2024 at 11:48 PM Mark Sapiro <mark(a)msapiro.net> wrote: > Mark Sapiro wrote: > > > update hyperkitty_email set mailinglist_id = 2 where mailinglist_id = 13; > > update hyperkitty_mailinglist_owners set mailinglist_id = 2 where > > mailinglist_id = 13; > > update hyperkitty_mailinglist_moderators set mailinglist_id = 2 where > > mailinglist_id = 13; > > update hyperkitty_thread set mailinglist_id = 2 where mailinglist_id = > 13; > > delete from hyperkitty_mailinglist where id = 13; > > update hyperkitty_mailinglist set name = 'list(a)lists.nog.ke', list_id = > > 'list.lists.nog.ke' where id = 2; > > Or instead of that you could just go to the new list(a)lists.nog.ke > archive in HyperKitty and delete it and then just do the > ``` > update hyperkitty_mailinglist set name = 'list(a)lists.nog.ke', list_id = > 'list.lists.nog.ke' where id = 2; > ``` > I went with this approach and worked super! Thank you. So, seeing as deleting a list retains its archives, if I want to delete a list together with its archives, do I first delete the archives, then follow with the list? -- 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]

2 years

[MM3-users] Re: Migrating mailman3 to latest ubuntu lts

by Helio Loureiro

Hi, I forgot to mention that, but there is no mailman-web on ubuntu packages on 18.04. So I can't find a way to run it. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Thu, 14 Dec 2023 at 18:50, Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/14/23 10:19, Jered Floyd wrote: > > > > Did you run the upgrade steps? > > > > https://docs.mailman3.org/en/latest/upgrade-guide.html > > > > For schema upgrades you will at least need to do "mailman-web migrate", > but please read the entire section as 3.1.1 to 3.3.9 is a big step. > > > These are all important and necessary steps, but "mailman-web migrate" > updates schemas for the mailman-web database. It does not update the > alembic migrations for the mailman database. > > -- > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to helio(a)loureiro.eng.br >

2 years, 4 months

[MM3-users] Re: Changes in Django admin interface are not syncing to postorius gui /database

by Mark Sapiro

On 11/9/24 06:52, Odhiambo Washington via Mailman-users wrote: > > I looked at Django Admin and Postorius and I see all my MLs in both. What you see in Django admin is in the HYPERKITTY section and corresponds to hyperkitty_* tables in the mailmanweb database. > What I am sure about is that I did NOT create my MLs using Django admin UI. > I either created them using the CLI or Postorius. > Having said that, I did run two tests: > 1. Create a ML in Postorius and check whether it appears in Django admin - > The list was visible in Django Admin Because the list you created had the hyperkitty archiver enabled. > 2. Create a ML in Django admin and check whether it appears in Postorius - > The list was NOT visible in Postrorius Because it's only in HyperKitty. > 3. Create a ML in CLI and check if it appears in both Django admin and > Postorius - List is visible in Postorius, but not in Django admin Becayse this list did not have the hyperkitty archiver enabled. > ``` > MariaDB [mailmansuite]> select list_name, list_id from mailinglist where > list_name like 'ulf%'; > +-----------+-------------------------------+ > | list_name | list_id | > +-----------+-------------------------------+ > | ulftest2 | ulftest2.lists.kictanet.or.ke | > | ulftest3 | ulftest3.lists.kictanet.or.ke | > +-----------+-------------------------------+ > ``` These are only Mailman lists. > The list that I created using Django admin is NOT listed here! Because it's only in HyperKitty. > ``` > MariaDB [mailmansuite]> select list_id, name from hyperkitty_mailinglist > where list_id like 'ulf%'; > +-------------------------------+-------------------------------+ > | list_id | name | > +-------------------------------+-------------------------------+ > | ulftest1(a)lists.kictanet.or.ke | ulftest1(a)lists.kictanet.or.ke | > | ulftest2.lists.kictanet.or.ke | ulftest2(a)lists.kictanet.or.ke | > +-------------------------------+-------------------------------+ > ``` > The list I created using Django admin and the one I created using > Postorius are both listed, but the one I created from CLI is not listed. Because for some reason, the CLI created list does not create the HyperKitty archive until there is a post or until the `new_lists_from_mailman` job runs even though hyperkitty is enabled. > So there must be some logic behind this. However, I don't know what it is. The bottom line is you can have lists in HyperKitty that are not in Mailman and vice versa. The only thing you can't do is create a list in HyperKitty via the HyperKitty web UI, but you can use hyperkitty_import to import a mbox for a list which is not in Mailman and will be only in HyperKitty. Also, while you can create a list in Mailman that isn't in HyperKitty, if the list has hyperkitty enabled it will be created in HyperKitty when the `new_lists_from_mailman` job runs. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: FYI: Django security releases issued: 4.0.6 and 3.2.14

by David Newman

On 7/7/22 12:26 PM, Mark Sapiro wrote: > On 7/7/22 11:10 AM, David Newman wrote: >> On 7/7/22 10:25 AM, Mark Sapiro wrote: >> >> pip install -U mailman postorius django-mailman3 hyperkitty >> mailman-web uwsgi >> >> and it downgraded Django back to 3.0.14. > > > Because mailman-web 0.0.5 has in its setup.cfg > ``` > install_requires = > Django<3.1 > ``` > try > ``` > pip install -U git+https://gitlab.com/mailman/mailman-web.git > ``` > to get the latest mailman-web whose Django requirement is > ``` > install_requires = > django >=2.2, !=3.0, <4 That seemed to work OK, thanks. mailman-web is now on a dev version of 0.0.6 and Django is now on 3.2.14. However, pip now throws a warning when looking at package info: (venv) mailman@somehost:/home/dnewman$ pip show mailman-web WARNING: Ignoring invalid distribution -jango (/opt/mailman/venv/lib/python3.9/site-packages) Name: mailman-web Version: 0.0.6.dev9+gc606169 Summary: Mailman 3 Web interface. Home-page: https://gitlab.com/mailman/mailman-web Author: Mailman Developers Author-email: mailman-developers(a)python.org License: GPLv3 Location: /opt/mailman/venv/lib/python3.9/site-packages Requires: django, hyperkitty, postorius, whoosh Required-by: How to correct that so the command runs clean with no warnings or errors? This is on a host running Debian 11 with mailman3 and friends installed in a venv. Thanks. dn

3 years, 10 months

[MM3-users] Re: "to" Headers for Non-Anonymous lists

by Mark Sapiro

On 6/9/25 14:23, Dan Caballero wrote: > Hello, > > At the request of a list owner, we changed the settings on a list to "Anonymous = No" so that list members could see who a message was coming from. > > It seems a side effect of the setting is that users are now using "reply-to" and some messages are going out to the list addressed in the manner below. > > "Last Name, First Name via list-name <list-name(a)caltech.edu>" This is a consequence of DMARC mitigations. > The list owner feels this is confusing and some members may inadvertently email the list when they intend to email the individual. When the From is munged in that way for DMARC the orikinal From is put in Reply-To: or perhaps Cc: depending on other settings. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/handlers/dmarc… for details of this process and its goals. Assuming your list's Reply goes to list setting is No Munging The original From: should be in Reply-To: of the delivered. It appears that the messages that are sent To: Last Name, First Name via list-name <list-name(a)caltech.edu> are sent by an MUA that is ignoring Reply-To: and replying to From:. > I understand this is likely a client side caching issue since most email clients create an index of contacts based on previously received emails. > > Aside from reverting back to "Anonymous = Yes", is there any setting we can change at the list level to force the "to" field to persist as the list email address? Do you mean you want the From: in delivered messages to be the original poster's From: so that replies to the From: go to the OP. You can accomplish this by setting DMARC mitigation action to No DMARC mitigations, however this will ensure that any mail whose From: domain publishes a DMARC policy of quarantine or reject will most likely be bounced by all large ESPs. We do are best to ensure that a simple reply to a message to which DMARC mitigations are applied will go to the poster unless the Reply goes to list setting says otherwise. But I am confused as to your goal. Previously when the list was anonymous, all replies went to the list. Maybe your goal is to have list replies be addressed to <list-name(a)caltech.edu> rather than Last Name, First Name via list-name <list-name(a)caltech.edu>. If that is the goal, you could try setting Reply goes to list setting to Reply goes to list. That will set a Reply-To: list's short description <list-name(a)caltech.edu>. That may be what you want as long as the responder's MUA honors Reply-To: over From: -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months

[MM3-users] Re: All addresses in a bounced list posting seem to be considered as bouncing

by Mark Sapiro

On 7/9/22 9:51 AM, Andy Smith wrote: > > Over in Exim's mainlog I then see that delivered out to list > members. One of them rejects it at SMTP time, which I think causes > this: > > Jul 09 12:46:13 2022 (71509) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) > Jul 09 12:46:13 2022 (71509) Peer: ('127.0.0.1', 35440) > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) handling connection > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'LHLO lists0.bitfolk.com' > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'MAIL FROM:<>' > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) sender: <> > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'RCPT TO:<users-bounces(a)mailman.bitfolk.com>' > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) recip: users-bounces(a)mailman.bitfolk.com > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'DATA' > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'QUIT' > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) connection lost > Jul 09 12:46:13 2022 (71509) Connection lost during _handle_client() The SMTP rejection should not cause that. An SMTP recipient reject is processed internally and does not result in anything sent via SMTP to the list-bounces address. > …and I think that bounce message somehow incremented the bounce > score for andy(a)bitfolk.com even though that address was only present > in the original post's Cc: and body. If the original post was the message delivered to users-bounces(a)mailman.bitfolk.com, it is possible that simplematch or another recognizer parsed those addresses from the message body. > Is there a good way to further debug this? Maybe by being able to > see the full content of the DSNs that Mailman generates? As I posted previously, the DSN that Mailman generates is defined at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/outgoi…, but this message is not sent anywhere. It is only saved for possible inclusion in an admin notification or a probe message. If you send me the post as received from the list, I can run it through flufl.bounce and see what that produces. You might also be able to find the fake dsn and/or the message received via SMTP to users-bounces(a)mailman.bitfolk.com in Mailman's var/messages/ directory, although these are pickles and need to be examined with `mailman qfile`. > I think I've seen this before in the last couple of weeks so I'm > sure it'll crop up again soon. I've seen it mention about bounce > score for users-leave before, but I only really paid attention today > when it also listed my own address. users-leave probably is parsed out of the message footer. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I read the doc and it says that when the DEBUG var is set to False we should do these commands: django-admin collectstatic --pythonpath example_project --settings settings django-admin compress --pythonpath example_project --settings settings I did the first one and got this: (env2) [mailman@localhost mailman-suite]$ pwd /var/lib/mailman/mailman-suite (env2) [mailman@localhost mailman-suite]$ django-admin collectstatic --pythonpath mailman-suite_project --settings settings You have requested to collect static files at the destination location as specified in your settings: /var/lib/mailman/mailman-suite/mailman-suite_project/static This will overwrite existing files! Are you sure you want to do this? Type 'yes' to continue, or 'no' to cancel: yes 0 static files copied to '/var/lib/mailman/mailman-suite/mailman-suite_project/static', 345 unmodified. why it did not copy the files??? El mar., 1 ago. 2017 a las 23:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/01/2017 02:40 PM, Rafael Mora wrote: > > Why isn't it sending emails? > > > > What do you think? > > > What exactly are you doing that you think should result in sent mail? > > -- > 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

8 years, 9 months

[MM3-users] Re: Hyperkitty 403 Forbidden Error

by Mark Sapiro

On 1/20/22 11:40 PM, Josef Dietl wrote: > Dear all, > > > > Sorry for coming back to a topic that seems to be done for 18 months now. > > I'm staring at this issue for a few days now (on and off). But I still get > these messages: > > > > Jan 19 22:43:27 2022 (149439) HyperKitty failure on > https://lists.[...]/hyperkitty/api/mailman/urls: > <html><title>Forbidden</title><body> > > <h1>Access is forbidden</h1><p>Please check the IP addresses > > assigned to MAILMAN_ARCHIVER_FROM in the settings file. > > </p></body></html> (403) > > > > . and consequently, nothing ends up in the archive. > > > > I have checked (among others): > - MAILMAN_ARCHIVER_FROM - doesn't make a difference. 127.0.0.1, external IP > address, different orders, '*'. OK. > (Asterisk makes a difference, see at the bottom) ??? I didn't see what. > - MAILMAN_ARCHIVER_KEY in mailman-web.py matches api_key in > mailman-hyperkitty.cfg (except for the quotes). According to the editor's > color coding, the quotes are "right", too. I have removed special characters > to circumvent diverging treatment in different environments > > - I guess it doesn't matter, but wget --user restadmin --password [.] > http://localhost:8001/3.1/lists works, too. That is Mailman core's REST API which is not the issue here. > - ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https" (probably also doesn't matter > > > > I'm running a fresh package installation from Debian Bullseye with > certificates from Certbot with nginx, so Certbot may have messed with my > nginx config, but even that seems to be OK: Yes, Certbot has inserted > http->https redirection, but I'd expect that a https base_url and > ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https" circumvents that. It should. Note that your primary resource for help with issue with Debian packages should be Debian. > Mailman info says ... > To provide all possible information, I'm also adding the nginx log that > seems to correspond to that request (no other requests at that time, give or > take five minutes): Yes, everything yields 403 response codes. > > > > [.] - - [19/Jan/2022:22:43:27 +0000] "GET > /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&key=[.] > HTTP/1.1" 403 175 "-" "python-requests/2.25.1" The issue here is accessing the hyperkitty API. The base URL for these accesses is configured in mailman-hyperkitty.cfg. From what I see here, that is something like `http(s)://host.example.com/hyperkitty/` If you append `api/` to that base URL and go there in a web browser do you get a page of documentation of the HyperKitty API? If so, then figure out why it works from a web browser and not when Mailman core does it. If you get the 403, figure out why. This is probably an nginx 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, 3 months

[MM3-users] Re: Database read only error on mailman_sync job

by Ugnius

Thank You, Mark for guideline. I accidentally posted here. I wanted to start new thread and just replaced subject of messages. Message was sent to this thread anyway. The reason of this issue was very simple. I creadet symlink in /usr/local/bin/django-admin to /project/home/manage.py, because I was unable to set original django-admin file to work as it should to work. Later I decided to run mailman project under other user and forgot about that symbolic link. So it was normal, that previous user had no privileges on database file. Thank You for helping. > On 12 Sep 2019, at 21:50, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 9/1/19 1:02 AM, Ugnius S wrote: >> >> I guess that issue is hyperkitty database, but I even do not know the name >> and location of that database. > > See the DATABASES definition in your Django settings. The default is a > sqlite3 database named mailmansuite.db in the same directory as 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 > _______________________________________________ > 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, 7 months

[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Shashikanth Komandoor

Hi Mark, Thank you for your help. I have traced the versions of different components of mailman 3. I am downloading through GIT LAB because I need to modify the code according to my organization's requirements like to add SMS notifications when a mail is waiting for pending approval and so. With your help, I have found out the commits I am using in my environment. I got them using the way you suggested "git log". That may be helpful for you to help dummies like me. *### Mailman Core Version ###* *commit 437cb49ffc29ef8960ef26d18bd883ed5aa61ded* *Merge: 98cf97b 0bca998* *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>* *Date: Thu Oct 15 14:02:36 2020 -0700* * Merge branch 'template' into 'master'* * Clarify the posting instruction in the list welcome message.* * See merge request mailman/mailman!723* *### django-mailman3 Version ###* *commit d9e675e5cc1b966f9cd02b2e492649972f8ddc40* *Merge: ea2b33a c091e43* *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* *Date: Thu Oct 15 00:40:51 2020 +0000* * Merge branch 'fix-ci' into 'master'* * Use GHCR for the CI image* * See merge request mailman/django-mailman3!108* *### Hyperkitty Version ###* *commit 36f43466763c2686cf4d69c982ea64b956c30939* *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* *Date: Mon Oct 5 04:54:44 2020 +0000* * Use GH registry to pull CI image.* *### Mailmanclient Version ###* *commit aaa529808e2d61899f90509da4ea802a70d2c8ff* *Merge: ff39dd8 8670751* *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* *Date: Thu Oct 15 01:09:32 2020 +0000* * Merge branch 'fix-ci' into 'master'* * Use GHCR for the CI image* * See merge request mailman/mailmanclient!130* *### Mailman Hyperkitty Version ###* *commit 87db8b03cc4ceba8ef8eafedeaaf11f99f2e50e0* *Merge: 35ff801 04deff5* *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>* *Date: Fri Jun 19 18:15:57 2020 +0000* * Merge branch 'fix_25' into 'master'* * Add a test for the presence of surrogates in the stringified message.* * Closes #25* * See merge request mailman/mailman-hyperkitty!7* *### Mailman-suite Version ###* *commit 3b8780f26d544cb333970eae43ccffc7e34314aa* *Merge: 74e7927 4463b31* *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>* *Date: Sat May 30 00:32:40 2020 +0000* * Merge branch 'doc_mb4' into 'master'* * Added comment about OPTIONS = {'charset': 'utf8mb4'} to settings.py.* * See merge request mailman/mailman-suite!8* *### Postorius Version ###* *commit 02e3183c3cd9e069d8d886426b76b08504ea5e1e* *Merge: 61242d2 321310c* *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* *Date: Thu Oct 15 00:43:14 2020 +0000* * Merge branch 'fix-ci' into 'master'* * Use the GHCR registry for CI image.* * See merge request mailman/postorius!549* I have removed only mailmanclient and re-cloned it from gitlab and ran the python setup.py develop command. But still the same error. Is there anything else I can do to get rid of that error. Thanks in advance. <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, Oct 27, 2020 at 6:56 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/26/20 6:10 PM, Shashikanth Komandoor wrote: > > > > How to find out the versions of the each and every component > > of the mailman 3 like mailman core, mailmancilent, postorius, > > hyperikitty, mailman-hyperkitty, django-mailman3, mailman-suite and so, > > after installation? > > > cd to the directory in which you cloned the gitlab project for the > component and do `git log` > > > > If I am running an old mailmanclient or older version of any > > other mailman component, please suggest how to upgrade either one or > > multiple components based on the requirement. Is there any link that > > would help me to upgrade ? > > > > I have used the > > link https://docs.mailman3.org/en/latest/devsetup.html to install the > > mailman 3 components. I expected that the procedure followed in this > > link would install the latest versions of the mailman 3 components. > > Please correct me if I am wrong. Is there any latest version > > compatibility table ? > > > If you installed each of mailman, mailmanclient, django-mailman3, > postorius and hyperkitty according to instructions like > > $ cd ~/mailman > $ git clone https://gitlab.com/mailman/mailmanclient.git > > Then set up mailmanclient: > > $ cd mailmanclient > $ python setup.py develop > $ cd .. > > from that document, you should have the latest version. If that is the > case, `git log` in the mailmanclient directory should begin like > > commit aaa529808e2d61899f90509da4ea802a70d2c8ff (HEAD -> master, > origin/master, origin/HEAD) > Merge: ff39dd8 8670751 > Author: Abhilash Raj <maxking(a)asynchronous.in> > Date: Thu Oct 15 01:09:32 2020 +0000 > > Merge branch 'fix-ci' into 'master' > > Use GHCR for the CI image > > See merge request mailman/mailmanclient!130 > > commit 8670751caff689733751ef323ef521c4a3fa1237 > Author: Abhilash Raj <raj.abhilash1(a)gmail.com> > Date: Wed Oct 14 17:36:58 2020 -0700 > > Use GHCR for the CI image > > commit ff39dd8f03a820f442f2251553c444370df3b914 > Merge: 80ebed4 76d44e1 > Author: Abhilash Raj <maxking(a)asynchronous.in> > Date: Fri Aug 7 19:35:05 2020 +0000 > > Merge branch 'invite' into 'master' > > Add support for inviting an email address to join a list. > > See merge request mailman/mailmanclient!129 > > or if you did this before Oct 15, maybe it starts with > commit ff39dd8f03a820f442f2251553c444370df3b914 > > The particular commit you need for your issue is > > commit 86eb0da3cdb48e253b0d36138ab7cf91259a7583 > Merge: c8dcb1e 28d1c3a > Author: Abhilash Raj <maxking(a)asynchronous.in> > Date: Sat May 16 08:02:21 2020 +0000 > > Merge branch 'held-count' into 'master' > > Add a new get_held_count() API to get a count of held messages. > > See merge request mailman/mailmanclient!122 > > > > Note that unless you intend to do actual development of Mailman 3, you > should be following > <https://docs.mailman3.org/en/latest/install/virtualenv.html> rather > than <https://docs.mailman3.org/en/latest/devsetup.html>. > > -- > 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

5 years, 6 months

Search results for query "sapiro"