Hi All,

 A couple ideas to add to the pile:

1. Add another option to add_members to disable subscription notifications to the owner of the list only for the duration of this add_members session. (to help with list admins getting deluged with subscription notices when they use add_members)

2. For lists with member_posting_only enabled and subscribe_policy set to require confirmation, subscribe the address that the user responds to the confirmation notice with instead of what they type in on the web page. Possibly even require a second confirmation. (will help with users who subscribe under an "aliased" address but actually post from another)

3. To help in sutuations where an unknown address subscribed to a list is forwarding all messages it receives from the list back to that list, setup a tracking feature that mails each address subscribed to a list with a unique number (perhaps in a diagnostic header?) and an explaination for the message. Then watch for one of those messages to come back through the list, catch it, extract the number, disable delivery for the address it was sent to, and notify the list admin. (A bit of an odd case, I know, but I had to do this manually on a list /w >50 subscribers recently due to a rogue subscriber...)

    				~ Rick ~

   -- .oooO "Man with closed Oooo. Rick C. Niess ( ) mouth gathers ( ) University of Southern Miss. \ ( no foot!" ) / resnet@usm.edu --\ )------------------(_/-------------------------------