feature reminder: no unsubscribe
I am setting up some more course mail lists and I remembered to check on our testbed box for a feature that a bunch of people requested in the past: that a mail list have a setting that subscribers cannot remove themselves without admin approval. This was sought for situations (like a class) where you don't want people to be able to opt out.
I did not find this in 2b1, is it implemented? Maybe just as something to drop into the config file instead of through the web? If not, is there a chance that it can get into the 2.0 code? Thanks much.
--chris
/////\\\\\/////\\\\
Christopher G. Kolar
Director, Department of Instructional Technology
Aurora University, Aurora, Illinois
ckolar@admin.aurora.edu -- www.aurora.edu/~ckolar
[PGP Public Key ID: 0xC6492C72]
On Thu, Apr 20, 2000 at 11:42:19AM -0500, Christopher Kolar wrote:
I am setting up some more course mail lists and I remembered to check on our testbed box for a feature that a bunch of people requested in the past: that a mail list have a setting that subscribers cannot remove themselves without admin approval. This was sought for situations (like a class) where you don't want people to be able to opt out.
I did not find this in 2b1, is it implemented? Maybe just as something to drop into the config file instead of through the web? If not, is there a chance that it can get into the 2.0 code? Thanks much.
I posted a patch to the CVS tree that adds exactly that feature, a couple of months ago. I think I'm the only one that uses it, though ;) (And the version i posted had a couple of bugs, too.) I can extract a new patch from my devel tree, if you are interested, but i doubt it'll be added to mailman 2.0 (no new features in betas ;)
I've been using it without much trouble, though it generates some confusion with the subscribers, occasionally.
-- Thomas Wouters <thomas@xs4all.net>
Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
"TW" == Thomas Wouters <thomas@xs4all.net> writes:
TW> I posted a patch to the CVS tree that adds exactly that
TW> feature, a couple of months ago. I think I'm the only one that
TW> uses it, though ;) (And the version i posted had a couple of
TW> bugs, too.) I can extract a new patch from my devel tree, if
TW> you are interested, but i doubt it'll be added to mailman 2.0
TW> (no new features in betas ;)Would someone volunteer to put together a list of unofficial patches and hacks? I don't currently have the time, unfortunately. We could probably host them at SourceForge (if I can figure out how to change http://mailman.sourceforge.net :)
If yo're interested and have the time, email me.
-Barry
On Thu, Apr 20, 2000 at 10:37:14PM -0400, Barry A. Warsaw wrote:
TW> I posted a patch to the CVS tree that adds exactly that TW> feature, a couple of months ago. I think I'm the only one that TW> uses it, though ;) (And the version i posted had a couple of TW> bugs, too.) I can extract a new patch from my devel tree, if TW> you are interested, but i doubt it'll be added to mailman 2.0 TW> (no new features in betas ;)Would someone volunteer to put together a list of unofficial patches and hacks? I don't currently have the time, unfortunately. We could probably host them at SourceForge (if I can figure out how to change http://mailman.sourceforge.net :)
is that a job-opening for a mailman sourceforge webmaster? ;)
anyway, I was thinking that since you can use things like php on sourceforge, we could create a simple system where you can submit a patch with comments and then have everybody vote for it... cause I have a lot of patches/hacks/ideas I can offer, but I know not all of them could be interesting for everbody...
Ricardo.
--
On Thu, Apr 20, 2000 at 10:37:14PM -0400, Barry A. Warsaw wrote:
Would someone volunteer to put together a list of unofficial patches and hacks? I don't currently have the time, unfortunately. We could probably host them at SourceForge (if I can figure out how to change http://mailman.sourceforge.net :)
If yo're interested and have the time, email me.
Unless the number of unofficial patches suddenly booms, i'd have the time, and i'm certainly interested ;) I also have currently 2, later today 3 'unofficial' patches lying around, plus some minor fixes that haven't made it into 2.0 yet, so there's definately an element of self-interest here ;)
(The patches are:
unsubscriptions (optionally) requiring approval like subscriptions
using a local file for poster_list (the list of email addresses that can post) instead of having to enter them by hand / using the 'file upload' option. I need this currently because we have several lists that are restricted to exactly the same subset of addresses, and i dont want to maintain a remote file and upload it to all lists every time it changes, mostly because there's 10 people 'in charge' of the list, and our subscribees can create their own email aliasses and *frequently* change their posting alias :P
(I'm actually waiting for the userdb stuff to go in, to add 'aliases' to the options page, so people can go and maintain it themselves. Probably with a change to the admin pages too, so that you can approve a held posting and immediately add the email address to a known subscriber ;)
- And later today, after I test it some more on an actual mailman installation, a new LockFile.py, that's more civil and more efficient with locking.
The minor fixes are mailman eating the 'From ' line of messages that went through approval (which means they dont show up as seperate messages, in the archive), and the 'From ' lines in the 'downloadable archives' having the wrong format, rendering the archives all but useless. (i have a python script somewhere that fixes old archives too ;)
PS: Barry, i couldn't find a good excuse to post something to the python-list, to see if the timeout problem pops up again, but i'm hoping this list exhibits the same behaviour ;-P
-- Thomas Wouters <thomas@xs4all.net>
Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
participants (4)
-
Barry A. Warsaw -
Christopher Kolar -
Ricardo Kustner -
Thomas Wouters