Hello pete,
On Fri, 11 Apr 2008, pete wrote:
so far spamdrop filtered 1200+ spam so far in ~2 months and miscategorized
only ~10 emails (it was only initially trained with 4k spam and 1k ham,
continous training would have improved the results even more).
Congratultions!
- the possibility to tell spamdrop with a -u (or any else) switch that
which user's mail is to be filtered, because on a virtual mail system every
maildir have the same uid:gid owner
It's possible with the latest nightly build, just like that, ie. you may
specify the given user by using the -u command line switch.
- the possibility to tell spamdrop that if a given user's queue
nonexistent, then create it. The best option would be the ability to
provide a template directory with the necessary files, which could be
copied+renamed when a new user arrives. By this, one could provide a
reasonable starter token base for newcomers.
Is it hard to implement these? Does it makes sense? :)
This is out of the scope of an anti-spam application, it should be handled
by maildrop, and I m pretty sure that maildrop creates the following
direcory structure:
Maildir/
cur/
new/
tmp/
You only have to add the following line to .mailfilter or to the global
maildroprc (note the trailing slash!):
to "Maildir/"
Adding a new user should include the following steps:
Let's say, your data directory is /var/lib/clapf/data/p/pete and
your queue directory is /var/lib/clapf/queue/p/pete.
Then you should:
1. Create these directories:
mkdir -p /var/lib/clapf/data/p/pete
mkdir -p /var/lib/clapf/queue/p/pete
2. Copy the default database file to /var/lib/clapf/data/p/pete
cp tokens.sdb /var/lib/clapf/data/p/pete
3. Fix the permissions:
chown -R pete /var/lib/clapf/data/p/pete
chown pete /var/lib/clapf/queue/p/pete
I hope it helped. If not, then let me know :-)
Digitally yours,
SJ.
--
