On Thu, September 19, 2013 15:11, Karsten Bräckelmann wrote:
A most informative and interesting explanation.
Thank you very much for taking the time to explain this to me. We presently
run SpamAssassin 3.3.1-2.el6 on our CentOS-6.4 based PostFix MX as part of the
Amavis-new package obtained fro
On 09/16/2013 10:12 AM, Kevin A. McGrail wrote:
Anyone have some examples of rules designed to catch words by content in
UTF-8 encoded messages? I'm doing some work on improving this.
Are you trying to match UTF-8 encoded messages as a stream of bytes, or
are you using normalize_charset? (An
On Thu, 2013-09-19 at 13:22 -0400, James B. Byrne wrote:
> Following some prior to SpamAssassin update these messages now appear in the
> maillog file:
The SA version you updated to (and from) would have been useful. Well,
given the warnings, it appears to be 3.3.x now.
> Sep 19 12:37:11.053 [27
Following some prior to SpamAssassin update these messages now appear in the
maillog file:
Sep 19 12:37:11.053 [27093] warn: netset: cannot include 127.0.0.1/32 as it
has already been included
Sep 19 12:37:11.056 [27093] info: config: failed to parse line, skipping, in
"/etc/mail/spamassassin/loca
On 09/19/2013 04:05 PM, Abhijeet Rastogi wrote:
I still don't understand why is there a need for A and NS lookups for
a domain. The only thing that's required is a A record query of
domain.com.dbl.rbl.locallyhostedrbl.com.
Maybe you haven't given it a second thought?.. maybe because there are
Hi David,
I was able to disable checks defined in /var/lib/spamassassin by
making their score 0 in local.cf. That reduced the CPU usage a lot.
Rate-limiting isn't an option because my inbound servers receive mails
at a very high rate that incoming queue starts to increase
indefinitely.
But, after
That'll only skip checks for a domain. Btw, I could finally do it by
commenting the lines that do the query in the perl module itself.
Thanks for the help.
I still don't understand why is there a need for A and NS lookups for
a domain. The only thing that's required is a A record query of
domain.c
qmail, as best I can recall, doesn't include rDNS in its Received:
headers (although there's probably a patch somewhere out there to do so)
So maybe that's the cause.
On Thu, 19 Sep 2013, Jason Haar wrote:
The fix is easy. The problem is you've chosen the defaults in the qmail
install: chan
On Thu, 19 Sep 2013, Jason Haar wrote:
qmail, as best I can recall, doesn't include rDNS in its Received:
headers (although there's probably a patch somewhere out there to do so)
So maybe that's the cause.
The fix is easy. The problem is you've chosen the defaults in the qmail
install: cha
On 18.09.13 15:36, Alfonso Alejandro Reyes Jiménez wrote:
>I would like to know what would be the best practice on the banner
>prompt, is it ok is we advice the antispam? I know the spammers wont
>care about it.
>
>I just want to know the best practice.
On Thursday 19 September 2013 at 10:58:09
On Thursday 19 September 2013 at 10:58:09, Matus UHLAR - fantomas wrote:
> On 18.09.13 15:36, Alfonso Alejandro Reyes Jiménez wrote:
> >I would like to know what would be the best practice on the banner
> >prompt, is it ok is we advice the antispam? I know the spammers wont
> >care about it.
> >
>
On 18.09.13 15:36, Alfonso Alejandro Reyes Jiménez wrote:
I would like to know what would be the best practice on the banner
prompt, is it ok is we advice the antispam? I know the spammers wont
care about it.
I just want to know the best practice.
I think some law in countries requires provi
12 matches
Mail list logo
