Mailing List Archive

List <-> news hosed again?
Seems to me the c.l.py mailing list -> news gateway stopped cold again late
last week. Less sure of the other direction, but I do believe I've seen
some older recent articles on DejaNews that haven't come thru on the list.

If you're reading this and are not on the mailing list, share the secret
<wink>.

another-day-another-day-ly y'rs - tim
List <-> news hosed again? [ In reply to ]
Tim Peters wrote:

> Seems to me the c.l.py mailing list -> news gateway stopped cold
> again late last week. Less sure of the other direction, but I do
> believe I've seen some older recent articles on DejaNews that
> haven't come thru on the list.

> If you're reading this and are not on the mailing list, share the
> secret <wink>.

We're looking into this; uunet changed their configuration and we
neglected to make a matching change. It should be fixed now
(presuming this message shows up on the uunet side of things).

--Guido van Rossum (home page: http://www.python.org/~guido/)
List <-> news hosed again? [ In reply to ]
[Guido]
> We're looking into this; uunet changed their configuration and we
> neglected to make a matching change. It should be fixed now
> (presuming this message shows up on the uunet side of things).

Alas, don't think it worked -- DejaNews doesn't have your msg yet, nor my
ISP's (admittedly flaky) c.l.py feed. Appears to have stopped working very
early AM (EDT) on 18-June-99.

in-the-last-hideous-stage-of-ego-surfing-withdrawal<wink>-ly y'rs - tim
List <-> news hosed again? [ In reply to ]
> [Guido]
> > We're looking into this; uunet changed their configuration and we
> > neglected to make a matching change. It should be fixed now
> > (presuming this message shows up on the uunet side of things).
>
> Alas, don't think it worked -- DejaNews doesn't have your msg yet, nor my
> ISP's (admittedly flaky) c.l.py feed. Appears to have stopped working very
> early AM (EDT) on 18-June-99.

Indeed, it didn't work. Inspection of the logs indicates that the
uunet news software raises a "500 command not understood" error
whenever our news server tries to upload anything; this suggests a
serious version skew. I think we may have to install a different
version of the news software (unless it is caused by bogus data sent
in a corrupted article that somehow upsets the command parser).

> in-the-last-hideous-stage-of-ego-surfing-withdrawal<wink>-ly y'rs - tim

You could always post to python-list@cwi.nl, that gateway still works...

--Guido van Rossum (home page: http://www.python.org/~guido/)
List <-> news hosed again? [ In reply to ]
> > [Guido]
> > > We're looking into this; uunet changed their configuration and we
> > > neglected to make a matching change. It should be fixed now
> > > (presuming this message shows up on the uunet side of things).
[Tim]
> > Alas, don't think it worked -- DejaNews doesn't have your msg yet, nor my
> > ISP's (admittedly flaky) c.l.py feed. Appears to have stopped working very
> > early AM (EDT) on 18-June-99.
[me]
> Indeed, it didn't work. Inspection of the logs indicates that the
> uunet news software raises a "500 command not understood" error
> whenever our news server tries to upload anything; this suggests a
> serious version skew. I think we may have to install a different
> version of the news software (unless it is caused by bogus data sent
> in a corrupted article that somehow upsets the command parser).

Hello, it's me again, interim webmaster :-)

Just like the previous time we experienced this, the uunet news server
mysteriously started accepting our posts again after several
complaints, *without* further action on our side. Thanks to Tim for
alerting us to this problem and thanks to Roger & Stanley at CNRI for
taking action (even if that action only was a couple of mails and
phone calls to uunet :-).

--Guido van Rossum (home page: http://www.python.org/~guido/)