From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/55573 Path: main.gmane.org!not-for-mail From: Ken Raeburn Newsgroups: gmane.emacs.gnus.general Subject: Re: nnimap and crossposting (Re: Moving from nnml to nnimap...) Date: Sat, 03 Jan 2004 22:28:46 -0500 Sender: ding-owner@lists.math.uh.edu Message-ID: References: <87he0ur0yg.fsf@enki.rimspace.net> <4nisl9envb.fsf@lockgroove.bwh.harvard.edu> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1073186934 17338 80.91.224.253 (4 Jan 2004 03:28:54 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 4 Jan 2004 03:28:54 +0000 (UTC) Original-X-From: ding-owner+M4113@lists.math.uh.edu Sun Jan 04 04:28:51 2004 Return-path: Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1Acywd-0007iR-00 for ; Sun, 04 Jan 2004 04:28:51 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 1AcywW-0005cq-00; Sat, 03 Jan 2004 21:28:44 -0600 Original-Received: from justine.libertine.org ([66.139.78.221] ident=postfix) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 1AcywS-0005cl-00 for ding@lists.math.uh.edu; Sat, 03 Jan 2004 21:28:40 -0600 Original-Received: from smtp03.mrf.mail.rcn.net (smtp03.mrf.mail.rcn.net [207.172.4.62]) by justine.libertine.org (Postfix) with ESMTP id 041393A006F for ; Sat, 3 Jan 2004 21:28:40 -0600 (CST) Original-Received: from 216-15-127-174.c3-0.smr-ubr3.sbo-smr.ma.cable.rcn.com ([216.15.127.174] helo=raeburn.org) by smtp03.mrf.mail.rcn.net with esmtp (Exim 3.35 #4) id 1AcywR-0000IE-00 for ding@gnus.org; Sat, 03 Jan 2004 22:28:39 -0500 Original-Received: from kal-el.raeburn.org ([2002:d80f:7fae:1:201:2ff:fe23:e26d]) by raeburn.org (8.11.6/8.11.6) with ESMTP id i043Slk19353; Sat, 3 Jan 2004 22:28:47 -0500 (EST) Original-Received: from raeburn by kal-el.raeburn.org with local (Exim 3.35 #1 (Debian)) id 1AcywY-0001Qq-00; Sat, 03 Jan 2004 22:28:46 -0500 Original-To: ding@gnus.org In-Reply-To: (Simon Josefsson's message of "Fri, 02 Jan 2004 22:41:12 +0100") Original-Lines: 47 User-Agent: Gnus/5.090006 (Oort Gnus v0.06) Emacs/21.1.50 (i686-pc-linux-gnu) Precedence: bulk Xref: main.gmane.org gmane.emacs.gnus.general:55573 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:55573 Simon Josefsson writes: >> My experimentation so far (playing with imtest, don't have the guest >> account and nnimap config set up yet) seems to indicate that the marks >> won't be propagated. If this is the case, I think it would be a good >> idea for the documentation to indicate this. > > IMAP doesn't understand the concept of crossposting, I think, so this > sounds normal. How does crosspost mark propagation work for nntp > groups? Using the xref header, I believe, which as far as I can tell, is generated on the fly for nnimap, and only lists the current group. I wonder, is there a way to go through all the groups and ask the server if a certain set of message-ids are present in each? It would probably be painfully slow if there are a lot of groups (I've got over 200 groups in my nnml hierarchy), and would require either staying connected until all the groups are scanned or storing the data in some magic place so the scan can be resumed if interrupted. Worst case, perhaps Gnus could create a variant on the Xref header, which says which folders the article was going to be copied to, and leave out the message numbers, but that presumably requires Gnus to download, edit, and upload each message, and it wouldn't work with something like Sieve doing the refiling as messages come in, which is where I'd prefer to get eventually. > I suspect it might be possible to implement something like it > for nnimap by looking in the nnmail message-id split log when applying > marks to a group (i.e., for each article with new marks, look up the > message id in the split log and find out what other groups it was > crossposted to and apply the same mark to it). That means this split log would have to be permanent, not per-session, so I could read (and mark expirable across groups) in this session a message I got during the last session. That per-server data will get very big, and slow to scan. And it would need to be shared between different client systems one might run Gnus on. On the one hand, that might not be much worse than the .newsrc.eld file, but I'd kinda like to be able to browse my mail on my home server from my Gnus session at work on occasion, and vice versa, and they really shouldn't have to share all the .newsrc.eld data. And isn't it part of the point of IMAP that such data lives on the server? Ken