From: "The Post Office" <postmaster-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>
To: linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org
Subject: test
Date: Sat, 27 Aug 2016 12:24:16 +0530 [thread overview]
Message-ID: <20160827065509.E8E451A1E61@ml01.01.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1651 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 Sat, 27 Aug 2016 12:24:16
+0530 from [125.67.200.247] ----- The following addresses had permanent fatal
errors ----- linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org ----- Transcript of the session follows
----- ... while talking to server 94.4.109.57: >>> RCPT To:<linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>
<<< 550 5.1.1 <linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>... Not known here [...]
Content analysis details: (5.0 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
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.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0019]
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: 2931 bytes --]
From: "The Post Office" <postmaster-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>
To: linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org
Subject: test
Date: Sat, 27 Aug 2016 12:24:16 +0530
Message-ID: <20160827065509.E8E451A1E61-y27Ovi1pjclAfugRpC6u6w@public.gmane.org>
The original message was received at Sat, 27 Aug 2016 12:24:16 +0530
from [125.67.200.247]
----- The following addresses had permanent fatal errors -----
linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org
----- Transcript of the session follows -----
... while talking to server 94.4.109.57:
>>> RCPT To:<linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>
<<< 550 5.1.1 <linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>... Not known here
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next reply other threads:[~2016-08-27 6:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-27 6:54 The Post Office [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-15 3:26 Test Automatic Email Delivery Software
2018-01-09 3:14 TEST Mail Delivery Subsystem
2018-01-09 3:14 TEST Mail Delivery Subsystem
2017-10-11 3:22 test MAILER-DAEMON
2017-10-11 3:22 test MAILER-DAEMON
2016-10-19 5:59 test linux-kernel-u79uwXL29TY76Z2rM5mHXA
2016-10-19 5:59 test linux-kernel
2016-08-27 6:54 test The Post Office
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=20160827065509.E8E451A1E61@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).