nvdimm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Automatic Email Delivery Software" <postmaster-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>
To: linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org
Subject: Hello
Date: Wed, 13 Dec 2017 13:27:16 +0800	[thread overview]
Message-ID: <20171213052239.955A92214E334@ml01.01.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]

Spam detection software, running on the system "blaine.gmane.org",
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
@@CONTACT_ADDRESS@@ for details.

Content preview:  The original message was received at Wed, 13 Dec 2017 13:27:16
   +0800 from lists.01.org [98.192.225.35] ----- The following addresses had
   permanent fatal errors ----- <linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org> Linux-nvdimm mailing
   list Linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org https://lists.01.org/mailman/listinfo/linux-nvdimm
   [...] 

Content analysis details:   (5.7 points, 5.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
-0.0 RCVD_IN_DNSWL_NONE     RBL: Sender listed at http://www.dnswl.org/, no
                            trust
                            [198.145.21.10 listed in list.dnswl.org]
-0.6 RP_MATCHES_RCVD        Envelope sender domain matches handover relay domain
-0.5 BAYES_05               BODY: Bayes spam probability is 1 to 5%
                            [score: 0.0132]
 2.2 AXB_XMAILER_MIMEOLE_OL_024C2 No description available.
 2.6 MSOE_MID_WRONG_CASE    No description available.
 1.9 FORGED_MUA_OUTLOOK     Forged mail pretending to be from MS Outlook



[-- Attachment #2: original message before SpamAssassin --]
[-- Type: message/rfc822, Size: 2958 bytes --]

From: "Automatic Email Delivery Software" <postmaster-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>
To: linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org
Subject: Hello
Date: Wed, 13 Dec 2017 13:27:16 +0800
Message-ID: <20171213052239.955A92214E334-y27Ovi1pjclAfugRpC6u6w@public.gmane.org>

The original message was received at Wed, 13 Dec 2017 13:27:16 +0800
from lists.01.org [98.192.225.35]

----- The following addresses had permanent fatal errors -----
<linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>



_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org
https://lists.01.org/mailman/listinfo/linux-nvdimm


             reply	other threads:[~2017-12-13  5:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13  5:27 Automatic Email Delivery Software [this message]
2017-12-13  5:27 Hello Automatic Email Delivery Software
2018-03-12  3:19 hello Post Office
2018-09-02 14:14 Hello Bounced mail
2018-09-02 14:14 Hello Bounced mail
2018-09-06  7:30 Hello paulettejq-8Cmw1+NI3eNeoWH0uzbU5w
2019-06-20  1:35 Hello John M.
2019-06-20  4:04 Hello John M.
2019-06-20 14:30 Hello John M.
2019-06-20 16:05 Hello John M.
2019-12-19  7:09 hello Mr Lili
2020-08-21  1:41 HELLO WIDOW COLON DENISE.G, =?UTF-8?B?wqA=?=

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=20171213052239.955A92214E334@ml01.01.org \
    --to=postmaster-hn68rpc1hr1g9huczpvpmw@public.gmane.org \
    --cc=linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.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).