How about this:
Use the same mailing list. The secretariat marks important messages as
important via the header flag customarily used for this purpose.
Set the mailing list to strip out important/urgent flag on messages from anyone
else.
This means that my existing email config still works and I don't have to mess
with it which would be rather painful given that I have email pagers and other
stuff connected through it.
-----Original Message-----
From: Tony Hansen [mailto:tony(_at_)att(_dot_)com]
Sent: Wednesday, July 12, 2006 8:08 AM
To: Ray Pelletier
Cc: ietf(_at_)ietf(_dot_)org
Subject: Re: The IETF 66 Attendees Alias
Another option to consider is to do the same thing that was
done to the ietf(_at_)ietf(_dot_)org 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(_at_)att(_dot_)com
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 mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf