nvdimm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "¹Ú °úÀå" <jun244356-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org
Subject: [±¤°í] Áö±ÝÀº ¼ÒÇü Ä«Æä â¾÷ ½Ã´ë
Date: Mon, 29 May 2017 09:56:44 +0500	[thread overview]
Message-ID: <2q52$lo5r17bpv-5$7y@dc6fs> (raw)

[-- Attachment #1: Type: text/plain, Size: 2301 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:  ¼ÒÇü Ä«Æä´Â ¾î´À ºê·£µå°¡ ÁÁÀ» ±î¿ä? 1. ´õº¥Æ¼ 2. ÄÄÆ÷ÁîÄ¿ÇÇ
   3. º¹°í´Ù¹æ 4. »ýÈ°Ä¿ÇÇ µµ¿òÀÌ µÇ¼Ì³ª¿ä? [...] 

Content analysis details:   (11.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]
 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
 2.4 RCVD_HELO_IP_MISMATCH  Received: HELO and IP do not match, but should
 0.0 T_HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail
                            domains are different
 0.0 FREEMAIL_FROM          Sender email is commonly abused enduser mail provider
                            (jun244356[at]gmail.com)
 0.2 FREEMAIL_REPLYTO_END_DIGIT Reply-To freemail username ends in digit
                            (jun244356[at]gmail.com)
-0.0 BAYES_20               BODY: Bayes spam probability is 5 to 20%
                            [score: 0.1040]
 1.4 AXB_XM_FORGED_OL2600   Forged OE v. 6.2600
 1.5 SUBJ_ILLEGAL_CHARS     Subject: has too many raw illegal characters
 0.0 T_FREEMAIL_FORGED_FROMDOMAIN 2nd level domains in From and
                            EnvelopeFrom freemail headers are different
 0.0 SUBJECT_NEEDS_ENCODING No description available.
 2.6 MSGID_RANDY            Message-Id has pattern used in spam
 1.0 RCVD_DOUBLE_IP_LOOSE   Received: by and from look like IP addresses
 1.9 FORGED_MUA_OUTLOOK     Forged mail pretending to be from MS Outlook

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: 3110 bytes --]

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

¼ÒÇü Ä«Æä´Â ¾î´À ºê·£µå°¡ ÁÁÀ» ±î¿ä?

1. ´õº¥Æ¼
2. ÄÄÆ÷ÁîÄ¿ÇÇ
3. º¹°í´Ù¹æ
4. »ýÈ°Ä¿ÇÇ

µµ¿òÀÌ µÇ¼Ì³ª¿ä?

[-- 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-05-29  4:56 UTC|newest]

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

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='2q52$lo5r17bpv-5$7y@dc6fs' \
    --to=jun244356-re5jqeeqqe8avxtiumwx3w@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).