You are not logged in. Login Now
 0-24   25-49   50-74   75-99   100-123      
 
Author Message
25 new of 123 responses total.
gelinas
response 50 of 123: Mark Unseen   May 9 01:10 UTC 2001

The text of SMTP error messages isn't really useful; although some
suggestions are made in RFC 821, they are also stated to be just
suggestions: the numbers are the information.

The receiving SMTP implementation sends the error; any similarity with
something that Marcus might write is purely coincidental.

5xx errors are "permanent"; that's why the message is rejected.  Contact
your correspondent by other means to ask, "What's up?"
scg
response 51 of 123: Mark Unseen   May 9 02:50 UTC 2001

Do all the mailers on Grex run sendmail directly to send the mail?  If they
send mail by connecting to localhost on port 25, Grex error messages could
be put in.

(for that matter, if they run sendmail directly, sendmail still could stick
in an error message, although probably not in that format).
senna
response 52 of 123: Mark Unseen   May 9 23:11 UTC 2001

I'm getting regular disconnects from telnet.  It's rather frustrating
bdh3
response 53 of 123: Mark Unseen   May 11 06:56 UTC 2001

Switch to linux.
cmcgee
response 54 of 123: Mark Unseen   May 12 00:04 UTC 2001

Twice today I have dialed in to Grex, gotten the "few minutes"
announcement, and then waited over 90 seconds for a login prompt.  Usually
it takes less than 5 seconds to get that prompt.  
cmcgee
response 55 of 123: Mark Unseen   May 12 02:24 UTC 2001

Er, I mean the "Welcome to Grex!  It may take a few seconds to connect."
announcement.  Still taking 60+ seconds to get login prompt.
aruba
response 56 of 123: Mark Unseen   May 12 02:58 UTC 2001

I've had the same experience.  Seems like the terminal server is having some
kind of problem.
blaise
response 57 of 123: Mark Unseen   May 12 03:14 UTC 2001

Re #54-#56: Last night it took over three minutes to get a prompt; when I then
did "uptime" I saw a current load of around 72.  Nothing showed up in ps -a
that looked problematic.
twinkie
response 58 of 123: Mark Unseen   May 12 07:43 UTC 2001

I noticed this strange message when I logged in just now:

TwinkieNet-=>ssh twinkie@cyberspace.org
Warning: Server lies about size of server public key: actual size is 767 bits
vs. announced 768.
Warning: This may be due to an old implementation of ssh.

Nothing earth-shattering, but I found it a bit interesting.

scg
response 59 of 123: Mark Unseen   May 12 09:26 UTC 2001

It's not the terminal server.  Grex's named isn't running.  Somebody who knows
the root password (I've forgotten it) should fix that.
eeyore
response 60 of 123: Mark Unseen   May 12 12:01 UTC 2001

I gave up on dialin last night, and this morning it was pretty slow too. 
Backtalk was incredibly slow last night, too.
scott
response 61 of 123: Mark Unseen   May 12 12:03 UTC 2001

Named has been restarted.  Things should work better now.
tpryan
response 62 of 123: Mark Unseen   May 12 13:33 UTC 2001

        Thnak you, I was also getting that delay.
ea
response 63 of 123: Mark Unseen   May 12 14:33 UTC 2001

I was having problems with backtalk last night (like it was giving me 
messages "Unable to find the server www.cyberspace.org") but it seems to 
be working fine now.
scott
response 64 of 123: Mark Unseen   May 12 15:16 UTC 2001

There's some weirdness going on over at Verio, such that I can't connect to
Grex over the Internet (right now I'm dialed in).  A traceroute shows what
looks like a routing loop.
carson
response 65 of 123: Mark Unseen   May 12 17:14 UTC 2001

(an attempt to connect from m-net.nether.net a couple of minutes ago
showed it looking for Grex's *old* IP address, 152.160.30.1.   huh?!)

(I connected using the direct [and correct] IP address.)
twinkie
response 66 of 123: Mark Unseen   May 12 17:21 UTC 2001

My computer has stopped accusing Grex of telling lies now :)

carson
response 67 of 123: Mark Unseen   May 12 19:41 UTC 2001

(more weirdness:  grex.org isn't resolving, but cyberspace.org seems
to work just fine.)
scg
response 68 of 123: Mark Unseen   May 12 19:50 UTC 2001

The named that got started up again last night or this morning was a very old
version of named, reading from a different config file than the current
version, and serving up a very old copy of the grex.org domain.  I found the
piece of paper I had the Grex root password written on, and restarted the
right one.  The secondary servers have now picked up the correct information.
It may take a day for the rest of the name servers around the Net to pick the
right information back up.
killbot
response 69 of 123: Mark Unseen   May 12 20:01 UTC 2001

can any one tell me what the server is talk
what 
tsty
response 70 of 123: Mark Unseen   May 13 16:51 UTC 2001

just foudn out about the 'user'   uce. great. question though, is
anything 'done' with an automagic-b0t, or is there pern/ppl intervention?
tsty
response 71 of 123: Mark Unseen   May 13 16:53 UTC 2001

i ask expecially since a week ago was my first use of uce and last night
a regular conversationalist told me his mail to me was bouncing - and my
mail queue is only about 70%. 
russ
response 72 of 123: Mark Unseen   May 14 12:47 UTC 2001

!mesg y
mesg: Unable to find your tty (ttyu6) in utmp file
ryan
response 73 of 123: Mark Unseen   May 18 19:03 UTC 2001

This response has been erased.

tpryan
response 74 of 123: Mark Unseen   May 18 21:23 UTC 2001

        ttyu6 seems to be the bugger in a lot of these problems,
including one I had a way back.
 0-24   25-49   50-74   75-99   100-123      
Response Not Possible: You are Not Logged In
 

- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss