Re: Per-user config; spamassassin; performance

2006-07-26 Thread Skaag Argonius
Charlie Brady wrote: > As Gordon says, nearly all of this exists already in SME Server (earlier > versions of which were known as "the e-smith server and gateway"). The > only significant thing missing is virtual users - because SME server is > also a file server, all users are real linux users, wi

Re: Per-user config; spamassassin; performance

2006-07-26 Thread Charlie Brady
On Tue, 25 Jul 2006, Skaag Argonius wrote: The way I see it, all the software is already there. You have daemontools, qpsmtpd, qmail's various components, vpopmail with mysql, or the ldap version even, maildrop, spamassassin, a slew of really nice plugins, antivirus plugins, and you even have s

qpsmtpd based "distro" (was Re: Per-user config; spamassassin; performance)

2006-07-25 Thread Gordon Rowell
Skaag Argonius wrote: > [...] I'm going to start working on this. If anyone cares to join, you'r welcome ;-) Have you looked at the SME Server - www.smeserver.org / www.contribs.org It doesn't have everything on your list, but it has quite a few and is an excellent base for the rest. Thanks

Re: Per-user config; spamassassin; performance

2006-07-25 Thread John Peacock
Skaag Argonius wrote: I personally think that it is not until all relevant software is packaged in a single, well known "distribution", maybe even with some catchy name, that we can see all services integrated at a level where advanced options are made available. I could be wrong though! The way

Re: Per-user config; spamassassin; performance

2006-07-25 Thread Skaag Argonius
I personally think that it is not until all relevant software is packaged in a single, well known "distribution", maybe even with some catchy name, that we can see all services integrated at a level where advanced options are made available. I could be wrong though! The way I see it, all the softw

Per-user config; spamassassin; performance

2006-07-25 Thread Bryan Scott
Wow. Thank you all for the good discussion, which has led me to a different way of thinking how to handle this. I can see why there isn't a concensus on how to handle per-user configurations, namely because there doesn't seem to be a Right Way to do it (yet). The architecture of SMTP doesn't

RE: config/spamassassin

2004-02-17 Thread Chris Stone
file issue. Did you see my other message regarding what changes are needed to the dnsbl and rhsbl plugin files for per_user_config support? Chris -Original Message- From: Gavin Carr [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 17, 2004 2:52 PM To: [EMAIL PROTECTED] Subject: Re: c

Re: config/spamassassin

2004-02-17 Thread Gavin Carr
Hi Chris, On Tue, Feb 17, 2004 at 01:19:58PM -0700, Chris Stone wrote: > Think that I was thinking something incorrectly - there can only be the one > config/plugin file, right? And then, via config/plugin, I set > > spamassassin_spamc per_recipient 1 filter 0/1 Correct. > And then in the /conf

RE: config/spamassassin

2004-02-17 Thread Chris Stone
Seems there was discussion about that not being supported(?) Is that still an issue or has that been addressed? Chris -Original Message- From: Gavin Carr [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 17, 2004 5:16 AM To: [EMAIL PROTECTED] Cc: Chris Stone Subject: Re: config/spamassassi

RE: config/spamassassin

2004-02-17 Thread Chris Stone
Gavin, Great - will give it a work over today and see how it works here.. Chris -Original Message- From: Gavin Carr [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 17, 2004 5:16 AM To: [EMAIL PROTECTED] Cc: Chris Stone Subject: Re: config/spamassassin On Tue, Feb 17, 2004 at 07

RE: config/spamassassin

2004-02-17 Thread Chris Stone
amassassin plugin, if there's not call to $self->qp->config() in the plugin? That means no current support for per_user_config? Thanks! Chris -Original Message- From: Gavin Carr [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 17, 2004 1:21 AM To: [EMAIL PROTECTED] Cc: Chris Sto

Re: config/spamassassin

2004-02-17 Thread Gavin Carr
#x27;s all setup, but I am to the point now of trying to figure > > out how to now point spamassassin at the per-user/domain configs and/or what > > the heck this config/spamassassin file contains - seems to be my 'missing > > link' in this setup. > > Yeah

Re: config/spamassassin

2004-02-17 Thread Gavin Carr
t; out how to now point spamassassin at the per-user/domain configs and/or what > the heck this config/spamassassin file contains - seems to be my 'missing > link' in this setup. Yeah sorry, the docs are a bit misleading in that regard - to my knowledge there's no spamassassi

RE: config/spamassassin

2004-02-16 Thread Chris Stone
this config/spamassassin file contains - seems to be my 'missing link' in this setup. So, do you know what the config/spamassassin file can contain? Is it limited to options that would be passed to the spamassassin plugin via the config/plugins file, such as reject_threshold and munge_subjec

RE: config/spamassassin

2004-02-16 Thread Aran Deltac
Chris, I'm pretty sure there is no official "config/spamassassin" file or the means to use this. Are you, perchance, referring to this posting: http://www.nntp.perl.org/group/perl.qpsmtpd/860 If you are, be aware that this is discussing a specific plugin that loads configuratio

config/spamassassin

2004-02-16 Thread Chris Stone
Seen a few postings (and in related plugin docs) referring lightly to the config/spamassassin configuration file. Since there isn't real docs I've found on this and there's no such file in the qpsmtpd distribution, I'm confused as to the use of that file - what's in i