linux-nvdimm.lists.01.org archive mirror
 help / color / mirror / Atom feed
From: buildinfo-s4a7dU60G1rB75U6l8LB6Q@public.gmane.org
To: linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org
Subject: Message could not be delivered
Date: Wed, 19 Apr 2017 22:46:27 +0800	[thread overview]
Message-ID: <20170419144633.DAFCD21954075@ml01.01.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1633 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:  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:   (6.2 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.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.0 T_HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail
                            domains are different
-0.0 BAYES_20               BODY: Bayes spam probability is 5 to 20%
                            [score: 0.0557]
 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: 2526 bytes --]

From: buildinfo-s4a7dU60G1rB75U6l8LB6Q@public.gmane.org
To: linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org
Subject: Message could not be delivered
Date: Wed, 19 Apr 2017 22:46:27 +0800
Message-ID: <20170419144633.DAFCD21954075-y27Ovi1pjclAfugRpC6u6w@public.gmane.org>

Message could not be delivered

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


             reply	other threads:[~2017-04-19 14:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-19 14:46 buildinfo-s4a7dU60G1rB75U6l8LB6Q [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-09-03  2:14 Message could not be delivered Automatic Email Delivery Software
2019-09-03  2:14 Automatic Email Delivery Software
2019-04-26  3:38 Automatic Email Delivery Software
2019-04-25  3:46 Bounced mail
2019-04-18  4:01 Returned mail
2019-04-04 11:26 MESSAGE COULD NOT BE DELIVERED michael-k-KJX8L1YACloTKYOLMXNBRxrm3jAUxWOA
2018-05-11  6:55 Automatic Email Delivery Software
2018-04-26  3:06 Message could not be delivered Mail Administrator
2018-04-26  3:06 Mail Administrator
2018-03-26  3:53 Post Office
2018-03-26  2:46 Mail Delivery Subsystem
2018-03-26  2:46 Mail Delivery Subsystem
2018-03-08  3:27 The Post Office
2018-03-08  3:27 The Post Office
2018-02-07 13:08 MESSAGE COULD NOT BE DELIVERED MAILER-DAEMON
2018-02-07 13:08 MAILER-DAEMON
2017-12-09  4:47 Message could not be delivered Mail Delivery Subsystem
2017-12-09  4:47 Mail Delivery Subsystem
2017-04-19 14:46 buildinfo
2017-04-04  4:41 Bounced mail
2017-04-04  4:41 Bounced mail
2016-09-07  6:49 Mail Administrator
2016-09-07  6:49 Mail Administrator

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=20170419144633.DAFCD21954075@ml01.01.org \
    --to=buildinfo-s4a7du60g1rb75u6l8lb6q@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).