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

[MM3-users] Re: Bulk delivery status change?

by Stephen Daniel

OK. Ran the script. No errors while running it, but when I look at the users through Postorius GUI, they still show as 'Disabled by Bounces' ?? On Sun, Nov 10, 2024 at 11:42 AM Stephen Daniel <swd(a)pobox.com> wrote: > Thanks all! I will use these pronto. > > On Sun, Nov 10, 2024 at 11:42 AM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 11/10/24 08:34, Odhiambo Washington via Mailman-users wrote: >> > On Sun, Nov 10, 2024 at 7:16 PM Stephen Daniel <swd(a)pobox.com> wrote: >> > >> >> Mistakes were made, and for while every single outbound email bounced. >> >> I've fixed the mistakes, but now in my largest and most active email >> list, >> >> every single user's delivery status is "Disabled by Bounces". >> >> >> >> Is there a way to bulk fix this? Or do I have to go into each user, >> one at >> >> a time, and fix them? >> > >> > Please see this thread: >> > >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> >> The script in that post does all lists. For a single list see >> >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> but note that the command line >> ``` >> $ shell -l list(a)example.com >> ``` >> should be >> ``` >> $ mailman shell -l list(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 >> >> _______________________________________________ >> 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 swd(a)pobox.com >> >

10 months

[MM3-users] Re: where to configure max_days_to_hold on MM3 GUI interface?

by Shashikanth Komandoor

Hello Mark, Thanks for helping me for moving ahead in my project. Troubling you again, I would like to put another request at you. As per your suggestion, I am trying to configure my list configuration through REST API for specially the parameter like max_days_to_hold as it is not available through interface and I am following the official links of mailman 3 i.e https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/listconf.html But I am getting "name is not defined" sort of errors as below: *>>> dump_json('http://localhost:9001/3.0/lists/ <http://localhost:9001/3.0/lists/>','ant(a)example.com/config <http://ant@example.com/config>',dict(display_name='My List'),'PATCH')Traceback (most recent call last): File "<stdin>", line 1, in <module>NameError: name 'dump_json' is not defined>>>* Actually I am new to REST API but hope this is the only issue that is preventing me to go ahead. Could you please help me by saying how should I handle this so that I should be able to configure *max_days_to_hold* of a list or multiple ? On Wed, Jan 29, 2020 at 11:20 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/28/20 8:42 PM, Shashikanth Komandoor wrote: > > > > But I could see that parameter value configurable on MM2 GUI > > interface in General Options but I don't see the same on the MM3 GUI > > interface. > > > There are many core settings not (yet) exposed in Postorius. > max_days_to_hold. is one of them. It can be set via `mailman shell` or > via the REST API > < > https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/rest.html#re… > >. > > -- > 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, 7 months

[MM3-users] Re: Problem creating list members using REST API

by Stephen Daniel

I can give you a program written in Go. Would that be helpful? On Tue, Jan 18, 2022 at 6:49 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/18/22 2:11 PM, Stephen Daniel wrote: > > The REST API documentation is a bit informal. As someone who is not > > familiar with mailman, and who doesn't know python, they are a bit of a > > slog. > > > Agreed. I guess we sort of assume that people dealing directly with the > REST API are familiar with both. > > > > It might be worth seeing if the code can be enhanced to allow the boolean > > values to be sent in using JSON booleans as well as JSON strings. > > > I think here we only have to deal with the REST API because other uses > of as_boolean are all on strings that come from config files. We can't > modify as_boolean directly, as it is part of a third party dependency > and is intended to be used with config files, not JSON objects, but I > think something like this will do it. > ``` > --- a/src/mailman/rest/helpers.py > +++ b/src/mailman/rest/helpers.py > @@ -249,6 +249,8 @@ class GetterSetter: > """ > if self.decoder is None: > return value > + if self.decoder is as_boolean and isinstance(value, bool): > + return value > return self.decoder(value) > > > > ``` > Perhaps you could try to test that. > > I just created https://gitlab.com/mailman/mailman/-/issues/970 for this. > It would help me in fixing this if you could provide a small piece of > your code that throws the error. > > -- > 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, 7 months

[MM3-users] Re: Emergency Moderation

by Abhilash Raj

On Sun, May 24, 2020, at 11:34 AM, Mark Sapiro wrote: > 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. Another way to achieve this request, without needing the Preferred Address route is to simply Patch the Member resource with the new address, which wouldn't trigger the full subscription workflow and would have the extra advantage of having the same delivery_mode and preferences. I created: https://gitlab.com/mailman/postorius/-/issues/425 to track this issue. > > -- > 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, Abhilash Raj (maxking)

5 years, 3 months

[MM3-users] Re: installing mailman3 core

by Mark Sapiro

On 5/29/20 7:41 AM, Ralf Wiegand wrote: > Mark - What is the difference between to two install methods? What are > my pros and cons? Installing from the GitLab repository will get the latest development version, however, you can also install from this repository via pip and pick a tag or commit to install <https://pip.pypa.io/en/stable/reference/pip_install/#git> `pip install mailman3` will install the latest released version. As of this writing, that's 3.3.1, so ``` pip install mailman3 ``` and ``` pip install git+https://gitlab.com/mailman/mailman@3.3.1 ``` should give the same result although the former installs from PyPI and the latter from GitLab. The advantage to installing the latest version from GitLab is you get features and fixes that haven't been released yet. The disadvantage is you might get new bugs, although the servers that support this list and all the Mailman 3 @python.org lists are generally running the latest GitLab versions, so any serious issues will be quickly found and fixed. > I have been using this: > >>>>> > > |# Note: if we are using a dedicated postgresql database server, all > postgresql changes need to be done on the actual postgresql server.| > |>>>| > |sudo yum install postgresql-server postgresql-contrib| > |sudo postgresql-setup initdb| > |sudo systemctl start postgresql| > |sudo systemctl enable postgresql| > |sudo -u postgres psql -c ||"SELECT version();"| > |sudo useradd -c ||"Mailman User"| |-s /bin/bash -m mailman| > |sudo -u postgres create role mailman;| > |sudo -u postgres createdb -O $USER mailman| > |sudo -u postgres psql -c ||"grant all privileges on database mailman to > mailman;"| > |sudo -u postgres psql -c ||"ALTER ROLE mailman WITH PASSWORD > 'secret123';"| > |sudo -u postgres psql -c ||"ALTER ROLE "||mailman||" WITH LOGIN;"| > |sudo echo ||"listen_addresses = '*' "| |>> > /var/lib/pgsql/10/data/postgresql.conf| > |sudo echo ||"# The user mailman will be able to access all databases > from a trusted location (any) without a password"| |>> > /var/lib/pgsql/data/pg_hba.conf| > |sudo echo ||"host all mailman 0.0.0.0/0 > trust"| |>> /var/lib/pgsql/data/pg_hba.conf| > |sudo systemctl restart postgresql| > |sudo ss -nlt | grep 5432| > |<<<| > |sudo yum install python36* --skip-broken -y| > |# check make sure you have both versions| > |sudo python --version| > |Python 2.7.5| > |sudo python3 --version| > |Python 3.6.8| > |sudo pip3 install psycopg2-binary| > |sudo chown mailman.mailman /opt/mailman| > |sudo chmod 755 /opt/mailman| > |# NOTE: The first initial mailman3 core setup has to be done manually.| > |# This is a important step to ensure the user "mailman" will run the > actual mailman3 application and not root.| > |# switch to user mailman| > |mailman# cd /opt/mailman| > |mailman# git clone https:||//gitlab.com/mailman/mailman.git| This gets the head of the GitLab master branch. > |mailman# cat <<EOT >> /opt/mailman/mailman/src/mailman/config/mailman.cfg| > |[devmode]| > |enabled: yes| > |recipient: root@localhost| > |[webservice]| > |hostname: localhost| > |port: 8001| > |show_tracebacks: yes| > |use_https: yes| > |[mta]| > |incoming: mailman.mta.postfix.LMTP| > |outgoing: mailman.mta.deliver.deliver| > |lmtp_host: localhost| > |lmtp_port: 8024| > |smtp_host: localhost| > |smtp_port: 25| > |[database]| > |class||: mailman.database.postgresql.PostgreSQLDatabase| > |url: postgres:||//mailman:secret123@<IP-ADDRESS or FQDN>/mailman| > |EOT| > |mailman# python3.6 -m venv venv-3.6| > |>>| > |mailman# source venv-3.6/bin/activate| > |(venv-3.6) [mailman@empire mailman]$ cd mailman| > |(venv-3.6) [mailman@empire mailman]$ python setup.py develop| > |(venv-3.6) [mailman@empire mailman]$ mailman info| > |<<| > | > | > | > | > |So I was told I don't have to do this, I can just simple do (rhel7) > | > |yum install pyhton3| > |pip install mailman| This gets the latest release from PyPI Other than that, you still have to do the configuration and install some dependencies as in the first method. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: Log rotation

by Darren Smith

Well, that is certainly a wealth of information from you two, thanks a ton! I've got a few things to try now. I'm going to have to look up the retry runner to see if that might help when we have to shut things down. I'll let you know what I find... On Tue, Apr 10, 2018 at 5:41 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/10/2018 03:39 PM, Abhilash Raj wrote: > > Yes, this is a known thing and the reason for it is that the SIGTERM > isn't delivered till the process wakes up next time. We can have the > process sleep for a smaller amount of time to fix this, but then it would > mean that it will be running much more often. > > > > It is the Retry runner, which has sleep_time set to 15m. I don't know if > you want to retry very often, like 2min or 5min, but you can change it by > adding the following snippet to your mailman.cfg > > > A long time ago (in a galaxy far away) Mailman 2.1 had a global > DELIVERY_RETRY_WAIT setting. This setting had been ineffective for > years, relying instead on the retry runner's sleep time. > > In 2.1.26, for what turned out to be a probably spurious reason, I made > DELIVERY_RETRY_WAIT effective again, although the retry runner still > sleeps for 15 minutes. > > We could implement something similar in MM 3 to allow the retry runner > to have a much shorter sleep time without actually retrying the delivery > that often. The down side of that is even though we aren't retrying > delivery each time the runner wakes up, we are dequeueing and requeueing > the message each time and this would have a file system impact. > > -- > 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, 5 months

[MM3-users] Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Simon Coggins

On 8 Nov 2021, at 11:11 am, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: Simon Coggins wrote: > On 7 Nov 2021, at 10:54 am, Mark Sapiro <mark(a)msapiro.netmailto<mailto:mark@msapiro.netmailto>:mark@msapiro.net<mailto:mark@msapiro.net>> wrote: > I wound up taking a different approach. I check for other references to > the message in the message store and only delete the message if there > are none. The fix is at > https://gitlab.com/mailman/mailman/-/merge_requests/932/diffshttps://gitlab…<https://gitlab.com/mailman/mailman/-/merge_requests/932/diffshttps://gitlab…> > Oh nice. That seems like a sensible solution. Thanks for tackling so quickly. I’ll do some testing today and roll it out once testing is complete. I made a small change to defend against 'impossible' situations. See https://gitlab.com/mailman/mailman/-/merge_requests/933/diffs<https://gitlab.com/mailman/mailman/-/merge_requests/933/diffs> Thanks for the heads up. I did a bunch of testing with the original patch and was happy with it so we’re running that in prod now. How far off is 3.3.6? Just working out if I apply this slight change or wait for the full release. _______________________________________________ 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.mailman3.org> --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: attachment.png Content-Type: image/png Name: attachment.png Replaced multipart/alternative part with first alternative.

3 years, 10 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Can we modify the docs? Ok, I'm going to add that config to main.cf and test Thank you El vie., 21 jul. 2017 a las 12:25, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 09:36 AM, Rafael Mora wrote: > > > > Postfix <http://www.postfix.org/>: To setup Postfix, add the following > > configuration to master.cf: > > > > # Support the default VERP delimiter.recipient_delimiter = > > +unknown_local_recipient_reject_code = 550owner_request_special = > > notransport_maps = > > hash:/path-to-mailman/var/data/postfix_lmtplocal_recipient_maps = > > hash:/path-to-mailman/var/data/postfix_lmtprelay_domains = > > hash:/path-to-mailman/var/data/postfix_domains > > > > > > I added that config at the bottom of the master.cf file and did a > 'postfix > > reload' and I got this error message: > > > > [root@localhost ~]# postfix reload > > /usr/sbin/postconf: fatal: file /etc/postfix/master.cf: line 129: bad > field > > count > > postfix/postfix-script: fatal: cannot execute /usr/sbin/postconf! > > > First of all, in a report such as this, it would really help if you > reported what is actually in master.cf in the vicinity of line 129. > > 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>. > > Also, what you post above is quite garbled. It is not clear what you > meant, but the lines to add should be > > > # Support the default VERP delimiter. > recipient_delimiter = + > unknown_local_recipient_reject_code = 550 > owner_request_special = no > transport_maps = > hash:/path-to-mailman/var/data/postfix_lmtp > local_recipient_maps = > hash:/path-to-mailman/var/data/postfix_lmtp > relay_domains = > hash:/path-to-mailman/var/data/postfix_domains > > > and should not be wrapped as in your post. > > -- > 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, 1 month

[MM3-users] Re: Badsignature on uwsgi-error.log

by Helio Loureiro

Hi Mark, Thanks for your response. I found what the issue was. I actually misspelled hyperkitty as hyPperkitty on the url. So the error on mailman-hyperkitty.cfg was: base_url: http://localhost:8000/hypperkitty/ I moved to: base_url: http://localhost:8000/hyperkitty/ and it was solved. Problem was the wrong link was getting a generic page from Django instead of error. And it was failing to do the parsing probably, which was taking wrongly as key mistake. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Thu, 21 Mar 2024 at 01:13, Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/20/24 14:25, Helio Loureiro wrote: > > Hi, > > > > I keep receiving a lot of errors like this: > > > > --- Logging error --- > > Traceback (most recent call last): > ... > > > "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", > > line 55, in unsign > > raise BadSignature('Signature "%s" does not match' % sig) > > django.core.signing.BadSignature: Signature "F6V0Dr_SvBsx5-cY8vcvLXrX8tA" > > does not match > ... > > > > The api_key on mailman-hypperkitty.cfg, SECRET_KEY and > MAILMAN_ARCHIVE_KEY > > on setting.py are the same. > > > Of those three, the api_key on mailman-hypperkitty.cfg and > MAILMAN_ARCHIVE_KEY must match. SECRET_KEY is different. It is a Django > thing and has nothing to do with the others. See > https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key > > If you changed it, that's the issue. If you know what it was previously, > you could set the previous value in SECRET_KEY_FALLBACKS, see > https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key-fallbacks > > -- > 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 >

1 year, 5 months

[MM3-users] Re: Hyperkitty issue(s)

by Mark Sapiro

On 5/27/20 2:24 PM, Bryan Loniewski wrote: > Hello -- > > I'm stuck trying to integrate Hyperkitty. I see the following errors in mailman.log and mailmansuite.log respectively: > > <snipped> > [2020-05-27 16:42:11 -0400] [5140] [ERROR] Error handling request /3.1/lists/bry_test4.lists-test.rutgers.edu/archivers > Traceback (most recent call last): > File "/opt/mailman/mm/venv/lib/python3.6/site-packages/gunicorn/workers/sync.py", line 134, in handle > self.handle_request(listener, req, client, addr) > File "/opt/mailman/mm/venv/lib/python3.6/site-packages/gunicorn/workers/sync.py", line 175, in handle_request > respiter = self.wsgi(environ, resp.start_response) > File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/database/transaction.py", line 50, in wrapper > rtn = function(*args, **kws) > File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/rest/wsgiapp.py", line 193, in __call__ > return super().__call__(environ, start_response) > File "falcon/api.py", line 274, in falcon.api.API.__call__ > File "falcon/api.py", line 269, in falcon.api.API.__call__ > File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/rest/lists.py", line 406, in on_get > for archiver in archiver_set.archivers > File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/rest/lists.py", line 407, in <dictcomp> > if archiver.system_archiver.is_enabled> File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/model/mailinglist.py", line 587, in system_archiver > raise AssertionError('Archiver not found: {}'.format(self.name)) > AssertionError: Archiver not found: hyperkitty I've been looking at the code, and I think this can occur if the mailing list has a configured archiver which is no longer known in mailman.config.config.archivers. I.e., the list has hyperkitty as an archiver, but hyperkitty is no longer configured as an archiver in Mailman. > and > > <snipped> > Traceback (most recent call last): ... > KeyError: 'file' This traceback is useless. All it says is a Django logging error occurred in trying to log the real exception. The interesting one is immediately before this in the log. > Note that I've kinda followed the Virtualenv route along with using Mark's helpful webpage re: his experiences. > > Some relevant? config files... > > mailman.cfg: > > <snip> > [archiver.prototype] > enable: yes > > [archiver.hyperkitty] > class: mailman_hyperkitty.Archiver > enable: yes > configuration: /opt/mailman/mm/mailman-hyperkitty.cfg > <snip> That looks good. > mailman-hyperkitty.cfg: > [general] > base_url: https://a_real_domain/mm3/hyperkitty > api_key: <movealong> > > I can provide additional conf file setups if warranted? I am curious (and perhaps this is in fact the issue) why when I run mailman conf I don't see the archiver.hyperkittty section even though its in the mailman.cfg file? I don't either and I don't know why., For example on lists.mailman3.org ``` mailman conf|grep [[]archiver [archiver.mail_archive] class: mailman.archiving.mailarchive.MailArchive [archiver.mail_archive] clobber_date: maybe [archiver.mail_archive] clobber_skew: 1d [archiver.mail_archive] configuration: python:mailman.config.mail_archive [archiver.mail_archive] enable: no [archiver.mhonarc] class: mailman.archiving.mhonarc.MHonArc [archiver.mhonarc] clobber_date: maybe [archiver.mhonarc] clobber_skew: 1d [archiver.mhonarc] configuration: python:mailman.config.mhonarc [archiver.mhonarc] enable: no [archiver.prototype] class: mailman.archiving.prototype.Prototype [archiver.prototype] clobber_date: maybe [archiver.prototype] clobber_skew: 1d [archiver.prototype] configuration: changeme [archiver.prototype] enable: yes ``` doesn't show hyperkitty and neither does ``` mailman conf -k enable [archiver.mail_archive] enable: no [archiver.mhonarc] enable: no [archiver.prototype] enable: yes ``` but ``` /mailman conf -s archiver.hyperkitty [archiver.hyperkitty] class: mailman_hyperkitty.Archiver [archiver.hyperkitty] clobber_date: maybe [archiver.hyperkitty] clobber_skew: 1d [archiver.hyperkitty] configuration: /opt/mailman/mm/deployment/mailman-hyperkitty.cfg [archiver.hyperkitty] enable: yes ``` So I don't think this per se is the issue. > Any suggestions? Try ``` mailman shell May 28 00:35:47 2020 (15162) patched 1/1 modules (sqlalchemy) 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 mailman.config import config >>> list(config.archivers) [<mailman.archiving.mhonarc.MHonArc object at 0x7fdd9ccff6a0>, <mailman.archiving.mailarchive.MailArchive object at 0x7fdd9ccffac8>, <mailman.archiving.prototype.Prototype object at 0x7fdd9ccffb38>, <mailman_hyperkitty.Archiver object at 0x7fdd9ccffe80>] >>> ``` Does yours list hyperkitty? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

Search results for query "sapiro"