From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id kDVNM8eRnWRQDwEASxT56A (envelope-from ) for ; Thu, 29 Jun 2023 16:14:31 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id 2I88M8eRnWSKOwAA9RJhRA (envelope-from ) for ; Thu, 29 Jun 2023 16:14:31 +0200 Received: from mail.notmuchmail.org (yantan.tethera.net [IPv6:2a01:4f9:c011:7a79::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 477223FE91 for ; Thu, 29 Jun 2023 16:14:31 +0200 (CEST) Received: from yantan.tethera.net (localhost [127.0.0.1]) by mail.notmuchmail.org (Postfix) with ESMTP id 954055F4A6; Thu, 29 Jun 2023 14:14:28 +0000 (UTC) Received: from mail.bitfolk.com (mail.bitfolk.com [IPv6:2001:ba8:1f1:f019::25]) by mail.notmuchmail.org (Postfix) with ESMTPS id 90A945F42C for ; Thu, 29 Jun 2023 14:14:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strugglers.net; s=alpha; h=Content-Type:MIME-Version:Message-ID:Subject:To: From:Date:In-Reply-To:Content-Transfer-Encoding:References:Sender:Reply-To:Cc :Content-ID:Content-Description:Resent-To; bh=53h9f14CtHptXTWDWFPgbKbu3sO1mzoUZeaWVAb48Xc=; b=hOVHQEY8nm3yUa3VqSth+h6/k7 Nffsj1K6ss2LI8gMJ+H8XaPzuRVzgpBgInltQfb84TsnQIhpOM/Gnd262Hf1C9+JWpmsh9twIzG5d xTZE/dlim2Mjg08Og5Vw95z7YSpgMsn2k/ycIk/YxbutPDyR1PLPrxoExYXdn1l0uO/uZQ2mQWn1N 4bOB+jMb/6ZtmHn/6bgbW5k3pj94UgkBhSXEZKS0XEivfl0gLO78B0gxT92hiu1E4OrmnKtRFwJKn p0GtEU0WSipcbRKFXdBs6djaVwv9QsHT8qx0MBAvM5TkNjGCw9ve5H2u05rP8iTJYNUbgMBiGiM5n am4lLF9Q==; Received: from andy by mail.bitfolk.com with local (Exim 4.94.2) (envelope-from ) id 1qEsPh-0004Vv-BK for notmuch@notmuchmail.org; Thu, 29 Jun 2023 14:14:25 +0000 Date: Thu, 29 Jun 2023 14:14:25 +0000 From: Andy Smith To: notmuch@notmuchmail.org Subject: What to do about message/rfc822 attachments? Message-ID: MIME-Version: 1.0 Content-Disposition: inline OpenPGP: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc X-URL: http://strugglers.net/wiki/User:Andy X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: andy@strugglers.net X-SA-Exim-Scanned: No (on mail.bitfolk.com); SAEximRunCond expanded to false Message-ID-Hash: RIOXRRJTLLD6LNWKU2UUTLRKILYH2GWH X-Message-ID-Hash: RIOXRRJTLLD6LNWKU2UUTLRKILYH2GWH X-MailFrom: andy@strugglers.net X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-notmuch.notmuchmail.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.3 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Migadu-Country: DE X-Migadu-Flow: FLOW_IN ARC-Seal: i=1; s=key1; d=yhetil.org; t=1688048071; a=rsa-sha256; cv=none; b=eL63c2wIl66Y/sUMa7FuqApmO/CaCeUJQirfqfhDzw0Ze4Grdd25kXENvzQMNLSXZRxZ5p oA/6zafF5aIKMPMrXSxtBrzrD5QSAXWW9NXyqCkq/ZZVjtxxqm+xBkEifFCs889EkefMD0 FVGafcLaQW09Rsh0/TWVesQ3m1YFJoXADSnE1TeljgqJrB3+YL3UGXfjmgEbwIjR/cBDte i7jAZ/C/QTrNl781nxA0c7/Q9+k1Hb2QHb1OKKV6YnZQ/1gNaU5mXm6WKTz8DuBKnWF+Xy uMIHlDUeNLmK82frpJBFHrtZP94qY3wNqZANLeq45TNmHGI8RIPByex/u91AHA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("body hash did not verify") header.d=strugglers.net header.s=alpha header.b=hOVHQEY8; dmarc=fail reason="SPF not aligned (relaxed)" header.from=strugglers.net (policy=none); spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 2a01:4f9:c011:7a79::1 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1688048071; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding:list-id:list-help: list-owner:list-unsubscribe:list-subscribe:list-post:dkim-signature: openpgp:openpgp; bh=BdjMikLtulhfSwxP+J+B+KJXttNM4SR5S+4WE+270Tc=; b=OWYsOS61mXExfxl3pBReiM5TTJIW18RW+xaWlWUIPhrO/Zrw98BiqUZ0XWj6AX2C1Di8DB RMX+NS1c+6sGYlp5b8StnDOiqo4arzDgOLvB3iihkRPT53/IlqFcNO+MyDxukPpY88yxYw jKgvsy9H4TiKGCC1AUShkclttwjpPa4vO9Ov1EdF2pOI4lL28ZZDFpJ2ybdDxZQPlJkDJ6 SJ0fBbp/UtGy5HWr6mSUZW/39ZhYAqBO1REOR7R2M8ynRtp1uDZLOQNJPHOe9akqhHkZt/ OpAWREHr13UHmi9utDxyNzcVYt9SEKWc1jiEl+qODtZqjl56hs/ttSOsZ7EJYA== Authentication-Results: aspmx1.migadu.com; dkim=fail ("body hash did not verify") header.d=strugglers.net header.s=alpha header.b=hOVHQEY8; dmarc=fail reason="SPF not aligned (relaxed)" header.from=strugglers.net (policy=none); spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 2a01:4f9:c011:7a79::1 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org X-Migadu-Scanner: scn0.migadu.com X-Migadu-Spam-Score: 0.99 X-Spam-Score: 0.99 X-Migadu-Queue-Id: 477223FE91 X-TUID: IA2TjSFE2qKj Hi, In this age of DKIM and DMARC, some mailing lists have decided to wrap the original message into a message/rfc822 attachment before sending it out to subscribers. Some do this unconditionally, for every message received. Some do it conditionally, for example only when the poster's domain has a DMARC policy of "reject". Popular mailing list software such as Mailman (both v2 and v3) offer both of those modes of operation. I am on multiple mailing lists that use both methods, though it is still a minority. What this means is that I see a message that looks like this: From: Joe Bloggs via somelist Message-ID: Subject: Joe's original subject References: (from Joe's post) In-Reply-To: (from Joe's post) That then contains a message/rfc822 attachment that contains the full original copy of Joe's post, with all its headers intact. I am a relatively new notmuch user. Am I correct in thinking that notmuch will look inside message/rfc822 containers and find the text/plain (and/or text/html) parts within and index them for full text search just as it would the message body in a conventional message? The threading should also work as intended too because the References/In-Reply-To are retained. So really I think the only wrinkle is that I need to remember that searching by a person's email address is not going to find all messages by them, because ones they send to such a list will not actually appear to notmuch to be from them, but instead from the lists's address. That is already an issue with mailing lists that rewrite the From: address (again for DKIM/DMARC reasons), but I was wondering if there were anything that people do with notmuch to improve matters given that all the info does actually exist in these wrapped messages. Is it somehow possible, or would be a worthwhile idea to, look for From: addresses and other useful headers also inside message/rfc822 containers? Thanks, Andy