Re: [Assp-user] Next official stable release?

[Pascal N. <pa...@no...>]

William L. Thomson Jr. schreef:
> Now with all the issues and instability. Really starting to question the
> direction of the project a bit and it's rather sad. If I have to get
> involved I will, but perl is not really my thing. That being said I am
> doing my part downstream packaging and making it easy for others to
> install and use ASSP.
> 
> Unfortunately this volunteer tasks is becoming daunting. There are lots
> of unofficial release. Way to many for me to package due to how we have
> to patch things. 
> 
> Please help. I am not here looking to bitch or whine. I don't want to
> create extra work for you all, and surely don't want any more myself.


I want to kick-in in this.
As a system administrator myself maniging email for about 5.000 domains,
I'm running assp now since july 2004. It stopped millions of spam until
now, but it's getting harder and harder to manage.
We are running it on 6 servers, with various setup's. We have many
program's "circling" around assp, but with every release we must
reprogram all our scripts.
Some examples: users get (if they want) every night a list of mail which
was attended to them, but blocked by assp.
In the mail they can see why (Bayesian, BombRe, HELO, DNSBL, etc), and
they have a link to put the sending emailadres into the whitelist.
But with every release the logfile changes, even the way the name of the
old logfiles is changed.
Somethings are getting double up now, and it's hard to tell, where it
will end. Things like URIBL are already fit into our qmail-server, and
this program (in C) reacts faster then the assp-version (Perl).
However we scan mails now twice.
If users want antivirus (clamd), it is even scanned three times.
.... and yes, now clamd is available in perl, but there is no way to say
which one does and which one does not antivirus-filtering. (today we do
the filtering on a per email way in the dot-qmail-file).
The reason we wanted to got 1.3 is because or URIBL is still working
even if there adress is in the spamlover (so we want to bring this to
assp insteadof Qmail), AND 1.2.x was still crashing on big headers if
they where spamlovers or whitelisted adresses.

After 3 days of working, I went totally confused back to 1.2.x (first
the load problem in 1.3.3.1, then the email-interface problem in
1.3.3.3, and of course: changed logfiles again).

Starting at a pure Bayesian filter, it is now turned into a monster...
Maybe it's time to make another setup?
If you don't believe me: I Looked at version 1.0.12 and compared it with
1.3.3.3

1.0.12  had 81 variables in the config-file
1.3.3.3 has 525 variables....

1.0.12  had a assp.pl of 3622 lines
1.3.3.3 has a assp.pl of 12919 lines!

I personally think it's time for a manager (which I'm NOT). I see a
great future for assp, but also the possiblity to die because to complex.

Anyway Fritz (and all the others): the work already done is very very
very much appreciated by me and thousand of others, it would be a pitty
to see it all disappear because you created a monster.
I'm thinking in a way to split it all up, and using a configure/setup
sort of thing.
In that case maybe a fast leightweight smtp-server can be setup? By now
every mail (even so spam) starts up a qmail-smtpd process (which is
killed offcourse when it's spam), but this could decrease the load/cpu
of many mailservers around the world in a very very big way.


P.S.
Sorry for the language errors, English is not my native language.
P.P.S.
This mail is more for assp-test insteadoff assp-user, but it's started
here...

best regards,
Pascal