From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:403:478a::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id qEr5Jw4ivGTOfAAASxT56A (envelope-from ) for ; Sat, 22 Jul 2023 20:38:06 +0200 Received: from aspmx1.migadu.com ([2001:41d0:403:478a::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id wB/BJw4ivGTA8QAAauVa8A (envelope-from ) for ; Sat, 22 Jul 2023 20:38:06 +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 03D4953397 for ; Sat, 22 Jul 2023 20:38:06 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=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; dmarc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1690051086; 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: in-reply-to:in-reply-to:references:references:list-id:list-help: list-owner:list-unsubscribe:list-subscribe:list-post; bh=e4ky8QEPo2BBlJEF0R/9+TJfrAI+NgbAPl0UeetXIgY=; b=jqifIJqidWr6YzoheK3xL44ynajhehSdW3bpI2uHW95uGP4bvcRsFLeuw+2tIMWQCYYYvE JbBnk9YnqDkIUVQWpVpepfBorrqr/MCE4pGWNg7fX7VRHOTBh5h/SvblyU4csrK4zYXOaN yopIkO/HrjKpSaRbOXijB1uTj4Ow3GR3VRgf7PjeTAzc8UOC61Q0x12LetSfitciTx+ts/ 5EeLPfaN8vVTdh3ZUEMO4XenZ0UIUBc7Qe1YFSSN/ZYdGD7vpscP3yBUtA3j4v+AkqGJl+ oFL2eM5xwA/ukEHznt/afFVZjFE7iJh/Qvx2PA41U+Kpp8N0xdDnLufdw+8FfA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=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; dmarc=none ARC-Seal: i=1; s=key1; d=yhetil.org; t=1690051086; a=rsa-sha256; cv=none; b=DLxBPPcWZftiVF1mgm/mwxK6L4nQo8B+GUyGM7VRhGJnOZEr1KVZHfHmtD3Hx/9MkB6CDW gUU0RWip4/rt81+e83cgzjcOaQPGBhtT9mdOw3FxoJ1bmaIBuH7OGv//4BiN4pLEbZ5njK 0ihRpFEuTUv5n++NYVlJgZSEksUVHgDvoxjLq3bQ2jCWh08y5RXZEEP6Ycrd7sIJ/zj/dl UI+GuCQRflUPLaIf+DM9a1cbDPwceoeQO+L3T3pveC7+Nj59aUOa4CB78PGO2jUPDhJAR1 RhxXOLIb4+50W+I6zDg7BDrluJmaWbxzt5LpTiI+V9xuDBDyD1TYhiS8YauDLA== Received: from yantan.tethera.net (localhost [127.0.0.1]) by mail.notmuchmail.org (Postfix) with ESMTP id A2BB35F707; Sat, 22 Jul 2023 18:38:03 +0000 (UTC) Received: from phubs.tethera.net (phubs.tethera.net [192.99.9.157]) by mail.notmuchmail.org (Postfix) with ESMTPS id 74A9F5F6D7 for ; Sat, 22 Jul 2023 18:38:01 +0000 (UTC) Received: from tethera.net (fctnnbsc51w-159-2-210-253.dhcp-dynamic.fibreop.nb.bellaliant.net [159.2.210.253]) by phubs.tethera.net (Postfix) with ESMTPS id D5965180172; Sat, 22 Jul 2023 15:37:59 -0300 (ADT) Received: (nullmailer pid 1019412 invoked by uid 1000); Sat, 22 Jul 2023 18:37:59 -0000 From: David Bremner To: Andy Smith , notmuch@notmuchmail.org Subject: Re: What to do about message/rfc822 attachments? In-Reply-To: References: Date: Sat, 22 Jul 2023 15:37:59 -0300 Message-ID: <87lef7g5bs.fsf@tethera.net> MIME-Version: 1.0 Message-ID-Hash: ZKN6R4HLB4CZRVASIU4NQDYX4TR6CGCP X-Message-ID-Hash: ZKN6R4HLB4CZRVASIU4NQDYX4TR6CGCP X-MailFrom: david@tethera.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-Flow: FLOW_IN X-Migadu-Country: DE X-Spam-Score: -1.60 X-Migadu-Queue-Id: 03D4953397 X-Migadu-Spam-Score: -1.60 X-Migadu-Scanner: mx0.migadu.com X-TUID: zxjV75GhM2FI Andy Smith writes: > > 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? Hopefully. I have been meaning to verify that. If not, it's a bug we should try to fix. > 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? How would we tell the difference between some list software forwarding a message/rfc822 part, and a human just forwarding a message? I'd prefer not to introduce (more) heuristics into the indexing process, but if there is some written RFC/standard these lists are following then we could try to follow it too.