[Pymilter] Is project still active/alive?

[Stuart D. Gathman]

On Tue, 28 Nov 2006, John Villalovos wrote:

> 1.  The RPM should not be called milter-*.rpm.  That seems to generic,
> IMHO.  How about calling it pymilter-*.rpm or python-milter-*.rpm

That is on TODO.  The core milter modules will be split out as pymilter.
That will leave 'milter' as the anti-spam application.  I might even
rename that to bmsmilter.  Pyspf has already been split out for 0.8.7.

> 2.  Why does the RPM install executables and stuff in /var/log/milter/
> ?  That should be a "logfile" directory.  Shouldn't a lot of that
> stuff go in /usr/share/pymilter/, /usr/lib/python-milter/, or
> /var/lib/pymilter/ or something like that?

That is in TODO.  Originally, the bms.py script was a 'config' file.
Except now it is a full fledged application.  I have already moved other
config files to /etc/mail.  Next up is moving the application somewhere.
I am thinking /usr/lib/milter.

There are log files that are also kind of a config.  They track 
auto-whitelisted and auto-blacklisted senders, but can also be 
manually updated.

> 3. Maybe change the RPM from Red Hat focus to Fedora focus.  Are
> people still using Red Hat 9 or earlier?  Though a package for CentOS
> or RHEL might be useful.

I have to upgrade all our RedHat customer by January to CentOS,
and will no longer put rh73 binaries in downloads.  The source rpms
should compile everywhere (and should be fixed if they don't), and
I figured most people would do that.  More importantly than distro,
the binary RPM locks in a Python version.

-- 
	      Stuart D. Gathman <stuart at bmsi.com>
    Business Management Systems Inc.  Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.