Documentation for config.db file?
Is there any documentation for the format of the config.db file?
Here's my situation. I've written a large database system for the membership information of an organization. Each member of the organization can login to the website with a password and edit his or her own member information (address, bio, password, etc). When a member makes a change to his email address, or when I add a new member, the program automatically makes a change to the majordomo list file, which is simply a text file with the email addresses in it. Well, now that I've switched the list to Mailman, I can no longer do this because I don't know how Mailman stores the subscriber info. I can easily modify a db file with PHP, I just need to know how the info in laid out in the file. Thanks. --Dan
Dionysos@Dionysia.org Daniel G. Delaney www.Dionysia.org/~dionysos/ PGP Public Key: /~dionysos/pgp.html
"DD" == Dan Delaney <Dionysos@Dionysia.org> writes:
DD> Is there any documentation for the format of the config.db
DD> file?It is a Python marshal containing a Python dictionary. The keys are taken from the attributes on the MailList object. Only the attributes which don't start with a leading underscore are saved.
DD> Here's my situation. I've written a large database system for
DD> the membership information of an organization. Each member of
DD> the organization can login to the website with a password and
DD> edit his or her own member information (address, bio,
DD> password, etc). When a member makes a change to his email
DD> address, or when I add a new member, the program automatically
DD> makes a change to the majordomo list file, which is simply a
DD> text file with the email addresses in it. Well, now that I've
DD> switched the list to Mailman, I can no longer do this because
DD> I don't know how Mailman stores the subscriber info. I can
DD> easily modify a db file with PHP, I just need to know how the
DD> info in laid out in the file.We do something very similar with the PSA membership. We use bin/sync_members to automate synchronizing the mailing list with our PSA members database, but depending on the information you've got, it's possible that bin/add_members or bin/remove_members might be more appropriate.
If not fit your bill exactly, remember that this stuff is very easy to code in Python. Take a look at the three scripts above for examples.
-Barry
participants (2)
-
Barry A. Warsaw -
Dan Delaney