>>I'm having a terrible headache with someone
>>who copied my list to another machine and set up a duplicate mailing list.
>>Since Majordomo supports the `who list' command, it seems that we can
>>posture but aren't in a position to `forbid' anything.
>
>Make the list private--that'll prevent `who list' from disclosing the
>membership. Tell the jerk that copied your list immediately disable
>it. If he doesn't, raise a stink with his superiors.
This doesn't address the `forbid' issue. I think it is very useful for
most people to use the `who' command to get colleagues' Email addresses,
and I don't want to make this a private list.
As for the `jerk', he got there first! He is complaining to MY
superiors that his is the only true list and that I should be forced to
cooperate with him and do what he tells me to. It would be hilarious if
he weren't such a persistent nuisance.
Also, this business about closing down lists. Our biggest problem
(which I have raised on this list before) is that people who subscribed
on my system don't understand that they are getting mail from his
system, and they get upset because they send mail here and it doesn't
get them unsubscribed.
Bill
--
Bill Silvert at the Bedford Institute of Oceanography
P. O. Box 1006, Dartmouth, Nova Scotia, CANADA B2Y 4A2
InterNet Address: silvert@biome.bio.ns.ca
(the address bill@biome.bio.ns.ca is only for mailing lists)
Follow-Ups:
References:
|
|
