I've been moving a number of our lists to mailman in recent days and the question about additional data to qualify subscribers has come up.
Some listowners want to know who the subscriber is and what their role is. All are working the legal community and more sensitive about such matters than the normal human.
So the question is: can I or should I add new elements like username or userrole to config.db? What are the ramifications?
And can I define new variables in the needed programs of Mailman?
I must confess that I'm still using Mailman 1.1. Could I address my problem with Mailman 2.x?
Any insights are appreciated.
Joe Hewitt email@example.com
"JH" == Joe Hewitt firstname.lastname@example.org writes:
JH> So the question is: can I or should I add new elements like
JH> username or userrole to config.db? What are the
You could, sure. I think the hardest part will be keeping the various data structures in sync. It shouldn't affect Mailman's operation, except perhaps to slow it down (because there's more data to marshal and unmarshal).
JH> And can I define new variables in the needed programs of
Not sure what you're asking here. It's easy to add attributes to the list objects, and Mailman's infrastructure will just happily persist them.
JH> I must confess that I'm still using Mailman 1.1. Could I
JH> address my problem with Mailman 2.x?
Sure, why not?