Gnus development mailing list
 help / color / mirror / Atom feed
From: Nick Papadonis <nick@coelacanth.com>
Cc: Nevin Kapur <nkapur@bellatlantic.net>, ding@gnus.org
Subject: Re: procmail/gnus problem?
Date: 06 Nov 2000 05:08:48 -0500	[thread overview]
Message-ID: <m366m1wgy7.fsf@turing.dynodns.net> (raw)
In-Reply-To: <vafitq1topg.fsf@lucy.cs.uni-dortmund.de>

Off www.gnus.org (Official Version) :
http://www.ccs.neu.edu/software/contrib/gnus/

I also looked at the info FAQ and it doesn't include section 4.8.

Looks like the one with gnus dist is incomplete or the 'official'
version on the web May-22-00 needs an update.

>>>>> "Kai" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:

    Kai> On 06 Nov 2000, Nick Papadonis wrote:
    >> This brings up the question, why does the FAQ say to insert the
    >> following in the startup file? : (setq
    >> gnus-secondary-select-methods '((nnml "")) nnmail-spool-file
    >> 'procmail nnmail-procmail-directory "~/incoming/"
    >> nnmail-delete-incoming t )

    Kai> This was correct until Gnus 5.7.  Sometime in the 5.8
    Kai> development cycle, mail-sources.el was introduced.  Maybe the
    Kai> FAQ is out of date?

    Kai> Where did you find the FAQ?  I just looked in the current
    Kai> version in the Gnus info file, but didn't find anything.

    Kai> kai -- The arms should be held in a natural and unaffected
    Kai> way and never be conspicuous. -- Revised Technique of Latin
    Kai> American Dancing


-- 

.. Nick Papadonis



  reply	other threads:[~2000-11-06 10:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-05 18:59 Nick Papadonis
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 [this message]
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=m366m1wgy7.fsf@turing.dynodns.net \
    --to=nick@coelacanth.com \
    --cc=ding@gnus.org \
    --cc=nkapur@bellatlantic.net \
    /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).