From: "Mail Administrator" <MAILER-DAEMON-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>
To: linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org
Subject: (unknown)
Subject:
Date: Thu, 8 Sep 2016 10:46:00 +0530 [thread overview]
Message-ID: <20160908051654.87ABD1A1F49@ml01.01.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1805 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: Your message could not be delivered Linux-nvdimm mailing list
Linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org https://lists.01.org/mailman/listinfo/linux-nvdimm
[...]
Content analysis details: (7.1 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
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: 01.org]
0.8 RCVD_IN_SORBS_WEB RBL: SORBS: sender is an abusable web server
[103.204.166.162 listed in dnsbl.sorbs.net]
-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.1 RCVD_IN_SBL RBL: Received via a relay in Spamhaus SBL
[103.204.166.162 listed in zen.spamhaus.org]
-0.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain
-0.0 BAYES_20 BODY: Bayes spam probability is 5 to 20%
[score: 0.1942]
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: 2518 bytes --]
From: "Mail Administrator" <MAILER-DAEMON-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>
To: linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org
Subject:
Date: Thu, 8 Sep 2016 10:46:00 +0530
Message-ID: <20160908051654.87ABD1A1F49-y27Ovi1pjclAfugRpC6u6w@public.gmane.org>
Your message could not be delivered
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next reply other threads:[~2016-09-08 5:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 5:16 Mail Administrator [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-05-16 3:48 (unknown) Mail Delivery Subsystem
2019-04-04 5:56 (unknown) Mail Delivery Subsystem
2019-03-29 0:36 (unknown) 邀请函
2019-03-04 3:42 (unknown) Automatic Email Delivery Software
2019-03-01 3:34 (unknown) Automatic Email Delivery Software
2019-02-28 3:36 (unknown) Post Office
2018-05-25 3:26 (unknown), Bounced mail
2018-03-23 3:05 (unknown), Mail Delivery Subsystem
2018-02-08 14:40 (unknown), Automatic Email Delivery Software
2017-12-01 2:56 (unknown), Post Office
2017-11-13 3:13 (unknown), Bounced mail
2017-09-21 7:47 (unknown), MAILER-DAEMON
2017-07-18 4:50 (unknown), ying.huang-ral2JQCrhuEAvxtiuMwx3w
2017-06-29 12:20 (unknown), The Post Office
2016-08-09 9:13 (unknown) 关淼官
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=20160908051654.87ABD1A1F49@ml01.01.org \
--to=mailer-daemon-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).