- Message from Jared Hall -
Date: Fri, 23 Jul 2021 00:07:52 -0400
From: Jared Hall
Subject: CHAOS: v1.2.2: Of Documentation
To: users@spamassassin.apache.org
Simon Wilson wrote:
could you, please, finally, describe what does this module do,
here to the list and/or to t
Hi,
I know we are on the spamassassin mailing list, but another more radical
way to block those is directly in postfix with a header_check before
giving it to spamassassin
/^X-Spam-Flag: Yes/ REJECT Outscatter
/^X-(Spam|AES)-Category: (SPAM|PHISHING)/ REJECT Outscatter
But as a forewarning, th
We don't run Postfix here, but we can probably look for it elsewhere in
our stack instead.
Thanks to everyone that answered :)
On 23/07/2021 10.43, Laurent S. wrote:
Hi,
I know we are on the spamassassin mailing list, but another more radical
way to block those is directly in postfix with a
On 23/07/2021 18:01, Simon Wilson wrote:
- Message from Jared Hall -
Date: Fri, 23 Jul 2021 00:07:52 -0400
From: Jared Hall
Subject: CHAOS: v1.2.2: Of Documentation
To: users@spamassassin.apache.org
Simon Wilson wrote: could you, please, finally, describe what does this
module do
On Fri, Jul 23, 2021 at 08:16:56AM +0300, Henrik K wrote:
>
> > 2C) The initial release of CHAOS.pm did all kinds of scoring. One of the
> > knocks I have about SpamAssassin is that is does not maintain counts of
> > hits.
> > My complaints about this go all the way back to 2010. Counts and Am
On Fri, 2021-07-23 at 19:49 +1000, Noel Butler wrote:
> I've still yet to see a list post explaining what this thing does
> so no he has not answered all questions about it, the most common sense
> thing of all time is if you advertise your wares, you at least tell
> people WTF it does, you don't s
Hi Andrew
dig + trace leads to primary DNS Server:
spamassassin.org. 3600IN SOA ns2.pccc.com.
pmc.spamassassin.apache.org. 2021072305 7200 3600 604800 3600
as published in the SOA record.
BUT:
; <<>> DiG 9.11.5-P4-5.1+deb10u5-Debian <<>> ANY
updates.spamassassin.org @ns2.pcc
Let me take a look ASAP.
On Fri, Jul 23, 2021, 08:03 Benoît Panizzon wrote:
> Hi Andrew
>
> dig + trace leads to primary DNS Server:
>
> spamassassin.org. 3600IN SOA ns2.pccc.com.
> pmc.spamassassin.apache.org. 2021072305 7200 3600 604800 3600
>
> as published in the SOA recor
TL;DR: Everything looks good to me.
I think you are just doing DNS calls that are either invalid or look like
you are trying to do discovery through recursion. For example:
dig -t txt 0.0.4.updates.spamassassin.org @ns2.pccc.com
;; ANSWER SECTION:
0.0.4.updates.spamassassin.org. 3600 IN CNAME
3
On 23.07.21 13:58, Andrew Colin Kissa wrote:
updates.spamassassin.org is not resolving, tested with various
DNS systems. Can the admins please check ?
updates.spamassassin.org gives no data, because it's empty:
% dig any updates.spamassassin.org @b.auth-ns.sonic.net.
; <<>> DiG 9.11.5-P4-5.1+
> updates.spamassassin.org gives no data, because it's empty:
ouch, my bad. I would have expected NXDOMAIN for non existing, but just
an 'empty' reply, because it exists but does not contain any RR is
not what I expected. Then I tripped over the recursion warning.
--
Mit freundlichen Grüssen
-B
On 2021-07-23 14:35, Kevin A. McGrail wrote:
TL;DR: Everything looks good to me.
+1
I think you are just doing DNS calls that are either invalid or look
like you are trying to do discovery through recursion. For example:
dig -t txt 0.0.4.updates.spamassassin.org [5] @ns2.pccc.com [2]
why
Martin,
most MTA should have some filter capabilities. Maybe not all MTA have
same powerful and efficient ways to perform such checks as postfix has ;-)
iirc something like this should work for exim
acl_smtp_data = check_message
check_message:
deny message = 'Outscatter detected'
regex = ^X-S
Yea, it was more meant as a "we don't use postfix specifically". My
fallback idea was also to do the filtering on the MTA we do use, instead
of in SpamAssassin.
That was just bad phrasing on my part. Sorry about that :)
On 23/07/2021 16.51, jahli...@gmx.ch wrote:
Martin,
most MTA should ha
On 2021-07-23 06:54, Benny Pedersen wrote:
On 2021-07-23 14:35, Kevin A. McGrail wrote:
TL;DR: Everything looks good to me.
+1
I think you are just doing DNS calls that are either invalid or look
like you are trying to do discovery through recursion. For example:
dig -t txt 0.0.4.updates.s
Hi
updates.spamassassin.org is not resolving, tested with various
DNS systems. Can the admins please check ?
Kind Regards,
Andrew
My bad, actually thought updates.spamassassin.org was one of the mirrored-by
urls but it is sa-update.spamassassin.org
> On 23 Jul 2021, at 14:35, Kevin A. McGrail wrote:
>
> TL;DR: Everything looks good to me.
17 matches
Mail list logo
