Action Items
New
[AI] {Jill} will send a list of survey respondents to Jim.
[AI] {Paul} will begin developing a list of generic topics addressing spam and mailing list management software.

Carry Over
[AI] {Jill, Jim and John-Paul} will discuss what is needed to present models to a development group and have developers incorporate the models into their work.
[AI] {Jim} will solicit feedback about the models from the mailing list survey respondents.
[AI] {Jill} will compile a list of what survey respondents desire from mailing list software by the next meeting.
[AI] {John-Paul} will work to find someone interested in packaging and maintaining Sympa for Fedora Core.
[AI] {Jim} will inform the group via the list of updates to the domain model incorporating Sympa developers’ comments.
[AI] {Jim and John-Paul} will discuss local-interface preference storing of attributes. And, will send a brief summary of the discussion to the WG via the list.
[AI] {SteveO} will gain a better understanding of Sympa documentation and translation requests and coordinate follow up w/ Renee and Jill.
[AI] {Jill} will send the URL for the workshop presentation to the list when available.
[AI] {Jill}, {Jim} and {John-Paul} will discuss the object and domain model intersection points.
[AI] {Jill} will develop VO survey distribution list.
[AI] {Jill} will follow up with NSF and DOE for possible VO survey candidates.

Attendees
Jill Gemmill, UAB (Chair)
John-Paul Robinson, UAB
Jeff Eaton, Carnegie Mellon University
Jim Phelps, University of Wisconsin – Madison
Paul Russell, University of Notre Dame
Terrie Clark, Internet2
Lisa Hogeboom, Internet2
Steve Olshansky, Internet2

Discussion

Twenty institutions have responded to the mailing list survey. While most respondents are public institutions, a few are private institutions. Eighteen respondents manage email at the institutional level and two manage email at the department/school level. Most respondents reported that an LDAP interface is necessary. Some also perceive the usefulness of an AuthN/AuthZ architecture. Although almost half reported having only a minor understanding of the AuthN/AuthZ architecture. Several respondents sent copies of their university’s email mailing list policies. Some respondents are evaluating replacement mailing list manager software. A matrix identifying current features, desired features and features that need improvement will be sent to the survey respondents and to the WG.

The group will invite the Sympa developers to participate in a future call to discuss mailing list management software’s role in spam management. Some issues on this topic are not relaying spam through a mailing list management software; a mailing list not becoming a source of email address for spamers and a mailing list management software providing message audit capabilities. Should these spam issues be addressed in mailing list management software? Or, should spam be addressed in a universities email policies and subsequently email servers? Should mailing list management software filter messages? Or, should the end user’s email program filter messages? Some lists unknowingly provide email addresses to spamers either through a request or a web interface/html page. Should this group make spam management a requirement of mailing list management software? The WG will provide recommendations on these issues.

As the next regularly scheduled call would have fallen the week of the Christmas holiday, the next call is Wednesday, January 5, 2004 at 12:00PM ET.