Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: "A. Lucien Meyers" <nospam.look@replyto.please.because.this.is.invalid>
Subject: Re: emergency - cannot use gnus ;-(
Date: Fri, 12 Apr 2002 13:25:37 +0000 (UTC)	[thread overview]
Message-ID: <slrnabdo25.332.nospam.look@localhost.consult-meyers.com> (raw)
In-Reply-To: <a96gdq1hn6@enews4.newsguy.com>

* those who know me have no need of my name <not-a-real-address@usa.net>:
>  <slrnabdbmk.2vp.nospam.look@localhost.consult-meyers.com> divulged:
>  
>  >At start gnus tells me:
>  >
>  >nntp (news.isp.ch) open error: ''.  Continue? (y or n)
>  
>  your news server (news.isp.ch) isn't accepting connections.  try again
>  later.

Very much wish this were true but it isn't. Immediately after
this error messege from gnus I can exit emacs and use slrn to
access the same news server.  Immediately after exiting slrn can
load emacs and try to access the same mail server using gnus and
get the same error message displayed above.

Lucien
-- 
If you receive this by error, please delete it and inform the sender.
http://www.consult-meyers.com recommends email encryption using GnuPG.


       reply	other threads:[~2002-04-12 13:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <slrnabdbmk.2vp.nospam.look@localhost.consult-meyers.com>
     [not found] ` <a96gdq1hn6@enews4.newsguy.com>
2002-04-12 13:25   ` A. Lucien Meyers [this message]
     [not found]     ` <a98hm602cpg@enews2.newsguy.com>
     [not found]       ` <slrnabgkmg.e2a.nospam.look@localhost.consult-meyers.com>
     [not found]         ` <ly662vsczc.fsf@gfn.org>
     [not found]           ` <slrnabguic.g8p.nospam.look@localhost.consult-meyers.com>
     [not found]             ` <vaf4rifl7jj.fsf@lucy.cs.uni-dortmund.de>
     [not found]               ` <slrnabj825.ce3.nospam.look@localhost.consult-meyers.com>
     [not found]                 ` <vaf8z7qi7ng.fsf@lucy.cs.uni-dortmund.de>
     [not found]                   ` <slrnabl449.97g.nospam.look@localhost.consult-meyers.com>
2002-04-15 13:12                     ` Urban Engberg
     [not found]                       ` <a9f1js220au@enews1.newsguy.com>
2002-04-16  6:44                         ` Urban Engberg
2002-04-16 18:29                           ` A. Lucien Meyers
2002-04-17  3:08                             ` Bob Babcock
     [not found]                       ` <n7662si0yw.fsf@nnelinux.ccieurope.com>
     [not found]                         ` <87n0w0x1c3.fsf@nomad.consult-meyers.com>
2002-04-18 20:34                           ` Paul Jarc
     [not found]                             ` <87pu0vbpsf.fsf@landhaus.consult-meyers.com>
     [not found]                               ` <vaf4ri7319h.fsf@lucy.cs.uni-dortmund.de>
     [not found]                                 ` <841ydbl9wq.fsf@mindspring.com>
2002-04-20 16:20                                   ` Nicolas Kowalski
     [not found]                                 ` <877kn33058.fsf@nomad.consult-meyers.com>
2002-04-22 10:33                                   ` Kai Großjohann

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=slrnabdo25.332.nospam.look@localhost.consult-meyers.com \
    --to=nospam.look@replyto.please.because.this.is.invalid \
    --cc=a.l.meyers@consult-meyers.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).