BTW: you can have Mailman use an SQL database for its config and membership database, so some folks just use the standard Mailman interface for building their membership database.
Ah, I like this tactic (sending an email) better for the reasons you mentioned. Can you point out some mailman docs/examples about using such a SQL database? Suppose I centralize the membership database on these Mailman tables can i still add some extra columns that would have meaning to my other uses but Mailman would just ignore? Is this not a wise idea to "pollute" the Mailman tables?
- SL -- TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational FAQ : http://trilug.org/faq/ TriLUG Member Services FAQ : http://members.trilug.org/services_faq/ TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc
