From mboxrd@z Thu Jan 1 00:00:00 1970 From: lukasz.stelmach@iem.pw.edu.pl (=?utf-8?Q?=C5=81ukasz?= Stelmach) Subject: Re: Sending org-mode nodes Date: Thu, 19 Nov 2009 18:03:43 +0100 Message-ID: <87lji2saz4.fsf@dasa3.iem.pw.edu.pl> References: <87aayjaih8.fsf@dasa3.iem.pw.edu.pl> <873a4a29ce.wl%maus.david@gmail.com> <87hbsqu86y.fsf@dasa3.iem.pw.edu.pl> <87skca93a9.fsf@gmx.de> <874ooqty72.fsf@dasa3.iem.pw.edu.pl> <873a4a8t5b.fsf@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NBAQF-0001rI-Mf for emacs-orgmode@gnu.org; Thu, 19 Nov 2009 12:03:55 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NBAQB-0001kg-QX for emacs-orgmode@gnu.org; Thu, 19 Nov 2009 12:03:55 -0500 Received: from [199.232.76.173] (port=45533 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NBAQB-0001kM-5o for emacs-orgmode@gnu.org; Thu, 19 Nov 2009 12:03:51 -0500 Received: from lo.gmane.org ([80.91.229.12]:45221) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NBAQ9-0006Lu-Ts for emacs-orgmode@gnu.org; Thu, 19 Nov 2009 12:03:50 -0500 Received: from list by lo.gmane.org with local (Exim 4.50) id 1NBAQ7-000133-CA for emacs-orgmode@gnu.org; Thu, 19 Nov 2009 18:03:47 +0100 Received: from dasa3.iem.pw.edu.pl ([194.29.147.110]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 19 Nov 2009 18:03:47 +0100 Received: from lukasz.stelmach by dasa3.iem.pw.edu.pl with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 19 Nov 2009 18:03:47 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Sebastian Rose writes: > lukasz.stelmach@iem.pw.edu.pl writes: >> Sebastian Rose writes: >>> lukasz.stelmach@iem.pw.edu.pl writes: >>>> David Maus writes: >>> //....// >>>> - Message-ID derived from node's ID. This would be quite useful for >>>> associating replies with original notes/nodes. >>> >>> >>> In that case, each mail sent from the subtree would have the same >>> message-ID, which is invalid, since the ID is made to identify a certain >>> email. It's supposed to be world wide unique for at least two years. >>> >>> Your provider would replace your (probably invalid) ID anyway. >> >> I've written *derived* which means >> org--- also fits. Right? > > Not sure. I only remember bad things with self generated > message-IDs. But I never tried it myself. Reading the RFCs will help. RFC 2822 The "Message-ID:" field provides a unique message identifier that refers to a particular version of a particular message. The uniqueness of the message identifier is guaranteed by the host that generates it (see below). (...) a good method is to put the domain name (or a domain literal IP address) of the host on which the message identifier was created on the right hand side of the "@", and put a combination of the current absolute date and time along with some other currently unique (perhaps sequential) identifier available on the system (for example, a process id number) on the left hand side. [...] > Well, if you often resend a node, it makes absolutely sense, I guess. I've rather thought about preparing an email with org-mode. Making notes, introducing a structure, think: wrinting a report. > I always write my mails from scratch. But, on the other hand, I could > imagine an Org-file with email templates like that. E.g. for mailing to > certain groups of people. This brings another option. Copy the whole node with its children into a message buffer and then run some code to make it look like it should (drawers, leading stars, attachments, tables etc.) -- Miłego dnia, Łukasz Stelmach