I've submitted a bug report to Ubuntu to get SA upgraded by the newest
version:
https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1856248
--
Chris
31.11972; -97.90167 (Elev. 1092 ft)
19:49:22 up 17 days, 10:32, 1 user, load average: 1.20, 0.91, 0.60
Description:Ubuntu 18.04.3
John Hardin wrote:
On Thu, 19 Dec 2019, Philipp Ewald wrote:
I have a solution with ClamAV for any image that is "not allowed". I
my case i create a md5sum from images i don't want to receive and but
them into hashtable.
This Hashtable place into /var/lib/clamav/NAME.hsb
On Thu, 19 Dec 2019, Philipp Ewald wrote:
I have a solution with ClamAV for any image that is "not allowed". I my case
i create a md5sum from images i don't want to receive and but them into
hashtable.
This Hashtable place into /var/lib/clamav/NAME.hsb
/var/lib/clamav/NAME.hsb looks like:
RW wrote:
On Thu, 19 Dec 2019 18:01:37 +0200
Henrik K wrote:
But if one wanted to check the forwarders after hermes.apache.org
properly, it would make more sense to add it in internal_networks,
since practicall it acts as the outer MX for you. That would enable
proper blacklist checks too.
I have a solution with ClamAV for any image that is "not allowed". I my case i
create a md5sum from images i don't want to receive and but them into hashtable.
This Hashtable place into /var/lib/clamav/NAME.hsb
/var/lib/clamav/NAME.hsb looks like:
On Thu, 2019-12-19 at 16:56 +, Chip M. wrote:
> On Wed, 18 Dec 2019, John Hardin wrote:
> > Can you post a spample
>
> This is a very interesting pattern that I've seen in a few (9) spams
> this week.
> Here's a spample (with only the To header MUNGED):
>
>
On 2019-12-19 17:45, Chip M. wrote:
Another interesting "tell" is its sloppy/ridiculous SPF:
v=spf1 ip4:52.0.0.0/8 ip4:3.0.0.0/8 ip4:54.0.0.0/8 ip4:107.0.0.0/8
ip4:18.0.0.0/8 ip4:34.0.0.0/8 -all
Perhaps they're anticipating Amazon gobbling up more IP space?!?
sadly spf supports
On Thu, 19 Dec 2019 18:01:37 +0200
Henrik K wrote:
> But if one wanted to check the forwarders after hermes.apache.org
> properly, it would make more sense to add it in internal_networks,
> since practicall it acts as the outer MX for you. That would enable
> proper blacklist checks too.
Mostly
On Wed, 18 Dec 2019, John Hardin wrote:
>Can you post a spample
This is a very interesting pattern that I've seen in a few (9) spams
this week.
Here's a spample (with only the To header MUNGED):
http://puffin.net/software/spam/samples/0062_snow_style_chaff_aws.txt
Lindsay, is that what
On 2019-12-19 17:04, Henrik K wrote:
Thinking about it more, atleast SPF would break, so not the best idea..
:-)
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
localhost.junc.eu
X-Spam-Status: No, score=-10.2, required=5.0, Autolearn=ham
autolearn_force=no,
On Thu, Dec 19, 2019 at 06:01:37PM +0200, Henrik K wrote:
>
> But if one wanted to check the forwarders after hermes.apache.org properly,
> it would make more sense to add it in internal_networks, since practicall it
> acts as the outer MX for you. That would enable proper blacklist checks
>
On Thu, Dec 19, 2019 at 02:58:42PM +, RW wrote:
>
> Because the trusted network outside of the internal network is trusted
> not to be under the control of a spammer, but you can't generally
> trust what's relayed through it. Forwarders that are listed at
> all usually have a low level of
Sorry, sent the previous one accidently.
On Thu, 19 Dec 2019 14:36:28 +
RW wrote:
> On Thu, 19 Dec 2019 12:49:34 +0200
> Henrik K wrote:
>
> > On Thu, Dec 19, 2019 at 12:43:43PM +0200, Henrik K wrote:
> > >
> > > hermes.apache.org[207.244.88.153] which sends these list mails is
> > >
Matus UHLAR - fantomas skrev den 2019-12-19 14:00:
not needed when you don't scan.
And I don't recommend training bayes with mailing list data, especially
not
SA-users.
how to tell spamassassin that maillist should not be bayes learned when
sa still is used on that maillists would be
On Thu, 19 Dec 2019 12:49:34 +0200
Henrik K wrote:
> On Thu, Dec 19, 2019 at 12:43:43PM +0200, Henrik K wrote:
> >
> > hermes.apache.org[207.244.88.153] which sends these list mails is
> > also supposed to hit RCVD_IN_DNSWL_HI, not _NONE? Your setup seems
> > wonky.
>
> Answering myself,
Matus UHLAR - fantomas skrev den 2019-12-19 12:03:
one of ways is not to pass mail received from 207.244.88.153 to
spamassassin.
On 19.12.19 12:30, Benny Pedersen wrote:
loosing bayes ham training
not needed when you don't scan.
And I don't recommend training bayes with mailing list data,
Matus UHLAR - fantomas skrev den 2019-12-19 12:03:
one of ways is not to pass mail received from 207.244.88.153 to
spamassassin.
loosing bayes ham training
On 19.12.19 16:34, Philip wrote:
Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by
fantomas.fantomas.sk (8.15.2/8.15.2/Debian-14~deb10u1) with SMTP id
xBJ3YZWh032473 for ; Thu, 19 Dec 2019 04:34:44 +0100
To: users@spamassassin.apache.org
From: Philip
Subject: White listing
Henrik K skrev den 2019-12-19 11:43:
or maybe just give more score negative to MAILING_LIST_MULTI ?
Normal SA rules will hit USER_IN_DEF_SPF_WL, due to "def_whitelist_auth
*@*.apache.org". Have you cleared these or why is it not hitting for
you?
if trusted_networks includes apache org ip
On Thu, Dec 19, 2019 at 12:43:43PM +0200, Henrik K wrote:
>
> hermes.apache.org[207.244.88.153] which sends these list mails is also
> supposed to hit RCVD_IN_DNSWL_HI, not _NONE? Your setup seems wonky.
Answering myself, DNSWL uses firsttrusted, so you've probably have some
Apache stuff in
On Thu, Dec 19, 2019 at 11:15:42AM +0100, Benny Pedersen wrote:
> Philip skrev den 2019-12-19 04:34:
> >How do I white list this mailing list for some reason all the messages
> >are now going to spam.
>
> X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on localhost.junc.eu
>
Riprendo quanto scritto nel suo messaggio del 18/12/2019...
> I've reported this to atleast Debian and Ubuntu along with a proper fix.
Many thanks!!!
--
dott. Marco Gaiarin GNUPG Key ID: 240A3D66
Associazione ``La Nostra Famiglia''
Philip skrev den 2019-12-19 04:34:
How do I white list this mailing list for some reason all the messages
are now going to spam.
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
localhost.junc.eu
X-Spam-Status: No, score=-2.0, required=5.0, Autolearn=no
autolearn_force=no,
23 matches
Mail list logo
