Another option to consider is to do the same thing that was done to the ietf@xxxxxxxx list years ago: split it up into a list of important announcements that only the secretariat can post to, and a list of general interest items that anyone can post to. The announcement list would handle the schedule change announcements and would need to be extremely low traffic. The general interest list would let people post about local restaurants, local beer choices, etc. In addition to offering an optout for the subscriptions at registration time, have the list manager send a message to each person subscribed indicating what the list is about and *how to unsubscribe*. The lists *should* follow all the standards and good practices for mailing lists found in RFCs 2369, 2418, 2919 and 3934. Tony Hansen tony@xxxxxxx Dave Crocker wrote: > > 4. Having a per-meeting special list has an obvious and reasonable basis. > However it makes each meeting's list a special case for IETF administration and > for attendees. Possible variations to consider: _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf