Hello,
We're currently integrating all of our systems
with our billing server. I've already got the
RADIUS services integrated, and now I'm tackling
the email services.
We use qmailadmin to allow our virtual domain
customers to easily manage their own email
domains. Qmailadmin does this quite well, and
I must say that it's probably the only thing
that keeps me using a Qmail+Vpopmail solution
instead of a Postfix+something-else solution.
However, the one problem that I can't seem to
solve quickly is how to deal with the dot-qmail
issues. We use various spam filtering and virus
filtering techniques on our mail server. Virus
filtering is system wide, as a matter of policy,
because we don't think it's ethical to knowingly
store viruses on our disks. But spam filtering
is performed on a per mailbox basis. We do this
because every user has different needs, and we
don't want to lock our users into one particular
solution.
As the internet changes so quickly, we *know*
that our spam filtering techniques *must* be
flexible. We need to be able to combine various
filters, remove old ineffective filters, and
add new filters quickly and easily to compete.
Also, we would like to be able to allow the user
to tweak their own filtering setup from a web
interface or multiple web interfaces as needed,
but within the constraints of the services they
are paying for.
Sound complicated? Yeah, I think so too.
Anyway, the web interface can wait, but right
now I really need some way to add, remove, and
re-order filters on a per mailbox basis *without*
making qmailadmin choke to death on the strange
dot-qmail syntax. I figure the only way to do
this is to use some third party filtering
application, like maybe maildrop, as qmailadmin's
"spam command". This way filtering can be turned
on and off quickly, and qmailadmin understands
the dot-qmail syntax.
It would then be the job of maildrop or whatever
to find and apply any filters we set up for the
user from our integration scripts. The trick is
that the filters MUST:
1.) reside in the user's directory under the vpopmail
hierarchy. This way if the user is deleted by
vpopmail then the filters are cleanly deleted
as well. This also allows filters to be set up
and tweaked on a per user basis.
2.) be easy to create, modify, delete, and sort
by an external script or program (i.e. our
integration scripts AND a future user web
interface)
I have a few ideas, but I don't want to re-invent
the wheel. Has anyone done something similar to
this before? Can you give me tips? Or a howto?
Thanks!
--
Jesse Guardiani, Systems Administrator
WingNET Internet Services,
P.O. Box 2605 // Cleveland, TN 37320-2605
423-559-LINK (v) 423-559-5145 (f)
http://www.wingnet.net
