From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-Status: No, score=-3.3 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from mail-qv1-xf32.google.com (mail-qv1-xf32.google.com [IPv6:2607:f8b0:4864:20::f32]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id E5D771F4B4 for ; Mon, 21 Sep 2020 18:01:55 +0000 (UTC) Received: by mail-qv1-xf32.google.com with SMTP id cy2so7926501qvb.0 for ; Mon, 21 Sep 2020 11:01:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=date:from:to:subject:message-id:mail-followup-to:mime-version :content-disposition; bh=i0dwiMZ0RrUn6dmvnCf84y5ohiHvRNBX2KRcvdRUoxY=; b=bhIE7EMT4GTVzZys0TpBl8AhAJZRSY5k0h6dSWUT2kpWoJyYsHn0aQ5MzyYQ7zo+i2 NyBxl6Bhf4QFQvGGSc6LxVVstm9ziz3FipM6sRZdewv9xSy0dQyoL1ym5JEgMOZ3tpCN zApYJyoi7P4gF2RIYFHyVWdSzInl0dbeVAJU0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mail-followup-to :mime-version:content-disposition; bh=i0dwiMZ0RrUn6dmvnCf84y5ohiHvRNBX2KRcvdRUoxY=; b=pAelFWG2Ry51TlG1n1zgijhhnpYqDIokoQu1vXMvhn++0oe33H48BWMWXiiljmNQXX caqTEPOGcYIdjhjUpyBa8BQYjcxH+ZuwdHrmaCtp92CPIzt2GLr9qHzBftma2hjks8fj HjOURp7j17WAHUKHuZAO5pTpgHAPWgnIcSr2t1D8e/u+2kwbOWLfPeYC2s0Yq9gmtqrp IAGy5OgCq5uxiHGmKGzyeCLcUFn20DX+6l42X9EbB/ispwbcm9rg/juXxQURmExI3TJ7 6HrJkk5pRZNi5KzjQTBySbUrkFCRrpptRqMsOGemy4IUWM9fvmi6Tyljlbw4E9yxfFfK OsYw== X-Gm-Message-State: AOAM530zyRE7KatdEZQSK/rsMqwB3xcMs+dMVVsfHnNEVdXodRsYs4pC 2mkqFfoNJbxTzG1xy2iLxHarpx9NogWaOXkg X-Google-Smtp-Source: ABdhPJx2dQstxH9E2I0UiJvbzLMuMuQhL6c/woiOhFZVocmi3PK1eBT6mw7m2ZYSQKur60vrniTmLw== X-Received: by 2002:a0c:9142:: with SMTP id q60mr1250887qvq.13.1600711314520; Mon, 21 Sep 2020 11:01:54 -0700 (PDT) Received: from chatter.i7.local ([89.36.78.230]) by smtp.gmail.com with ESMTPSA id m6sm9693825qkh.106.2020.09.21.11.01.53 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 21 Sep 2020 11:01:54 -0700 (PDT) Date: Mon, 21 Sep 2020 14:01:52 -0400 From: Konstantin Ryabitsev To: meta@public-inbox.org Subject: 2 problems with listid matching Message-ID: <20200921180152.uyqluod7qxbwqubo@chatter.i7.local> Mail-Followup-To: meta@public-inbox.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline List-Id: Hello: Attempting to subscribe radiotap@radiotap.org has highlighted two problems with list-id matching. When the email comes in from the mailing list, the header is set as: List-Id: radiotap.NetBSD.org Public-inbox doesn't find this because the above list-id header is not compliant with the RFC (it should be inside angle brackets). However, even when <> are added, the match still fails due to capitalization: the List-Id value from the email header is lc'd first before it is compared with the listid= value in the config file (which isn't lc'd). So, if the config file value is using capitalization, the match will never succeed. I think public-inbox should recognize this list-id header even though it's not compliant, and it should lc both values before comparing them, since the canonical value uses capitalization. Best regards, -K