From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/31870 Path: main.gmane.org!not-for-mail From: prj@po.cwru.edu (Paul Jarc) Newsgroups: gmane.emacs.gnus.general Subject: Re: (provide 'nnmaildir) Date: 20 Jul 2000 10:19:57 -0400 Sender: owner-ding@hpc.uh.edu Message-ID: References: <20000715005611.8018.qmail@multivac.student.cwru.edu> <20000717182810.13970.qmail@multivac.student.cwru.edu> NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035168231 16498 80.91.224.250 (21 Oct 2002 02:43:51 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 02:43:51 +0000 (UTC) Return-Path: Original-Received: from fisher.math.uh.edu (fisher.math.uh.edu [129.7.128.35]) by mailhost.sclp.com (Postfix) with ESMTP id B3CD5D051F for ; Thu, 20 Jul 2000 10:21:02 -0400 (EDT) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by fisher.math.uh.edu (8.9.1/8.9.1) with ESMTP id JAC27753; Thu, 20 Jul 2000 09:20:45 -0500 (CDT) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Thu, 20 Jul 2000 09:19:47 -0500 (CDT) Original-Received: from mailhost.sclp.com (postfix@sclp3.sclp.com [204.252.123.139]) by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id JAA01832 for ; Thu, 20 Jul 2000 09:19:30 -0500 (CDT) Original-Received: from multivac.student.cwru.edu (multivac.STUDENT.CWRU.Edu [129.22.239.69]) by mailhost.sclp.com (Postfix) with SMTP id 10C14D051F for ; Thu, 20 Jul 2000 10:20:04 -0400 (EDT) Original-Received: (qmail 6173 invoked by uid 500); 20 Jul 2000 14:19:57 -0000 Mail-Followup-To: ding@gnus.org Original-To: ding@gnus.org In-Reply-To: Steve Harris's message of "19 Jul 2000 08:36:19 -0700" Original-Lines: 33 X-Mailer: Gnus v5.7/Emacs 20.7 Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:31870 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:31870 Steve Harris writes: > Is the problem that nnimap eventually has to send ranges of these > UIDs, and thus must understand them *as numbers* at some point? Well, nnimap has to use *something*, treat it as a number (since that's what Gnus expects), and preferably be able to handle ranges sent back to it by Gnus. Courier's UIDs aren't an ideal choice of this something because of their low density. But there must at least be a mapping between nnimap's article numbers and IMAP's UIDs. > Also, does nnimap care - so far as talking to Gnus - whether one UID > is greater than another? I don't know whether nnimap cares, exactly, but Gnus cares: article numbers (which currently are UIDs) must be increasing - the article must be numbered in the order they arrive. > > Since nnmaildir seem to be coming, it might be a more realistic > > solution for you. > > This one's confusing. Will nnmaildir be able to talk IMAP, or do you > mean that nnmaildir would work for a local maildir spool? Since I'm > connecting to my mail host from afar, I need IMAP. nnmaildir will work only for local maildirs - for some value of `local'. If you can NFS-mount your maildir on your local system, nnmaildir should work for you. I've fixed the new-messages-showing- up-as-old bug. I'm using it now for my mail reading, and it seems to work. Still incomplete, though: no groups or expiration yet. paul