From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/55763 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: Tue, 06 Jan 2004 20:00:57 -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 1073437289 32598 80.91.224.253 (7 Jan 2004 01:01:29 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 7 Jan 2004 01:01:29 +0000 (UTC) Original-X-From: ding-owner+M4303@lists.math.uh.edu Wed Jan 07 02:01:21 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 1Ae24X-0003WC-00 for ; Wed, 07 Jan 2004 02:01:21 +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 1Ae24K-0002r7-00; Tue, 06 Jan 2004 19:01:08 -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 1Ae24C-0002qw-00 for ding@lists.math.uh.edu; Tue, 06 Jan 2004 19:01:00 -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 994AE3A0026 for ; Tue, 6 Jan 2004 19:00:59 -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 1Ae24A-0003tL-00 for ding@gnus.org; Tue, 06 Jan 2004 20:00:58 -0500 Original-Received: from kal-el.raeburn.org (mail@kal-el.raeburn.org [18.101.0.230]) by raeburn.org (8.11.6/8.11.6) with ESMTP id i0710wC02466; Tue, 6 Jan 2004 20:00:58 -0500 (EST) Original-Received: from raeburn by kal-el.raeburn.org with local (Exim 3.35 #1 (Debian)) id 1Ae249-00069u-00; Tue, 06 Jan 2004 20:00:57 -0500 Original-To: ding@gnus.org In-Reply-To: (Simon Josefsson's message of "Sun, 04 Jan 2004 16:13:33 +0100") Original-Lines: 54 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:55763 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:55763 Simon Josefsson writes: > Hm. What about: when marking an article, use the current > nnimap-split-rule to determine which groups would receive the current > message, and then use the imap-search logic above on only those > groups, to find any crossposted copies? Will probably be rather slow > anyway, and assumes nnimap-split-rule knows about all split rules, but > it is an improvement. Good idea ... except that one of my group names is constructed when the init file is loaded, using (format-time-string "all.%Y-%m"). And if I get to use Sieve eventually, the spam rating calculation, at least, would be likely to differ between Gnus and Sieve. I want those format-time-string groups to be "all mail I got during month X and haven't deleted", so I can search for messages I got, but am not sure from what list, as long as I know approximately when, without having to pull down a summary of *all* my mail. If I had a way to do that with Gnus, I could probably make do with it being one group instead of one per month. If I could specify a date range with an nnvirtual group, and have that range propagated into a search on any component nnimap groups, I could probably even make do with a huge nnvirtual group to gather together all the list-oriented and other groups. That wouldn't eliminate cross-posting, but it would cut out a lot of it. > I think the nnmail split-log already is permanent, it is used for, > e.g., `nnmail-split-fancy-with-parent' which have similar needs (e.g., > find destination groups for earlier messages based on message-id). Ah, you mean the nnmail message-id cache file? Good point. But I'd have to set nnmail-message-id-cache-length to something absurdly large, or the data will get thrown away. It defaults to 1000, which won't have nearly the same performance problems as a complete list. (And see the aforementioned problems with Sieve.) > When nnimap crosspost split an article into several groups, it add > client-specific message flags on each message, indicating the mailbox > and article number of the other crossposted copies. For example, if > article 4711 in mailbox INBOX.foo have a mark > gnus-crosspost-INBOX.bar-42, then when marking INBOX.foo:4711 the same > mark be applied to INBOX.bar:42 as well. There is one immediate I'm told some IMAP servers like Cyrus will limit the number of flags to something like 32 per mailbox. Even listing the group names and not the message numbers would quickly exceed that limit. A single flag, gnus-(not-)crossposted, might be enough to tell Gnus whether or not the other groups need to be scanned, but it would still suck to have to rescan all of them. Too bad IMAP doesn't allow arbitrary client-defined string attributes for messages... Ken