Search results for "2021" - Mailman-users

Re: Postorius no connection to REST API

by Abhilash Raj

> On Aug 20, 2021, at 9:29 AM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > > >> On Aug 20, 2021, at 2:53 AM, Richard Rosner <rrosner5(a)gmail.com> wrote: >> >> WARNING 2021-08-20 11:49:22,941 3975 django.request Not Found: /mailman3 >> WARNING 2021-08-20 11:49:22,941 3975 django.request Not Found: /mailman3 >> WARNING 2021-08-20 11:49:22,954 3975 django.request Not Found: /mailman3 >> WARNING 2021-08-20 11:49:22,954 3975 django.request Not Found: /mailman3 >> [pid: 3975|app: 0|req: 17/16] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:10 2021] GET /mailman3 => generated 5651 bytes in 13321 msecs \ >> (HTTP/1.1 404) 5 headers in 170 bytes (1 switches on core 0) >> [pid: 3975|app: 0|req: 17/17] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:07 2021] GET /mailman3 => generated 5651 bytes in 16373 msecs \ >> (HTTP/1.1 404) 5 headers in 170 bytes (1 switches on core 1) >> WARNING 2021-08-20 11:49:32,820 3975 django.request Not Found: /accounts >> WARNING 2021-08-20 11:49:32,820 3975 django.request Not Found: /accounts >> [pid: 3975|app: 0|req: 18/18] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:32 2021] GET /accounts => generated 5651 bytes in 251 msecs (H\ >> TTP/1.1 404) 5 headers in 170 bytes (1 switches on core 0) >> WARNING 2021-08-20 11:49:43,517 3975 django.request Not Found: /archives >> WARNING 2021-08-20 11:49:43,517 3975 django.request Not Found: /archives >> [pid: 3975|app: 0|req: 19/19] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:43 2021] GET /archives => generated 5651 bytes in 99 msecs (HT\ >> TP/1.1 404) 5 headers in 170 bytes (1 switches on core 1) >> >> The proxy pass config is >> <IfModule mod_proxy_uwsgi.c> >> ProxyPass /mailman3/favicon.ico ! >> ProxyPass /mailman3/static ! >> Proxypass "/mailman3" "http://127.0.0.1:8000/mailman3" >> ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" >> ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" >> ProxyPass "/accounts" "http://127.0.0.1:8000/accounts" >> ProxyPass "/django" "http://127.0.0.1:8000/django" >> ProxyPass "/user-profile" "http://127.0.0.1:8000/user-profile" >> ProxyPass "/archives" "http://127.0.0.1:8000/archives" >> </IfModule> > > There seem to be extra entries in this, depending on where you installed from, there are only some URLs that you need. Also, replace, /django with /admin. > You need one of the /postorius and /mailman3, one between `/archives` or `/hyperkitty`. `/django` is probably not useful I think, `/accounts` looks fine. Do, either one of those listed above and `/admin` work for you? -- thanks, Abhilash Raj (maxking)

3 years, 10 months

Re: Setting for archiving multi email domains?

by Duane Raymond

> What is the full error including traceback from Mailman's mailman.log > for the shunted messages? My test just now raised the following error: Mar 09 20:52:55 2021 (26267) ACCEPT: <CAMs==2HNnd_6+4=iWZhK3d7oTvqk2W80wMdCJ+Y9eRFUKno1mA(a)mail.gmail.com> Mar 09 20:52:56 2021 (26271) Uncaught runner exception: 'NoneType' object has no attribute 'preferences' Mar 09 20:52:56 2021 (26271) Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/core/pipelines.py", line 50, in process handler.process(mlist, msg, msgdata) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/handlers/member_recipients.py", line 84, in process for member in mlist.regular_members.members File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/handlers/member_recipients.py", line 83, in <genexpr> recipients = set(member.address.email File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/model/roster.py", line 239, in members yield from self._get_members(DeliveryMode.regular) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/model/roster.py", line 226, in _get_members if member.delivery_mode in delivery_modes: File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/model/member.py", line 212, in delivery_mode return self._lookup('delivery_mode') File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/model/member.py", line 174, in _lookup pref = getattr(self.address.preferences, preference) AttributeError: 'NoneType' object has no attribute 'preferences' Mar 09 20:52:56 2021 (26271) SHUNTING: 1615323176.8137882+cd8501dd322d0ca6b4a3a187d57bc691cd0ec343 and running the following command raised the result below root@mail:~# mailman qfile var/queue/shunt/1615323176.8137882+cd8501dd322d0ca6b4a3a187d57bc691cd0ec343.pck [----- start pickle -----] <----- start object 1 -----> Received: from mail-ej1-x62e.google.com (mail-ej1-x62e.google.com [IPv6:2a00:1450:4864:20::62e]) by mail.fairsayforum.com (Postfix) with ESMTPS id DAB464236D for <test(a)campaigningforum.com>; Tue, 9 Mar 2021 20:52:54 +0000 (UTC) Received: by mail-ej1-x62e.google.com with SMTP id mm21so31549207ejb.12 for <test(a)campaigningforum.com>; Tue, 09 Mar 2021 12:52:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fairsay.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=EgptMSUIn7D50wRC/g0b3CRiIpplElahV/29ypgLKLk=; b=kw8eSDmuxOf1yjek6lbb1wMr7gG/F/3mteeWDjd0xka58taUMLjyI97iXivysixDJv PuUL24pBi4VpIhZat19rC0rVP8jeAbUMOVDBrQdJ/9comxSsxWTeqnvxXyoSfPtJD4sw U0ytrse1sOGme5OXWQ433+10i9b/pUN0umYe8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=EgptMSUIn7D50wRC/g0b3CRiIpplElahV/29ypgLKLk=; b=mOnXvqUQj9zgzoFLUkgEKDyuyH8WdyYA/KhYelsnqXITSXdoMsxw9yHneoUkZNh+96 ZjONXBkZhlDvmonwINQKF2sLOQ6RRoAdKnH16ecmc7rP+1zT9nGXFkYvNQMcFHCahD8T PPVgjmEuBkOC+6qAWE5oIWY7qehYw1sQtQdqlk2E4qgyPGrWen17NoMP7J0dlHaMprL8 +M26NpELA35CyLOfJuuLq4lBNUb1jq6rNlFkpJTuPGNJror6YSDxeB5jQR8XlErr+G8S Wfwgq98pf4+aPHR8CYGOjVAtFaITZWgjZPDC+IeAmICsu04V4Vn6d/p4hUeGLnQF39le dLlw== X-Gm-Message-State: AOAM532vFY+zWnSLvJnCElbuzUooTINttm38iDprNZmsxMc/DRls5JrB q17o0OwrGirg6bKKbkaskSLkQ/K4xnaPVorxc9zZkd0eiU27+sS8 X-Google-Smtp-Source: ABdhPJxC/QTIs31D7ELVUIIF4tE5go1LieVZjr+GrWo2/12dRVznfTMEJsgbMJLjdjTBzFjxYK33Xm3QgNd2L4suX+s= X-Received: by 2002:a17:906:1a16:: with SMTP id i22mr5432371ejf.522.1615323174025; Tue, 09 Mar 2021 12:52:54 -0800 (PST) MIME-Version: 1.0 From: Duane Raymond <duane.raymond(a)fairsay.com> Date: Tue, 9 Mar 2021 21:52:36 +0100 Message-ID: <CAMs==2HNnd_6+4=iWZhK3d7oTvqk2W80wMdCJ+Y9eRFUKno1mA(a)mail.gmail.com> Subject: Test to identify shunting error To: test(a)campaigningforum.com Content-Type: multipart/alternative; boundary="000000000000fc503e05bd20bba9" Message-ID-Hash: 3THPVXHXTHRNBXZHN2TD5VBUWIMXOEY2 X-Message-ID-Hash: 3THPVXHXTHRNBXZHN2TD5VBUWIMXOEY2 X-MailFrom: duane.raymond(a)fairsay.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header --000000000000fc503e05bd20bba9 Content-Type: text/plain; charset="UTF-8" Test to identify shunting error --000000000000fc503e05bd20bba9 Content-Type: text/html; charset="UTF-8" <div dir="ltr">Test to identify shunting error<br></div> --000000000000fc503e05bd20bba9-- <----- start object 2 -----> { '_parsemsg': False, 'envsender': 'noreply(a)campaigningforum.com', 'lang': 'en', 'listid': 'test.campaigningforum.com', 'original_size': 2436, 'received_time': datetime.datetime(2021, 3, 9, 20, 52, 54, 941548), 'rule_hits': [], 'rule_misses': [ 'dmarc-mitigation', 'no-senders', 'approved', 'emergency', 'loop', 'banned-address', 'member-moderation', 'nonmember-moderation', 'administrivia', 'implicit-dest', 'max-recipients', 'max-size', 'news-moderation', 'no-subject', 'digests', 'suspicious-header'], 'to_list': True, 'version': 3, 'whichq': 'pipeline'} [----- end pickle -----]

4 years, 3 months

Re: New messages not being archived

by Sarah H

The site is behind a proxy, yes. apache serves the client site redirecting 80 to 443 and serving SSL for the site then proxying to Nginx for postorius/hyperkitty at 8080. I've also tried going straight to 8080 bypassing the proxy internally using localhost or loopback to the same end result. The log is mostly these three errors repeatedly with the same above wall of html between them, some of them end with (404) after the last html tag indicating url not found and browsing to them gives the same custom 404 page for postorius. Jul 15 12:37:08 2021 (471314) HyperKitty failure on http://lists.client.org/hyperkitty/api/mailman/archive: Jul 15 12:37:08 2021 (471314) Traceback (most recent call last): File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message raise ValueError(result.text) ValueError: Jul 15 12:37:08 2021 (471314) Exception in the HyperKitty archiver: I was able to find (about 5000 lines up in the log for a single post attempt... it's a bit excessive to print the html response every error) this when I dug through instead of tailing the last 500 lines. [15/Jul/2021:12:37:06 -0700] "GET /3.1/addresses/sarah.h@email HTTP/1.1" 200 380 "-" "GNU Mailman REST client v3.3.2" and at the start of the block: [15/Jul/2021:12:37:03 -0700] "GET /3.1/lists/admin.lists.client.org/member/sarah.%40email HTTP/1.1" 200 516 "-" "GNU Mailman REST client v3.3.2" Jul 15 12:37:05 2021 (471317) ACCEPT: <162637782380.3116.619498070458942231@sysname>

3 years, 11 months

Re: Postorius no connection to REST API

by Abhilash Raj

> On Aug 20, 2021, at 2:53 AM, Richard Rosner <rrosner5(a)gmail.com> wrote: > > WARNING 2021-08-20 11:49:22,941 3975 django.request Not Found: /mailman3 > WARNING 2021-08-20 11:49:22,941 3975 django.request Not Found: /mailman3 > WARNING 2021-08-20 11:49:22,954 3975 django.request Not Found: /mailman3 > WARNING 2021-08-20 11:49:22,954 3975 django.request Not Found: /mailman3 > [pid: 3975|app: 0|req: 17/16] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:10 2021] GET /mailman3 => generated 5651 bytes in 13321 msecs \ > (HTTP/1.1 404) 5 headers in 170 bytes (1 switches on core 0) > [pid: 3975|app: 0|req: 17/17] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:07 2021] GET /mailman3 => generated 5651 bytes in 16373 msecs \ > (HTTP/1.1 404) 5 headers in 170 bytes (1 switches on core 1) > WARNING 2021-08-20 11:49:32,820 3975 django.request Not Found: /accounts > WARNING 2021-08-20 11:49:32,820 3975 django.request Not Found: /accounts > [pid: 3975|app: 0|req: 18/18] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:32 2021] GET /accounts => generated 5651 bytes in 251 msecs (H\ > TTP/1.1 404) 5 headers in 170 bytes (1 switches on core 0) > WARNING 2021-08-20 11:49:43,517 3975 django.request Not Found: /archives > WARNING 2021-08-20 11:49:43,517 3975 django.request Not Found: /archives > [pid: 3975|app: 0|req: 19/19] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:43 2021] GET /archives => generated 5651 bytes in 99 msecs (HT\ > TP/1.1 404) 5 headers in 170 bytes (1 switches on core 1) > > The proxy pass config is > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > Proxypass "/mailman3" "http://127.0.0.1:8000/mailman3" > ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" > ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" > ProxyPass "/accounts" "http://127.0.0.1:8000/accounts" > ProxyPass "/django" "http://127.0.0.1:8000/django" > ProxyPass "/user-profile" "http://127.0.0.1:8000/user-profile" > ProxyPass "/archives" "http://127.0.0.1:8000/archives" > </IfModule> There seem to be extra entries in this, depending on where you installed from, there are only some URLs that you need. You need one of the /postorius and /mailman3, one between `/archives` or `/hyperkitty`. `/django` is probably not useful I think, `/accounts` looks fine. Top level URL patterns are basically listed here[1], but it depends on where did you install from and what the url patterns are. [1]: https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/urls.py#L25 > _______________________________________________ > 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)

3 years, 10 months

Re: user mail not accepted

by Mark Sapiro

On 4/26/21 5:16 AM, Christian Stalberg via Mailman-users wrote: > I have a user whose moderation rule is 'Accept immediately' yet when they > send a message for distribution to the list, they only receive it and it is > not distributed via the list. Logfile entries below. Please advise. Btw I > have another list on this same instance which is running fine. Thank you. > > [26/Apr/2021:12:06:25 +0000] "GET /3.1/lists/ssan.lists.ccalternatives.org > HTTP/1.1" 200 453 "-" "GNU Mailman REST client v3.3.2" > [26/Apr/2021:12:06:25 +0000] "POST > /3.1/members/find?list_id=ssan.lists.ccalternatives.org&subscriber=christian > %40sewagesludgeactionnetwork.com HTTP/1.1" 200 1257 "-" "GNU Mailman REST > client v3.3.2" > [26/Apr/2021:12:06:25 +0000] "PATCH > /3.1/members/7186cd45bde34d4fa7e7b5ab36b97272 HTTP/1.1" 204 0 "-" "GNU > Mailman REST client v3.3.2" > [26/Apr/2021:12:06:26 +0000] "GET /3.1/lists/ssan.lists.ccalternatives.org > HTTP/1.1" 200 453 "-" "GNU Mailman REST client v3.3.2" > [26/Apr/2021:12:06:26 +0000] "POST > /3.1/members/find?list_id=ssan.lists.ccalternatives.org&subscriber=christian > %40sewagesludgeactionnetwork.com HTTP/1.1" 200 1288 "-" "GNU Mailman REST > client v3.3.2" > [26/Apr/2021:12:06:26 +0000] "GET > /3.1/lists/ssan(a)lists.ccalternatives.org/requests/count?token_owner=moderato > r HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.2" > [26/Apr/2021:12:06:26 +0000] "GET > /3.1/lists/ssan(a)lists.ccalternatives.org/held/count HTTP/1.1" 200 73 "-" > "GNU Mailman REST client v3.3.2" > [26/Apr/2021:12:06:26 +0000] "GET > /3.1/members/7186cd45bde34d4fa7e7b5ab36b97272/preferences HTTP/1.1" 200 295 > "-" "GNU Mailman REST client v3.3.2" These entries don't tell anything about a post to the list. They are all from Mailman's REST API relating to Postorius interactions with core. However the absence of messages like Apr 26 07:32:39 2021 (17860) ACCEPT: <message_id> and Apr 26 07:32:41 2021 (17857) HyperKitty archived message <message_id> to https://example.com/archives/list/list_adderss/message/message_id_hash/ assuming you are looking at the correct time span, says there wasn't an accepted list post. Mailman's smtp.log may have more info, but the complete, raw message that the user receives may be more helpful. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

Re: SMTPSenderRefused - howto enable STARTTLS for local mail drop

by Mark Sapiro

On 12/6/21 11:20 PM, Stefan Bauer wrote: > Unfortunately i need this, as the postfix is listening on all interfaces > and we have the policy to enforce TLS only. Nothing special in the logs: > > Dec 07 08:14:14 2021 (12303) Using agent: <mailman.mta.bulk.BulkDelivery > object at 0x7fbc29b1c4a8> > Dec 07 08:14:14 2021 (12303) Connecting to localhost:25 There should be a `Dec 07 08:14:14 2021 (12303) Starttls` entry here. > Dec 07 08:14:14 2021 (12303) envsender: v-test-bounces@domain, recipients: > ['recipient(a)own.domain'], size(msgtext): 5809 ... > > Is my mailman version maybe too old for this setting? > > I'm running GNU Mailman 3.1.1 (Between The Wheels) Yes, it's too old. STARTTLS support was added in Mailman 3.3.0 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

Help! List traffic shunted to gmail/yahoo spam folders

by Matt Wilbur EFS

Hello, I've been through DKIM hell and back. Now I'm to the point where when I "show original" mail with gmail it says SPF, DKIM and DMARC all pass, but it's still going to the spam folders. Has anyone sorted this? thanks! matt ----- show original: Delivered-To: somebody(a)gmail.com Received: by 2002:a02:968f:0:0:0:0:0 with SMTP id w15csp1521828jai; Sat, 10 Jul 2021 14:33:32 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy72rM7rrvKmz7wlOVjj2M02l971IurhWQqYjQlhjZNhtJ1m7uph2Y/p85GAtq4x56KMLi4 X-Received: by 2002:a05:6830:270b:: with SMTP id j11mr3612659otu.352.1625952812813; Sat, 10 Jul 2021 14:33:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1625952812; cv=none; d=google.com; s=arc-20160816; b=LSNHINAAV62ePpOJ85HzOKFKSRBzP4htN0SkBgG3HnZp7eVAUY7td/ibOWIsVDy0Iz AcAK6WoRhDKhHmlnx71LAo3COnbmD5TWGle/Kp8cx2tMS5bxRXw+Rb5FZYblTPIiwyFo 7u7zXTTxKCzbyCQgAmpvsQN55N41TRq1je6dTMdo1j4T6msO5pvLzfnJRT3Oo+ZP3sYY K3lOEEl1MNFcmVTxsHY73tdNMncq5TTLGdqdYvT+GDd5a6QnjrkWQvhk783kppNB6kFC dgiXst5Ql/jUbe4NnS1T+i/md+WcXTitmryEtY8lxzCjEnT6NFA5IcHw/tChpH4OqyPv MGIQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:reply-to:from:list-unsubscribe :list-subscribe:list-post:list-help:list-archive:archived-at:list-id :subject:precedence:message-id-hash:content-language:mime-version :user-agent:date:message-id:to:dkim-signature:dmarc-filter :dkim-signature; bh=4HN4XCD73340TTta47Nw8NNNFEbWsNLm9zWdectMYcI=; b=K3ANa/+WBrM8ChcoYKIUkoRZ3sgDZB77S3BRFFu2WZCOBA5pGlG176jCzA1hOz7b+6 1ewP/Imzh16yBVGzugL+/JQZJlCWV1F5S6jq8xeoQIPbkM2JGKIUFAS9+Sk+JNKDTMl4 nMTFiDVfTMkgK6f1guKxBhqHroJKJ4eAUwxjHcX17nZwvY5SOeP0UqnyQaGmeRnJuXel fcdBoY5TqnDMxq7709anmcYRQuIahso/UPjzZrdMsrTJaRhScAxfa0ZQOVnjf4bkyf0D 1/eLCHEl+oZlzNXT06ghOzPFC91g/TxComGBLRWc1G5nk92gqBPrQh9690sbOuqmHZA8 ybPA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=(a)sditdg.org header.s=mail header.b=BteyCkCY; dkim=neutral (body hash did not verify) header.i=(a)gmail.com header.s=20161025 header.b="Kt/xXWZE"; spf=pass (google.com: domain of testing-bounces(a)sditdg.org designates 65.50.252.27 as permitted sender) smtp.mailfrom=testing-bounces(a)sditdg.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=sditdg.org Return-Path: <testing-bounces(a)sditdg.org> Received: from sditdg.org ([65.50.252.27]) by mx.google.com with ESMTPS id w3si10563091oiv.8.2021.07.10.14.33.32 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 10 Jul 2021 14:33:32 -0700 (PDT) Received-SPF: pass (google.com: domain of testing-bounces(a)sditdg.org designates 65.50.252.27 as permitted sender) client-ip=65.50.252.27; Authentication-Results: mx.google.com; dkim=pass header.i=(a)sditdg.org header.s=mail header.b=BteyCkCY; dkim=neutral (body hash did not verify) header.i=(a)gmail.com header.s=20161025 header.b="Kt/xXWZE"; spf=pass (google.com: domain of testing-bounces(a)sditdg.org designates 65.50.252.27 as permitted sender) smtp.mailfrom=testing-bounces(a)sditdg.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=sditdg.org Received: from sditdg.org (localhost [127.0.0.1]) by sditdg.org (Postfix) with ESMTP id 9079DC1DF0; Sat, 10 Jul 2021 14:33:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sditdg.org; s=mail; t=1625952811; bh=4HN4XCD73340TTta47Nw8NNNFEbWsNLm9zWdectMYcI=; h=To:Date:Subject:List-Id:List-Archive:List-Help:List-Post: List-Subscribe:List-Unsubscribe:From:Reply-To:From; b=BteyCkCYE4gLRLEUV+nsoK7PM5Ayj0ce+ZgWkUdqtbwQynND4zs1PLPwebsALsP5k NYVnZLBJGHoXOA256v+imGl4BD8IFXe1onyY6VSKcJfx/2vYwfwwnDyB3zkc9s9BYO K0B4EPVOepbjClhUg5Z5JnOSyZhoIWjQHZwFsXpY+di5B2y5sDMvDyWLJHh3GGhw8y zijl2IJZDCaF3iVq4EFlxP4UfHvQ+bmfkGGmjYVJvkmsQWAsTFUb7UawK3w3m9Z6LN W+hV9H3L+95O+CIfUz0q7kG7T5gwz/eoce9ewv7xhimpVPjuatgLt4hFJcvzwaohmp S/u54SwGh0iVA== Received: from cat.efs.org (cat.efs.org [10.128.128.46]) by sditdg.org (Postfix) with ESMTPS id 0D110C1DF0 for <testing(a)sditdg.org>; Sat, 10 Jul 2021 14:33:29 -0700 (PDT) X-Spam-Status: No Authentication-Results: cat.efs.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=(a)gmail.com header.b="Kt/xXWZE" X-EFS-MailScanner-EFA-Watermark: 1626557599.13472@k3T7MnvZ29zIPokD4fCFrg X-EFS-MailScanner-EFA-From: somebody-else(a)gmail.com X-EFS-MailScanner-EFA: Found to be clean X-EFS-MailScanner-EFA-ID: 4GMjtw2R5xzYrqBb X-EFS-MailScanner-EFA-Information: Please contact matt(a)efs.org for more information Received: from mail-pl1-f180.google.com (mail-pl1-f180.google.com [209.85.214.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (no client certificate requested) by cat.efs.org (MailScanner Milter) with SMTP id 4GMjtw2R5xzYrqBb for <testing(a)sditdg.org>; Sat, 10 Jul 2021 14:33:12 -0700 (PDT) DMARC-Filter: OpenDMARC Filter v1.4.1 cat.efs.org 4GMjtw2R5xzYrqBb Authentication-Results: cat.efs.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: cat.efs.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-pl1-f180.google.com with SMTP id v14so9940plg.9 for <testing(a)sditdg.org>; Sat, 10 Jul 2021 14:33:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=g3zLYH4xKxcPrHOD18z9YfpQcnk/GaJedfustWU5uGs=; b=Kt/xXWZEIVQlTx1hyx4VeQlW8OZc+z5Uxz8vkIaQJkK5PhHmc6/0safN0MGVJcXoBe ii3/LXmMTkbbZEztKBdVIV5TI8ZqvMOS2uvJk//lFVgq/AbcKOGcrNTfg7tTpfL7knQY 79CWtAE/etBKni0pONNORAevyCQq07YwJRFvSuZDEB2mWnk+SxQpkudgEX6ngXtNKqiW OroAx3fTcEO/tEQEVCKCdJAOSi5T1gmk/nTonU1zpmw+LJTOBcgCYZu4ppIwsss1eRbH TgaZO8yhoHztSP8MCjF2fwG5GYdcgYtI1Scq8XQVVe9f7mdrOU1NMDT6+8fiZltvSg0y KaUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=g3zLYH4xKxcPrHOD18z9YfpQcnk/GaJedfustWU5uGs=; b=Jdlw1Ajc3T80d9gzMNci+0GYQ1vI7B1AzIc+4qv4t/x57S1l6PkmwmtiDV9HqJIVcA wUE9Fuih0yFJHMRwSQX/nsPLIKwmC4HO34V3Diy0NltMDSTBQFjTJ8xJY6kSmX8IXSN5 fBBvQkS9AjQbLZUm7a4ttfK6o4A5gBKSaj60I7+sc5hUxCLK+hEcb7F1pnD0AoE2/Zlz nLfyg2FNA+/BclTgRI7kgjY0+ro67BdU4KS3/E5ltSngLRSMijouKzAp9ITzzms1pBKT OkFPwRPQ3PBzcBPGF4SrQK7pcUKhdsmua7upMia3pOBjh/HvC9aUgsGUsj+T5xqOe0xU ANcA== X-Gm-Message-State: AOAM531v1T1CpYQn1gzRqHpER9tizVVsXfwKmSdvQBkSgRi3IBxptEIl Vhgt9h0ndeYsYoGUJOo+P1ttSeVVslSmlA== X-Received: by 2002:a17:90b:798:: with SMTP id l24mr46030558pjz.141.1625952789010; Sat, 10 Jul 2021 14:33:09 -0700 (PDT) Received: from [192.168.86.248] (cpe-76-93-161-126.san.res.rr.com. [76.93.161.126]) by smtp.gmail.com with ESMTPSA id d2sm8574671pjo.50.2021.07.10.14.33.08 for <testing(a)sditdg.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 10 Jul 2021 14:33:08 -0700 (PDT) To: testing(a)sditdg.org Message-ID: <fb1474b0-27d5-65ed-26b2-1753b95994c0(a)gmail.com> Date: Sat, 10 Jul 2021 14:33:07 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 Content-Language: en-US Message-ID-Hash: ZY5T327H5SEXWCMGQQMQCDSJ6IYBLNHA X-Message-ID-Hash: ZY5T327H5SEXWCMGQQMQCDSJ6IYBLNHA X-MailFrom: somebody-else(a)gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header X-Mailman-Version: 3.2.2 Precedence: list Subject: [Testing] test List-Id: <testing.sditdg.org> Archived-At: <https://sditdg.org/mailman3/hyperkitty/list/testing@sditdg.org/message/ZY5T…> List-Archive: <https://sditdg.org/mailman3/hyperkitty/list/testing@sditdg.org/> List-Help: <mailto:testing-request@sditdg.org?subject=help> List-Post: <mailto:testing@sditdg.org> List-Subscribe: <mailto:testing-join@sditdg.org> List-Unsubscribe: <mailto:testing-leave@sditdg.org> From: Matt Wilbur gmail via Testing <testing(a)sditdg.org> Reply-To: Matt Wilbur gmail <somebody-else(a)gmail.com> Content-Type: text/plain; charset="us-ascii"; format="flowed" Content-Transfer-Encoding: 7bit test _______________________________________________ Testing mailing list -- testing(a)sditdg.org To unsubscribe send an email to testing-leave(a)sditdg.org

3 years, 11 months

Re: archiving problem & updates

by Mark Sapiro

On 2/19/21 7:19 AM, Christian Stalberg via Mailman-users wrote: > I see two messages waiting to be archived. Below is excerpt from the > logfile: > > Feb 10 13:40:49 2021 (974) held message approved, message-id: > <CAGrL7FsaX8EG9pMUZreJrQt1xkEyR3ySuw2-xn3m443O0N3j1A(a)mail.gmail.com> > [10/Feb/2021:13:40:49 +0000] "POST > /3.1/lists/ncpoa(a)lists.ccalternatives.org/held/5 HTTP/1.1" 204 0 "-" "GNU > Mailman REST client v3.3.1" > [10/Feb/2021:13:40:49 +0000] "GET > /3.1/lists/ncpoa(a)lists.ccalternatives.org/held?count=0&page=1 HTTP/1.1" 200 > 90 "-" "GNU Mailman REST client v3.3.1" > [10/Feb/2021:13:40:49 +0000] "GET > /3.1/lists/ncpoa(a)lists.ccalternatives.org/held?count=10&page=1 HTTP/1.1" 200 > 90 "-" "GNU Mailman REST client v3.3.1" > [10/Feb/2021:13:40:50 +0000] "GET > /3.1/lists/ncpoa(a)lists.ccalternatives.org/requests HTTP/1.1" 200 90 "-" "GNU > Mailman REST client v3.3.1" > [10/Feb/2021:13:40:50 +0000] "GET > /3.1/lists/ncpoa(a)lists.ccalternatives.org/held?count=50&page=1 HTTP/1.1" 200 > 90 "-" "GNU Mailman REST client v3.3.1" > Feb 10 13:40:55 2021 (846) HyperKitty failure on > https://lists.ccalternatives.org/archives/api/mailman/archive: <html>^M > <head><title>413 Request Entity Too Large</title></head>^M > <body bgcolor="white">^M > <center><h1>413 Request Entity Too Large</h1></center>^M > <hr><center>nginx/1.14.2</center>^M > </body>^M > </html>^M > (413) > Feb 10 13:40:55 2021 (846) Exception in the HyperKitty archiver: <html>^M > <head><title>413 Request Entity Too Large</title></head>^M > <body bgcolor="white">^M > <center><h1>413 Request Entity Too Large</h1></center>^M > <hr><center>nginx/1.14.2</center>^M > </body>^M > </html>^M > Feb 10 13:40:55 2021 (846) Traceback (most recent call last): > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman_hyperkitty/__init_ > _.py", line 154, in _archive_message > url = self._send_message(mlist, msg) > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman_hyperkitty/__init_ > _.py", line 210, in _send_message > raise ValueError(result.text) > ValueError: <html>^M > <head><title>413 Request Entity Too Large</title></head>^M > <body bgcolor="white">^M > <center><h1>413 Request Entity Too Large</h1></center>^M > <hr><center>nginx/1.14.2</center>^M > </body>^M The issue is that one of the messages in var/archives/hyperkitty/spool/ is throwing this exception and that effectively stops archiving of new messages. I'm not sure what causes Request Entity Too Large, but I suspect it is a very large message body. You can examine the messages in var/archives/hyperkitty/spool/ with Mailman's `bin/mailman qfile` command, but I suspect the problem is caused by the largest of the files. You can just move it aside, and that should allow archiving to resume. -- 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

Re: statistics monitoring for Mailman3

by Mohsen Masoudfar

Hi Mark, Thanks again for the nice Python script. There is an issue with outlook.com. They add a '^M' (carriage Return) before msgid!! Here is part of the log that shows that. This is not in every log, though. I updated the get_log_data function (please see below), I believe it is not the smartest solution, but it seems to be working for me. Mar 14 12:53:19 2021 (11696) ('127.0.0.1', 55180) Data: b'QUIT' Mar 14 12:53:19 2021 (11696) ('127.0.0.1', 55180) connection lost Mar 14 12:53:19 2021 (11696) Connection lost during _handle_client() Mar 14 12:53:21 2021 (11701) <MN2PR20MB324587763E970CC56351F8C5B66D9(a)MN2PR20MB3245.namprd20.prod.outlook.com> smtp to testlist3(a)newlistserv.aaas.org for 1 recips, completed in 0.013000726699829102 seconds Mar 14 12:53:21 2021 (11701) <MN2PR20MB324587763E970CC56351F8C5B66D9(a)MN2PR20MB3245.namprd20.prod.outlook.com> post to testlist3(a)newlistserv.aaas.org from testlist3(a)newlistserv.aaas.org, 7940 bytes LOGRETS = ('^(?P<time_stamp>[^(]*) \(\d+\) (?:\n|\r\n)') LOGREMI = (' (?P<msgid><[^>]*>) smtp to (?P<listname>[^ ]*) for (?P<count>\d+) recips, completed ') def get_log_data(log): data = [] with open(log) as fp: for line in fp.readlines(): mo = re.match(LOGRE, line) if not mo: mts = re.match(LOGRETS, line) if mts: dt = datetime.datetime.strptime(mts.group('time_stamp'), '%b %d %H:%M:%S %Y') if not mts: mmi = re.match(LOGREMI, line) if mmi: mid = mmi.group('msgid') lname = mmi.group('listname') count = int(mmi.group('count')) data.append([dt, mid, lname, count]) continue continue dt = datetime.datetime.strptime(mo.group('time_stamp'), '%b %d %H:%M:%S %Y') mid = mo.group('msgid') lname = mo.group('listname') count = int(mo.group('count')) data.append([dt, mid, lname, count]) return data Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, March 12, 2021 2:42 PM To: MM3 Users <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: statistics monitoring for Mailman3 [EXTERNAL EMAIL] On 3/12/21 11:22 AM, Mohsen Masoudfar wrote: > I was checking on log rotating on smtp.log. On my server it does not rotate. I could use log-rotator to rotate that, but could not find any information how to inform the mailman process of the rotation, e.g. which signal to send him? The `mailman reopen` command is the recommended way, or you can send the `master` a SIGUSR1. The master's PID is in the file var/master.pid or /var/run/mailman/master.pid if you've configured `layout: fhs`. -- 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

4 years, 3 months

HyperKitty failure

by horvath.arpad.szfvar＠gmail.com

Hi, I try to connect mailman3 to hyperkitty, but there is no success so far. You can see the details below. How can I solve the problem? As I have several domain name (like lists.xxx.hu, xxx.hu, yyy.hu) on the same server, so I guess localhost won't work. In mailman-hyperkitty.cfg there is a line: base_url: http://lists.xxx.hu/hyperkitty/ /etc/mailman3/mailman-web.py includes "*" in ALLOWED_HOSTS I have an error message in /var/log/mailman3/mailman.log Dec 30 21:41:23 2021 (126976) HyperKitty failure on http://lists.xxx.hu/hyperkitty/api/mailman/archive: (405) Dec 30 21:41:23 2021 (126976) Exception in the HyperKitty archiver: Dec 30 21:41:23 2021 (126976) 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 210, in _send_message raise ValueError(result.text) ValueError In /var/log/mailman3/web/mailman-web.log WARNING 2021-12-30 20:41:23,816 127032 django.request Method Not Allowed (GET): /hyperkitty/api/mailman/archive [pid: 127032|app: 0|req: 101/101] 109.230.236.204 () {38 vars in 592 bytes} [Thu Dec 30 20:41:23 2021] GET /hyperkitty/api/mailman/archive?key=lHzJB%2FzfSWUrbPKZ84JNSlLXHVyCDt8T => generated 0 bytes in 1 msecs (HTTP/1.1 405) 6 headers in 189 bytes (1 switches on core 0) WARNING 2021-12-30 20:41:23,854 127032 django.request Method Not Allowed (GET): /hyperkitty/api/mailman/archive On Debian 11, I have these packages ii mailman3 3.3.3-1 all Mailing list management system ii mailman3-full 3.3.3-1 all Full Mailman3 mailing list management suite (metapackage) ii mailman3-web 0+20200530-2 all Django project integrating Mailman3 Postorius and HyperKitty ii python3-django-mailman3 1.3.5-2 all Django library to help interaction with Mailman3 (Python 3 version) ii python3-mailman-hyperkitty 1.1.0-10 all Mailman3 plugin to archive emails with HyperKitty Thanks, Arpad

3 years, 6 months

Mailman-users search results for query "2021"