|
|
| Author |
Message |
| 25 new of 293 responses total. |
hash
|
|
response 178 of 293:
| 
Aug 15 17:23 UTC 2002 |
is it 'set autosave' ? that doesn't seem to segfault.
I'm still trying to figure out why 'set save' segfaults but really no other
set commands or random strings do.
|
carson
|
|
response 179 of 293:
|
Aug 15 17:23 UTC 2002 |
(try "set autosave" instead.)
|
rksjr
|
|
response 180 of 293:
|
Aug 19 02:07 UTC 2002 |
A grexer sent e-mail to me last Wednesday, however, I did
not receive the "you have new mail" notice until today
(Sunday, sometime between 9:40 am and 7:19 pm), and I have
logged on five times since Wednesday. Does the "you have new
mail" notice appear only when e-mail arrives from outside of
the Grex system?
|
mdw
|
|
response 181 of 293:
|
Aug 19 23:30 UTC 2002 |
Nope. What is the timestamp in the "From" line at the start of this
message in your mailbox? That time should be the time that the mail was
actually delivered to your mailbox, which should be closely correlated
to when you see "You have new mail", if you're logged in and not idle.
That time should also be later than the timestamps in the "Received"
headers, which should track where mail was received by intermediate
points, which is typically where mail delivery delays happen.
|
rksjr
|
|
response 182 of 293:
|
Aug 20 21:24 UTC 2002 |
Re #181: Even viewing Pine's "Display of full headers", I
can see nothing in the "From:" line after "...@cyberspace.org>".
|
gelinas
|
|
response 183 of 293:
|
Aug 21 02:37 UTC 2002 |
It's not "From:" it's "From ". However, pine may be showing it as
"Return-Path:". In which case, look at the time in the next line, which
should begin "Received:". Comparing that time with the time in each of the
following "Received:" lines should show where the delay occurred.
|
carson
|
|
response 184 of 293:
|
Aug 21 02:37 UTC 2002 |
(nothing at the VERY top of the message? just above the "Return-Path:"
line? there's actually two "From:" lines in every e-mail, and the one to
which Marcus refers should be at the very beginning of the message.)
|
carson
|
|
response 185 of 293:
|
Aug 21 02:38 UTC 2002 |
(Joe slipped in, and is more correct than I in stating that it's a "From"
line and not a "From:" line. confused yet?) :)
|
rksjr
|
|
response 186 of 293:
|
Aug 21 03:34 UTC 2002 |
I think I've found the "from" line everyone is referring
to, i.e. the line which begins "Received: (from".
The following is the Pine "Display of full headers" for
the e-mail in consideration with the sender's name and
userid replaced by "[name]" and "[userid]" and the subject
line erased:
Received: (from [userid]@localhost) by grex.cyberspace.org
(8.6.13/8.6.12) id
LAA19150 for rksjr@grex.cyberspace.org; Wed, 14 Aug 2002
11:08:56 -0400
Date: Wed, 14 Aug 2002 11:08:56 -0400
From: [name] <[userid]@cyberspace.org>
Message-Id: <200208141508.LAA19150@grex.cyberspace.org>
To: rksjr@grex.cyberspace.org
Subject: [subject line erased]
|
carson
|
|
response 187 of 293:
|
Aug 21 04:06 UTC 2002 |
(wild. I just looked at some mail I have on Grex, and it *doesn't*
have a "From" line either.)
|
gelinas
|
|
response 188 of 293:
|
Aug 21 04:16 UTC 2002 |
No, that's not the line we were talking about, but if that is all there is,
it's interesting.
The "From " at the beginning of a line is part of th "mbox" format and is why
a similarly placed "from" in the text of a message is preceded by an angle
bracket: ">From this, we see . . ."
|
polytarp
|
|
response 189 of 293:
|
Aug 21 11:43 UTC 2002 |
joot:x:0:1:John Remmers' root:/a/r/e/remmers/joot:/bin/csh
That would appear to have a need-to-be-fixed-real-quick error.
|
davel
|
|
response 190 of 293:
|
Aug 21 12:43 UTC 2002 |
Eh? Looks fine to me. (Unless you're being a grammatical purist & saying
that it should be "Remmers's" instead of "Remmers'" - in which case I can only
say that that's not a "need-to-be-fixed-real-quick error".)
|
remmers
|
|
response 191 of 293:
|
Aug 21 13:19 UTC 2002 |
Guess it depends on which grammar books you believe. Note that
'zoot' apparently subscribes to the opposite philosophy.
|
polytarp
|
|
response 192 of 293:
|
Aug 21 13:22 UTC 2002 |
I'm just saying that you should fix it.
REAL QUICK
Thanks.
|
remmers
|
|
response 193 of 293:
|
Aug 21 13:43 UTC 2002 |
Nah.
|
jep
|
|
response 194 of 293:
|
Aug 21 17:21 UTC 2002 |
Backtalk is running exceedingly slowly right now. It took a few
minutes just to display this item, with it's 11 new responses.
|
dpc
|
|
response 195 of 293:
|
Aug 22 18:56 UTC 2002 |
Twice in the past week or so, e-mail to me from recycle.com
has been bounced by Grex. My correspondent sent me hard-
copy of the bounce message, which reads as follows:
The original message was received at Tue, 20 Augs 2002 16:47:07 -0400
(EDT) from [192.168.254.13}
----- The following addresses had permanent fatal errors -----
<dpc@cyberspace.org>
(reason: 553 <dpc@cyberspace.org>... One generation passeth away,
and anothergeneration cometh: but the earth abideth for ever."
----- Transcript of session follows -----
... while talking to grex.cyberspace.org.:
>>>RCPT To:<dpc@cyberspace.org>
<<< 553 <dpc@cyberspace.org>...One generation passeth away,
and another generation cometh: but the earth abideth for ever.
550 5.1.1 <dpc@cyberspace.org>... User unknown
End of message. So what does *that* mean?
|
mdw
|
|
response 196 of 293:
|
Aug 22 20:43 UTC 2002 |
It means that the machine that tried to talk to grex is so badly
configured it looks exactly like either a mail flooder or a spammer to
grex. In fact, while these aren't things grex checked, the IP address
from which the last such failure "dpc@cyberspace.org>...One" came has no
reverse arpa ip-address to name DNS entry, and does not accept incoming
mail connections. The particular check that was tripped here is an
important one for grex; this was tripped more than 2100 times in the
past 4 1/2 days, and at least at a quick glance at the logs, most of
those failures probably are spammers.
The kindest thing is probably to suggest that your correspondent find
another mail system run by people who know what they're doing.
Alternatively, you might ask your correspondent to ask his postmaster to
familiarize himself with RFC 2821, and especially section 3.6, and to
check his mail system with compliance to that section.
|
gull
|
|
response 197 of 293:
|
Aug 22 21:00 UTC 2002 |
By the way, I finally figured out why replies I sent to a mailing list
I'm on kept tripping off the spam filters. It turns out this mailing
list's software likes to insert spaces into Subject lines to make them
wrap prettily. Subject lines with lots of spaces seem to be one of the
things Grex filters on.
|
carson
|
|
response 198 of 293:
|
Aug 22 21:05 UTC 2002 |
(so does SpamAssassin, FWIW.)
|
mdw
|
|
response 199 of 293:
|
Aug 22 21:41 UTC 2002 |
What mailing list software was this?
|
gull
|
|
response 200 of 293:
|
Aug 23 12:57 UTC 2002 |
LISTSERV 1.8d
|
dpc
|
|
response 201 of 293:
|
Aug 23 20:42 UTC 2002 |
Thanx for the help on both the "cornerhealth.org" problem and
the "recycle.com" problem, folks. The answers make sense,
even to someone technologically-challenged like me!
|
tod
|
|
response 202 of 293:
|
Aug 23 20:49 UTC 2002 |
This response has been erased.
|
