I run a several mailing lists and have come across a common problem in several
of them and I wonder if others see the same thing and how they deal with it.
This is longer than intended, but I'd like to get some info so please be kind.
First the question then details below...
Do some list maintainers NOT allow people to subscribe to their lists
because of where they are getting their email service? Basicly have people
gotten fed up with certain sites that they will just refuse to add people from
that site to their list because they have a pattern of failure shortly after
subscription.
-------
There is a site that puts message restrictions on it's users so that after
they have X messages in their inbox, it starts bouncing the messages back
to the bounce address in the header. For many things this should not be a
problem, but if you have an active list, or a user that subscribes to
just about everything he can get his hands on as many new users do, then
it's bounce city. I am not sure that the user even gets notification that
this he has exceeded his quota or by how much. It can also be a problem if the
user goes on vacation or travel or ... for a few days.
I have found a pattern for this site that about a month, or less, after the
user subscribes to the list there gets to be a rather high number of bounce
messages of the quota exceeded variety. Then I drop said user and rarely
do they re-subscribe only to be dropped again after the next flurry where they
disappear. After contacting their support group, they tell me that they
have a 100 message limit for their users and no way of increasing that,
even if the user is willing to pay more to get it.
Others problems include uucp sites that go through sites that send status
messages back if the uucp site hasn't been contactable in YY hours,
then YY+, YY++, ...
I am at the point that I may just go about modifying the subscription
process to check for a "bad-site" list, and if there is a host name
match send a kind rejection letter telling them to get service from
somewhere else. I don't want to be the only person that is doing this
so I am checking to see if any others have done such a thing and/or
what other solutions may be worked out. Having an exploder at the
remote site is a possibility for some, but how to tell people there is
an exploder at their local site without lots on manual checking...
--Gene
PS: The biggest offender for this problem is people at compuserve.com.
They have a 100 message limit.
|
|
