Topic: Spam Filter Server-Manager Panel

[ntblade]

Hi everyone,
I've installed the Spam Filter Server-Manager Panel contrib from Swerts-Knudsen.dk and it works just fine.  Thanks!
However, sending email is pretty slow when the real time black lists are enabled.
Would I be right in saying that smtp-front qmail checks to see that my own address is blacklisted before sending mail?
If so, is it possible to disable this behaviour?
I only need spam checking for incomming mail.

Many thanks for any help.

[charlien]

I noticed the same thing. Have you found a fix for this, other than turning it off?

[ntblade]

I noticed the same thing. Have you found a fix for this, other than turning it off?

Hi, Thanks for your reply.
No I haven't as I wasn't sure if this was the cause of slow email sending.
Have you tried turning it off?

[compdoc]

What Sensitivity is the panel set to? Mine gets kinda weird if its set higher than Medium(.

Shouldnt have to, but try adding your domain to the white list:

*yourdomain.com

What RBL's do you use? I started out using three of them, but found sbl-xbl.spamhaus.org works fine by itself...

[jgates]

Hi,

FYI and as feedback (+'ve) I have always had my domain in the whitelist in that format and only use spamhaus.

Sending and delivery of mail has been quite acceptable.

John

[ntblade]

Adding my domain(s) to the whitelist fixed it.  Thanks!
N

[gzartman]

Hi,

FYI and as feedback (+'ve) I have always had my domain in the whitelist in that format and only use spamhaus.
John

This doesnt' make any sense.  You don't need to do this because SA doesn't even scan mail sent from you to other users on your sys.  Have a look at tcp.smtp in /etc/tcprules.

[brianr]

I spoke to Jesper about this, and he said that he had not been able to disable Spamassassin scanning outgoing email, unless Clamav was also disabled for outgoing mail (on his Calamv panel).  I can confirm that this is the case.

However i'll try enabling clamav on outgoing and putting my domain in the whitelist, and report back if that solves the problem.

[gzartman]

I spoke to Jesper about this, and he said that he had not been able to disable Spamassassin scanning outgoing email, unless Clamav was also disabled for outgoing mail

This may be a design flaw in his contrib as this is possible using the externalinterfacesfilter and internalinterfacesfilter SMTP configuration dbase keys.  On my sys, I have the external filter set to SA and the internal to my AV scanner.  Note from the following email header from a message sent to myself did not get scanned by SA:

Return-Path: <greg@leiinc.com>
Delivered-To: greg@server.leiinc.com
Received: (qmail 12230 invoked by alias); 7 Nov 2004 18:02:58 -0000
Delivered-To: alias-localdelivery-greg@leiinc.com
Received: (qmail 12227 invoked from network); 7 Nov 2004 18:02:58 -0000
Received: from 67-41-84-25.eugn.qwest.net (67.41.84.25)
  by server.leiinc.com (63.224.194.227) with ESMTP; 07 Nov 2004 18:02:58 -0000
Message-ID: <418E6482.5040705@leiinc.com>
Date: Sun, 07 Nov 2004 10:08:02 -0800
From: Greg Zartman <greg@leiinc.com>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To:  greg@leiinc.com
Subject: test
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

[mrjhb3]

Greg,

Could you post your output from:

/sbin/e-smith/db configuration show smtpfront-qmail
and what you have listed under the qmail section of  /etc/amavis-ng/amavis.conf (around line 152)
please?

I'd like to compare what you have set vs. what I currently have set to see if we can find a solution to this.

Thanks,

JB

[gzartman]

Following is my smtpfront-qmail dbase information.  I'm not using amavis, so can't send information with respect to this.

[root@server root]# /sbin/e-smith/db configuration show smtpfront-qmail
smtpfront-qmail=service
    ConcurrencyRemote=40
    ExternalInterfacesFilter=/var/qmail/bin/qmail-spamc
    Instances=40
    InternalInterfacesFilter=/var/qmail/bin/scanner
    Proxy=enabled
    RBLList=bl.spamcop.net:list.dsbl.org:sbl.spamhaus.org
    access=public
    authentication=disabled
    status=enabled

[idyll]

I run the SA option and if you wildcard your own domain you will be flooded with SPAM.

My system blocks hundreds of email with "guess" names addressed to my domain.

regards,

patrick

[gzartman]

I run the SA option and if you wildcard your own domain you will be flooded with SPAM.
My system blocks hundreds of email with "guess" names addressed to my domain.

I don't think we're speaking the same language here...  This isn't a whitelist issue, but an issue with when SA gets called to scan mail.  You should never put yourself in the SA whitelist or blacklist.  This defeats the purpose of what SA is doing.

Greg

[idyll]

Is there more than one whitelist? I was referring to the whitelist associated with incoming email filtered via SA.

I was responding to the two posts above indicating they had added their own domains to the "whitelist".

Were you addressing me or the two folks above?

?

patrick

[mrjhb3]

Following is my smtpfront-qmail dbase information.  I'm not using amavis, so can't send information with respect to this.

[root@server root]# /sbin/e-smith/db configuration show smtpfront-qmail
smtpfront-qmail=service
    ConcurrencyRemote=40
    ExternalInterfacesFilter=/var/qmail/bin/qmail-spamc
    Instances=40
    InternalInterfacesFilter=/var/qmail/bin/scanner
    Proxy=enabled
    RBLList=bl.spamcop.net:list.dsbl.org:sbl.spamhaus.org
    access=public
    authentication=disabled
    status=enabled

Thanks Greg,  what is /var/qmail/bin/scanner?  I don't have that on my system.  I am re-loading a test box now to confirm.  I don't know what I was thinking, but I thought amavis and clamav were part of the same package.  No, No, as I have learned.  I'll have to see what the differences are.

JB