|
Grex > Helpers > #130: Grex System Problems - Winter 2003/2004 |  |
|
| Author |
Message |
| 25 new of 384 responses total. |
gelinas
|
|
response 198 of 384:
| 
Jan 19 18:19 UTC 2004 |
Probably as good as any. What's up?
|
albaugh
|
|
response 199 of 384:
|
Jan 19 18:40 UTC 2004 |
For I'm not sure how long now an e-quaintance who receives my grex e-mail OK
cannot get mail delivered [back] to grex. After a few days, he gets a bounce
message that looks like this:
From: "Mail Delivery System" <MAILER-DAEMON@out1.mx.nwbl.wi.voyager.net>
To: <auser@voyager.net>
Sent: Monday, December 29, 2003 11:34 AM
Subject: Undelivered Mail Returned to Sender
This is the Postfix program at host out1.mx.nwbl.wi.voyager.net.
I'm sorry to have to inform you that the message returned
below could not be delivered to one or more destinations.
For further assistance, please send mail to <postmaster>
If you do so, please include this problem report.
You can delete your own text from the message returned below.
The Postfix program
<auser@cyberspace.org>: connect to
grex.cyberspace.org[216.93.104.34]: read timeout
I guess I should contact the voyager.net postmaster (my e-quaintance isn't
computer savvy), but before I do, does the grex "side" have anything to
comment on about this?
|
gelinas
|
|
response 200 of 384:
|
Jan 19 19:00 UTC 2004 |
My _guess_ is that they've set a too-short timeout on the voyager end.
Hmm...
Jan 18 02:08:37 grex sendmail[19179]: NOQUEUE: SYSERR: putoutmsg
(out0.mx.nwbl.wi.voyager.net): error on output channel
sending "220 ESMTP spoken here": Connection refused by
out0.mx.nwbl.wi.voyager.net
The connection is supposed to be something like:
} telnet grex.cyberspace.org 25
} Trying 216.93.104.34...
} Connected to grex.cyberspace.org.
} Escape character is '^]'.
} 220-grex.cyberspace.org Sendmail 8.6.13/8.6.12 ready at Mon, 19 Jan 2004
13:57:13 -0500
} 220 ESMTP spoken here
Apparently, that second line never gets back to out?.mx.nwbl.wi.voyager.net,
and then things time-out/break.
|
albaugh
|
|
response 201 of 384:
|
Jan 19 19:05 UTC 2004 |
Does that mean that the grex side is "failing" in some way, or is it still
something on the voyager.net side. BTW, I'm very sure that my e-quaintance
would have mentioned if this problem ocurred with other systems he tries to
send e-mail to...
|
gelinas
|
|
response 202 of 384:
|
Jan 19 19:21 UTC 2004 |
I think it's on the voyager side: grex is trying to send something, but
voyager doesn't accept it.
|
cross
|
|
response 203 of 384:
|
Jan 19 20:33 UTC 2004 |
This response has been erased.
|
eprom
|
|
response 204 of 384:
|
Jan 19 22:24 UTC 2004 |
why is procmail acting funny again?
|
gelinas
|
|
response 205 of 384:
|
Jan 19 23:07 UTC 2004 |
(Voyager is rejecting the message with a "time out" error, but grex is
reporting "connection refused.")
|
naftee
|
|
response 206 of 384:
|
Jan 20 01:23 UTC 2004 |
re 200 IS THAT THE MAILLOG?
|
eprom
|
|
response 207 of 384:
|
Jan 20 02:08 UTC 2004 |
re#204
nevermind...i'm stupid...I turned on the verbose logging and figured it out.
|
tsty
|
|
response 208 of 384:
|
Jan 22 06:58 UTC 2004 |
re 123 & 139 ... "valerie left grex" ????????? surely you jest!
|
slynne
|
|
response 209 of 384:
|
Jan 22 14:01 UTC 2004 |
Heh, I guess you havent logged on a while.
|
gull
|
|
response 210 of 384:
|
Jan 22 15:44 UTC 2004 |
Maybe he doesn't read coop.
|
happyboy
|
|
response 211 of 384:
|
Jan 22 17:13 UTC 2004 |
/pops some popcorn and puts "lost weekend" into the vcr
|
naftee
|
|
response 212 of 384:
|
Jan 24 04:19 UTC 2004 |
Use PicoSPAN, not backtalk, when mass-forgetting items.
|
lowclass
|
|
response 213 of 384:
|
Jan 24 05:53 UTC 2004 |
OKay, one simple and possibly pwertinent question. Is it possible to do a
Fixseen on an individual Item instead of a whole ocnference? Seems somebody
has offered us the benefit of Greek classics, and sooner or later, somebody
will come along and do it as some sort of implicit censorship to ANY item,
or author of an item they might dislike.
No, I do not know Scripting, much less C. maybe the idea is of use,
in any case.
|
bhoward
|
|
response 214 of 384:
|
Jan 24 12:21 UTC 2004 |
"fixseen" or "seen" defaults to all items in a conference if no arguments
are given.
If you want to "fix" a single item, just add that item's number as an
argument. For example:
fix 1
seen 1
fixseen 1
all do the same thing, and mark all the responses in item 1 as
already read.
|
keesan
|
|
response 215 of 384:
|
Jan 24 13:49 UTC 2004 |
Can you fixseen 63-end?
|
kip
|
|
response 216 of 384:
|
Jan 24 14:40 UTC 2004 |
Yes, you can, though I think if you want to just deal with agora and the
repeated items, fixseen 100-171 would do the trick.
|
ryan
|
|
response 217 of 384:
|
Jan 24 17:06 UTC 2004 |
This response has been erased.
|
naftee
|
|
response 218 of 384:
|
Jan 24 18:47 UTC 2004 |
By the way, there's still lots of space left on the device:
/dev/sd0e 706783 446639 189466 70% /bbs
|
naftee
|
|
response 219 of 384:
|
Jan 24 18:48 UTC 2004 |
re 216 'r 100-171 pass' also works.
Or just 'forget 100-171'. That too.
|
drew
|
|
response 220 of 384:
|
Jan 24 19:41 UTC 2004 |
Read since jan 23 pass in the conferences that I check regularly generated
a 2+ megabyte file. No way I can spare the connect time to download it, let
alone the real-time to read it. This is more than an order of magnitude
greater than the usual traffic. What's going on here?
|
naftee
|
|
response 221 of 384:
|
Jan 24 19:57 UTC 2004 |
What are you talking about?
|
rcurl
|
|
response 222 of 384:
|
Jan 24 22:44 UTC 2004 |
I just did a fixseen on agora. However it took many minutes to "fix" all
the damage.
|