nvdimm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "µµ³Îµå Æ®·³ÇÁ" <hellohs-8eaMts54rL0AvxtiuMwx3w@public.gmane.org>
To: linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org
Subject: ¿À´Ã ±ÞµîÁÖ ¾îÁ¦ ¾î¶»°Ô ¾Ë¾ÒÀ»±î¿ä?
Date: Tue, 17 Oct 2017 12:40:34 +0400	[thread overview]
Message-ID: <2ssn8017p-c-88$--4563ig$0g-689@9i61.r6.bp6> (raw)

[-- Attachment #1: Type: text/plain, Size: 2369 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:  ¾È³çÇϼ¼¿ä. Ŭ·´ ȸ¿ø ¿©·¯ºÐ ÁÁÀº Á¤º¸ À־ ¾Ë·Áµå¸³´Ï´Ù.
   ÁÖ½ÄÅõÀÚ·Î ¾ÈÁ¤ÀûÀ¸·Î °í¼öÀÍÀ» ³»±â À§Çؼ­´Â [...] 

Content analysis details:   (9.6 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: bit.ly]
-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]
 1.3 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net
              [Blocked - see <http://www.spamcop.net/bl.shtml?221.195.112.45>]
 1.2 RCVD_NUMERIC_HELO      Received: contains an IP address used for HELO
-0.6 RP_MATCHES_RCVD        Envelope sender domain matches handover relay domain
 0.0 FROM_ILLEGAL_CHARS     From: has too many raw illegal characters
 0.0 T_HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail
                            domains are different
 2.4 RCVD_HELO_IP_MISMATCH  Received: HELO and IP do not match, but should
-1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
                            [score: 0.0000]
 2.6 MSGID_RANDY            Message-Id has pattern used in spam
 1.5 SUBJ_ILLEGAL_CHARS     Subject: has too many raw illegal characters
 0.0 SUBJECT_NEEDS_ENCODING No description available.
 1.9 FORGED_MUA_IMS         Forged mail pretending to be from IMS
 1.0 RCVD_DOUBLE_IP_LOOSE   Received: by and from look like IP addresses

The original message was not completely plain text, and may be unsafe to
open with some email clients; in particular, it may contain a virus,
or confirm that your address can receive spam.  If you wish to view
it, it may be safer to save it to a file and open it with an editor.


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

[-- Attachment #2.1.1: Type: text/plain, Size: 246 bytes --]

¾È³çÇϼ¼¿ä. Ŭ·´ ȸ¿ø ¿©·¯ºÐ

ÁÁÀº Á¤º¸ À־
¾Ë·Áµå¸³´Ï´Ù.

ÁÖ½ÄÅõÀÚ·Î ¾ÈÁ¤ÀûÀ¸·Î °í¼öÀÍÀ» ³»±â À§Çؼ­´Â

¾È³çÇϼ¼¿ä. Ŭ·´ ȸ¿ø
¿©·¯ºÐ

ÁÁÀº Á¤º¸ ÀÖ¾î
°øÀ¯µå¸³´Ï´Ù.

±ÞµîÁÖ ¸ÅÁÖ ¹«·á·Î ÁÖ´Â
»çÀÌÆ®ÀÔ´Ï´Ù.

http://bit.ly/2ywVMsN

[-- Attachment #2.1.2: Type: text/plain, Size: 178 bytes --]

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

             reply	other threads:[~2017-10-17  8:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-17  8:40 µµ³Îµå Æ®·³ÇÁ [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-03-28 21:39 ÈçºÎËõ¶ÌÉú²úÖÜÆÚ£¬×¼Ê±½»»õºÍ½µµÍ¿â´æ ÏòÔóÌì
2018-03-27  8:48 ÖÐ ²ã ¸É ²¿ Èç ºÎµ± ÔÆÃî÷ë
2017-09-13  2:46 ÁÖ½Ä Å¬·´ ȸ¿øºÐµé²² Èñ¼Ò½ÄÀÖ¾î °øÀ¯Çմϴ٠Ŭ·´Àå
2017-08-19 12:11 Ó²¼þµç·Éè¼Æ¡¢¹ÊÕ϶¨Î»Ó빤³Ì°¸Àý·ÖÎö Òüƽ½¨
2017-08-18 20:06 ÈçºÎ¹æ»®²úƷƽ̨£¿ÈçºÎ½øÐм¼Êõ¹æ»®£¿ ÁÎêØÓÑ
2017-08-18  3:06 ´ÓÖ»¶Ô¼¼Êõ¸ºÔðת±äΪ¶ÔÈ«Á÷³Ì¸ºÔð Æֵϰ®
2017-07-10 17:16 »Ø¸´£ºÈçºÎ±ÜÃâ²ú Æ·¾­ÀíÂÙÂä³É"ÎÊÌâ¾­Àí"£¿ Ï¿­
2017-07-10 17:02 ת·¢£ºÌá¸ß²úÆ·µÄÖÊÁ¿£¬ÌáÉý²úÆ·µÄ¾ºÕùÁ¦£¬È·±£Êг¡³É¹¦ Ò¶ÄþÒä
2017-05-29  4:56 [±¤°í] Áö±ÝÀº ¼ÒÇü Ä«Æä â¾÷ ½Ã´ë ¹Ú °úÀå

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='2ssn8017p-c-88$--4563ig$0g-689@9i61.r6.bp6' \
    --to=hellohs-8eamts54rl0avxtiumwx3w@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).