Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: FAQ for gnu.emacs.gnus
Date: Mon, 23 Dec 2002 19:11:48 +0100	[thread overview]
Message-ID: <84y96gbo63.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m2u1h4psjx.fsf@localhost.localdomain>

Dave Bennett <dbennett@micoks.net> writes:

> kai.grossjohann@uni-duisburg.de (Kai =?iso-8859-1?q?Gro=DFjohann?=) writes:
>
>> I wonder what might be the problem...  Ah!  You're using Gnus 5.7, and
>> all the documentation on the web refers to 5.8 or higher, I guess.
>
> I didn't see anything that would indicate such a radical difference
> between 5.7 and 5.8 in the text of the documentation or FAQs.

Well, one difference between 5.7 and 5.8 is that the way to specify
how Gnus should fetch mail.

(setenv "MAILHOST" "your.pop.server")
(setq nnmail-spool-file "po:your.pop.account")

The above is for 5.7, I think.  I can't check and my memory is
faulty, so please don't beat me up if there is an error there.  Note
that the "po:" string is literal wereas your.pop.account and
your.pop.server are placeholders.

(setq mail-sources '((pop :server "your.pop.server"
                          :user "your.pop.account"
                          ;; May omit the password stanza.
                          :password "your.password")))

This ought to work with 5.8.

-- 
~/.signature is: umop ap!sdn    (Frank Nobis)


  parent reply	other threads:[~2002-12-23 18:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <687ke6jfbm.fsf@fencepost.gnu.org>
     [not found] ` <uisxp165f.fsf@hotpop.com>
2002-12-20 15:16   ` Dave Bennett
     [not found]     ` <84vg1o7c6e.fsf@lucy.cs.uni-dortmund.de>
     [not found]       ` <m2u1h4psjx.fsf@localhost.localdomain>
2002-12-23 18:11         ` Kai Großjohann [this message]
2002-12-24  3:53           ` (setenv "MAILHOST" "your.pop.server") (setq nnmail-spool-file "po:your.pop.account") Don Saklad
     [not found]             ` <8465tjg585.fsf@lucy.cs.uni-dortmund.de>
     [not found]               ` <y44u1h33dld.fsf@nestle.ai.mit.edu>
2002-12-26 12:42                 ` Kai Großjohann
     [not found]                   ` <y44lm2cdb89.fsf@nestle.ai.mit.edu>
     [not found]                     ` <84ptrok8zp.fsf@lucy.cs.uni-dortmund.de>
     [not found]                       ` <y441y44ziu9.fsf@nestle.ai.mit.edu>
2002-12-26 19:41                         ` Kai Großjohann
2002-12-26  3:52     ` FAQ for gnu.emacs.gnus Galen Boyer
     [not found]       ` <m2r8c4g504.fsf@localhost.localdomain>
     [not found]         ` <uisxg4v1u.fsf@standardandpoors.com>
     [not found]           ` <m2lm2cfppo.fsf@localhost.localdomain>
     [not found]             ` <844r90ihxp.fsf@lucy.cs.uni-dortmund.de>
2002-12-27  0:14               ` Robin S. Socha
     [not found] ` <871y4e5bu3.fsf@millingtons.org>
     [not found]   ` <87el8cws4d.fsf@computer.localdomain>
2002-12-20 18:24     ` Glyn Millington
2002-12-20 21:16       ` Martin Christensen
2002-12-22 20:07   ` urfaust

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=84y96gbo63.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@uni-duisburg.de \
    /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).