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

[MM3-users] Re: "Something went wrong | Mailman REST API not available. Please restart Mailman core.

by Mark Sapiro

On 10/29/25 16:25, Hirayama, Pat wrote: > Thanks, Mark. Yeah, it's an odd one. These are from around 22:10-22:14 in mailman.log within the mailman-core container. > > [2025-10-29 22:10:26 +0000] [31] [ERROR] Socket error processing request. > Traceback (most recent call last): > File "/usr/local/lib/python3.8/site-packages/gunicorn/workers/sync.py", line 134, in handle > self.handle_request(listener, req, client, addr) > File "/usr/local/lib/python3.8/site-packages/gunicorn/workers/sync.py", line 190, in handle_request > util.reraise(*sys.exc_info()) > File "/usr/local/lib/python3.8/site-packages/gunicorn/util.py", line 625, in reraise > raise value > File "/usr/local/lib/python3.8/site-packages/gunicorn/workers/sync.py", line 175, in handle_request > respiter = self.wsgi(environ, resp.start_response) > File "/usr/local/lib/python3.8/site-packages/mailman/database/transaction.py", line 50, in wrapper > rtn = function(*args, **kws) > File "/usr/local/lib/python3.8/site-packages/mailman/rest/wsgiapp.py", line 193, in __call__ > return super().__call__(environ, start_response) > File "/usr/local/lib/python3.8/site-packages/falcon/api.py", line 269, in __call__ > responder(req, resp, **params) > File "/usr/local/lib/python3.8/site-packages/mailman/rest/post_moderation.py", line 163, in on_get > resource = self._make_collection(request) > File "/usr/local/lib/python3.8/site-packages/mailman/rest/helpers.py", line 172, in _make_collection > entries = [self._resource_as_dict(resource) > File "/usr/local/lib/python3.8/site-packages/mailman/rest/helpers.py", line 172, in <listcomp> > entries = [self._resource_as_dict(resource) > File "/usr/local/lib/python3.8/site-packages/mailman/rest/post_moderation.py", line 153, in _resource_as_dict > resource = self._make_resource(request.id) > File "/usr/local/lib/python3.8/site-packages/mailman/rest/post_moderation.py", line 76, in _make_resource > msg = getUtility(IMessageStore).get_message_by_id(key) > File "/usr/local/lib/python3.8/site-packages/mailman/database/transaction.py", line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File "/usr/local/lib/python3.8/site-packages/mailman/model/messagestore.py", line 103, in get_message_by_id > return self._get_message(row) > File "/usr/local/lib/python3.8/site-packages/mailman/model/messagestore.py", line 95, in _get_message > with open(path, 'rb') as fp: > FileNotFoundError: [Errno 2] No such file or directory: '/opt/mailman/var/messages/WD/BX/WDBXUFG34LR6QJUQXUWXRHZ4OO4GMQ52' This is https://gitlab.com/mailman/mailman/-/issues/877 and https://gitlab.com/mailman/mailman/-/issues/924, fixed in mailman core 3.3.5 by https://gitlab.com/mailman/mailman/-/merge_requests/836 How old is your mailman core? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 1 week

[MM3-users] Re: Postorius claims 2 messages held when there are none - out of sync

by Mark Sapiro

On 6/26/23 10:27 PM, Ken Alker wrote: > > So is the only thing stored in var/messages/ the held messages, and > nothing more? Two kinds of messages are in the message store. They are messages which are held for moderator action and bounce DSN messages. Held messages should be removed from the message store when they are handled by a moderator. If there are no held messages in Postorius for any list, any in the message store can be safely removed. Bounce DSNs are only needed for a very short time. They are saved when a bounce is received and removed after a few days by the task runner, but they are only needed until they are attached to the admin notice which happens within minutes, and this was only implemented in Mailman 3.3.5. Prior to that bounce DSNs weren't saved. Probably most if not all of the messages in your message store are not needed and could be deleted, but it's more complicated than that because there are also entries in various database tables that should be removed as well. > Is there an outline as to how to clean up the var/messages hierarchy? > (I assume one has to be careful not to remove current held messages and > maybe old ones that have not been processed; or maybe "old ones" can all > be assumed orphaned, and thus, removed w/o concern?) You could try something like this in mailman shell ``` >>> pendings = getUtility(IPendings) >>> messages = getUtility(IMessageStore) >>> mids = [] >>> for mlist in getUtility(IListManager): ... requests = IListRequests(mlist) ... for request in requests.held_requests: ... key, data = requests.get_request(request.id) ... if data.get('_mod_message_id'): ... mids.append(data.get('_mod_message_id')) ... >>> for key, data in pendings: ... mid = data.get('_mod_message_id') ... if data['type'] != 'probe' and mid and mid not in mids: ... pendings.confirm(key, expunge=True) ... messages.delete_message(mid) ... >>> commit() This will find all the message ids from all held message requests, and then find those pendings for message ids not DSNs and not found in requests and delete the pending an the message store message. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: HyperKitty failure

by Mark Sapiro

On 1/1/22 2:14 AM, horvath.arpad.szfvar(a)gmail.com wrote: > I changed base_url to the https one, reloaded nginx, restarted mailman3-web. > > Now there is an other error message in mailman.log (I can't find the a meaningful result for InvalidChunkLength error message in this list and in google search) > > Jan 01 10:54:40 2022 (126976) Connection to HyperKitty failed: ("Connection broken: InvalidChunkLength(got length b'', 0 bytes read)", InvalidChunkLength(got length b'', 0 bytes read)) This exception is raised by urllib3 and is documented at https://urllib3.readthedocs.io/en/stable/reference/urllib3.exceptions.html#… ... > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message > url = self._send_message(mlist, msg) > File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 198, in _send_message > result = requests.post( > File "/usr/lib/python3/dist-packages/requests/api.py", line 119, in post > return request('post', url, data=data, json=json, **kwargs) > File "/usr/lib/python3/dist-packages/requests/api.py", line 61, in request > return session.request(method=method, url=url, **kwargs) > File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in request > resp = self.send(prep, **send_kwargs) > File "/usr/lib/python3/dist-packages/requests/sessions.py", line 697, in send > r.content > File "/usr/lib/python3/dist-packages/requests/models.py", line 831, in content > self._content = b''.join(self.iter_content(CONTENT_CHUNK_SIZE)) or b'' > File "/usr/lib/python3/dist-packages/requests/models.py", line 756, in generate > raise ChunkedEncodingError(e) > requests.exceptions.ChunkedEncodingError: ("Connection broken: InvalidChunkLength(got length b'', 0 bytes read)", InvalidChunkLength(got length b'', 0 bytes read)) We are trying to archive the message via a POST request to the URL https://lists.xxx.hu/hyperkitty/api/mailman/archive and the response is chunked with an invalid chunk length. What happens if you go to https://lists.xxx.hu/hyperkitty/api/ in a web browser. That should return a page of documentation of the API. Does it? Can you go to https://lists.xxx.hu/hyperkitty/api/lists and get a response from Django REST framework which is a json representation of your mailing lists info? I don't know what could be causing this error, but I suspect something in the configuration of the web server that is serving this request -- 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

[MM3-users] Re: DMARC DNS settings for MM3?

by Mark Sapiro

On 1/30/22 20:25, Jay Hamilton-Roth wrote: > Emails from our list are currently being blocked by Google & Yahoo because of the "Dmarc policy of the sender domain" (according to Google Postmaster). > > Our list doesn't do any munging for "Reply goes to list" and our DMARC Mitigations is set for "No DMARC mitigations" and we're not DMARC Mitigating unconditionally. > > Given this is our MM3 policy, it's not clear what the DMARC DNS policy should be for consistency (note: we currently don't have a DMARC DNS setting). > > MM3 documentation doesn't have enough info, and reading up on DMARC Records it's not clear if we should be: > > v=DMARC1;p=reject;pct=100;rua=mailto:postmaster@ourdomain.com > > -or- > > v=DMARC1;p=quarantine;pct=100;ruf=mailto:postmaster@ourdomain.com > > -or something else- Have you seen https://wiki.list.org/DEV/DMARC ? Nothing you publish as a DMARC policy or SPF will affect the DMARC actions of recipient domains for list mail unless you set DMARC mitigations for your lists to make the mail be From: your domain. As long as you leave the From: intact, it is the DMARC policy of the From: domain that counts, and if you make any transformation at all to the message (content filtering, subject prefixing, munging Reply-To:, etc) you will break the From: domain's DKIM signature and DMARC will fail at the receiving MTA. As far as recommendations go, what we do for this list for example is we set DMARC mitigation action to Replace From with list address and DMARC Mitigate unconditionally to No. We publish SPF "v=spf1 mx a ~all" We publish DMARC "v=DMARC1\; p=none" and we DKIM sign all our outgoing mail. Our Python.org lists are similar except we publish DMARC "v=DMARC1\; p=none\; pct=100\; rua=mailto:rxxx@dmarc.postmarkapp.com\; sp=none\; aspf=r\;" because we've signed up with postmarkapp.com for their free reporting service. We do publish a DMARC policy and DKIM sign outgoing mail because we believe this helps mail delivery, but without DMARC mitigation action = Replace From with list address or Wrap the message ... it won't stop recipients from treating list mail as failing DMARC. -- 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: 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/

5 years, 3 months

[MM3-users] Re: hyperkitty failed to create a thread

by Mark Sapiro

On 2/11/19 10:01 AM, Abhilash Raj wrote: > > Please create a bug report at https://gitlab.com/mailman/hyperkitty/issues with the affected messages. > > It would help us recreate the problem if you could attach a raw messages in the issue. I am > assuming the messages aren't sensitive since the archive are open. Otherwise, feel free to omit > any sensitive information. > > I haven't looked at the threading code in HK since a long time, but my impression is that it > looks at the 'In-Reply-To' header to figure out if the current email is a response to a previous > email that it received. > > In some cases, the order of the incoming messages can cause this to break, like when the > reply comes in first and the original messages comes in later. I am not sure exactly what is > happening here, but looking at the raw messages should help us reproduce and possibly > fix the issue. I downloaded the February mbox from <https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/export/wlug@l…> and imported it to a test list with 'django-admin hyperkitty_import and see the same issue. Examination of the mbox shows for the first message Message-ID: < <SN6PR01MB4719346533C08BF4FF62B880C36C0(a)SN6PR01MB4719.prod.exchangelabs.com>> This will be wrapped, so here's an excerpt Message-ID: < <SN6....prod.exchangelabs.com>> Note the folding of the header and the double angle brackets. The next message has (again excerpted to avoid wrapping) Message-ID: < <BL0....prod.exchangelabs.com>> In-Reply-To: SN6....prod.exchangelabs.com Note again the doubling of the angle brackets in the Message-ID and the absence of angle brackets in the In-Reply-To: The Message-ID: and In-Reply-To: headers of subsequent messages have the same issues. In looking at other mboxes downloaded from Hyperkitty, I see that the absence of References: and the dropping of the angle brackets from In-Reply-To: seem to be usual, and importing such a mbox preserves the threading. However, the doubling of the angle brackets is not usual and is almost certainly the cause of the problem. Do you have any of the original messages? What do the headers look like in those? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 2 months

[MM3-users] Re: Starting new thread in Postorius -> disappears

by Mark Sapiro

On 11/29/2017 05:05 PM, Cameron Smith wrote: > > On November 21, I sent the message below, as a part of this very thread, to Thor and cc’d the mailman 3 list. But the message never showed up in HyperKitty [1]. I don’t know if other list members received it in their email inboxes or not. Your post was received: Nov 21 14:31:20 mailman postfix/cleanup[15735]: 2B3798008D: message-id=<836BFAB0-4879-4EDF-9026-FEC17D4A2BEC(a)mail2.cetsi.com> Nov 21 14:31:20 mailman postfix/qmgr[20545]: 2B3798008D: from=<ccsmith(a)mail2.cetsi.com>, size=10048, nrcpt=1 (queue active) delivered to Mailman core: Nov 21 14:31:20 mailman postfix/lmtp[15737]: 2B3798008D: to=<mailman-users(a)mailman3.org>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.31, delays=0.28/0/0/0.02, dsn=2.0.0, status=sent (250 Ok) and immediately discarded: Nov 21 14:31:21 2017 (19106) DISCARD: <836BFAB0-4879-4EDF-9026-FEC17D4A2BEC(a)mail2.cetsi.com> > Thor obviously received the message (it was addressed to him directly), because he referenced it in a message that is in the archives [1]. However, I never received an email copy of his message from the list. Possibly you never received a list copy of his message because you were directly addressed and your list option "Receive list copies (possible duplicates)" is set to No. > So, what’s going on? As to why your post was discarded, unfortunately, the logs don't give more info. There are a couple of possibilities. If your post contained an attachment with Content=Type: application/subtype where sub-type doesn't contain 'signature' it would have been discarded by a header filter rule. Also it looks like you sent the message From: <ccsmith(a)mail2.cetsi.com>. If that is not an address on your <ccsmith(a)cetsi.com> account, it would have been discarded as a non-member post. > What baffles me is that more people are not complaining about this. Is it just that no one has noticed? Or is it some subtle misconfiguration in my system? And in Thor’s apparently. And maybe in the lists.mailman3.org system as well. I see nothing so far to indicate anything at lists.mailman3.org is broken in this respect. The only "unusual" thing is this is now a new thread <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>, but presumably that is because your post was in reply to your earlier post which wasn't archived. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 5 months

[MM3-users] Re: Mailman recovery test did not go as planned

by Mark Sapiro

On 8/5/22 09:38, bob B via Mailman-users wrote: > I have a test Mailman 3 environment. We are using docker, and we are running the database outside of docker in mysql. > I need to perform a DR recovery test. > > I shut down Mailman in docker (mailman-core & mailman-web, the only docker images I have running for Mailman). Does shutting down mailman-web also shut down Django qcluster? If not, this could be an issue. > While Mailman was stopped, I had our database team take a backup dump of the database. > I then restarted Mailman in docker. > I threw some more messages at a test list. > I validated that the new messages were delivered, and showed up in the archive. > I shut down Mailman again. > I had the database team restore the Mailman database from the backup. > I started Mailman > I logged into Mailman > I was expecting to see the messages in the archive prior to the backup and all the messages after the backup would be gone. I would expect that too. > When went into the list archive, I get a spinning icon and no messages showed up. I don't offhand know what the issue would be unless Django qcluster was running the whole time. > I quit, restarted my browser, and logged in again, and the same thing. > I then sent a test message to the list and the message was delivered to the list. > Then when I went to check the archive, the spinning icon was gone and that test message was there along with all the messages before the backup was taken. Possibly one of the Django periodic jobs, maybe cache_cleanup or daily_cleanup would fix it without a message. > Is this normal? After a restore did the new message cause a refresh of archived messages etc? > Is there a way to do this without sending a message to a list after a restoration of the database? > > Are there better steps I should take when restoring the database? I don't know what better you could do as far as the save and restore are concerned as long as shutting down mailman-web stops qcluster. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: Upgrade

by Darren Smith

Boy howdy did that work... Thanks! On Mon, Apr 16, 2018 at 11:22 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/16/2018 10:12 AM, Darren Smith wrote: > > > "/opt/mailman3/conda/lib/python3.6/site-packages/ > sqlalchemy/engine/strategies.py", > > line 160, in create > > engineclass.__name__)) > > TypeError: Invalid argument(s) 'pool_pre_ping' sent to create_engine(), > > using configuration PGDialect_psycopg2/QueuePool/Engine. Please check > that > > the keyword arguments are appropriate for this combination of > components." > > > > Anyone able to point me where to go to look for a solution for this? > > > You need to update SQLAlchemy to >= 1.2 for this, but there is another > issue that requires at least 1.2.3 (current is 1.2.6) > > > -- > 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/ >

8 years

[MM3-users] Re: Where does sender postorius@ come from?

by Jens Günther

Am 16.06.23 um 01:10 schrieb Mark Sapiro: > On 6/15/23 14:03, Jens Günther wrote: >> >> >> Am 15.06.23 um 00:34 schrieb Mark Sapiro: >>>> - Then I tried settings_local.py with: >>>> EMAIL_CONFIRMATION_FROM = 'myaddress(a)something.org' > > > Sorry, this is actually a different setting. There are actually two more > that control this. These are DEFAULT_FROM_EMAIL > <https://docs.djangoproject.com/en/4.2/ref/settings/#default-from-email> > and SERVER_EMAIL > <https://docs.djangoproject.com/en/4.2/ref/settings/#server-email>. Note > that the defaults mentioned in the Django docs are probably overridden > in your settings.py, but you should set them in settings_local.py Thank you Mark. I changed now DEFAULT_FROM_EMAIL to my address, restartet container and it works. Also it works if I delete the EMAIL_CONFIRMATION_FROM-line again and do not put the SERVER_EMAIL, at least for the password-reset. Can you tell the diffenrence between the 3? Would you recommend to set all 3 to my admin-mailaddress?

2 years, 10 months

Search results for query "sapiro"