From: John Owens <jowens@ece.ucdavis.edu>
Cc: John Owens <jowens@ece.ucdavis.edu>, ding@gnus.org
Subject: Re: marks in gnus / uw imapd: what marks / how to set?
Date: Mon, 4 Aug 2003 11:08:58 -0700 [thread overview]
Message-ID: <16174.41274.451000.736598@ece.ucdavis.edu> (raw)
In-Reply-To: <ilu7k5tqpjo.fsf@latte.josefsson.org>
Simon Josefsson writes:
John Owens <jowens@ece.ucdavis.edu> writes:
> Simon Josefsson writes:
> The Gnusish way to do this would be to make Gnus read VM mailboxes
> properly. I wonder if this is difficult. Is the VM mailbox format
> described anywhere? Maybe it is just babyl and some external marks
> stuff? I'm not really familiar with VM.
>
> It's not a hard format. My elisp fu is weak, but I would certainly be
> willing to help with the transition. It's a simple format: every
> message has the following header:
>
> X-VM-v5-Data: ([nil nil nil nil t nil nil nil nil]
> ["2009" "Monday" "4" "August" "2003" "09:23:04" "+0200" "Simon Josefsson" "jas@extundo.com" "<iluu18xrinb.fsf@latte.josefsson.org>" "58" "Re: marks in gnus / uw imapd: what marks / how to set?" "^From:" nil nil "8" nil nil (number " " mark " R Simon Josefsson Aug 4 58/2009 " thread-indent "\"Re: marks in gnus / uw imapd: what marks / how to set?\"\n") nil nil nil nil nil nil]
> nil)
What format is the file? mbox, babyl, etc? It sounds pretty simple
to add a nnvm, if the files is in a already supported format. Simply
copy nnmbox or nnbabyl, remove some cruft and add a
nnvm-request-update-info that frob Gnus's flags using the headers.
It's just mbox, with this one magic header per message (X-VM-v5-Data)
that contains the marks, and a bunch of other magic headers on only
the first message in the folder (X-VM-Message-Order,
X-VM-Summary-Format, X-VM-Labels, X-VM-VHeader, X-VM-Last-Modified,
X-VM-IMAP-Retrieved, X-VM-POP-Retrieved, and X-VM-Bookmark), none of
which make any difference for this purpose and can be safely ignored
(and probably should be deleted).
Hm, if you can create a VM mailbox with say 5 messages with some
different flags and make it available, I can attempt to create a nnvm.
I'll send you a file separately, and if anyone else is interested in
looking at such a file, please let me know and I'll send it to you
too. I'm sure it's a simple (< 1 hour) task for someone familiar with
creating a nn.
On another note, then, let's say I want to do a one-to-one conversion
of VM folders to nnimap folders. What would be the procedure for doing
this if I don't want to do anything other than the one-to-one mapping
(i.e. I don't want to run through new splitting rules)? Any way to do
this for each of ~200 folders efficiently?
JDO
next prev parent reply other threads:[~2003-08-04 18:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-03 23:51 John Owens
2003-08-04 7:23 ` Simon Josefsson
2003-08-04 14:09 ` John Owens
2003-08-04 15:07 ` Simon Josefsson
2003-08-04 16:39 ` John Owens
2003-08-04 17:51 ` Simon Josefsson
2003-08-04 18:08 ` John Owens [this message]
2003-08-04 21:03 ` Simon Josefsson
[not found] ` <16174.41574.488000.239166@ece.ucdavis.edu>
2003-08-04 21:00 ` Simon Josefsson
-- strict thread matches above, loose matches on Subject: below --
2003-08-03 20:36 John Owens
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16174.41274.451000.736598@ece.ucdavis.edu \
--to=jowens@ece.ucdavis.edu \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).