From: Kurt H Maier <khm@sciops.net>
To: 9front@9front.org
Subject: Re: *****SPAM***** [9front] test
Date: Mon, 21 Sep 2020 13:33:00 -0700 [thread overview]
Message-ID: <20200921203300.GD43872@wopr> (raw)
In-Reply-To: <20200921195429.4839eb21@lenovo.sphairon.box>
Your SpamAssassin installation is misconfigured. Notes inline.
On Mon, Sep 21, 2020 at 07:54:29PM +0200, Stefan Hertenberger wrote:
> > 0.9 SPF_FAIL SPF: sender does not match SPF record
> > 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid
> > 0.1 DKIM_INVALID DKIM or DK signature exists, but is not valid
These are caused by invalid forwarding confix on a-b.xyz. It needs to
strip DKIM and rewrite From: if it's going to behave like this. I
suspect but cannot prove that migadu is adding the dkim signatures,
which then don't match the Fron: line since 9front.org mail doesn't come
from migadu.
> > 2.0 FROM_SUSPICIOUS_NTLD_FP From abused NTLD
> > 1.3 RDNS_NONE Delivered to internal network by a host with no rDNS
> > 0.5 FROM_SUSPICIOUS_NTLD From abused NTLD
These are the majority of the weights causing the SPAM tag from SA, and
again it's because xyz is a spam hotbed and also because a-b.xyz's IP
address reverse-resolves to ten.a-b.xyz.
If you intend to continue receiving 9front mail through this domain,
it's probably simplest to whitelist the domain in your sa-spamd rules,
since nothing sl does to the 9front list will change any of these
things. Dropping a 'whitelist_from_rcvd *@9front.org a-b.xyz' into your
spamassassin rules may do it, but without seeing the full headers of the
as-delivered message I can't be sure.
khm
next prev parent reply other threads:[~2020-09-21 20:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 15:40 test kvik
2020-09-21 17:12 ` [9front] test Stanley Lieber
2020-09-21 17:16 ` hiro
2020-09-21 17:36 ` ori
2020-09-21 17:40 ` Stanley Lieber
2020-09-21 17:51 ` ori
2020-09-21 17:59 ` ori
2020-09-21 18:27 ` Kurt H Maier
2020-09-21 17:58 ` hiro
2020-09-21 18:42 ` Stanley Lieber
2020-09-21 21:40 ` hiro
2020-09-21 22:20 ` hiro
2020-09-22 12:57 ` Ethan Gardener
2020-09-22 13:12 ` hiro
2020-09-21 17:59 ` Lyndon Nerenberg
2020-09-21 17:54 ` *****SPAM***** " Stefan Hertenberger
2020-09-21 20:33 ` Kurt H Maier [this message]
2020-09-21 21:23 ` kvik
2020-09-21 21:36 ` Kurt H Maier
2020-09-21 21:42 ` kvik
2020-09-21 21:57 ` Kurt H Maier
2020-09-21 22:32 ` kvik
2020-09-22 1:04 ` Kurt H Maier
2020-09-21 22:16 ` hiro
2020-09-22 18:57 ` Stefan Hertenberger
2020-09-22 19:38 ` Kurt H Maier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200921203300.GD43872@wopr \
--to=khm@sciops.net \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).