Gnus development mailing list
 help / color / mirror / Atom feed
From: Nick Papadonis <nick@sturgeon.coelacanth.com>
Subject: procmail/gnus problem?
Date: Sun, 5 Nov 100 13:59:21 -0500 (EST)	[thread overview]
Message-ID: <200011051859.NAA25338@sturgeon.coelacanth.com> (raw)

Hi.  

I have HOURS trying to find a solution to this problem. I don't know if anyone can point me in the right direction. 

Recently I set up procmail, and attempted to change the gnus startup file to import my procmail directory.  I added the following:
(setq
 gnus-secondary-select-methods '((nnml ""))
 nnmail-spool-file 'procmail
 nnmail-procmail-directory "~/incoming/"
 nnmail-delete-incoming t
)

My mailing lists are spooled into ~/incoming/ and have extensions like 'list.gnus.spool'.
I thought they would be imported to -> list.gnus, etc...

When starting gnus 5.8.8 I get the following error:
Wrong type argument: listp, procmail

I am using xemacs 21.1.12.

Any insight into this error appreciated.  I saw something in the list where nnmail-spool-file shouldn't be set to procmail, but wasn't sure if thats what I wanted.

Thanks.

- Nick

Here is a backtrace.

Backtrace:
Signaling: (wrong-type-argument listp procmail)
  nnmail-get-new-mail(nnml nnml-save-nov "~/Mail/" nil)
  nnml-request-scan(nil "")
  gnus-request-scan(nil (nnml ""))
  gnus-read-active-file-1((nnml "") nil)
  gnus-read-active-file(nil nil)
  gnus-setup-news(nil nil nil)
  byte-code("..." [dont-connect did-connect gnus-group-quit gnus-run-hooks gnus-startup-hook gnus-make-newsrc-file gnus-startup-file gnus-current-startup-file gnus-slave gnus-use-dribble-file gnus-dribble-read-file gnus-use-grouplens bbb-login add-hook gnus-summary-mode-hook gnus-grouplens-mode gnus-setup-news nil level gnus-setup-news-hook gnus-start-draft-setup gnus-group-list-groups gnus-group-first-unread-group gnus-configure-windows group gnus-group-set-mode-line gnus-started-hook] 4)
  gnus-1(nil nil nil)
  gnus(nil)
  call-interactively(gnus)
  command-execute(gnus t)
  execute-extended-command(nil)
  call-interactively(execute-extended-command)



             reply	other threads:[~2000-11-05 18:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-05 18:59 Nick Papadonis [this message]
2000-11-05 20:00 ` Nevin Kapur
2000-11-06  8:59   ` Nick Papadonis
2000-11-06  9:49     ` Kai Großjohann
2000-11-06 10:08       ` Nick Papadonis
2000-11-06 10:55     ` Gnus FAQ bug report (was: Re: procmail/gnus problem?) Kai Großjohann
2000-11-06 17:00       ` Justin Sheehy
2000-11-12 11:24   ` procmail/gnus problem? Randal L. Schwartz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200011051859.NAA25338@sturgeon.coelacanth.com \
    --to=nick@sturgeon.coelacanth.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).