|
Grex > Helpers > #147: Grex System Problems - Winter 2005/06 | |
|
| Author |
Message |
| 25 new of 260 responses total. |
marcvh
|
|
response 205 of 260:
|
Mar 5 00:46 UTC 2006 |
I'm (repeatedly) experiencing the "participation file truncated to
0 bytes so next time you bbs every item is brandnew" bug again. It's
become annoying enough that I've thrown some simple shell logic into
profile to automatically back up my participation files and warn me
about empties, so with luck this problem won't prove so annoying to me
personally.
|
mary
|
|
response 206 of 260:
|
Mar 5 03:26 UTC 2006 |
This response has been erased.
|
mary
|
|
response 207 of 260:
|
Mar 5 03:30 UTC 2006 |
I'm having the same problem.
|
mcnally
|
|
response 208 of 260:
|
Mar 5 03:35 UTC 2006 |
Hmmm.. I've never encountered it.
Out of curiosity, marc and mary (and denise if she's reading,
as I believe she's the first one to report this behavior..)
do you always use picospan or sometimes use backtalk or fronttalk?
|
marcvh
|
|
response 209 of 260:
|
Mar 5 04:43 UTC 2006 |
Always Picospan, never back or fronttalk. I haven't noticed any obvious
pattern to when it happens, e.g. breaking the TCP connection without
exiting Picospan, but of course you don't usually notice it until later.
|
mary
|
|
response 210 of 260:
|
Mar 5 12:11 UTC 2006 |
I use Backtalk rarely. Maybe this will help - before I log off I tend to
do a "check" and notice all conferences read. When I log back in is when
I find the problem. The last conference I usually touch is General. But
a week or so ago my last stop was indeed a conference with very little
activity, finance, maybe? When I logged back in it was that conference
that showed all items as new even though, on exit, it showed I was
caught-up. Odd.
|
other
|
|
response 211 of 260:
|
Mar 5 14:19 UTC 2006 |
I am still experiencing the weirdness in Pistachio (Backtalk) where it
reports a non-zero number of new responses but the "Read New" button
appears dimmed and is non-responsive. It only works if there are unread
items.
|
albaugh
|
|
response 212 of 260:
|
Mar 9 19:25 UTC 2006 |
When trying to telnet to grex just now:
Connected to cyberspace.org
telnetd: All network ports in use.
Connection closed by foreign host.
I thought there was supposed to be no need for a telnet queue any more!
(then posting entered via backtalk)
|
cross
|
|
response 213 of 260:
|
Mar 9 21:07 UTC 2006 |
This response has been erased.
|
keesan
|
|
response 214 of 260:
|
Mar 12 01:25 UTC 2006 |
I forwarded a recently bounced mail to webmaster@sorbs.net, which is where
collegeclub is getting its blacklist, and it bounced back to me with a message
about some virus. How does one communicate with that place? Do they accept
mail from anyone on their list?
|
other
|
|
response 215 of 260:
|
Mar 16 15:12 UTC 2006 |
Supplemental to resp:agora,4,211 above:
I am still experiencing the weirdness in Pistachio (Backtalk) where
it reports a non-zero number of new responses but the "Read New"
button appears dimmed and is non-responsive. It only works if there
are unread items.
This behavior went away when I unchecked the setting "view new items
before items with new responses" in the two conferences in which it was
happening. So, it appears that the script for that setting is broken.
|
keesan
|
|
response 216 of 260:
|
Mar 16 18:29 UTC 2006 |
AOL still has us blacklisted. I wrote their postmaster saying I was going to
advise all my friends to get a different ISP that did not blacklist places
where spam originated two months ago. Would it help if a lot of other
grexers also complained to AOL? I could not get through to the place that
was selling the blacklist to AOL.
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:
XXXX@aol.com
SMTP error from remote mail server after initial connection:
host mailin-01.mx.aol.com [64.12.137.249]: 554- (RTR:BL) http://postma
ster.info.aol.com/errors/554rtrbl.html
554- AOL does not accept e-mail transactions from IP addresses which
554- generate complaints or transmit unsolicited bulk e-mail.
554 Connecting IP: 216.86.77.194
|
nharmon
|
|
response 217 of 260:
|
Mar 16 18:34 UTC 2006 |
I do not care enough about e-mail on grex to try and contact AOL's
postmaster. I'm not sure there are many who do.
The only way to get AOL to unblock us is for their own customers to
throw a fit.
|
keesan
|
|
response 218 of 260:
|
Mar 16 19:01 UTC 2006 |
I will suggest that to two of their customers, writing from some place other
than grex.
|
keesan
|
|
response 219 of 260:
|
Mar 16 19:06 UTC 2006 |
I just wrote two of them suggesting that they ask AOL to use some other way
of blocking spam, and that they find a cheaper and better ISP for themselves.
|
rcurl
|
|
response 220 of 260:
|
Mar 16 20:57 UTC 2006 |
Some non-profit charitable organizations are supporting members of Grex and
use it for e-mail and web sites. They are being "screwed" by Grex not doing
anything about being blacklisted on AOL, where many of their members might
have their e-mail. Grex is probably going to lose this support.
|
keesan
|
|
response 221 of 260:
|
Mar 16 21:12 UTC 2006 |
Can the members with AOL email write AOL about this? Can you (from another
account) write to any members with AOL and explain the problem and suggest
they find a better ISP?
|
rcurl
|
|
response 222 of 260:
|
Mar 16 21:14 UTC 2006 |
There is no reason for the members with AOL to write AOL about this. It is
the organization's problem, not theirs, is their thinking.
|
tod
|
|
response 223 of 260:
|
Mar 16 21:41 UTC 2006 |
re #220
Some non-profit charitable organizations are supporting members of Grex and
use it for e-mail and web sites.
Those non-profits are ill advised and should switch to something more
professional like http://www.grassroots.org/
|
nharmon
|
|
response 224 of 260:
|
Mar 16 22:57 UTC 2006 |
IMHO, the executives of non-profit charities that are relying on Grex
for internet access are not being good stewards of their organizations.
|
mcnally
|
|
response 225 of 260:
|
Mar 16 23:50 UTC 2006 |
Sindi, the realities of the situation are that AOL has little cause
to worry about blocking mail from Grex, just as they don't care
about whether they should be accepting mail from the small ISP I
work for, which also gets blocked periodically. An unpleasant irony
of Grex's situation is that the phishers who started getting us
blacklisted were logging in to Grex from AOL. But it would be
irresponsible of us to block mail and telnet from all AOL users --
that's a huge portion of the internet and we'd make many people
unhappy. The asymmetry in size, however, means that AOL doesn't
have to use similar restraint in blocking Grex. Well over 99% of
AOL customers have never met and will never try to e-mail anyone
from Grex, so why should AOL care about unblocking us?
Unless / until their own customers start complaining about their
approach and threatening to take their business elsewhere AOL isn't
going to care. Otherwise the incentives are actually all on AOL's
side -- heck, if people get fed up about not being able to send
mail to their customers they figure that at least some percentage
of those people will switch to AOL just to get their mail through,
which hardly gives them a convincing reason to adopt a more reasonable
spam control policy.
It's not that the Grex staff don't care about the situation. But,
speaking solely for myself here, I've fought this battle before
(over and over, actually) and I'm tired of losing it. It's a
complicated, multi-sided problem, with technical, political, and
economic facets, each of which have their own sub-issues.
What you see when you're looking at the current situation is
essentially a very small part of the problem -- only the most recent
symptom and its immediate repercussions. Some of us who have been
dealing with the issue for years see this as just the latest battle
in a losing campaign.
That said, I think there are staff members who are more than willing
to take reasonable steps to, well, if not *solve* the problem, at
least make it a little better. But frankly most of the suggestions
which have been offered so far for what we should be doing come from
people with limited technical experience and clearly little or no
idea about what's practical to implement. Nobody on staff has the
time to write a whole new component of the mail system to solve this
week's problem, especially when history has shown us that next week
the inexhaustible supply of spammers will simply move on to some other
tactic and we'll be right back at square one..
|
rcurl
|
|
response 226 of 260:
|
Mar 16 23:54 UTC 2006 |
Re #224: it is common for non-profit charitable organizations to assist one
another. Are you suggesting, then, that Grex is also not a good steward for
itself?
|
nharmon
|
|
response 227 of 260:
|
Mar 17 00:07 UTC 2006 |
*yawn*
|
naftee
|
|
response 228 of 260:
|
Mar 17 00:29 UTC 2006 |
you're supposed to cover your mouth.
and get bitten.
|
keesan
|
|
response 229 of 260:
|
Mar 17 01:53 UTC 2006 |
Maybe I can ask all users of AOL that want to receive mail from me to set up
a grex mail account, where they can at least get incoming mail.
|