|
Grex > Helpers > #147: Grex System Problems - Winter 2005/06 | |
|
| Author |
Message |
| 25 new of 260 responses total. |
keesan
|
|
response 25 of 260:
| 
Dec 26 16:19 UTC 2005 |
I am setting my terminal in .cshrc with /usr/bin/tset, which exists.
I probably dialed in with linux on previous occasions and when I was asked
about whether my terminal is [VT100] I typed linux. If I type linux or vt100
things work, the problem was when I hit the enter key for the default vt100
and it was interpreted as 'tset' being my terminal. I can try ssh'ing with
DOS and hitting the Enter key some time. Maybe nobody else who dials in with
DOS also accesses grex with linux and set it up this way.
|
cross
|
|
response 26 of 260:
|
Dec 26 16:58 UTC 2005 |
This response has been erased.
|
aruba
|
|
response 27 of 260:
|
Dec 26 20:14 UTC 2005 |
Re #21: I care more about clarity than speed most of the time, too. But if
you pick one library of classes and call it "standard", you can't get away
form the fact that other people have different libraries that are more
standard to them than yours. So what's clear to you won't be to them.
If you have to drag a lot of libraries along with you whenever you port
something to someplace new, that's a drawback in my book. Sometimes it's
worth it, sometimes it's not.
|
keesan
|
|
response 28 of 260:
|
Dec 26 20:27 UTC 2005 |
Re 26, sometimes I telnet to grex after dialing with DOS.
Why 'dialup?vt100' ? Sometimes I dial with linux, or ssh with linux.
|
keesan
|
|
response 29 of 260:
|
Dec 26 20:32 UTC 2005 |
I changed the tset line in .login to
tset -m '?vt100'
and was able, while still online with ssh, to type login
and login name and password and Enter key and get logged in.
Probably as vt100 (which is sure to mess up lynx or pine since I am in linux).
|
cross
|
|
response 30 of 260:
|
Dec 27 04:47 UTC 2005 |
This response has been erased.
|
keesan
|
|
response 31 of 260:
|
Dec 27 20:06 UTC 2005 |
Grex seems to be on the RBL blacklist again - a mail just bounced back with
that explanation.
|
gull
|
|
response 32 of 260:
|
Dec 27 20:09 UTC 2005 |
Looks like it's listed in SORBS and in Spamcop.
|
keesan
|
|
response 33 of 260:
|
Dec 27 22:46 UTC 2005 |
I tried to email myself from grex to my freeshell account, which would not
accept mail from grex, which I find funny because recently freeshell was
also on the spamcop blacklist and I could not mail people from freeshell.
A good reason to have two shell accounts.
From Mailer-Daemon@cyberspace.org Tue Dec 27 16:55:35 2005
Date: Tue, 27 Dec 2005 16:55:35 -0500
From: Mail Delivery System <Mailer-Daemon@cyberspace.org>
To: keesan@cyberspace.org
Subject: Mail delivery failed: returning message to sender
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
keesan@freeshell.org
SMTP error from remote mail server after MAIL FROM:<keesan@cyberspace.org>:
host smtp.freeshell.org [192.94.73.21]: 550 5.7.1 216.86.77.194 blocked
according spamcop.net:see http://spamcop.net/bl
------ This is a copy of the message, including all the headers. ------
Return-path: <keesan@cyberspace.org>
Received: from keesan (helo=localhost)
by grex.cyberspace.org with local-esmtp (Exim 4.54)
id 1ErL4x-0004wq-PN
for keesan@freeshell.org; Tue, 27 Dec 2005 15:05:51 -0500
Date: Tue, 27 Dec 2005 15:05:51 -0500 (EST)
From: Sindi Keesan <keesan@grex.cyberspace.org>
To: keesan@freeshell.org
Subject: Mail delivery failed: returning message to sender (fwd)
Message-ID: <Pine.BSO.4.63.0512271505300.12571@grex.cyberspace.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Sender: Sindi Keesan <keesan@cyberspace.org>
Sindi Keesan
---------- Forwarded message ----------
Date: Tue, 27 Dec 2005 00:44:58 -0500
From: Mail Delivery System <Mailer-Daemon@cyberspace.org>
To: keesan@cyberspace.org
Subject: Mail delivery failed: returning message to sender
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
SMTP error from remote mail server after initial connection:
host mx08.gis.net [208.218.130.52]: 551 Connection refused. Your ip number
216.86.77.194 was found on the spamcopbl.gis.net RBL database
------ This is a copy of the message, including all the headers. ------
Return-path: <keesan@cyberspace.org>
Received: from keesan (helo=localhost)
by grex.cyberspace.org with local-esmtp (Exim 4.54)
id 1Er7dq-00010n-5o
for XXXXX; Tue, 27 Dec 2005 00:44:58 -0500
Date: Tue, 27 Dec 2005 00:44:58 -0500 (EST)
From: Sindi Keesan <keesan@grex.cyberspace.org>
To: XXXXX
Subject: Re: hi to all
In-Reply-To: <6.1.2.0.1.20051222223045.01a79540@pop.gis.net>
Message-ID: <Pine.BSO.4.63.0512270043031.11667@grex.cyberspace.org>
References: <Pine.BSO.4.63.0512222052160.29871@grex.cyberspace.org>
<6.1.2.0.1.20051222223045.01a79540@pop.gis.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Sender: Sindi Keesan <keesan@cyberspace.org>
|
bhoward
|
|
response 34 of 260:
|
Dec 28 00:36 UTC 2005 |
According to http://www.spamcop.net/w3m?action=checkblock&ip=216.86.77.194,
"in the past 302.3 days, it has been listed 17 times for a total
of 15.8 days"
|
keesan
|
|
response 35 of 260:
|
Dec 28 02:23 UTC 2005 |
So how long until grex can send outgoing mail to anyone using spamassassin,
one or two days? How do we get it unblocked? Can't they put grex and
freeshell on a whitelist somehow? I tried to forward returned mail from grex
to freeshell so I could send it from there, and freeshell is also blocking
grex mail. Do they block on the From line or on the ISP if they don't match?
I could try sending directly via an ISP when grex or freeshell are
blacklisted but I use freeshell as From and Replyto.
|
cross
|
|
response 36 of 260:
|
Dec 28 19:15 UTC 2005 |
This response has been erased.
|
tod
|
|
response 37 of 260:
|
Dec 28 19:30 UTC 2005 |
warning: libc.so.38.2: minor version >= 3 expected, using it anyway
PicoSpan T3.3a; designed by Marcus Watts
copyright 1984 NETI; licensed by Unicon Inc.
|
gull
|
|
response 38 of 260:
|
Dec 28 20:38 UTC 2005 |
Re resp:35: Being listed on Spamcop is not, in itself, enough to get
Spamassassin to reject mail in its default configuration. Spamassassin
works on a "point" system. Various signs of spam are worth certain
numbers of points. If the score exceeds a user-configurable threshold,
the mail is tagged as spam or rejected, depending on the configuration.
Being listed in bl.spamcop.net is only worth 1.8 points towards a
default spam threshold of 5.
Most likely, some clueless mail admin is blocking all mail from hosts
in Spamcop's blacklist. There are blacklists that I feel are accurate
enough to use that way, but bl.spamcop.net definitely isn't one of
them.
|
tod
|
|
response 39 of 260:
|
Dec 29 07:00 UTC 2005 |
!help
Welcome to Grex's help archives!
Please mail staff with additions, corrections, or if you need help!
Valerie Mates, valerie@cyberspace.org. Last update 6/5/97
Available documents are:
0. The new, excellent, Grex FAQ. Highly recommended!
1. An Introduction to Grex ("Take Me To Your Modem")
2. Frequently Asked Questions (more useful to non-Grexers)
3. An Introduction To The Picospan Conferencing ("BBS") System.
4. The Grex Declaration Of Principles
5. Who pays for Grex? Can I help? Does this cost money?
6. Phone list
7. Article about Grex that was in the People's Food Co-op Newsletter
8. Choose this option to get >>>help from a real live person<<<
9. Run the menu system.
A. Run Lynx.
B. Go to the conferences ("BBS").
C. Change settings on your account (password, name, shell, .plan file, etc)
D. Frequently Asked Questions about Grex's Party program
E. Frequently Asked Questions about Web Pages on Grex
Choose a number (or letter), or q to quit: 6
Last update: 4/25/2001 by scott@cyberspace.org
The phone numbers for Grex are:
phone number device modem type max. speed
------------------------------------------------
+1 734 761 3000 Groovy GVC 14.4 14400 bps
+1 734 761 5041 Groovy GVC 14.4 14400 bps
+1 734 761 3411 Groovy GVC 14.4 14400 bps
+1 734 761 3451 Groovy GVC 14.4 14400 bps
+1 734 761 3554 Groovy GVC 14.4 14400 bps
+1 734 761 3596 Groovy GVC 14.4 14400 bps
+1 734 761 2517 Groovy GVC 14.4 14400 bps
In normal operation, these numbers trunk hunt, so dialing (734) 761-3000
will give you the first available line out of these seven. All of the
modems connect to a terminal server which makes an 8-bit telnet connection
to Grex.
Press Enter to continue...
|
keesan
|
|
response 40 of 260:
|
Dec 29 16:52 UTC 2005 |
Tod, can you volunteer to write up a replacement page for some staff member
to post?
We are still blacklisted by spamcop.
Your ip number was found on spamcopgl.gis.net RBL database.
Freeshell is apparently using this same database by itself:
blocked according spamcop.net. See http://spamcop.net/bl.
It is at least three days now - if we ask nicely will spamcop take us off the
list?
|
tod
|
|
response 41 of 260:
|
Dec 29 16:55 UTC 2005 |
re #40
I don't know the numbers but I'd be glad to write a revision.
|
keesan
|
|
response 42 of 260:
|
Dec 29 17:00 UTC 2005 |
It is possible to get on the spamcop whitelist. Spamex (provides disposable
email addresses) just managed to do this. They are also supposed to take us
off the list when the spamming stops. Did it stop? Do they report to us
where exactly the spam is coming from?
|
mary
|
|
response 43 of 260:
|
Dec 29 19:06 UTC 2005 |
Maybe before we try to get off any spam lists we should make sure
we don't deserve to be blocked. Grex has a problem with a very few
users abusing our open mail. Staff knows about it and is trying to
fix it. It's not fixed yet.
|
gull
|
|
response 44 of 260:
|
Dec 29 19:41 UTC 2005 |
It's listed because Spamcop users have reported it as a source of spam
ten times in the last week. Unfortunately they don't show you what got
you listed, so it's a bit hard to say for sure who's causing the
problem.
|
bhoward
|
|
response 45 of 260:
|
Dec 30 01:31 UTC 2005 |
Dollars to donuts we were listed due to a recent spate of accounts
created from users on AOL's networks that sign-in and blast a ton
of spam before getting shut down.
These spammers seem to have automated the account creation process
and installation of their spamming scripts which makes me wonder
if it is time to implement some kind of CAPTCHA to protect against
scripted account creation and maybe also institute some sort of
fixed delay before allowing access to mail on grex.
I don't think we have the staffing to require formal validation
like we do for membership but even a simple requirement that an
account be older than say 10 days before it is allowed to send mail
might be enough of a barrier to slow the hit-and-run spammers.
Alternatively, maybe someone out there has implemented per-user
outbound mail quotas for exim (though I didn't find anything the
last time I checked).
|
cross
|
|
response 46 of 260:
|
Dec 30 01:40 UTC 2005 |
This response has been erased.
|
nharmon
|
|
response 47 of 260:
|
Dec 30 02:05 UTC 2005 |
Here is a thought... ASCII art. Generate some word in ASCII art that the
person creating the account has to recognize in order to complete
his/her registration. A text-based version of what yahoo does. :)
|
bhoward
|
|
response 48 of 260:
|
Dec 30 02:19 UTC 2005 |
Re#46 Personally, I want to preserve the ability for non-members to
send mail. I just would like to raise the barrier to make it difficult
for automated account creation.
Having new users placed into a trial group until they ran some sort
of CAPTCHA requesting access and having that access granted after a
48 hour delay would probably do the job. Adding a per-day outbound
mail quota on top of that would pretty much kill the problem without
unduly restricting new members.
|
aruba
|
|
response 49 of 260:
|
Dec 30 04:19 UTC 2005 |
Re #47: That's a cute idea!
|