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) but I can't "down" them... Well, it's better than
At 11/05/2002 11/05/2002 -0700, chris wrote:
>Hello list,
>
> I understand that a method of running "per-domain scanning" would be to
>use MX records to point to different IP's that are local to your single mail
>server running qmail-scanner. Then you would have separate instances of
>TCPSERV
Hello list,
I understand that a method of running "per-domain scanning" would be to
use MX records to point to different IP's that are local to your single mail
server running qmail-scanner. Then you would have separate instances of
TCPSERVER running that are listening to those IP's. In you
Hmm. The notification message by qmail-scanner w/ clamav support seems a
little bit busy.
At Sat, 11 May 2002 10:23:12 +0900,
Kazuhiko wrote:
> [sub-clamav.pl ]
(snip)
> &debug("clamav_scanner: $DD");
>
> if ($DD =~ /(.*) FOUND/) {
This line should be the following...
if ($DD =~ /:
On Saturday 11 May 2002 04:12, James Beam wrote:
> This is from a previus post:
>
> "Q-S will only notify the recips if it determines that the recipient is a
> local mailbox. Therefore make sure the your local domains are part of the
> local_domain_array in qmail-scanner-queue.pl. For example my
