Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: Connectons to gmane suddenly are non-usable
Date: Thu, 16 Feb 2006 10:21:39 +0100	[thread overview]
Message-ID: <v9u0azr74s.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <loom.20060216T050904-848@post.gmane.org>

On Thu, Feb 16 2006, Harry Putnam wrote:

> Forward of help request from gmane.discuss
>
>   From: Harry Putnam <reader@jtan.com>
>   Subject: Connection to gmane suddenly no work
>   Newsgroups: gmane.discuss
>   Date: Wed, 15 Feb 2006 20:42:12 -0500
>   Message-ID: <7koe182i6j.fsf@callisto.jtan.com>

(I didn't see this in gmane.discuss yet.)

> Sometime yesterday my ability to connect to gmane stopped working on
> my home computer.  I'm posting this from a user account on jtan.com.
>
> My home IP is dynamic (changes are several days apart or longer but
> unpredictable).  IPs are Assigned from sbcglobal.net.  I've been
> connecting to gmane for about 2yrs from there.
[...]
> I thought it might tell something to telnet a post but after what
> seems like a normal connection I get this message on send:
>
>   441 You are not allowed to post to gmane.discuss
>
> Any ideas on how to debug this?

I doubt that this is a Gnus problem.  Is your IP (or IP range) listed
in <URL:http://gmane.org/denied.php>?  If you can't post to
gmane.discuss via NNTP, you might want to use the web interface
<http://news.gmane.org/gmane.discuss>. 

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/




  reply	other threads:[~2006-02-16  9:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-16  4:12 Harry Putnam
2006-02-16  9:21 ` Reiner Steib [this message]
2006-02-16 14:46   ` Harry Putnam
2006-02-16 16:05     ` Reiner Steib

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=v9u0azr74s.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.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).