1 Return-Path: <felipe.contreras@gmail.com>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 33BE6431FBC
\r
6 for <notmuch@notmuchmail.org>; Thu, 19 Apr 2012 07:03:58 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5
\r
12 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
\r
13 FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled
\r
14 Received: from olra.theworths.org ([127.0.0.1])
\r
15 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
16 with ESMTP id scTrhzJSt--z for <notmuch@notmuchmail.org>;
\r
17 Thu, 19 Apr 2012 07:03:53 -0700 (PDT)
\r
18 Received: from mail-ee0-f53.google.com (mail-ee0-f53.google.com
\r
19 [74.125.83.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client
\r
20 certificate requested) by olra.theworths.org (Postfix) with ESMTPS id
\r
21 9FFE3431FB6 for <notmuch@notmuchmail.org>; Thu, 19 Apr 2012 07:03:53 -0700
\r
23 Received: by eekb47 with SMTP id b47so3529419eek.26
\r
24 for <notmuch@notmuchmail.org>; Thu, 19 Apr 2012 07:03:51 -0700 (PDT)
\r
25 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
\r
26 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
\r
28 bh=7QEjX/UaKYAndCGLL+edeVQlxZQ1WfcakxWpDz9Qw0I=;
\r
29 b=zA4FTBKRi+PGShsMowN/+gGkXLXaGAmC8+wkMEwXc+ScIFGOr5rt6j6gNDZxzY7ifW
\r
30 qVBiR7o4v2wIdWzkeigUJvWMMNufUPzeRl7t1TwyNr2NBuKxYujTDOKFGWO4U9RD0IET
\r
31 h2QPi4vleX5ss0Btn0WAX1YOGch0Cp6bfcFICevAHbBMaOxaqV/WPtyyVbqEfAyNsln5
\r
32 9efVCk3GKy+vQDK4CQiXP8nPmy77GTGUeeMD5x5Nv1IoxhgxbsUIcnn5eeG9Ldq0TaqC
\r
33 ME13tFFxd1vLPqmxspyK1i4ufrr00M9F7ExHRzhvZJaCl+RTxqgHVdOgTt6leVsjz2xK
\r
36 Received: by 10.14.39.197 with SMTP id d45mr352032eeb.89.1334844230910; Thu,
\r
37 19 Apr 2012 07:03:50 -0700 (PDT)
\r
38 Received: by 10.213.19.67 with HTTP; Thu, 19 Apr 2012 07:03:50 -0700 (PDT)
\r
39 In-Reply-To: <m2aa28oynl.fsf@guru.guru-group.fi>
\r
40 References: <1334752753-23970-1-git-send-email-felipe.contreras@gmail.com>
\r
41 <1334752753-23970-2-git-send-email-felipe.contreras@gmail.com>
\r
42 <873981chpj.fsf@nikula.org>
\r
43 <CAMP44s2Ukz=kDaPHYG+jzR3pDfZGP+6Ojqc4Xz5J8PxEd9fKcQ@mail.gmail.com>
\r
44 <87vckxazq7.fsf@nikula.org>
\r
45 <CAMP44s1117VXAOnURjFAeva93oiJsKKPji4awN_SoNFo0QvPPw@mail.gmail.com>
\r
46 <8739819ey5.fsf@nikula.org> <m2aa28oynl.fsf@guru.guru-group.fi>
\r
47 Date: Thu, 19 Apr 2012 17:03:50 +0300
\r
49 <CAMP44s2K6C9evr3tJaZ7KXJrRNU4mCXSu0o+GjHKEshtCZBNPQ@mail.gmail.com>
\r
50 Subject: Re: [PATCH v2 1/3] Add 'compose' command
\r
51 From: Felipe Contreras <felipe.contreras@gmail.com>
\r
52 To: Tomi Ollila <tomi.ollila@iki.fi>
\r
53 Content-Type: text/plain; charset=UTF-8
\r
54 Cc: Felipe Contreras <felipe.contreras@ngmail.com>, notmuch@notmuchmail.org
\r
55 X-BeenThere: notmuch@notmuchmail.org
\r
56 X-Mailman-Version: 2.1.13
\r
58 List-Id: "Use and development of the notmuch mail system."
\r
59 <notmuch.notmuchmail.org>
\r
60 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
61 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
62 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
63 List-Post: <mailto:notmuch@notmuchmail.org>
\r
64 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
65 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
66 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
67 X-List-Received-Date: Thu, 19 Apr 2012 14:03:58 -0000
\r
69 On Thu, Apr 19, 2012 at 12:31 PM, Tomi Ollila <tomi.ollila@iki.fi> wrote:
\r
70 > On Wed, Apr 18 2012, Jani Nikula <jani@nikula.org> wrote:
\r
72 >> On Wed, 18 Apr 2012, Felipe Contreras <felipe.contreras@gmail.com> wrote:
\r
73 >>> On Wed, Apr 18, 2012 at 5:20 PM, Jani Nikula <jani@nikula.org> wrote:
\r
74 >>>> On Wed, 18 Apr 2012 16:34:30 +0300, Felipe Contreras <felipe.contreras@gmail.com> wrote:
\r
75 >>>>> On Wed, Apr 18, 2012 at 4:06 PM, Jani Nikula <jani@nikula.org> wrote:
\r
77 >>>>> > Running "notmuch compose" more than once within a second would result in
\r
78 >>>>> > identical message ids for the messages, which is not a good idea. That's
\r
79 >>>>> > not likely in interactive use, but the notmuch cli is highly scriptable,
\r
80 >>>>> > so someone is bound to hit this.
\r
82 >>>>> > Some paranoid might also be worried about "leaking" the time you run
\r
83 >>>>> > "notmuch compose"... which may be different from the actual time you
\r
84 >>>>> > send the message.
\r
86 >>>>> It's still better than the current situation; nothing. In any case,
\r
87 >>>>> people that have not needed this would not be affected; their UI would
\r
88 >>>>> override the Message-ID.
\r
90 >>>>> So do you have a better suggestion for a Message-ID?
\r
92 >>>> The easy way would be to just use g_mime_utils_generate_message_id()
\r
93 >>>> [1]. It doesn't give you any control of the part before @, but I'm not
\r
94 >>>> sure if that really matters.
\r
96 >>> This is what gmime does:
\r
97 >>> g_strdup_printf ("%lu.%lu.%lu@%s", (unsigned long int) time (NULL),
\r
98 >>> (unsigned long int) getpid (), count++, fqdn);
\r
100 >>> Which actually has some of the issues you mentioned.
\r
102 >> Thanks for looking into gmime source. The implementation is a bit of a
\r
105 >>> I can do the same if you want (add pid and count). The advantage of
\r
106 >>> using our own format is that not only would it be more unique, but it
\r
107 >>> would not have "@fqdn".
\r
109 >> I'm starting to think doing our own would be the best, although I
\r
110 >> wouldn't object to using the gmime implementation "for now".
\r
112 > I think I would be disappointed if I had to use message id:s generated
\r
113 > by gmime -- just that "time leakage" problem. I guess the message-id
\r
114 > is usually generated just before the mail is sent so the date in message
\r
115 > id and Date: header are about equal. If message id is generated one time
\r
116 > and Date: another then the time taking to write an email leaks... (except
\r
117 > if Date: is also generate at 'notmuch compose' execution time (uhh ;/)
\r
119 > Anyway, gmime implementation or something having time(NULL).getpid()
\r
120 > could be used "for now".
\r
122 I agree. I was going to send a first batch of patches using gmime's
\r
123 implementation for now, but since apparently I have to add a bunch of
\r
124 features to my notmuch-compose patch, I'm most likely going to wait
\r
125 since I'm having trouble getting even a working setup right now.
\r