Received: from sample.test.com (192.168.1.2) by smtp.mail.com (192.168.1.3) with Microsoft SMTP Server id 8.1.375.2; Thu, 31 Dec 2009 11:02:37 +0800 Received: from tst33 ([192.168.1.1]) by sample.test.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 31 Dec 2009 11:02:35 +0800From: "firstname.lastname@example.org" To: "email@example.com" Content-Class: urn:content-classes:message Date: Thu, 31 Dec 2009 11:02:32 +0800 Subject: Send the message using the network Thread-Topic: Send the message using the network Thread-Index: AcqJxbIiyzk4CLcJSOa1mph6h4PKgg== Message-ID: <firstname.lastname@example.org> Accept-Language: zh-TW Content-Language: zh-TW X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-Exchange-Organization-AuthSource: HCS02.mail.com X-MS-Has-Attach: X-MS-Exchange-Organization-SCL: 0 X-MS-TNEF-Correlator: x-originalarrivaltime: 31 Dec 2009 03:02:35.0458 (UTC) FILETIME=[B3FA7A20:01CA89C5] Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: base64 MIME-Version: 1.0
From: email@example.com這封郵件是由adalf0722@yahoo.com.tw 寄出的 To: firstname.lastname@example.org 收件者為shaq.email@example.comContent-Class: urn:content-classes:messageDate: Thu, 31 Dec 2009 11:02:32 +0800 這訊息是在Thu, 31 Dec 2009 11:02:32 +0800 建立的 Subject: Send the message using the network
Received: from tst33 ([192.168.1.1]) by sample.test.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 31 Dec 2009 11:02:35 +0800這封郵件是從tst33送到sample.test.com，發生的時間點為31 Dec 2009 11:02:35 +0800，發信的機器稱它自己為tst33(A的電腦)，它的真實IP為192.168.1.1，sample的mail server是使用微軟的smtp services，版本為5.0.2195.6713，注意from後面的tst33，這是機器說它自己叫tst33的，也就是它是可以欺騙mail server的，但是後面帶的ip是它真實的ip，如果去比對的話，就可以發現它有沒有欺騙囉，現在的mail程式有的可以做reverse DNS，很容易就發現此信是不是偽造的
Received: from sample.test.com (192.168.1.2) by smtp.mail.com (192.168.1.3) with Microsoft SMTP Server id 8.1.375.2; Thu, 31 Dec 2009 11:02:37 +0800 第二個Received是說這封郵件是從sample.test.com送過來的(剛從smtp services寄出)，它自己說它叫sample.test.com，它的真實IP為192.168.1.2，由叫smtp.mail.com的機器收下來，它的真實IP為192.168.1.3，收件的是微軟的exchange server，exchange的版本為8.1.375.2，傳輸時間為Thu, 31 Dec 2009 11:02:37 +0800
A typical email header displays several lines that begin with "Received." Note the last "Received" line; this line will look something like this:
Received from genericwebsite.org (123.456.789.101)
If the "Received from" information does not match the email address of the sender or the company being represented in the email, it usually means that the message did not truly come from that individual or company.
Dependency scope is used to limit the transitivity of a dependency, and also to affect the classpath used for various build tasks.
There are 6 scopes available:
compile This is the default scope, used if none is specified. Compile dependencies are available in all classpaths of a project. Furthermore, those dependencies are propagated to dependent projects.
provided This is much like compile, but indicates you expect the JDK or a container to provide the dependency at runtime. For example, when building a web application for the Java Enterprise Edition, you would set the dependency on the Servlet API and related Java EE APIs to scope provided because the web container provides those classes. This scope is only available on the compilation and test classpath, and is not transitive.
runtime This scope indicates that the dependency is not required for compilation, but is for execution. It is in the runtime and test classpaths, but not the compile classpath.
test This scope indicates that the dependency is not required for normal use of the application, and is only available for the test compilation and execution phases.
system This scope is similar to provided except that you have to provide the JAR which contains it explicitly. The artifact is always available and is not looked up in a repository.
import(only available in Maven 2.0.9 or later) This scope is only used on a dependency of type pom in the <dependencyManagement> section. It indicates that the specified POM should be replaced with the dependencies in that POM's<dependencyManagement> section. Since they are replaced, dependencies with a scope of import do not actuall