Hi, it was with great pleasure that I realized that the successor of MailWatch was in python/django my language/web framework of choice. Thanks a lot!
Even if I didn't really have the time to test it on a real mail server the tests I made in my virtual env show it's a great improvement over MW. I'd be willing to provide the italian localization if no one else have volonteered. I have installed it on squeeze from a .deb package. Now some questions/notes: 0. the debian package seems to miss the python-celery dependancy that is required by settings.py. "pip install" followed by "dpkg-reconfigure baruwa" did the trick, no package is available so that configuration cannot work right away. 1. Is there any technical reason why mysql is the default choice? I'd really would prefere PostgreSQL and django should work with both. As far as the CustomFunctions I think it would be easy to create a pg version, I can provide it if needed. 2. I don't personally like to set host/user/pass in the CustomFunctions. I consider them as code provided by Baruwa and they should be upgradable without problems. They live in /etc/MailScanner, they are indeed a configuration for MailScanner, but they are code for baruwa... In addition, the same configuration is repeated 3 times in 3 files, that is not very DRY. I propose to set configuration in another file and read that file from these 3 files. Ideally that should be settings.py... I the MW configuration I used to have a db.ini file and both settings.py and *.pm read they're conf from that file. I can provide the patch if you like the idea. thanks again for baruwa sandro *:-) -- Sandro Dentella *:-) http://www.reteisi.org Soluzioni libere per le scuole http://sqlkit.argolinux.org SQLkit home page - PyGTK/python/sqlalchemy _______________________________________________ Baruwa mailing list [email protected] http://lists.baruwa.org/mailman/listinfo/baruwa
