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

[MM3-users] Re: Mailman, etc. upgrade woes and persistent bugs

by Allan Hansen

Thank you, Mike. I will see how to get this across to my users. :-) With love, Allan > On Feb 12, 2021, at 11:55 , Mark Sapiro <mark(a)msapiro.net> wrote: > > On 2/12/21 10:27 AM, Allan Hansen wrote: >> They need to resubscribe to each list they want the new address to be used for. >> Subscriptions involves permissions from the moderators. It’s not a >> simple process, especially if you are on many lists. > > > Not true if they have a Django account. See my reply at > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. > > > -- > 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, 6 months

[MM3-users] Re: Cannot Create New List

by Mark Sapiro

On 11/9/25 11:19, dap1--- via Mailman-users wrote: > I created the superuser (used default, mailman). > > When I try to login I get a 403 error. No errors are in the apache2 log. What's in /opt/mailman/mm/var/logs/error.log? Do you get the 403 when going to the login page or when submitting the login form? is it a generic 403 error page or a styled page that says user or password is incorrect? Are you sure you are using the correct password. You can use mailman-web changepassword to be sure? > No, I am not logged in. I am an admin on mailman2 so I thought it would import credentials. But I am unable to log in as anyone (password problem). Mailman 3 is completely different from Mailman 2.1 in this respect. In mailman 2.1 an address listed as owner only meant that address was sent admin notices. Being able to manage a list meant knowing the list admin password whether or not you were listed as an owner, and similarly for moderator. In Mailman 3 the authentication is being logged in as a person who is a superuser or who has an address matching that of an owner or moderator. And the login's are managed by django-allauth. There are multiple reasons why import21 won't create those logins, not the least of which is that Mailman 2.1 authentication is per list and Mailman 3 authentication is per user. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/8-mil… and perhaps also https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/archi… > I see 3 options on the archive page, recent, active and popular. None of which show any threads. Since the list has been dormant for quite a while there are no 'recent' posts nor 'active' posts. I don't know what makes a thread 'popular'. I guess the only way to know what is going on at this point is to be able to login as superuser. 'favorites' are posts you've marked as a favorite and 'popular' are posts with some number of up votes. None of these will exist in an imported archive as those are HyperKitty things with no pipermail equivalent. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 1 week

[MM3-users] Re: Connection to HyperKitty failed: ('Connection aborted.', OSError(0, 'Error'))

by Mark Sapiro

On 11/28/23 18:01, Mark Labeste wrote: > Hi Admin, Any idea on this error? It happen when you wrote a tread it send the mail but not save on the archive. > > Nov 28 20:34:51 2023 (8407) Connection to HyperKitty failed: ('Connection aborted.', OSError(0, 'Error')) > Nov 28 20:34:51 2023 (8407) Connection to HyperKitty failed: ('Connection aborted.', OSError(0, 'Error')) > Nov 28 20:34:51 2023 (8406) Connection to HyperKitty failed: ('Connection aborted.', OSError(0, 'Error')) > Nov 28 20:34:51 2023 (8400) Connection to HyperKitty failed: ('Connection aborted.', OSError(0, 'Error')) > Nov 28 20:34:51 2023 (8400) Could not archive the message with id <168853565119.17959.11384406081068301715(a)email1.example.com> > Nov 28 20:34:51 2023 (8400) archiving failed, re-queuing (mailing-list testmaillist.example.com, message <168853565119.17959.11384406081068301715(a)email1.example.com>) > Nov 28 20:34:51 2023 (8400) Exception in the HyperKitty archiver: ('Connection aborted.', OSError(0, 'Error')) > Nov 28 20:34:51 2023 (8400) Traceback (most recent call last): > File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 710, in urlopen > chunked=chunked, > File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 386, in _make_request > self._validate_conn(conn) > File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 1042, in _validate_conn > conn.connect() > File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/connection.py", line 429, in connect > tls_in_tls=tls_in_tls, > File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/util/ssl_.py", line 450, in ssl_wrap_socket > sock, context, tls_in_tls, server_hostname=server_hostname > File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/util/ssl_.py", line 493, in _ssl_wrap_socket_impl > return ssl_context.wrap_socket(sock, server_hostname=server_hostname) > File "/usr/lib64/python3.6/ssl.py", line 365, in wrap_socket > _context=self, _session=session) > File "/usr/lib64/python3.6/ssl.py", line 776, in __init__ > self.do_handshake() > File "/usr/lib64/python3.6/ssl.py", line 1036, in do_handshake > self._sslobj.do_handshake() > File "/usr/lib64/python3.6/ssl.py", line 648, in do_handshake > self._sslobj.do_handshake() > OSError: [Errno 0] Error mailman_hyperkitty is unable to connect to HYPERKITTY. Check your setting for base_url in mailman_hyperkitty.cfg. See <https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html#connec…> The messages that haven't been archived are queued in Mailman's var/archives/hyperkitty/spool/ directory and will be archived when you fix this issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[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

9 months, 3 weeks

[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

3 years, 1 month

[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, 7 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, 6 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, 7 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, 6 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, 8 months

Search results for query "sapiro"