Preston Holmes wrote: > It doesn't seem like it would be that hard to combine django- > extensions export_emails command with Mailmans sync_members script > inside a cron job or a URL triggered script. > > Usage: /usr/share/mailman/bin/sync_members [options] -f file listname
If users can manage their Mailman subscriptions via email or the MM web interface, using the sync_members approach, just like trying to "automate" MM by "calling" the email or web interface, can be problematic. How is Django supposed to know if a subscriber changed some options in MM, for example, setting themselves to NOMAIL? This approach is uni-directional and to make it bi-directional, you'll have to replicate a good part of the Mailman web front-end. The easiest and most robust approach is to have Mailman store its configuration in a SQL database instead of Python pickles and have Django connect to the same database. Another option, and one that I hadn't mentioned in my previous posts, is to forget about using Mailman and use something like Sympa, which offers a SOAP interface. It was designed from the outset to integrate with other things whereas Mailman is quite monolithic, which makes for a challenging integration. -- Regards, Clifford Ilkay Dinamis 1419-3266 Yonge St. Toronto, ON Canada M4N 3P6 <http://dinamis.com> +1 416-410-3326 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
