Original Message From: Brandon MercerTo: [EMAIL PROTECTED]Sent:
Monday, September 22, 2003 11:52 AMSubject:
[Qmail-scanner-general]test_installation works real life
fails> Hello,> I'm starting all over
again. The machine setup is a slackware 9.0> box with a >
fresh install of perl
Well this is bordering on a qmail setup issue and not a qmail-scanner issue.
But let me throw in my .02 cents
Cream[DONut] wrote:
> bare with me for a second.
>
> I have set up a vpopmail domain called quarantine,
> I have added quarantine to /etc/hosts for 127.0.0.1,
Well that doesn't work the w
Cream[DONut] wrote:
> im banging my head against the wall here trying to figure out why my
> new server is giving this error on every mail being recived
>
> smtpd log:
> @40003f5d88e4297096d4 tcpserver: ok 3785 0:192.168.16.26:25
>> 192.168.16.242::2916
> @40003f5d88e43a7969ec X-Qmail-Scann
I upgraded to 1.20rc2 today in preparation to add sophie...and what do you
know, outside users could no longer send email. Of course since I left my
brain in bed on my pillow it took me ALL FREAKIN DAY to remove the QMAILSCAN
line out of /etc/tcp.smtp and test. Whadda-you-know.. outside users co
Boily Sylvain wrote:
> Hi,
>
> Does it possible to set a list of domain for qmail-scanner who want to
> scan or not ?
> Thanks
Start at http://www.no-way.org/software and see if that .diff doesn't help
you out.
Google is your friend. Search time .3 minutes, fifth google hit.
http://www.google.c
We run several mail servers on Slackware 8.1, which has perl 5.6.1, and
qmail and qmail-scanner 1.13. We've tried deploying 2 new servers with
Slackware 9.0 (perl 5.8.0) and either qmail-scanner 1.16 or 1.20rc1.
Neither works. We believe it is because the new Slackware/perl lacks
/usr/bin/suidperl
