Search results for "2021" - Mailman-users

user mail not accepted

by Christian Stalberg

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"

4 years, 2 months

Re: New messages not being archived

by Mark Sapiro

On 7/15/21 12:55 PM, Sarah H wrote: > > 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. The code is if result.status_code != 200: logger.error("HyperKitty failure on %s: %s (%s)", url, result.text, result.status_code) raise ValueError(result.text) > Jul 15 12:37:08 2021 (471314) HyperKitty failure on http://lists.client.org/hyperkitty/api/mailman/archive: So the above log entry should be followed by result.text and result.status_code. The next entry below is from the `raise ValueError(result.text)` What do you get from curl http://lists.client.org/hyperkitty/api/mailman/archive and what if you change the scheme in the base_url setting to https? > 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: And this one below is is because of the above exception. > 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> These are from the Mailman REST API and are not relevant to your issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

Re: The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header.

by Marco Marinello

Dear Mark, configuration needed much troubleshooting so I'm sure I always restarted mailman core along apache2 but since it's still a testing environment, I took the liberty to test it again for you. # pip install https://gitlab.com/mailman/hyperkitty/-/archive/1.3.5/hyperkitty-1.3.5.zip # pip install https://gitlab.com/mailman/mailman-hyperkitty/-/archive/1.2.0/mailman-hyper… # systemctl restart mailman apache2 # tail -f /var/log/mailman/mailman.log /opt/hyperkitty_django/hyperkitty.log ==> /opt/hyperkitty_django/hyperkitty.log <== ERROR 2021-10-22 23:03:19,225 25973 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. WARNING 2021-10-22 23:03:19,226 25973 django.request Unauthorized: /hyperkitty/api/mailman/archive WARNING 2021-10-22 23:03:19,226 25973 django.request Unauthorized: /hyperkitty/api/mailman/archive ==> /var/log/mailman/mailman.log <== Oct 22 21:03:19 2021 (26091) HyperKitty failure on http://127.0.0.1:8080/hyperkitty/api/mailman/archive: <html><title>Auth required</title><body> <h1>Authorization Required</h1><p>The archiver key must be sent over the Authorization HTTP header. </p></body></html> (401) Oct 22 21:03:19 2021 (26091) Exception in the HyperKitty archiver: <html><title>Auth required</title><body> <h1>Authorization Required</h1><p>The archiver key must be sent over the Authorization HTTP header. </p></body></html> Oct 22 21:03:19 2021 (26091) Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.9/site-packages/mailman_hyperkitty/__init__.py", line 151, in _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/venv/lib/python3.9/site-packages/mailman_hyperkitty/__init__.py", line 207, in _send_message raise ValueError(result.text) ValueError: <html><title>Auth required</title><body> <h1>Authorization Required</h1><p>The archiver key must be sent over the Authorization HTTP header. </p></body></html> # pip freeze | grep yperk HyperKitty @ https://gitlab.com/mailman/hyperkitty/-/archive/1.3.5/hyperkitty-1.3.5.zip mailman-hyperkitty @ https://gitlab.com/mailman/mailman-hyperkitty/-/archive/1.2.0/mailman-hyper… All the best, Marco

3 years, 8 months

Re: Does anyone have a working DKIM/ARC configuration?

by Philip Colmer

Here are the full headers from a new email. I've redacted the various domains and IP addresses but hopefully it all makes sense. Received: from AM6EUR05HT027.eop-eur05.prod.protection.outlook.com (2603:10a6:10:2b0::12) by DB7P191MB0378.EURP191.PROD.OUTLOOK.COM with HTTPS via DU2PR04CA0157.EURPRD04.PROD.OUTLOOK.COM; Tue, 14 Sep 2021 07:13:02 +0000 ARC-Seal: i=2; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=fail; b=eb5egkxeCkJnvUpwA/HTQ6aYeCJfbfL3yRdCaAhD9aVMwhljOA6V9RhgWVkVHYRpf77BZvw4IztiAU8Y/sUAUAt7s3f77M4qZ37RzOIWktDkKknW8xFxsOQaJIOaxdWjE7L53F51JMmPlOIQ/RgvkIZyiN77GTCCoxhkayzZaL5O8Gc3Rop9kY90sBNRCi/B1DU1keJ45U+KBfnulEWGE3r2DJ9BrfI8WiQCYFIvR1Ryr0wY8uqQiWlitgbfprEl7mkDzR4x/tNUvowVDqltiedfrM3ML7+AHUW4PI2Ih78Uvv6T0+fZHVrRKCOyczU0S9RilRLxMlh+lEtr+Q9GGg== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=jmWFlJwqirfiVtLi98SrRrGA3zfBLMBC8UI7ReTsiOc=; b=n07Rdb5JFtRW5a+UmP0zCEJLks5YOE8ZLI6tzNU37BgF8rsqXy2K+Mj5N5742DMymdKnUnYF99nUp79v9BxwQX7EUt7mCXOlzjo//yR8QzV5mhqBroHoisznRxs70HzISZFDCwzMKgL1/BM6jIMVKWry9aTIt2Ii8ofS/Unw7coGBPccNtALvjJ585UUt2cVfIWPjVgt/ZPJ3d/RRsiao5Ot/Myhzyo3rHpl4nZHoxFDeWWK5kZ1Gy+hUxIqZWz9UswzX8K+i9OshilBicia/q/0RHpUCg1vNQsEIQYMRsNTDmvh+moPz2SVDhgLgJ7UOVjSMaO87T2DTacvEykjBg== ARC-Authentication-Results: i=2; mx.microsoft.com 1; spf=pass (sender ip is 1.2.3.4) smtp.rcpttodomain=destination.org smtp.mailfrom=mmserver.org; dmarc=bestguesspass action=none header.from=mmserver.org; dkim=test (signature was verified) header.d=mmserver.org; dkim=fail (signature did not verify) header.d=sender.org; arc=fail (47) Received: from AM6EUR05FT022.eop-eur05.prod.protection.outlook.com (2a01:111:e400:fc11::4b) by AM6EUR05HT027.eop-eur05.prod.protection.outlook.com (2a01:111:e400:fc11::306) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4500.18; Tue, 14 Sep 2021 07:13:02 +0000 Authentication-Results: spf=pass (sender IP is 1.2.3.4) smtp.mailfrom=mmserver.org; destination.org; dkim=fail (signature did not verify) header.d=sender.org;destination.org; dmarc=bestguesspass action=none header.from=mmserver.org;compauth=pass reason=109 Received-SPF: Pass (protection.outlook.com: domain of mmserver.org designates 1.2.3.4 as permitted sender) receiver=protection.outlook.com; client-ip=1.2.3.4; helo=mmserver.org; Received: from mmserver.org (1.2.3.4) by AM6EUR05FT022.mail.protection.outlook.com (10.233.240.168) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4500.18 via Frontend Transport; Tue, 14 Sep 2021 07:13:01 +0000 X-IncomingTopHeaderMarker: OriginalChecksum:C027C4C73C859E8BC4DD2D6EB0A2AFC55128E8E6AB569058BEFA2927BD59B759;UpperCasedChecksum:69084D51601C2F94765803933A8A1E513A3CE3B72501EEBE615F8404D9524BF9;SizeAsReceived:5583;Count:36 Received: from ip-172-31-73-169.ec2.internal (localhost [127.0.0.1]) by mmserver.org (Postfix) with ESMTP id 1EB91BDF09 for <philip(a)destination.org>; Tue, 14 Sep 2021 07:13:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mmserver.org; s=mailman; t=1631603581; bh=jmWFlJwqirfiVtLi98SrRrGA3zfBLMBC8UI7ReTsiOc=; h=Date:To:Subject:List-Id:List-Archive:List-Help:List-Owner: List-Post:List-Subscribe:List-Unsubscribe:From:Reply-To:From; b=c1hpMtUIu4xFaJHhKlp9wvMuMchhYHt8jZhx7iR79DwnuFFRd/YbDd7AvspoQ4tkb ob4ZZRRsX8P0Aw3w2iOOEGVOu7cuJgeOCs3tyjFDb1yfo3GAsbvKeaRQPblbo6Oaob bUuo+5OY825Jdk2FoVAKrxqrkrC4q2OsFoVGFIAc= ARC-Seal: i=1; cv=none; a=rsa-sha256; d=mmserver.org; s=mailman; t=1631603580; b=MriwQYAoGLx6qYcQ3jvD1X6WZP2bfE7/esgXKfCV7gSfQcLpbd3iwiJVFBD+4TX3jfTcG tGL6iZ69TrW2A4QS9zn7j0WbZh0YuDea6OGe0SLqJz3vVsVQJXmiduZET4LVkZKWVOMsghR 2Bti7RMvNwok2WQzsKkOf+cXmUFDOcg= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mmserver.org; s=mailman; t=1631603580; h=from : sender : reply-to : subject : date : message-id : to : cc : mime-version : content-type : content-transfer-encoding : content-id : content-description : resent-date : resent-from : resent-sender : resent-to : resent-cc : resent-message-id : in-reply-to : references : list-id : list-help : list-unsubscribe : list-subscribe : list-post : list-owner : list-archive; bh=3DIn1IpjU5aYg7foYX2PvB0NxFt3Yvxu7ufHWw90s3M=; b=fNNEcs1c31725Mfmd4md62MVMIRbGHfnDf3SHY+W5Yz+Cb5RTYJhCpoSA6VpFUSgeGEYT DsjJDpwSbXucdbc2ar1s2TcZpshXBtGb7XSxdJy3ZWpGJ+nZdX+OvBTz8OvtggE6W/W/+KH 41/BqNmfc1MKlWsJH+q0cdwChifyo2I= ARC-Authentication-Results: i=1; mmserver.org; dkim=pass header.d=sender.org header.i=(a)sender.org header.a=rsa-sha256 header.s=google header.b=xCTkYbMD; dkim-atps=neutral; arc=none; dmarc=pass (Used From Domain Record) header.from=sender.org policy.dmarc=none Authentication-Results-Original: mmserver.org; dkim=pass header.d=sender.org header.i=(a)sender.org header.a=rsa-sha256 header.s=google header.b=xCTkYbMD; dkim-atps=neutral; arc=none; dmarc=pass (Used From Domain Record) header.from=sender.org policy.dmarc=none Received: from mail-pl1-f173.google.com (mail-pl1-f173.google.com [209.85.214.173]) by mmserver.org (Postfix) with ESMTPS id 99732BDF09 for <test(a)mmserver.org>; Tue, 14 Sep 2021 07:12:58 +0000 (UTC) Received: by mail-pl1-f173.google.com with SMTP id n4so7551535plh.9 for <test(a)mmserver.org>; Tue, 14 Sep 2021 00:12:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sender.org; s=google; h=mime-version:from:date:message-id:subject:to; bh=3DIn1IpjU5aYg7foYX2PvB0NxFt3Yvxu7ufHWw90s3M=; b=xCTkYbMDUx+tagAdAlyZE+awc/wc1iCI/PWp0jeuJFDM23WMTGo24PJjUFfCV4DH5G fKko+n5wov5IKcBpjLvcmg2OGuOQPGAl1ATWtCbl+SgZD4LBWftNLVz3XxJq2IDxb3me WF+IHsh3nunXExR17sEQx12pbXPhGmmy3G8We7jrZOLVfX0oRZ8Y6QiY1ACetrQ/FlyZ /T4axvHlXsiceP6rr6HwvHdj8XN2NbjkXZF265tfc/l2EdVXyTJlnhxxuxXFGTcBIPN1 OZadmYo5Q8VCsg78leQDp8eBAATL9JwUmFUDhL2U8KCWKXCCQJ4qVKReEqJB4PK5l5hZ 4nmg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=3DIn1IpjU5aYg7foYX2PvB0NxFt3Yvxu7ufHWw90s3M=; b=4mwQclptSSJQVxNaNlxhXDyNREM5qDVMMr8a2AvZFBoVQ6k8z1B8bMkEZB5I32NRnR BNTQUy7XQ2rVx171IgoTC24RPcQvWAd0Eg9+1On7vaMG5bIsY90ED1oavJA5NQ2KVXXn vVLr7JcKg0fsuk/xoy9bzRCZ5D5nYGYE6dCPb20iTTInM2QaXQgpoCElv0PQ7N3lvLeL KXqrhDc9bMVqbYNmu7rIkdAI+N6iY0IB+mMF16GTSM6RlMOuthl1jEQP4QK/7ShupDIM DFWC4U1vdK0+LA5Ep0ajUzgRLAK0k6GqBa+MlOsTxaYCHfruFzVGMYLu+BGhvlK+auc0 J/SA== X-Gm-Message-State: AOAM530xf2FH9mmbMhx3lhbVy3KOURBUXCxFSudsrgoQ/IHguihpAlkq fdjxxPp3FZqmjlPEPCHf6YHBtWkKPAk7jmICOiu0mHBYPA28SvgG X-Google-Smtp-Source: ABdhPJx9DHXrQn1DY+0svX/d2C3cT/h78ckSVX6QV//8wP5/4oBzLKHy5TqrppqktHiH0uZ4L+MDNmPNm1KPNNzet1s= X-Received: by 2002:a17:90a:f192:: with SMTP id bv18mr472417pjb.134.1631603577579; Tue, 14 Sep 2021 00:12:57 -0700 (PDT) Date: Tue, 14 Sep 2021 08:12:48 +0100 Message-ID: <CAKTSSTiPRjknheqN7QbvEZAzscCyRePz4JvQB1fDa39xuShMSA(a)mail.gmail.com> To: test(a)mmserver.org Message-ID-Hash: ORMUWLHDNPOVZ24JYJ3PMESIUSRL7XCC X-Message-ID-Hash: ORMUWLHDNPOVZ24JYJ3PMESIUSRL7XCC X-MailFrom: philip.colmer(a)sender.org 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 X-Mailman-Version: 3.3.4 Precedence: list Subject: [Test] How does your garden grow? List-Id: <test.mmserver.org> List-Help: <mailto:test-request@mmserver.org?subject=help> List-Owner: <mailto:test-owner@mmserver.org> List-Post: <mailto:test@mmserver.org> List-Subscribe: <mailto:test-join@mmserver.org> List-Unsubscribe: <mailto:test-leave@mmserver.org> From: Philip Colmer via Test <test(a)mmserver.org> Reply-To: Philip Colmer <philip.colmer(a)sender.org> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-IncomingHeaderCount: 36 Return-Path: test-bounces+philip=destination.org(a)mmserver.org X-MS-Exchange-Organization-ExpirationStartTime: 14 Sep 2021 07:13:01.9563 (UTC) X-MS-Exchange-Organization-ExpirationStartTimeReason: OriginalSubmit X-MS-Exchange-Organization-ExpirationInterval: 1:00:00:00.0000000 X-MS-Exchange-Organization-ExpirationIntervalReason: OriginalSubmit X-MS-Exchange-Organization-Network-Message-Id: 8da823d6-328d-433c-6822-08d9774f16e0 X-EOPAttributedMessage: 0 X-EOPTenantAttributedMessage: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa:0 X-MS-Exchange-Organization-MessageDirectionality: Incoming X-MS-PublicTrafficType: Email X-MS-Exchange-Organization-AuthSource: AM6EUR05FT022.eop-eur05.prod.protection.outlook.com X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-UserLastLogonTime: 9/14/2021 7:12:57 AM X-MS-Office365-Filtering-Correlation-Id: 8da823d6-328d-433c-6822-08d9774f16e0 X-MS-TrafficTypeDiagnostic: AM6EUR05HT027: X-MS-Exchange-EOPDirect: true X-Sender-IP: 1.2.3.4 X-SID-PRA: TEST(a)mmserver.org X-SID-Result: PASS X-MS-Exchange-Organization-PCL: 2 X-MS-Exchange-AtpMessageProperties: SA|SL X-MS-Exchange-Organization-SCL: 0 X-Microsoft-Antispam: BCL:0; X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 14 Sep 2021 07:13:01.8683 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: 8da823d6-328d-433c-6822-08d9774f16e0 X-MS-Exchange-CrossTenant-Id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-CrossTenant-AuthSource: AM6EUR05FT022.eop-eur05.prod.protection.outlook.com X-MS-Exchange-CrossTenant-AuthAs: Anonymous X-MS-Exchange-CrossTenant-FromEntityHeader: Internet X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM6EUR05HT027 X-MS-Exchange-Transport-EndToEndLatency: 00:00:00.9874238 X-MS-Exchange-Processed-By-BccFoldering: 15.20.4500.018 X-Microsoft-Antispam-Mailbox-Delivery: abwl:0;wl:0;pcwl:0;kl:0;iwl:0;ijl:0;dwl:0;dkl:0;rwl:0;ucf:0;jmr:0;ex:0;auth:1;dest:I;ENG:(5062000283)(90000117)(91040095)(91044021)(91045095)(9050020)(9060116)(9100336)(5061607266)(5061608174)(4900116)(2008001114)(2008000189)(4920091)(6250099)(4950132)(4990091); X-Message-Info: 5vMbyqxGkdefRiIkrqg4ZwpGLfyUyJn4v5cLoN5lKwXdusI/i41s1qBGsktqj/swtQInJ01+vhFDsyZNXWXqrj0a99+1or22N3ukmdiSyb1k1ptz10WM/SSCU9mbDX6xYzh1iipr2J9mGgoqib5s1JOfhLrVHogoibBIRTGVaeukc7ecTQyRj4ux3Nwhmt43YYWKeqDG4XgX8obB2vWFqw== X-Message-Delivery: Vj0xLjE7dXM9MDtsPTA7YT0wO0Q9MTtHRD0yO1NDTD0tMQ== X-Microsoft-Antispam-Message-Info: =?us-ascii?Q?g0Qa183Yfq7SY4i7wKx716EEM1w+IyCwbRK9aOFS0Ep+WmpHoOy5Mq966RH7?= =?us-ascii?Q?9RGYWFY1IfZ2w0/ytYgAPbgXGg5okckkKLB3ZKlxNlnfDk/nySn8C6RlCu/t?= =?us-ascii?Q?V6A+kb6zzWQI+PvdwNu1jQew8agjL2Yg8SHSrZJisyu/i5B9cTNrHZTYvX3w?= =?us-ascii?Q?uz9Ozh1NW9HkJTxWtXYTCKtLieIWGobTQbm8fYLF56QCyRJ/sMYWuCwqS1F5?= =?us-ascii?Q?fnsXlwODnSocVPvp2o3SeQXP8xsZ4zT+BX2QRVQG8h7+1iXk9YMNvPkLmIZN?= =?us-ascii?Q?QFZbPndZUuQs9NLggIjHnNkIMBboM+J9C8LBw3V3hm6F1zpHHj8hCGRUSZ4l?= =?us-ascii?Q?XaKZRgKU2G/TSyG1leZYA500/bUGq+1WIcmDt0r7CUc6FLut3toh/roeRjtW?= =?us-ascii?Q?ZmtOwwUTonV4L5h0L7xU4Z+R9EWr9lltQVzXTicTgtrkK32cekaHBL75q+h+?= =?us-ascii?Q?siwo3kUnFJbpeF73jSYExCXeez/DBILLqfGstDQ0bujnK19S7U1RNai1MzOn?= =?us-ascii?Q?BRevh9pn+DzRqiJl3fvMCl9IuARFm9ikxvZXVROuX2hHAliC9rv8OeBH2UWF?= =?us-ascii?Q?Agdb/l+3/X4/GoDLMSDfZevqRjk+T+lke7rNTQoq430CpI85izZCSu3OU+es?= =?us-ascii?Q?DNlxMI3x4G7eHZAHTaC6h8AN/1KDymKmLF2Cim/wyVdoZJW6i9GRBJ4eMAB4?= =?us-ascii?Q?iGGErK5+hPfBPYPpcbFHouJspu6q51ijmY3u/tSivCdveYGEboYopxTLn+qq?= =?us-ascii?Q?TKs7XM+U2ZcnV9Y4FzICuhkPzT4KNuIWhu4p+zbaFbtpBVhMHy02mv7pEEgZ?= =?us-ascii?Q?dvAKMghz0KxeloCEuV5Wg8Lf9ODixXm6v87r0zayges5sK+kHo8o9TkujXBw?= =?us-ascii?Q?slz5LBpRKEM+jpuy6jZLZT2AP0Y+wgmkmGZ+DFZ6+WNR35NWprI/qwAsKwRk?= =?us-ascii?Q?ZkPn8fAsYIYDCq4QJWtE9ni4HG2dNgONZ3/bRiQPKyp7eWoqA7bJa06r0fVc?= =?us-ascii?Q?treJR24f8ritZD/lmZbsb907n/qQrB1lGGtp/YFv82onwV1gd+398pVU9FM9?= =?us-ascii?Q?N19gzh6Z+abRCDRybKg9q00ooajOolfuZrBWGh6Elrqz9mlUE41MH7v/gRfS?= =?us-ascii?Q?9zh2D5b1ONLz?= MIME-Version: 1.0 I've started looking at OpenARC but the documentation is scarce and it isn't clear if the project is being maintained. My preference would be to stick with Mailman for ARC support if possible. I'm also trying to get Google's servers to accept the emails so that I can compare the headers, just in case it is a Microsoft issue ... but at the moment, Microsoft is accepting the emails and Google isn't :(

3 years, 9 months

Re: django request error

by github＠lunique.fr

I found the update that caused the issue on Debian 10 : apache2 (2.4.38-3+deb10u6) buster-security; urgency=high [ Yadd, Moritz Muehlenhoff ] * Initialize the request fields on read failure to avoid NULLs (Closes: CVE-2021-34798) * mod_proxy_uwsgi: Fix PATH_INFO setting for generic worker (Closes: CVE-2021-36160) * Fix ap_escape_quotes with pre-escaped quotes (Closes: CVE-2021-39275) * Sanity checks on the configured UDS path (Closes: CVE-2021-40438) -- Yadd <yadd(a)debian.org> Thu, 30 Sep 2021 05:50:49 +0200 The *good* solution is to replace by the following line : ProxyPass /mailman3/ unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ You can notice the "/" after mailman3 *and* localhost. This way, https://lists.tdl/mailman3/ will work again. This is not a bug, this a new feature ;-)

3 years, 7 months

Logging subscriptions and unsubscriptions

by Christian Schoepplein

Hi, I am in the process to migrate from mailman 2 to mailman 3 and currently I am setting up the new environment and do some tests and play around with the new system. I'd like to have a seperate log for list subscriptions and unsubscriptions. For that reason I added the following section to the mailman-extra.cfg file: [logging.subscribe] path: subscribe.log That created a file called subscribe.log but not everything regarding subscription / unsubscriptions is added to the file. When subscribing and unsubscribing a user via mail only the following line is shown: Aug 27 10:58:31 2021 (28) tmod(a)mm3.example.com: held subscription request from chris(a)example.com Nothing regarding the finished subscription and absolutely nothing regarding the unsubscription performed later. Also in mailman.log I can find the following lines: Aug 27 10:58:05 2021 (28) deque: do_confirm_verify Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/mailman/app/workflow.py", line 69, in __next__ return step() File "/usr/lib/python3.8/site-packages/mailman/app/subscriptions.py", line 356, in _step_send_confirmation raise StopIteration StopIteration Aug 27 10:58:31 2021 (28) deque: subscribe_from_restored Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/mailman/app/workflow.py", line 69, in __next__ return step() File "/usr/lib/python3.8/site-packages/mailman/app/subscriptions.py", line 326, in _step_get_moderator_approval raise StopIteration StopIteration Aug 27 10:58:33 2021 (29) OWNER: <163005471133.28.13827351997075408419@mailman-core> Is this because a higher logging level or is this an error? I can find nothing really helpfull regarding subscriptions and unsubscriptions in any logfile. Is this wanted or can this changed by any configuration setting or are this information stored in the database? Cheers, Schoepp

3 years, 10 months

Request Entity Too Large

by Christian Stalberg

Now mail sent to mm3 for distribution is not going out, for two different lists. The mailman.log shows this error: Oct 17 21:50:00 2021 (491) ACCEPT: <030601d7c3a0$ee342f20$ca9c8d60$(a)somedomain.com> Oct 17 21:50:04 2021 (488) HyperKitty failure on https://somedomain.net/archives/api/mailman/archive: <html> <head><title>413 Request Entity Too Large</title></head> <body bgcolor="white"> <center><h1>413 Request Entity Too Large</h1></center> <hr><center>nginx/1.14.2</center> </body> </html> (413) Oct 17 21:50:04 2021 (488) Exception in the HyperKitty archiver: <html> <head><title>413 Request Entity Too Large</title></head> <body bgcolor="white"> <center><h1>413 Request Entity Too Large</h1></center> <hr><center>nginx/1.14.2</center> </body> </html> Oct 17 21:50:04 2021 (488) 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> <head><title>413 Request Entity Too Large</title></head> <body bgcolor="white"> <center><h1>413 Request Entity Too Large</h1></center> <hr><center>nginx/1.14.2</center> </body> </html> Please advise. TY. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Saturday, October 16, 2021 11:21 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/ On 10/16/21 9:52 AM, Christian Stalberg via Mailman-users wrote: > When I go to https://.../admin/ I get a Django Administration screen > and in the upper right hand corner I see > > WELCOME, <username>. VIEW SITE / CHANGE PASSWORD / LOG OUT And my point was if you go to Users under Authentication and Authorization you should find that alekos.pantazis is a user. If you go to your own https://www.grizz.org/user-profile/ page, do you see a gravatar to the right of the Username, First name, Last name boxes, and does going there produce the same error in the logs. If that's all OK, then I don't know what produced the original error, but I think you can ignore it. If that produces the same error in the logs, then something is wrong with your django-mailman3 installation, but I don't know what. -- 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/

3 years, 8 months

Re: Broken web UI after upgrade

by Odhiambo Washington

On Fri, Dec 16, 2022 at 10:07 AM Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > > On Thu, Dec 15, 2022 at 11:31 AM Jörg Schulz <info(a)joergschulz.de> wrote: > >> I had this issue (using the dockerized version) when >> >> - UWSGI_STATIC_MAP=/static=/opt/mailman-web-data/static >> >> has been set to the wrong path. Maybe it's just the same: that your web >> server doesn't find the location for the static files. >> > > That seems quite unlikely because: > 1. The archives displayed properly before the upgrade. > 2. The static path is correctly set for nginx: > > server { > ... > > location / { > proxy_pass http://127.0.0.1:8000; > proxy_set_header X-Forwarded-For > $proxy_add_x_forwarded_for; > proxy_set_header X-Forwarded-Host $host; > proxy_set_header X-Forwarded-Server $host; > proxy_set_header X-Forwarded-Proto $scheme; > proxy_redirect off; > } > > location /static/ { > alias /opt/mailman/mm/static/; > } > > I am probably getting closer to where the problem is. By looking at nginx error_log while access the site, I see that there are just two CSS files that are missing, as shown in the error lo here: https://pastebin.ubuntu.com/p/7wbwMgqMyS/ Question is - why is it specifically looking for these two files - /opt/mailman/mm/static/CACHE/css/output.93545e20bc30.css -/opt/mailman/mm/static/CACHE/css/output.e1f0c6022e8f.css Where are these files supposed to come from and why are they missing? I have looked at my current CACHE directory and compared with the backup of the same site before upgrade and these files aren't the same either: root@list:/opt/mailman-bak-20221204/mm/static/CACHE/css# cd /opt/ root@list:/opt# ls -al /opt/mailman/mm/static/CACHE/css/ total 176 drwxr-xr-x 2 mailman mailman 4096 Dec 16 03:18 . drwxr-xr-x 4 mailman mailman 4096 Dec 16 03:18 .. -rw-r--r-- 1 mailman mailman 162923 Dec 16 03:18 output.1044280414ca.css -rw-r--r-- 1 mailman mailman 1209 Dec 16 03:18 output.29fe9f743a79.css -rw-r--r-- 1 mailman mailman 569 Dec 16 03:18 output.e68c4908b3de.css root@list:/opt# ls -al /opt/mailman-bak-20221204/mm/static/CACHE/css/ total 176 drwxr-xr-x 2 mailman mailman 4096 Feb 11 2021 . drwxr-xr-x 4 mailman mailman 4096 Feb 11 2021 .. -rw-r--r-- 1 mailman mailman 163370 Feb 11 2021 output.7687ae03f0d2.css -rw-r--r-- 1 mailman mailman 773 Feb 11 2021 output.d3034b4f9b48.css -rw-r--r-- 1 mailman mailman 1677 Feb 11 2021 output.dfd065ec006f.css I think the two files hold the clue to solving the issue. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 6 months

Re: HyperKitty failure

by William Oliver

On Thu, 2021-12-30 at 21:19 +0000, horvath.arpad.szfvar(a)gmail.com wrote: > 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 > [snip] I'm no expert, but here's a previous discussion I found: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… I don't know if it applies, but it looks close. billo

3 years, 6 months

Exception with processing subscription confirmation email

by Eric Broens

Hi, A new user tried to subscribe to a mailinglist, received the confirmation mail, and replied to it. The subscriber is however not subscribed and remains listed in the "pending confirmation" list. The following exception appears in the error.log. Does anyone knows how to resolve this? In the past we didn't experience any issues and no changes but security updates have been installed. Apr 29 16:15:55 2021 (1581) deque: do_confirm_verify Traceback (most recent call last): File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/workflow.py", line 69, in __next__ return step() File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/subscriptions.p y", line 356, in _step_send_confirmation raise StopIteration StopIteration Apr 29 16:16:28 2021 (1490) Uncaught runner exception: Expecting ':' delimiter: line 1 column 256 (char 255) Apr 29 16:16:28 2021 (1490) Traceback (most recent call last): File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/runners/command.py" , line 208, in _dispose mlist, msg, msgdata, parts, results) File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/commands/eml_confir m.py", line 54, in process mlist).confirm(token) File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/subscriptions.p y", line 578, in confirm workflow.restore() File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/workflow.py", line 146, in restore data = json.loads(state.data) File "/usr/lib64/python3.6/json/__init__.py", line 354, in loads return _default_decoder.decode(s) File "/usr/lib64/python3.6/json/decoder.py", line 339, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) File "/usr/lib64/python3.6/json/decoder.py", line 355, in raw_decode obj, end = self.scan_once(s, idx) json.decoder.JSONDecodeError: Expecting ':' delimiter: line 1 column 256 (char 255) Apr 29 16:16:28 2021 (1490) SHUNTING: 1619705788.5856323+57a1a759275c59b732cfa8e2985f76cfcc27dda5 Thanks in advance, Eric

4 years, 2 months

Mailman-users search results for query "2021"