Re: Wish. . .

[Jason L Tibbitts III <tibbs @ hpc . uh . edu>]

>>>>> "MTA" == Mordechai T Abzug <morty@frakir.gsfc.nasa.gov> writes:

MTA> I was hoping to let users do unzubscribes, so that wouldn't be what i
MTA> was looking for.

OK, well, I was taking the easy way out.

MTA> What would work would be some mechanism that would treat a list as
MTA> four separate files:

Sounds complicated enough.  Not terribly difficult, though, depending on
just how much functionality you want.  Majordomo2 has sublists, which are
lists of addresses with a bit of added data but not much else.  These can
be named arbitrarily and used for various purposes.  You could also
override the subscription class mechanism, although that would probably be
less useful.

So you want a main list, consisting of all of the regular subscribers, a
sublist of people that came from the database, and a sublist of people to
be excluded if they show up on the database list.  Yeah, it could be done,
but it wouldn't be pretty and, well, unzubscribing from a list isn't
normally an option that you'd think would add you to a list.

It seems to me that the best place to handle this is in your database
instead of in Majordomo.  Why put those addresses in the list if they don't
want to be in the list?  It would probably be pretty easy to add a hook in
the unzubscribe routine to call some bit of code to modify the entry in
whatever database you're building the list from.

 - J<