I have a very general question to ask qmail-scanner users.
Most of these commercial AV outfits sell license PER DOMAIN on a mail
server that may contain hundreds of domains.
Using qmail-scanner to invoke the AV executables for every e-mail that
comes in, technically one could just use a single
On Sun, May 12, 2002 at 05:31:50PM -0700, chris wrote:
> Right, I DO want to use it. I just didn't want to have to create multiple
> instances of supervise for each one.. I guess I was hoping supervise could
> observe one "run" that contained multiple TCPSERVER and if any of them died,
> it woul
>
> well, you just got rid of the reason why you where using daemontools in
> the first place... if you don't want daemontools, don't use it.
Right, I DO want to use it. I just didn't want to have to create multiple
instances of supervise for each one.. I guess I was hoping supervise could
obse
On Fri, May 10, 2002 at 12:36:19PM -0400, Steven Faguy wrote:
> I've been looking at archives for the list for about 4 months but haven't
> found anything to help here.
You don't mention that you even installed Qmail-Scanner correctly. Did you
"./configure ..." or did you install manually? I'm su
In the qmail-scanner-queue.pl i have got the below
as follow:-
# ./configure --spooldir /var/spool/qmailscan
--qmaildir /var/qmail --bindir /var/qmail/bin --qmail-queue-binary
/var/qmail/bin/qmail-queue --admin root --domain --notify sender,admin,recips
--local-domains a.net,b.com,c.org --
On Sunday 12 May 2002 03:18, chris wrote:
> Yep, that works, sort of. It appears that the second instance (as in
> the example) isn't controllable via SVC -d /service/qmail-smtpd
> anymore. SVC -u /service/qmail-smtpd DOES cause the two instances to
> start up (by using the & detach correctly)
