From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id F15C76DE13FF for ; Mon, 3 Jun 2019 07:02:59 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -2.698 X-Spam-Level: X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[AWL=-0.197, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wwbWBlfXJRzp for ; Mon, 3 Jun 2019 07:02:58 -0700 (PDT) Received: from ra.horus-it.com (ra.horus-it.com [94.130.34.199]) by arlo.cworth.org (Postfix) with ESMTPS id B7CEF6DE1329 for ; Mon, 3 Jun 2019 07:02:58 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by ra.horus-it.com (Postfix) with ESMTP id 3C85748C1CDE for ; Mon, 3 Jun 2019 16:02:53 +0200 (CEST) X-Virus-Scanned: at horus-it.com From: Ralph Seichter DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monksofcool.net; s=k1; t=1559570568; bh=oVgHb4A2OYlbxIqIMqNniy3aP48fW8Q8N5XaYSANx+g=; h=From:To:Subject:In-Reply-To:References:Date:Message-ID: Content-Type; b=XyXXxywGcmwWhmCOIGGuhbHW0kS/BDOLsQjsF0n0Tq7J3jZhsF6fQFW5nGuBc4m7C B648aW3GHQxpSLArA53jB1PSNlcllFYJEhkL/ziNkAdDMQF91zSKVtRcpWEEtThPX8 Jm/jvxF9Ud8MQOUV0AGs0SckyZH7k/WFzC+Q3ao9mlZmsv8Ttip3e5xUyGfC5r3GqG 3H9uj4rMCvdvs4VNhb3+ye92lPIl72PHSLJbUAyktHXZFIvifa1vUFc8U2gD2WNw4+ A0hYZ2uJ32J339Q6mIwrn6Pn8tLlbKtlmwMUBFu+UjYEi0RA4m9IgDSOaVqTHq5IIE UL9tJp08sT6ZA== To: notmuch@notmuchmail.org Subject: Re: feature request: caching message arrival time In-Reply-To: <87muiyhkpy.fsf@fifthhorseman.net> References: <8736kuhtky.fsf@fifthhorseman.net> <875zpppevs.fsf@ra.horus-it.com> <87tvd9gw5w.fsf@fifthhorseman.net> <87v9xnt5as.fsf@swing.csc.kth.se> <87muiyhkpy.fsf@fifthhorseman.net> Mail-Followup-To: notmuch@notmuchmail.org Date: Mon, 03 Jun 2019 16:02:48 +0200 Message-ID: <87zhmyrcl3.fsf@ra.horus-it.com> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jun 2019 14:03:00 -0000 * Daniel Kahn Gillmor: > Since notmuch actually knows when it recieved the message [...] Not meaning to complicate things, but Notmuch does not receive messages at all. ;-) One needs to rely on some software to populate the Maildir tree (Dovecot LMTP in my case, Postfix or some other MTA for local delivery in other cases). Any software transporting the raw messages can, and sometimes must, manipulate the header data, and the order in which files within the Maildir tree are created is also not determined by Notmuch. As an example: My nightly backup script disables local delivery for the duration of the backup process. Once reactivated, delivery of queued messages resumes, but it is not guaranteed to happen in the order of arrival. So even the local MTA, although trusted, might induce issues in terms of delivery time. -Ralph