Gnus development mailing list
 help / color / mirror / Atom feed
From: Mark Thomas <swoon@bellatlantic.net>
Subject: Re: problem with gnus-no-server
Date: Tue, 06 Aug 2002 12:54:48 -0400	[thread overview]
Message-ID: <wf1ofcgndc3.fsf@svelte.home> (raw)
In-Reply-To: <wf1y9bkgele.fsf@svelte.home>


I've managed to work around the problem.

The maillist.debian.laptop entry in my ~/.newsrc.eld was:

> 	 ("maillist.debian.laptop" 2
> 	  ((1 . 6080))
> 	  ((dormant
> 	    (1 . 3)
> 	    (4376 . 4379))
> 	   (expire 3364 3374
> 		   (3761 . 3762)
> 		   (3765 . 3766)
> 		   3911 4473
> 		   (5189 . 5190)
> 		   5280 5283 5437 5474 5587 5589 5657 5713
> 		   (5723 . 5724)
> 		   (5728 . 5729)
> 		   5942 6001 6012)
> 	   (reply 1 4377 4381)
> 	   (tick 230 754 1380
> 		 (2093 . 2094)
> 		 3735 4014 4781
> 		 (4787 . 4788)
> 		 5467 5529 5968)
> 	   (seen
> 	    (1 . 6080))
> 	   (cache 1380))
> 	  "nnml:"
> 	  ((total-expire . t)
> 	   (expiry-wait . 28)
> 	   (to-list . "debian-laptop@lists.debian.org")
> 	   (subscribed . t)))

When I changed the
  "nnml:"
back to
  (nnml "")
I was able to use gnus-no-server.

It appears that all the new method-backend pairs are being written as
  "method:backend"
instead of
  (method "backend")

I supposed this is the New And Improved way?  What should my nnml
entries look like?  What about nndir entries, which currently look
like
  (nndir "e:/mthomas/mail/CMU/" (nndir-directory "e:/mthomas/mail/CMU"))

Cheers,

-Mark



  reply	other threads:[~2002-08-06 16:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-06 16:22 Mark Thomas
2002-08-06 16:54 ` Mark Thomas [this message]
2002-08-06 18:32   ` Paul Jarc

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=wf1ofcgndc3.fsf@svelte.home \
    --to=swoon@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).