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

[MM3-users] Re: Mailman3 on python3.13 debian testing package

by Mark Sapiro

On 2/12/25 23:12, Thomas Krichel wrote: > > Feb 13 06:49:56 2025 (857955) Uncaught runner exception: 'pathlib._local.PosixPath' object does > not support the context manager protocol > Feb 13 06:49:56 2025 (857955) Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 179, in _one_iteration > self._process_one_file(msg, msgdata) > ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 272, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/lib/python3/dist-packages/mailman/runners/outgoing.py", line 111, in _dispose > self._func(mlist, msg, msgdata) > ~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/mailman/mta/deliver.py", line 89, in deliver > refused = agent.deliver(mlist, msg, msgdata) > File "/usr/lib/python3/dist-packages/mailman/mta/base.py", line 167, in deliver > callback(mlist, message_copy, msgdata_copy) > ~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/mailman/mta/decorating.py", line 32, in decorate > decorator.process(mlist, msg, msgdata) > ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/mailman/handlers/decorate.py", line 250, in process > process(mlist, msg, msgdata) > ~~~~~~~^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/mailman/handlers/decorate.py", line 88, in process > header = decorate('list:member:regular:header', mlist, d) > File "/usr/lib/python3/dist-packages/mailman/handlers/decorate.py", line 212, in decorate > template = getUtility(ITemplateLoader).get(name, mlist, **extradict) > File "/usr/lib/python3/dist-packages/mailman/model/template.py", line 211, in get > path, fp = find(default_uri, mlist, code) > ~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/mailman/utilities/i18n.py", line 157, in find > for search_path in raw_search_order: > ^^^^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/mailman/utilities/i18n.py", line 117, in search > templates_dir = str(resources.enter_context( > ~~~~~~~~~~~~~~~~~~~~~~~^ > files('mailman').joinpath('templates'))) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3.13/contextlib.py", line 528, in enter_context > raise TypeError(f"'{cls.__module__}.{cls.__qualname__}' object does " > f"not support the context manager protocol") from None > TypeError: 'pathlib._local.PosixPath' object does not support the context manager protocol > Feb 13 06:49:56 2025 (857955) SHUNTING: 1739429396.7636604+dba2fc372ce4c206e3bb753c1162bc3b768b7528 > Feb 13 06:49:56 2025 (857955) SHUNTING: 1739429396.7636604+dba2fc372ce4c206e3bb753c1162bc3b768b7528 > > Then there are repeated messages that hyperkitty can't archive the > message. Lots of them. > > No email reaches the list. I did not notice, but now the listowner > has written to me. Because the messages are being shunted because of the above exception which is a Python 3.13 issue https://gitlab.com/mailman/mailman/-/issues/1190 fixed by https://gitlab.com/mailman/mailman/-/merge_requests/1309. Once you fix that issue by either downgrading Python or installing the changes from https://gitlab.com/mailman/mailman/-/merge_requests/1309 you can reprocess those messages with `mailman unshunt` -- 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: Re-send subscription response and file permission error in queue

by Mark Sapiro

On 9/8/20 10:56 PM, accounts-mailman(a)holbrook.no wrote: > A user sent subscription request to the `..-join@` address of a list. Email domain wasn't set up properly, so response got rejected. Now, if the user tries to send another request, no reponse comes back. In the log I find a python stack trace saying subscription already pending. > > ``` > Sep 08 10:32:44 2020 (19918) Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 171, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 264, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/lib/python3/dist-packages/mailman/runners/command.py", line 196, in _dispose > mlist, msg, msgdata, parts, results) > File "/usr/lib/python3/dist-packages/mailman/commands/eml_membership.py", line 104, in process > ISubscriptionManager(mlist).register(subscriber) > File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", line 520, in register > list(workflow) > File "/usr/lib/python3/dist-packages/mailman/app/workflow.py", line 69, in __next__ > return step() > File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", line 227, in _step_sanity_checks > raise SubscriptionPendingError(self.mlist, self.address.email) > mailman.interfaces.subscriptions.SubscriptionPendingError > ``` I'll look at this when I get some time. I'm still catching up after being off line for 12 days. > Furthermore I am getting a permission denied error in the attempt of shunting the message, which I don't quite understand because the folder has user `list` group `list` and `700` mode: > > ``` > Sep 08 10:25:29 2020 (19918) SHUNTING: 1599553529.9889646+88be5afa0bf3111a83e68cc97ce2000723ad93fd > Sep 08 10:29:49 2020 (19918) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman3/queue/command/1599553789.306307+6fee74af69263553b5ffd0e73cc095ab651bd855.pck' > Sep 08 10:29:49 2020 (19918) Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 156, in _one_iteration > msg, msgdata = self.switchboard.dequeue(filebase) > File "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 150, in dequeue > with open(filename, 'rb') as fp: > PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/queue/command/1599553789.306307+6fee74af69263553b5ffd0e73cc095ab651bd855.pck' > ``` > > How can I remove the pending subscription, or re-send the response email? In Postorius, pull down Subscription Requests and select Pending Confirmation and delete the request. > And what could be the cause of the permission error? Mailman can't read the /var/lib/mailman3/queue/command/1599553789.306307+6fee74af69263553b5ffd0e73cc095ab651bd855.pck file. This is strange since it wrote it, but check the modes and user/group of all the directories in the path and the file itself. Could it be a SELinux or apparmor issue? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

[MM3-users] Re: Error 500 on held_messages page

by Mark Sapiro

On 2/3/22 08:01, Stephan Krinetzki wrote: > Hello all, > > we now have at least one mailing list (there may be more affected) that generates a 500 error when calling the held_messages page. After looking at the held messages via the mailman shell, we have identified three mails that have neither a subject nor a message body. How can we remove these three mails from the database? This shouldn't be an issue, at least with Mailman core 3.3.5, unless I don't understand. Note that there are 3 tables involved. The request (IListRequests), the pendings (IPended and IPendedKeyValue), and the held message (IMessageStore). > This is the mailman shell command we used: > > mailman shell -l listname(a)lists.example.com > <removed> > 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. > Die Variable 'm' ist die listname(a)lists.example.com Mailingliste > >>> msg_db = getUtility(IMessageStore) > >>> req_db = IListRequests(m) > >>> reqs = list(req_db.held_requests) > >>> for req in reqs: > ... print('{}: {}'.format(req.id, req.request_type)) > ... > 32598: 1 > [...] > 107656: 1 > 107737: 1 > 107758: 1 OK, you have requests. > >>> from mailman.app.moderator import handle_message > >>> handle_message(m, 107758, Action.discard) > >>> reqs = list(req_db.held_requests) > >>> for req in reqs: > ... print('{}: {}'.format(req.id, req.request_type)) > ... > 32598: 1 > [...] > 107656: 1 > 107737: 1 OK, you discarded the message held with request id 107758. > >>> handle_message(m, 92927, Action.discard) > Traceback (most recent call last): > File "<console>", line 1, in <module> > File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/app/moderator.py", line 112, in handle_message > key, msgdata = requestdb.get_request(id) > TypeError: 'NoneType' object is not iterable > >>> There is no request with id 92927. Why do you think there should be? If by remove them from the database, you mean just from the messagestore, you can do (using your above) msg_db.delete_message('the_message_id') To delete a pending request for which there is no request id, e.g. the id 92927 above, you could do ``` pendings = getUtility(IPendings) for token, data in pendings.find(pend_type='held message'): if data and data['id'] == 92927: pendings.confirm(token, expunge=True) ``` Mailman core 3.3.5 has a lot of changes to address this issue. Also see https://gitlab.com/mailman/mailman/-/issues/946 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: messages go to shunt queue

by Danil Smirnov

Thanks Mark! The change provided has fixed the issue. Danil On Thu, Sep 10, 2020 at 6:35 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 9/10/20 6:43 AM, Danil Smirnov wrote: > > Hi guys, > > > > I've faced weird Core behaviour after the last upgrade of the docker > > images. All the messages sent to a list now go straight to shunt queue > with > > the following error in the logs: > > > > --- > > Sep 06 22:41:32 2020 (27) Traceback (most recent call last): > ... > > File "/usr/lib/python3.8/site-packages/mailman/rules/dmarc.py", line > 217, > > in is_reject_or_quarantine > > for record in txt_rec.items[0].strings) > > KeyError: 0 > > Sep 06 22:41:32 2020 (27) SHUNTING: > > 1599432092.4326646+4cbb58a0dd5d9705946ca583835e63ec175536e3 > > > See <https://gitlab.com/mailman/mailman/-/issues/743>. > > -- > 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/ >

5 years, 11 months

[MM3-users] Re: User display name entry field input ignored

by Christian

Okay. What if I want to change the name from "None" to "firstname lastname" ? How can that be accomplished please? -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Sunday, June 26, 2022 5:22 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: User display name entry field input ignored On 6/26/22 08:03, Christian via Mailman-users wrote: > Whether I try and add users using mass subscribe, or individually, it > seems the display name field entry is ignored. The default is then > "none" for the user. Please advise. Thank you! If the address you are mass subscribing is already known to mailman, i.e., is an existing user, it is that user that will be subscribed with that user's display name, even if it is None. If that address is not an existing user, the user will be subscribed with the display name you provide. -- 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

[MM3-users] Re: Apache Conf

by Thomas G

Same result with Alias "/static/" "/opt/mailman/static/" I have sometimes: [Fri Oct 19 22:05:52.583841 2018] [proxy_http:error] [pid 8328:tid 140435053815552] (104)Connection reset by peer: [client 1xxxxxxx1794] AH01102: error reading status line from remote server localhost:8000 [Fri Oct 19 22:05:52.583874 2018] [proxy:error] [pid 8328:tid 140435053815552] [client 1xxxxxxx:51794] AH00898: Error reading from remote server returned by /static/hyperkitty/libs/jquery/jquery-1.10.1.min.js But it's not systematic. Alias seem to be ignored by the proxy. Le ven. 19 oct. 2018 à 20:48, Mark Sapiro <mark(a)msapiro.net> a écrit : > On 10/19/18 12:17 PM, Thomas G wrote: > > Hi tried both. > > > > Same result. > > > > xxxx - - [19/Oct/2018:21:14:22 +0200] "GET /static/postorius/js/script.js > > HTTP/1.1" 404 4051 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) > > Gecko/20100101 Firefox/60.0" > > > What's in the apache error log? > > -- > 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/ >

7 years, 10 months

[MM3-users] Re: exim4 + mailman3 lmtp failure

by Thomas Drillich

Hello Mark, Andrew, thank you for your hints, the hosts_override gives me the way to solve my problem. It was a problem of DNS + resolv.conf, 1. inside resolv.conf there is a domain search defined, - search example.com - 2. Inside the Domain example.com there exists a record "* in a 85.25.8.21", so the question localhost resolvs to localhost.example.com ... 85.25.8.21 After I added the localhost in a 127.0.0.1 into the domain, the exim transport delivers correctly. greetings Thomas Am 06.05.20 um 22:39 schrieb Mark Sapiro: > On 5/6/20 1:33 PM, Mark Sapiro wrote: >> I think you need to add >> >> hosts_override = true >> >> to your transport definition to tell exim to use `hosts = localhost` >> rather than the host part of the email address. >> > Please report back if this is the solution. If it is, we'll update the docs. > > > _______________________________________________ > 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/ -- mit freundlichem Gruss -- regards Thomas Drillich Heugasse 4 / D-55116 Mainz / Germany fon +49-6131-570-2621 mobil +49-162-469-5875

6 years, 3 months

[MM3-users] Re: Message does not appear in archive

by tokyoprogressive＠mailbox.org

Thank you to all for helping me find it. Sent from my iPhone > On Aug 31, 2018, at 1:12, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 08/30/2018 02:59 AM, Simon Hanna wrote: >> >> It is being archived. You can find it here >> >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… >> >> You can see it listed here >> >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/2018/8/ >> >> Hyperkitty has a "little" problem with caching and cache-invalidation... > > > And various searches such as "forum" will also find it. It is unclear > why it doesn't appear in the "Recently active discussions" list on the > overview even though I've stopped and started qcluster, gunicorn (the > wsgi server for Django) and mailman. > > -- > 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/

7 years, 11 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Is there a ´default´ admin account?? El vie., 21 jul. 2017 a las 20:34, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 06:07 PM, Rafael Mora wrote: > > I want to use Mailman to send emails to our customers. > > > So you need to create a list and add your customers as members. > > Please note that Mailman is not a substitute for a customer relations > management system. It can be used in that way, but a true CRM system has > advantages ove Mailman. Mailman is primarily designed to support > discussion lists such as this one. > > > > I´m getting this error when I click on sign up and log in: > > > > FilterError at /accounts/login/ > > /bin/sh: sassc: command not found > > > See the third bullet under > <http://docs.list.org/en/latest/prodsetup.html#dependencies>. > > > -- > 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

9 years

[MM3-users] Re: No DBA password when installing Mailman3 with remote database server

by Markus Grandpré

Dear Mr. Sapiro, thank you very much for your request, that is OK for me. You are also welcome to make changes to the documentation. Furthermore, I would like to ask you to contact the colleagues who convert your Mailman3 software into Debian packages. I think that the Mailman3 software should install successfully even if you do not have the DBA password at hand. Best regards, Markus Grandpré On 03.11.22 17:17, Mark Sapiro wrote: > On 11/3/22 03:57, Markus Ludwig Grandpré wrote: >> >> thank you very much for your answers. Below this text you will find a >> brief documentation how I finally managed to install mailman3 and >> mailman3web packages under Debian 11 with a remote PostGreSQL server >> v10.22. > > > Thank you for providing this documentation. With your permission, I > would like to add this to the wiki at > https://wiki.list.org/DOC/5%20Downloading%20and%20installing%20Mailman. > Is that OK, if so may I also acknowledge you as the author? > -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

3 years, 9 months

Search results for query "sapiro"