Hello Dave,
Wednesday, August 15, 2001, 3:26:24 PM, you wrote:
DS> =?ISO-8859-1?B?Qm9yaXMgS/ZzdGVy?= <[EMAIL PROTECTED]> wrote:
>>I would like to announce my QSP - a new approach in blocking SPAM with
>>SHA authentication, special support for mailinglists, individual
>>templates and so on.... Its
>>a very modular system comes with rich API to make your own extensions.
DS> Could explain how QSP differs from TMDA?
I dont know TMDA very good, but I will show you some benefits of QSP.
QSP does not require any changes in your qmail distribution. You dont
need to change your configuration or whatever, just run make and thats
all.
QSP has no -dated sender address for the moment. Its planned for later
releases but it has no priority for the moment.
If i send a message to the mailinglist, everyone can read it and
answer my text on the web. If someone sends a CC to me, its denied as
long as the sender is not authenticated.
QSP goes a radical way against spam.
QSP goes a complete other way as the other engines i know so far -
please dont understand me wrong, its possible that there are other and
better solutions out there but this is not important to me. I want to
protect myself against spam, I have developed my way of protection
against it and it works for me very good.
You can install QSP on a webserver for all your users or for a single
home-user, on your intranet and so on. The protection itself must by
enabled by the user himself, if the user want to use QSP.
Of course, a web-interface is planned, too. Everything comes step by
step.
You have individual templates for each automated reply if you like.
QSP does not check the usual things as MX-Check or DNS resolving, it
is not using RBL blacklists because it is +not+ required! This is a
very interesting aspect. If someone really wants such a feature, we
will code additional modules for it - but for now its not required.
Some people are writing a MX or DNS resolver - but... why? Its not
required in QSP and the protection works well believe me hehe.
QSP has a modular design and comes with development libraries for
python. You can write your own QSP extension in less than 5 minutes, i
will show coding examples in the next 1-2 weeks on my page.
QSP has a lot of planned modules for nearly every kind of protection
against spam.
The current status is:
SHA digest authentication complete. This means if you want to send a
message, you need to authenticate yourself against our SHA protected
authentication engine. I have a special list for my business partners
who do not need to authenticate (saves trouble and phonecalls).
Special anti-fake engine against spam from MAILINGLISTS is nearly
complete, too. Its currently in the testing phase and works well.
If you get spam from a mailinglist, you will wounder what happens if
you install QSP and if you have configured it. QSP does not need to
know the spammer to block him. My logs show that QSP blocked a lot of
mails last night so its expected to work, you all can test it yourself
when the source come out
QSP is a bigger project as the most other scripts and it is well
planned and designed. QSP is no product from a script kiddie, its
designed and developed by an experienced developer (me) hahaha. I am
using CVS and I have my own QA labs for testing.
I have my own company about software development so you can expect a more ore
less good quality solution (maybe not it the starting phase because of
a lot of debug code to have better control, but soon).
I dont want to say "hey use my QSP" - I only say if you dont like
spam, give QSP a try and take a look to our project homepage where you
can find a box with the current status of all modules. If there is a
discussion "what to use now", I would say "give QSP a try, it
costs nothing and comes with source"
Lets assume that QSP does let spam in. A spammer uses a new technique,
anything unexpected. If someone is a developer and if he analyzes this
kind of new spam, he can write a QSP module and publish it on my page
if he want.
Its possible to write extensions for QSP with at "free for non
commercial usage". This means if you want to earn money with writing
extensions for QSP, you are welcome. The conditions are: You have to
publish your module with source directly from the beginning. In your
license, ask the user to register if he likes your module, if not it�s
ok, too you have to accept it. This way is better than "we code for
nothing".
My english is not the best, sorry. The source is available in 09/2001,
the core code is working for a "try it" soon.
Take a look to the modules directory for QSP - at the moment, nearly
daily new modules are published to the QSP storyboard for development.
--
Best regards,
bk mailto:[EMAIL PROTECTED]
QSP: Qmail Spamkiller Project: http://www.x-itec.de/QSP
