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

[MM3-users] Re: Mass change Digest delivery mode

by iMark

Le 2026-08-05 04:52, Mark Sapiro a écrit : > The last line > ``` > member.delivery_mode = DeliveryMode.plaintext_digests > ``` > needs to be > ``` > member.preferences.delivery_mode = > DeliveryMode.plaintext_digests > ` `` Super! Thank you very much. Here is the working final (I hope the formatting gets preserved across mail clients). ------------------------------------------------ How to change the Deliverymode for users in one list from MIME Digest to PlainText Digest ------------------------------------------------ su mailman (venv)$ mailman shell -l mylist(a)mydomain.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 mylist(a)mydomain.com mailing list >>> from mailman.interfaces.member import DeliveryMode >>> for member in m.subscribers.members: ... if member.delivery_mode != DeliveryMode.regular: ... member.preferences.delivery_mode = DeliveryMode.plaintext_digests ... >>> commit() >>> exit() ------------------------------------------------ NOTE TO SELF: Line 10 use 1 tab or 4 spaces after the first ellipse Line 11 use 2 tabs or 8 spaces after the second ellipse. Line 12 <ENTER>after the third and final ellipse ------------------------------------------------

2 months, 1 week

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

by Shashikanth Komandoor

Hi Mark, Thank you very much for your response. I understood myself as quite ignorant even to find out the versions of each of the component. But my "mailman info" output looks like the below: *(venv3) [root@dlist-lsmgr mailman]# mailman info* *GNU Mailman 3.3.2rc2 (Tom Sawyer)* *Python 3.6.8 (default, Aug 10 2019, 06:54:07)* *[GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]* *config file: /var/lib/mailman/mailman/var/etc/mailman.cfg* *db url: postgres://<username>:<password>@127.0.0.1/mailman* *devmode: DISABLED* *REST root url: http://localhost:8001/3.1/ <http://localhost:8001/3.1/>* *REST credentials: restadmin:restpass* *(venv3) [root@dlist-lsmgr mailman]# pwd* */var/lib/mailman/mailman* 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? 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 ? Also please suggest me an URL that would install the latest versions of mailman 3 components and allow me to do customizations related to our domain. <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 Mon, Oct 26, 2020 at 4:16 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/25/20 8:22 AM, Shashikanth Komandoor wrote: > > Hi Team, > > > > I am currently running Mailman 3 with version 3.3.2rc2 and > in > > built postfix version 2.10.1-6 on RHEL 7.5 with PostgreSQL 11.9 version > > with default values. As of now, we don't have any lists and just > installed > > software components only. > > > > After the installation and configuration, I have tried > > creating the domains and lists. I was successful in creating them but > when > > I tried to login and browse the lists using LDAP authentication, I am > > getting the "Mailman REST API not available. Restart Mailman core". > > > > I see the below trace in the mailmansuite.log. > > > > > *Traceback (most recent call last): File > > > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/mailmanclient/restbase/base.py", > > line 119, in __getattr__ return self._get(name) File > > > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/mailmanclient/restbase/base.py", > > line 86, in _get raise KeyError(key)KeyError: 'get_requests_count > ... > > > > I don't see any error messages in the mailman.log. And I > > also executed a few curl commands in getting the details of the lists > > created and list info which I got their results successfully. > > > > Could you please guide where exactly I am missing or do I > > need to make any changes in my customizations ? > > > I think the issue is your mailmanclient is too old. The version of > Postorius you are running requires mailmanclient >3.3.1 which is only > available from GitLab <https://gitlab.com/mailman/mailmanclient>. > > What version of Postorius is this? It appears to be >1.3.3. If you > install Postorius from unreleased code on GitLab, you have to install > all of mailman, mailmanclient and django-mailman3 as well. > > > -- > 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, 11 months

[MM3-users] Re: Archive date/time vs elapsed time

by Mark

On 2023-06-27 13:34, Mark Sapiro wrote: > On 6/26/23 7:46 PM, Mark wrote: >> Hi >> >> In the archive's "Recent", "Most active" etc displays, the date and >> time of each post is shown. >> >> However, when viewing by "Thread" listing, each post shows the elapsed >> time since it was posted ie. the number of days, hours since it was >> posted (eg. 1 day, 2 hours). > > I don't see this. It may have been recently changed. Please visit the > archive of this list at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/ > and if you see the issue there, post a URL of a page on which you see > it. No, I don't see it on the MM users' archive. The archive where I'm seeing it is HyperKitty version 1.3.4 on a Debian packaged MM 3.3.3 The problem lay therein? In the Hyperkitty docs there doesn't appear to be any mention of options or changes for the display of datetime/elapsed-time

3 years, 3 months

[MM3-users] Re: very few moderation capabilities for moderators

by Guillermo Hernandez (Oldno7)

On 17/9/21 19:58, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 17/9/21 17:24, Mark Sapiro wrote: >> On 9/17/21 6:18 AM, Guillermo Hernandez (Oldno7) via Mailman-users >> wrote: >>> On 16/9/21 16:40, Mark Sapiro wrote: >>>> >>>> Are you asking what the equivalent MM 3 scripts would be? >>>> >>> More or less: I'm asking for a general direction here. I think I >>> cannot use tthe "withlist" method as before, inside a python script, >>> and I'm not sure how to do it. >> >> >> You can run scripts via withlist in Mailman 3 similarly to Mailman 2. >> See >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… >> >> > First, thanks for the prompt response, Mark. > > Maybe I'm a little bit ofuscated, but I readed this doc many times > when I was searching how to do it... but I cannot imagine how to do a > shell or a python script, using the needed parameters, that sets hold > on a member of a list. > > I'll try to do some tests tomorrow. I've followed the indications of a mailman -C /usr/local/mailman3/var/etc/mailman.cfg shell --details I've been trying to "translate" the python script that I made for mailman2 to new mailman3, but obviously, I'm missing something. It seems that mailman cannot locate the "module" needed. The script is named "moderar.py": *-*-*-*-*-*-*-*-*-* (begin of /usr/local/mailman3/moderar.py) /usr/local/mailman3 # cat moderar.py #! /usr/local/bin/python3 # # script via withlist para moderar a pelo en mailman3 # import os import sys sys.path.insert(0, '/usr/local/mailman3') os.environ['PYTHONPATH'] = '/usr/local/mailman3' os.environ['DJANGO_SETTINGS_MODULE'] = 'settings' os.environ['MAILMAN_CONFIG_FILE'] = '/usr/local/mailman3/var/etc/mailman.cfg' import mm_cfg def moderar(mlist, member): if not mlist.Locked(): mlist.Lock() mlist.setMemberOption(member, mm_cfg.Moderate, True) mlist.Save() mlist.Unlock() *-*-*-*-*-*-*-*-*-* (end of /usr/local/mailman3/moderar.py) When I execute a mailman withlist -r moderar -l list_to_use(a)mydomain.com address(a)moderate.com The system returns: Traceback (most recent call last): File "/usr/local/bin/mailman", line 11, in <module> load_entry_point('mailman==3.3.4', 'console_scripts', 'mailman')() File "/usr/local/lib/python3.7/site-packages/click/core.py", line 829, in __call__ return self.main(*args, **kwargs) File "/usr/local/lib/python3.7/site-packages/click/core.py", line 782, in main rv = self.invoke(ctx) File "/usr/local/lib/python3.7/site-packages/mailman/bin/mailman.py", line 68, in invoke return super().invoke(ctx) File "/usr/local/lib/python3.7/site-packages/click/core.py", line 1259, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/usr/local/lib/python3.7/site-packages/click/core.py", line 1066, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/local/lib/python3.7/site-packages/click/core.py", line 610, in invoke return callback(*args, **kwargs) File "/usr/local/lib/python3.7/site-packages/click/decorators.py", line 21, in new_func return f(get_current_context(), *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/mailman/commands/cli_withlist.py", line 293, in shell r = call_name(dotted_name, m, *run_args) File "/usr/local/lib/python3.7/site-packages/mailman/utilities/modules.py", line 69, in call_name named_callable = find_name(dotted_name) File "/usr/local/lib/python3.7/site-packages/mailman/utilities/modules.py", line 52, in find_name module = import_module(module_path) File "/usr/local/lib/python3.7/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1006, in _gcd_import File "<frozen importlib._bootstrap>", line 983, in _find_and_load File "<frozen importlib._bootstrap>", line 965, in _find_and_load_unlocked ModuleNotFoundError: No module named 'moderar' I've done a ln -s /usr/local/mailman3/moderar.py /usr/local/lib/python3.7/site-packages/mailman/bin/moderar.py But with the same result. And I'm not sure if I'm doing well importing "mm_cfg" in the script. My enviroment is open wide installation of mailman, python, etc. in a FreeBSD 12.2-RELEASE-p10 Mailman Core Version GNU Mailman 3.3.4 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.7.9 (default, Nov 6 2020, 21:14:59) [Clang 8.0.1 (tags/RELEASE_801/final 366581)] Postorius version: 1.3.5 If someone can give a hint it will be much appreciated.

5 years, 1 month

[MM3-users] Re: postorius configuration of the from-part

by Wolfgang Bock

Hello, thanks for your information. After creating the dmarc-entries in the DNS-databases everthing works as wanted! Regards Wolfgang Am 13.11.2019 um 06:02 schrieb Mark Sapiro: > On 11/12/19 2:27 PM, Wolfgang Bock via Mailman-users wrote: >> Hello, >> >> can someone give me an advice how I can configure in the >> postorius-menues the view of the from-part of my list-member like in >> this mailinglist: >> >> Wolfgang Bock_via Mailman-users_ <mailman-users(a)mailman3.org> > > The above is the result of Settings -> DMARC Mitigatations -> DMARC > mitigation action = "Replace From: with list address" > > You can apply that to only messages From: a domain the publishes a DMARC > policy of reject or quarantine or to all messages depending on DMARC > Mitigate unconditionally. > > >> case 1 reply goes to the list or to the member >> case 2 reply goes only to the list > > The DMARC Mitigatations settings are independent of the various reply > settings on the Alter Messages tab. >

6 years, 11 months

[MM3-users] Re: From address of subscription notifications

by worik

On 27/02/19 11:54 AM, Mark Sapiro wrote: > On 2/26/19 2:11 PM, worik wrote: >> When I subscribe some body to to a list I on I get a notification that >> says it comes from changeme(a)example.com >> >> As far as I can tell no subscribers are getting mail with that, so this >> is not a crises. But it is untidy and I cannot find where to change it. >> >> SERVE_FROM_DOMAIN is set in the mailman-web/environment section of >> docker-compose.yaml (I am using the docker distribution...) > You set it in your mailman.cfg. As it says in mailman/config/schema.cfg > > There is no `mailman/config/schema.cfg` on my system. Should I raise a issue over at the docker-mailman github? I have: /opt/mailman/core/mailman-extra.cfg /opt/mailman/core/var/etc/mailman.cfg Should I change it in the second one? -- If not me then who? If not now then when? If not here then where? So, here I stand, I can do no other root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand)

7 years, 7 months

[MM3-users] Re: Subscribing users stuck in pending hell

by Quanah Gibson-Mount

--On Wednesday, May 24, 2023 3:34 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On May 24, 2023 9:45:45 AM PDT, Quanah Gibson-Mount > <quanah(a)fast-mail.org> wrote: > > >> That shell script seems to have errors: >> >>>>> pendings = getUtility(IPendings) >>>>> for token, data in pendings.find( >> ... token_owner=TokenOwner.subscriber, >> ... pend_type='subscription'): >> ... print("hello") >> ... >> Traceback (most recent call last): >> File "<console>", line 3, 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) >> TypeError: find() got an unexpected keyword argument 'token_owner' > > > Your Mailman core is too old for that script. Tell me your core version > and I will try to make one that works for you. Thanks Mark! We're hoping to upgrade to something more current next month. Right now apt shows: apt show mailman Package: mailman Version: 1:2.1.29-1+deb10u5 Regards, Quanah

3 years, 4 months

[MM3-users] Re: Debian upgrade Hyperkitty not archiving

by Phil Steel-Wilson

On 1/03/2026 10:24 am, Mark Sapiro wrote: > On 2/28/26 14:29, Phil Steel-Wilson via Mailman-users wrote: >> >> I have a bunch of pck files in the spool directory that i think are >> the messages from 2021 to the present but i cant get hyperkitty to >> look at them. > > Those are messages which HyperKitty failed to archive. > <https://gitlab.com/mailman/mailman-hyperkitty> is a small module with > methods called by Mailman core to get information from HyperKitty and > to pass messages to HyperKitty to be archived. If archiving fails the > message is stored in Mailman's var/archives/hyperkitty/spool/ > directory (maybe /var/lib/mailman/archives/hyperkitty/spool/ in the > Debian package). > > Each new post causes mailman-hyperkitty to retry all the messages. > Mailman's mailman.log (I think /var/log/mailman/mailman.log in the > Debian package). That log will contain information about the failures > which will help you diagnose the issue (probably misconfiguration) > For the record we think it was selinux, sorry about the noise.

7 months, 2 weeks

[MM3-users] Re: venv and upgrade from python 3.11 to 3.13 because of OS-upgrade

by Andreas Vetter

On Donnerstag, 12. März 2026 18:10:13 Mitteleuropäische Normalzeit Mark Sapiro wrote: > On 3/12/26 07:05, Stephen J. Turnbull wrote: > > Andreas Vetter writes: > > > How should I upgrade? > > > > I haven't done this, so take it with a grain of salt. > > <instructions snipped> > > Steve's suggestion is good, however there are a couple of > incompatibility issues between the currently released version of Mailman > core and Python 3.13 and also between mailman-web and django-allauth. > For this reason you should upgrade these in your venv from GitLab. > > pip install git+https://gitlab.com/mailman/mailman@master > > pip install git+https://gitlab.com/mailman/mailman-web@master Thank you Steve and Mark for your help. One more question. When next version of mailman and mailman-web is released. How would I switch back from git to "normal". Again, thank you very much. Also for all the time you put in here to help people. -- Mit freundlichen Gruessen, Andreas Vetter

7 months

[MM3-users] Re: howto reallow a banned email ?

by Nicolas Pettiaux

much thanks. I use mailman 2 interface (and will switch soon to 3) i'll look asap. --- Nicolas Pettiaux - PhD - nicolas(a){educode,pettiaux}.be - Président de Educode asbl Informer, former et susciter la réflexion des acteurs du monde de l'enseignement face aux évolutions d'un monde numérique - http://2019.educode.be & http://2018.educode.be Le 2019-06-19 6:33, Mark Sapiro a écrit : > On 6/18/19 9:12 PM, Nicolas Pettiaux wrote: >> >> By mistake a user has been banned to post to mailman list. How can I >> allow him not only to post but also to become a member of a list ? >> >> I have not found any info on the web, or I have been unable to search >> correctly. > > > Do you have the Postorius web UI in your installation? If so go to the > list's Ban List and remove the unwanted entry. > > Or is this perhaps a Mailman 2 question? If so you'll find the ban_list > in the web admin UI at Privacy options... -> Subscription rules.

7 years, 3 months

Search results for query "sapiro"