From: lukasz.stelmach@iem.pw.edu.pl (Łukasz Stelmach)
To: emacs-orgmode@gnu.org
Subject: Re: Sending org-mode nodes
Date: Thu, 19 Nov 2009 18:03:43 +0100 [thread overview]
Message-ID: <87lji2saz4.fsf@dasa3.iem.pw.edu.pl> (raw)
In-Reply-To: 873a4a8t5b.fsf@gmx.de
Sebastian Rose <sebastian_rose@gmx.de> writes:
> lukasz.stelmach@iem.pw.edu.pl writes:
>> Sebastian Rose <sebastian_rose@gmx.de> writes:
>>> lukasz.stelmach@iem.pw.edu.pl writes:
>>>> David Maus <maus.david@gmail.com> 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-<ID>-<current-time>-<user-mail-address> 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
next prev parent reply other threads:[~2009-11-19 17:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 16:46 Sending org-mode nodes lukasz.stelmach
2009-11-19 8:43 ` David Maus
2009-11-19 10:20 ` lukasz.stelmach
2009-11-19 11:12 ` Sebastian Rose
2009-11-19 13:56 ` lukasz.stelmach
2009-11-19 14:51 ` Sebastian Rose
2009-11-19 15:54 ` Bernt Hansen
2009-11-19 16:50 ` Łukasz Stelmach
2009-11-19 17:03 ` Łukasz Stelmach [this message]
2009-11-19 18:22 ` Sebastian Rose
2009-11-20 13:35 ` Łukasz Stelmach
2009-11-20 22:38 ` Sebastian Rose
2009-11-19 15:23 ` Eric Schulte
2009-11-19 17:26 ` Eric Schulte
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lji2saz4.fsf@dasa3.iem.pw.edu.pl \
--to=lukasz.stelmach@iem.pw.edu.pl \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).