From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/7683 Path: main.gmane.org!not-for-mail From: Allan Poindexter Newsgroups: gmane.emacs.gnus.general Subject: more nnbabyl woes Date: 20 Aug 1996 15:59:23 -0500 Sender: allan@royal-oak.csc.ti.com Message-ID: Reply-To: allan@csc.ti.com NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035147963 8190 80.91.224.250 (20 Oct 2002 21:06:03 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 21:06:03 +0000 (UTC) Return-Path: ding-request@ifi.uio.no Original-Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by deanna.miranova.com (8.7.5/8.6.9) with SMTP id OAA03890 for ; Tue, 20 Aug 1996 14:16:04 -0700 Original-Received: from gatekeep.ti.com (news.ti.com [192.94.94.33]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) id for ; Tue, 20 Aug 1996 23:00:28 +0200 Original-Received: from osage.csc.ti.com ([192.91.61.31]) by gatekeep.ti.com (8.6.13) with ESMTP id PAA22035 for ; Tue, 20 Aug 1996 15:59:55 -0500 Original-Received: from royal-oak.csc.ti.com (royal-oak.csc.ti.com [192.91.61.73]) by osage.csc.ti.com (8.7.5/8.7.3) with SMTP id PAA20223 for ; Tue, 20 Aug 1996 15:59:24 -0500 (CDT) Original-Received: by royal-oak.csc.ti.com (SMI-8.6/SMI-SVR4) id PAA13187; Tue, 20 Aug 1996 15:59:24 -0500 Original-To: ding@ifi.uio.no Original-Lines: 63 X-Mailer: Gnus v5.3/Emacs 19.33 Xref: main.gmane.org gmane.emacs.gnus.general:7683 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:7683 I have a series of nnbabyl newsgroups defined. Below is a typical example: ("nnbabyl+clist:gnus" 4 ((1 . 2) (15 . 16) 24 112 115 (118 . 121) 127 139 148 152 157) ((expire 16) (reply 15) (tick 157)) (nnbabyl "clist" (nnmail-spool-file procmail) (nnmail-use-procmail t) (nnmail-procmail-directory "~allan/mail/.inboxes") (nnmail-procmail-suffix ".c") (nnbabyl-mbox-file "~allan/mail/nnbabyl/nnclist") (nnbabyl-active-file "~allan/mail/nnbabyl/.active/clist") (nnbabyl-get-new-mail t)) ((to-address . "ding@ifi.uio.no"))) The only differences between the definitions of the different groups are: 1. Different nnmail-procmail-suffix settings according to what category the groups go into. ".c" means a computer related mailing list. ".a" is administrative messages. ".mail" is my main personal email etc. 2. Different nnbabyl-mbox-file and nnbabyl-active-file settings to correspond with the suffix distinctions. (I toyed with the idea of one active file but wasn't sure it would work so I decided to try this first.) 3. Different group parameters. Non-mailing-list groups have no to-address (of course). Some are auto-expire, etc. After a couple of false starts (e.g. don't set nnmail-spool-file to "'procmail" since the variable list isn't evaluated) this setup worked great when I started it up. Gnus quickly sucked my procmail directory dry and produced the newsgroups in a most gratifying manner. The problems started when I tried to get more new mail. The M-g command would return immediately without getting any of the new mail. I looked at the server buffer and there were two definitions of each of the servers. I deleted the server definitions that were writable and left only one copy of each (a read-only definition). This zapped the server-alist in my .newsrc.eld but seemed to fix the problem. It was not to be, however. Soon the problem reappeared but this time there were no double server definitions to blame. Gnus would always read the mail correctly on startup but at some indeterminate time afterwards it would fail to see any new mail. On a hunch I tried manually closing the server to see what would happen. Bingo. It always reads the mail correctly when the server is not already open and then fails after an indeterminate number of later M-g's. Does anyone have any ideas? In order to make my workaround more palatable does anyone have a suggestion for having M-g close the server automatically before it tries to read new mail? I tried setting nnmail-pre-get-new-mail-hook in the group parameters but that did not work.