At Tue, 12 Oct 2010 21:22:30 +0200, David Maus wrote: > The problem I see here is that the message-id identifies the message, > but not its location. A message with a given message-id could exist > literally everywhere: In IMAP mailbox A, local mailbox B, on a usenet > server... Or in all three places. > > Without the information where the message resides, Org is unable to > resolve or dereference the link -- unless you introduce some mechanism > to tie the mid: link to a resolving function, that in turn is tied to > a user specific mailer... Even worse: Without the folder information > the mid: is tied to a specific user setup (mailboxes and the like). Hi David, That would be the general idea. Once you have an “all mail” mailbox (or two) with fast search, you can use this to find any message-id quickly. This binds the link to the user setup at resolve-time, but it unbinds the link at the time that it is stored. This means that the user can move mail from one folder to another, switch mail servers entirely, or change email clients without links in org files breaking. I am only proposing mid: links as an alternative; others may of course prefer wl: links. > The folder information is vital to be able to resolve the link, > e.g. during export. You can define rules that translate a link to a > location in your realm to a public accessible link. E.g. if the link > points to a nntp folder at gmane, you can easily derive a http: link > when exporting a file to html. http://mid.gmane.org/87fwwbrzbd.wl%25dmaus@ictsoc.de I’m not convinced this is the right solution for everybody, but I think it would work better for my use. best, Erik
Attachment:
pgpms4s6vOcSs.pgp
Description: PGP signature