From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/87602 Path: news.gmane.org!.POSTED!not-for-mail From: Harry Putnam Newsgroups: gmane.emacs.gnus.general Subject: Can anyone explain this error message? Date: Thu, 27 Jul 2017 10:58:55 -0400 Organization: Still searching... Message-ID: <86iniekjtc.fsf@local.lan> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1501167623 12530 195.159.176.226 (27 Jul 2017 15:00:23 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 27 Jul 2017 15:00:23 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) To: ding@gnus.org Original-X-From: ding-owner+m35816@lists.math.uh.edu Thu Jul 27 17:00:15 2017 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from mxfilter-048035.atla03.us.yomura.com ([107.189.48.35]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dakGj-0002Un-RG for ding-account@gmane.org; Thu, 27 Jul 2017 17:00:05 +0200 X-Yomura-MXScrub: 1.0 Original-Received: from lists1.math.uh.edu (unknown [129.7.128.208]) by mxfilter-048035.atla03.us.yomura.com (Halon) with ESMTPS id 4840a2e4-72dc-11e7-b087-b499baabecb2; Thu, 27 Jul 2017 15:00:09 +0000 (UTC) Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.87) (envelope-from ) id 1dakGB-0005JY-8r; Thu, 27 Jul 2017 09:59:31 -0500 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by lists1.math.uh.edu with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87) (envelope-from ) id 1dakG8-0005Ix-RN for ding@lists.math.uh.edu; Thu, 27 Jul 2017 09:59:28 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtps (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.87) (envelope-from ) id 1dakG7-0000Me-P5 for ding@lists.math.uh.edu; Thu, 27 Jul 2017 09:59:28 -0500 Original-Received: from [195.159.176.226] (helo=blaine.gmane.org) by quimby.gnus.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1dakFq-00084V-8i for ding@gnus.org; Thu, 27 Jul 2017 16:59:17 +0200 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1dakFg-00080K-PE for ding@gnus.org; Thu, 27 Jul 2017 16:59:00 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 48 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:PeIBTo+lYvH3JbBPI7P7ZiGbz7Y= List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:87602 Archived-At: When I start gnus, or scan for news/mail I get this error in echo area (wrapped for mail): Mail source (directory :path /home/reader/spool/in/ :suffix .in :predicate #[(file) \301!\302\230\207 [file file-name-nondirectory cron_tr.in] 2]) error (Searching for program). Continue? (y or n) y In gnus I have this: (setq mail-sources '((file :path "/var/spool/mail/reader") (directory :path "/home/reader/spool/in/" :suffix ".in"))) There are dozens of mbox style files in there, all ending in *.in When scanned, gnus slurps them up and delivers to nnml groups of the same name minus the `.in' part. But for some reason the file mentioned in the error (cron_tr.in) has a problem. I don't see anything unusual about it, but did delete it.. Of course it gets recreated when procmail delivers more msgs to it. Just like all the other *.in files... Once again I hit the error after it gets recreated. [Further note from a day later: I see now after deleting all tine *.in files that all are causing the same error with different filename. of course. All `searching for program'. What program would that be... far as I know its gnus itself that does the slurping, after procmail writes to those mbox style files. I made no changes in .procmailrc .gnus or .emacs, however: I did recreate the emacs directory created by git, from a backup of a few hours earlier, due to problems with gnus failing to get mail from several nnimap groups following a git pull and rebuild of emacs yesterday (170725). Something I've done with no problems a time or two in the past. That is when the error started to appear. Must have lost something that handles the transfer of of those mbox files to nnml folders.