From: Stefan Hertenberger <stefan@alarum.de>
To: 9front@9front.org
Subject: Re: *****SPAM***** [9front] test
Date: Mon, 21 Sep 2020 19:54:29 +0200 [thread overview]
Message-ID: <20200921195429.4839eb21@lenovo.sphairon.box> (raw)
In-Reply-To: <1E3083B627E4EDD1DF08AA61E95E4DA2@a-b.xyz>
Am Mon, 21 Sep 2020 17:40:20 +0200
schrieb kvik@a-b.xyz:
> Spam detection software, running on the system "vbsd.alarum.de",
> has identified this incoming email as possible spam. The original
> message has been attached to this so you can view it or label
> similar future email. If you have any questions, see
> postmaster for details.
>
> Content preview: I've changed DMARC policy to 'none'. Let's see if
> this mail still gets to spam. P.S. Sorry for spamming the list.
>
> Content analysis details: (5.1 points, 5.0 required)
>
> pts rule name description
> ---- ----------------------
> -------------------------------------------------- -0.0
> RCVD_IN_MSPIKE_H4 RBL: Very Good reputation (+4) [94.23.1.103
> listed in wl.mailspike.net] 0.0 URIBL_BLOCKED ADMINISTRATOR
> NOTICE: The query to URIBL was blocked. See
> http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
> for more information.
> [URIs: a-b.xyz]
> 0.2 HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level
> mail domains are different
> 0.0 T_PDS_OTHER_BAD_TLD Untrustworthy TLDs
> [URI: a-b.xyz (xyz)]
> 0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record
> 0.9 SPF_FAIL SPF: sender does not match SPF record
> (fail) [SPF failed: Please see
> http://www.openspf.org/Why?s=mfrom;id=9front-bounces%40ewsd.inri.net;ip=94.23.1.103;r=vbsd.alarum.de]
> 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 0.0 UNPARSEABLE_RELAY Informational:
> message has unparseable relay lines
> -0.0 RCVD_IN_MSPIKE_WL Mailspike good senders
> 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
>
>
hi,
SpamAssassin still thinks this is spam.
Stefan
next prev parent reply other threads:[~2020-09-21 17:54 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 ` Stefan Hertenberger [this message]
2020-09-21 20:33 ` *****SPAM***** " Kurt H Maier
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=20200921195429.4839eb21@lenovo.sphairon.box \
--to=stefan@alarum.de \
--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).