From 7fa842e61f50b91257511bbbc2848285807cf8cc Mon Sep 17 00:00:00 2001 From: Dmitry Kurochkin Date: Wed, 18 Apr 2012 17:43:43 +0400 Subject: [PATCH] Re: [PATCH v2 1/3] Add 'compose' command --- 8f/36b21bdc6167014fae179b9d888ad01245ddd3 | 106 ++++++++++++++++++++++ 1 file changed, 106 insertions(+) create mode 100644 8f/36b21bdc6167014fae179b9d888ad01245ddd3 diff --git a/8f/36b21bdc6167014fae179b9d888ad01245ddd3 b/8f/36b21bdc6167014fae179b9d888ad01245ddd3 new file mode 100644 index 000000000..7413bb03d --- /dev/null +++ b/8f/36b21bdc6167014fae179b9d888ad01245ddd3 @@ -0,0 +1,106 @@ +Return-Path: +X-Original-To: notmuch@notmuchmail.org +Delivered-To: notmuch@notmuchmail.org +Received: from localhost (localhost [127.0.0.1]) + by olra.theworths.org (Postfix) with ESMTP id 2A9A3431FB6 + for ; Wed, 18 Apr 2012 06:45:41 -0700 (PDT) +X-Virus-Scanned: Debian amavisd-new at olra.theworths.org +X-Spam-Flag: NO +X-Spam-Score: -0.799 +X-Spam-Level: +X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5 + tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, + FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled +Received: from olra.theworths.org ([127.0.0.1]) + by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) + with ESMTP id EFEOpR0lUAs0 for ; + Wed, 18 Apr 2012 06:45:36 -0700 (PDT) +Received: from mail-lpp01m010-f53.google.com (mail-lpp01m010-f53.google.com + [209.85.215.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) + (No client certificate requested) + by olra.theworths.org (Postfix) with ESMTPS id 630C4431FAE + for ; Wed, 18 Apr 2012 06:45:36 -0700 (PDT) +Received: by lahc1 with SMTP id c1so5843345lah.26 + for ; Wed, 18 Apr 2012 06:45:34 -0700 (PDT) +DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; + h=from:to:cc:subject:in-reply-to:references:user-agent:date + :message-id:mime-version:content-type; + bh=RUkpxaykPeAjMEoHTFWvUVxLttl2ncj+rmt6EfuRJCQ=; + b=C6qa1puPTdy/UDVxJTcXYVtI1nVrUnv9uNhTXWyb/j2lPBI8GTjn0Gx9a21b5F/kB/ + iLaXp2Zx5hUWBOy5JMCg+xxgt1OWXESY5z167Ei0nk4dJnhifTF+nGrJ6/8+mHooPYgI + KoRoVTBG720grI6jytEnm4yc4HJhEM4wkWsSCu9CjVNrpanub/pC9+3Tsn18KIVzJuYR + 679CkfYkgMzkq3MeWBHMNlmJuipQ+xFh8QAbxodj7qL3tgoEkqLE6/tTqGdR3dvbEqP/ + q2GYh4dm0ZIZHE+Z735lAjL+hbFYnq2ZlFFpUoIrZySPhchan/Lx9e1RKl+d7gw/5jxR + RiNA== +Received: by 10.152.110.4 with SMTP id hw4mr2181226lab.44.1334756734695; + Wed, 18 Apr 2012 06:45:34 -0700 (PDT) +Received: from localhost ([91.144.186.21]) + by mx.google.com with ESMTPS id q5sm2575868lbd.13.2012.04.18.06.45.33 + (version=TLSv1/SSLv3 cipher=OTHER); + Wed, 18 Apr 2012 06:45:33 -0700 (PDT) +From: Dmitry Kurochkin +To: Felipe Contreras +Subject: Re: [PATCH v2 1/3] Add 'compose' command +In-Reply-To: + +References: <1334752753-23970-1-git-send-email-felipe.contreras@gmail.com> + <1334752753-23970-2-git-send-email-felipe.contreras@gmail.com> + <873981chpj.fsf@nikula.org> + +User-Agent: Notmuch/0.12+104~gf9ad237 (http://notmuchmail.org) Emacs/23.4.1 + (x86_64-pc-linux-gnu) +Date: Wed, 18 Apr 2012 17:43:43 +0400 +Message-ID: <874nshm9yo.fsf@gmail.com> +MIME-Version: 1.0 +Content-Type: text/plain; charset=us-ascii +Cc: notmuch@notmuchmail.org +X-BeenThere: notmuch@notmuchmail.org +X-Mailman-Version: 2.1.13 +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: Wed, 18 Apr 2012 13:45:41 -0000 + +Hi Felipe. + +Felipe Contreras writes: + +> On Wed, Apr 18, 2012 at 4:06 PM, Jani Nikula wrote: +> +>> Running "notmuch compose" more than once within a second would result in +>> identical message ids for the messages, which is not a good idea. That's +>> not likely in interactive use, but the notmuch cli is highly scriptable, +>> so someone is bound to hit this. +>> +>> Some paranoid might also be worried about "leaking" the time you run +>> "notmuch compose"... which may be different from the actual time you +>> send the message. +> +> It's still better than the current situation; nothing. In any case, +> people that have not needed this would not be affected; their UI would +> override the Message-ID. +> + +I disagree. If notmuch CLI generates a Message-ID, it must be a good +one. Otherwise we make users falsely believe that they do have a proper +Message-ID while in fact they do not. And that would bite them sooner +or later. + +Regards, + Dmitry + +> So do you have a better suggestion for a Message-ID? +> +> -- +> Felipe Contreras +> _______________________________________________ +> notmuch mailing list +> notmuch@notmuchmail.org +> http://notmuchmail.org/mailman/listinfo/notmuch -- 2.26.2