Gnus development mailing list
 help / color / mirror / Atom feed
From: Sean Doran <smd@ebone.net>
Subject: nnml -> nnimap (preserving Xrefs)
Date: 30 Aug 2000 07:55:12 +0200	[thread overview]
Message-ID: <52em3770ov.fsf@sean.ebone.net> (raw)


Hi -

   I thought I did something very clever with the
following nnimap-split-rule and a small function.
I use it as follows:
        1/ enter nnml group
        2/ M P a
        3/ B m nnimap+server:~/Mail/IMAP/INBOX
        4/ leave (now-empty) nnml group
        5/ in group buffer, point on an nnimap+server: group
        6/ M-g

   It's a bit of a hack, but the net result is that
anything that was caught by my previous nnmail-split-fancy
is now cross-posted into multiple nnimap groups, with
marks preserved.  I'm pretty happy.  However, now I have
two problems.

   First problem: it took a bit to realize I needed the
                  "my-imap-splitter" function to avoid
                  EVERYTHING being crossposted into "misc"
                  (instead of just new mail being moved there)
                  I (naively) did "mv misc INBOX" + M-g
                  and now there are *lots* of duplicates
                  in each group.   How do I get rid of them?

   Second problem: How does anything know that the
                   the nnimap-split-rule crossposted an
                   article?  That is, how do I get marks
                   to propagate to all the groups an
                   nnimap article is crossposted into?

   Any help in migrating a huge pile of large-ish, heavily
crossposted nnml groups into nnimap will be appreciated!

        Sean.

(setq nnimap-split-rule 
      '(("server"
	 (".*"
	  (("~/Mail/IMAP/\\5" "^Xref: .+ \\(.+\\):.+ \\(.+\\):.+ \\(.+\\):.+ \\(.+\\):.+ \\(.+\\):.+")
	   ("~/Mail/IMAP/\\4" "^Xref: .+ \\(.+\\):.+ \\(.+\\):.+ \\(.+\\):.+ \\(.+\\):.+")
	   ("~/Mail/IMAP/\\3" "^Xref: .+ \\(.+\\):.+ \\(.+\\):.+ \\(.+\\):.+")
	   ("~/Mail/IMAP/\\2" "^Xref: .+ \\(.+\\):.+ \\(.+\\):.+")
	   ("~/Mail/IMAP/\\1" "^Xref: .+ \\(.+\\):.+")
	   ("~/Mail/IMAP/misc" my-imap-splitter))))))

; we have to allow crossposting here...
(setq nnimap-split-crosspost t)

(defun my-imap-splitter (group)
  "called with the headers narrowed, returns t iff there is no ^Xref: line, nil otherwise"
  (let ((regexp "^Xref: "))
    (goto-char (point-min))
    (progn (not (re-search-forward regexp nil t)))))





             reply	other threads:[~2000-08-30  5:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-30  5:55 Sean Doran [this message]
2000-08-30  8:45 ` Simon Josefsson
2000-09-01 10:36   ` Steinar Bang
2000-09-01 10:58     ` Simon Josefsson

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=52em3770ov.fsf@sean.ebone.net \
    --to=smd@ebone.net \
    /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).