MIME Mail View

zhaozj2021-02-16  45

Q What is MIME? What is MIME mail?

A MIME, a full name "MultiPurpose Internet Mail Extensions", more exact Chinese name is "Multi-Use Internet Mail Extension". It is an email technical specification that currently extensively applied, and the basic content is defined in RFC 2045-2049.

Naturally, MIME mail is an email compliant with MIME specification, or email based on MIME specification.

Before MIME is introduced, you can only send basic ASCII code text information using RFC 822, if you want binary files, sounds, and animation, etc., it is very difficult. MIME provides a method of attaching a variety of different coded files in the mail to compensate for the lack of the original information format. In fact, it is not only email coding, and now MIME is a part of the HTTP protocol standard.

Let's take a few examples of MIME mail, let us first have an intuitive impression on the format of MIME encoding. Example 1 is the simplest, only a plain text body, basically the RFC 822 format; Example 2 is complex, including plain text and hypertext body; Example 3 is the most complicated, including plain text, hypertext body, within Embedded resources and file accessories. Among them, the space after the line number and the line number is to analyze convenient and additionally, "... ..." indicates that the large segment coding is omitted here.

example 1

1 Date: Thu, 18 Apr 2002 09:32:45 0800

2 from:

3 TO:

4 Subject: Test

5 MIME-VERSION: 1.0

6 Content-Type: Text / Plain; Charset = "ISO-8859-1"

Seduce

8 this is a simple mail.

9

Example 2

1 from: "bhw98"

2 reply-to: bhw98@sina.com

3 TO:

4 Subject: Re: Help

5 x-mailer: Foxmail 4.2 [CN]

6 MIME-VERSION: 1.0

7 Content-Type: Multipart / alternative;

8 boundary = "===== 002_dragon307572345230 _ ====="

9

10

11 this is a multi-part message in mime format.

12

13 - ===== 002_dragon307572345230 _ =====

14 Content-Type: Text / Plain; Charset = "GB2312"

15 Content-Transfer-Encoding: Quoted-Printable

16

17 bluesky7810 = a3 = ac = C4 = fa = ba = c3 = a3 = a1

18

19 = a1 = a1 = a1 = a1 = D4 = DA = CF = C2 = C6 = AA = D7 = EE = BA = f3 = bf = C9 = D2 = D4 = CF = C2 = D4 = D8 = b0 = a1 = A3 = AC = C4 = E3 ... ... ...

30 = a1 = a1 = a1 = a1 = a1 = a1 = a1 = a1 = a1 = a1 = a1 = a1 = a1 = a1 = a1 = a1 = a1 = a1 = a1 = a1 = A12003-04-07

31

32 - ===== 002_dragon307572345230 _ =====

33 Content-Type: Text / HTML; Charset = "GB2312"

34 Content-Transfer-Encoding: Quoted-Printable

35

36

37

38

39 http-equiv = 3dContent-Type>

40

... ...

79

80

81 - ===== 002_dragon307572345230 _ ===== -

82

Example 3

1 return-path:

2 Delivered-to: bhw98@sina.com

3 RECEIVED: (qmail 75513 invoked by alias); 20 May 2002 02:19:53 -0000

4 RECEIVED: from unknown (Helo Bluesky) (61.155.118.135)

5 by 202.106.187.143 with smtp; 20 May 2002 02:19:53 -0000

6 Message-ID: <007F01C311C $ 742FEC00 $ 0100007F @ bluesky>

7 from: "=? GB2312? B? WLBATRXEZEZOWNCG ==? ="

8 TO: "BHW98"

9 cc:

10 Subject: =? GB2312? B? Ztk1xlbgtk6 / 2rpm0pi =? =

11 Date: Sat, 20 May 2002 10:03:36 0800

12 MIME-VERSION: 1.0

13 Content-Type: Multipart / Mixed;

14 boundary = "---- = _ nextpart_000_007a_01c3115f.80dfc5e0" 15 x-priority: 3

16 x-msmail-priority: Normal

17 X-MAILER: Microsoft Outlook Express 5.00.2919.6700

18 x-mimeole: produced by Microsoft Mimeole V5.00.2919.6700

19

20 this is a multi-part message in mime format.

twenty one

22 ------ = _ nextpart_000_007a_01c3115f.80dfc5e0

23 Content-Type: Multipart / Related; Type = "Multipart / Alternative";

24 boundary = "---- = _ nextpart_001_007b_01c3115f.80dfc5e0"

25

26

27 ------ = _ nextpart_001_007b_01c3115f.80dfc5e0

28 Content-Type: Multipart / Alternative;

29 boundary = "---- = _ nextpart_002_007c_01c3115f.80dfc5e0"

30

31 ------ = _ nextpart_002_007c_01c3115f.80dfc5e0

32 Content-Type: Text / Plain; Charset = "GB2312"

33 Content-Transfer-Encoding: Quoted-Printable

34

35 BHW98, = C4 = E3 = ba = C3!

36 = D5 = E2 = Ca = C7 = CE = D2 = D0 = B4 = B5 = C4 = B6 = E0 = B4 = AE = BF = DA = CD = A8 = D0 = C5 = B5 = C4 = B3 = CC = D0 =

37 = f2, = C7 = EB = D6 = B8 = BD = CC!

38

39

40 ------ = _ nextpart_002_007c_01c3115f.80dfc5e0

41 Content-Type: Text / HTML; Charset = "GB2312"

42 Content-Transfer-Encoding: Quoted-Printable

43

44

45 = C7 = E7 = c0 = ca </ title></p> <p>46 <meta content = 3d "text / html; charset = 3dgb2312" http-equiv = 3dContent-Type></p> <p>47 <style> body {</p> <p>48 Color: # 0033cc; font-family: = CB = CE = CC = E5, Arial, Helvetica; font-size: =</p> <p>49 9pt; margin-left: 10px; margin-top: 25px</p> <p>50}</p> <p>51 </ style> 52 <meta content = 3d "MSHTML 5.00.2920.0" Name = 3dGenerator> </ head></p> <p>53 <body background = 3dcid: 007901C3111C $ 72b978a0 $ 0100007f @ bluesky =</p> <p>54 bgcolor = 3d # ffffff></p> <p>55 <DIV></p> <p>56 <div> BHW98, = C4 = E3 = ba = c3! </ Div></p> <p>57 <p> = D5 = E2 = CA = C7 = CE = D2 = D0 = B4 = B5 = C4 = B6 = E0 = B4 = AE = BF = DA = CD = A8 = D0 = C5 = B5 = C4 = B3 = Cc =</p> <p>58 = D0 = f2, = C7 = EB = D6 = b8 = bd = cc! </ P> </ div></p> <p>59 <p> </ p> </ body> </ html></p> <p>60</p> <p>61 ------ = _ nextpart_002_007c_01c3115f.80dfc5e0 -</p> <p>62</p> <p>63 ------ = _ nextpart_001_007b_01c3115f.80dfc5e0</p> <p>64 Content-Type: Image / JPEG; Name = "=? GB2312? B? X fayrgzvrauslbh? ="</p> <p>65 Content-Transfer-Encoding: Base64</p> <p>66 Content-ID: <007901C311C $ 72B978A0 $ 0100007F @ Bluesky></p> <p>67</p> <p>68 / 9J / 4aqskzjrgabageasabiaad / 7qvoughvdg9zag9widmumaa4qklna 0aaaaaabaasaaaaaea</p> <p>69 Aqbiaaaaaaaaaaiaaaaaaaaaaa4qklnbaoaaaaaaaaAaAaAaAacgabGabGab</p> <p>70 Aaaaaaaaai4qklna / Uaaaaaaegal2zmaaeabgzmaayaaaaaaaaaaaaaaaaaeaaaaaaea</p> <p>... ...</p> <p>169 RXVW98VAWQ12XQ44Q0CKTHFDWKGSKT4TIUKT4Q / / 9K =</p> <p>170</p> <p>171 ------ = _ nextpart_001_007b_01c3115f.80dfc5e0 -</p> <p>172</p> <p>173 ------ = _ nextpart_000_007a_01c3115f.80dfc5e0</p> <p>174 Content-Type: Application / Msword; Name = "Readme.doc"</p> <p>175 Content-Transfer-Encoding: Base64</p> <p>176 Content-Disposition: attachment; filename = "readme.doc"</p> <p>177</p> <p>178 0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7 / CQAGAAAAAAAAAAAAAAABAAAAJgAAAAAAAAAA</p> <p>179 EAAAAAAAAAAAAAAD AAAAAAAAAAAD /</p> <p>180</p> <p>... ...</p> <p>1688 aaaaaaaaaaaaaaaaaa =</p> <p>1689</p> <p>1690 ------ = _ nextpart_000_007a_01c3115f.80dfc5e01691 Content-Type: Application / X-Zip-compressed;</p> <p>1692 name = "=? GB2312? B? Tuc0rr / azajqxbxe1ltc6y56axa =? ="</p> <p>1693 Content-Transfer-Encoding: Base64</p> <p>1694 Content-Dispsisition: attachment;</p> <p>1695 filename = "=? GB2312? B? Tuc0rr / azajqxbxe1ltc6y56axa =? ="</p> <p>1696</p> <p>1697 uESDBBQAAAAIAFKAOI7QOMOVLW0AAABWAAUAAAAATUC0RR / AZAJQXBXE1LTC6Y5KB2PTXHTWVNUZ</p> <p>1698 / 4 KK3iQoakBkryqksgBrkb7iynemwmm6ckg0jci0boznetbjj9snlaesdotfqd8z846tq6phb1</p> <p>1699 hrztjok0VHGF1AGT4RMY6D8TDUGFTJUOPCBIR9J VVSIY4YKRNTREN87V / UD53CEE 6557VN7L73</p> <p>... ...</p> <p>3125 zajqxbxe1ltc6y5kb2nqswugaaaaaaeaaqbcaaaaaarayQ0AAA ==</p> <p>3126</p> <p>3127 ------ = _ nextpart_000_007a_01c3115f.80dfc5e0 -</p> <p>3128</p> <p>Q How to get this source code when you start studying MIME mail?</p> <p>A Some functions relatively complete mail client software, such as Microsoft's Outlook Express, domestic Foxmail, which provides the functionality of viewing and saving mail source (original information). In Foxmail, select the "Original Information" of the Mail List Right-click on the Menu to view, the "File-Export" of the main menu is saved. In Outlook Express, the corresponding operations are "attributes" and "Save". The saved .eml file can call these programs to open.</p> <p>Q Please tell us about the composition of MIME mail?</p> <p>A generally, the MIME message consists of two parts of the message head and the message body. Now we are concerned about MIME mail, so in the following discussion, there is "message" as "message". In the above example, 1-6 lines of Example 1, 1-8 lines of Example 2, 1-18 of Example 3, are the header; 8-9 lines of Example 1, the 10-82 rows of Example 2, The 20-3128 line of Example 3 is a mail body. Between the email head and the mail body, separated by a space line, the second line of the second line of Example 1, the fourth line of Example 3, and Example 3. The email head is not allowed to appear. Some emails cannot be identified by the mail client software, which is the original code, that is, because the first line is empty.</p> <p>The email header contains important information such as senders, recipients, themes, time, MIME versions, and mail content. Each information is called a domain, and the domain name is added ":": "and the information content, which can be a row, longer can also take up multiple lines. The first line of the domain must "head", that is, the left side cannot have blank characters (spaces and tabs); the continuation must be headed with blank characters, and the first blank character is not inherent, decoding it is filtered off. . As the 7-8 lines of Example 2, 4-5 lines, 13-14 lines, respectively, respectively, respectively.</p> <p>The mail body contains the content of the message, which is pointed out by the "Content-Type" field of the mail head. Common simple types have Text / Plain and Text / HTML (hypertext). The Multipart type that appears in Example 2 and Example 3 is the essence of MIME mail. The mail body is divided into multiple segments, each segment contains two parts of the segment and the segment, and the two parts are separated by a blank line. Common Multipart types have three: Multipart / Mixed, Multipart / Related and Multipart / Alternative. From their name, it is not difficult to informed the respective meaning and use of these types. The hierarchical relationship between them is indicated as shown below:</p> <p> ----------------------- Multipart / Mixed --------------------- ------- </p> <p>| | |</p> <p>| ----------------- Multipart / Related ---------------- |</p> <p>| | | | | |</p> <p>| | ----- Multipart / Alternative ------ ---------- | ------ |</p> <p>| | | | | Inline Resources | | | Accessories |</p> <p>| | | ------------ ------------ | -------- | -- - |</p> <p>| | | | Pure text text | | Hypertext | | | | | |</p> <p>| | | ------------ ------------ | -------- | -- - |</p> <p>| | | | | Inline Resources | | | Accessories |</p> <p>| | ---------------------------------- | ------ |</p> <p>| | | | | |</p> <p>| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ------ |</p> <p>| | |</p> <p> ----------------------------------- --------------------- </p> <p>It can be seen that if you want to add an attachment in your message; if there is an inline resource, you must define the Multipart / Related segment; if plain text is coexisting, at least the Multipart / Alternative segment is to define. What is "at least"? For example, if there is only plain text and hypertext body, the type is enlarged in the email header, defined as Multipart / Related, or even multipart / mixed, is allowed. The common feature of Multipart criteria is that the "Boundary" parameter string is specified in the segment header, and each sub-segment in the segment is collected. All sub-sections start with "-" Boundary row, and the father ends with the "-" Boundary "-" line. The segment and the segment are also separated by a space. In the case where the mail body is a multipart type, the beginning of the mail body (first "-" Boundary line) can have some additional text lines, which should be ignored when the comment is decoded. There are also some additional text lines, and will not be displayed. If you are interested, you may wish to verify it.</p> <p>Combined with Boundary delimited and Multipart hierarchical diagram, we analyzed the email hierarchical relationship between Example 2 and Example 3.</p> <p>In Example 2, 10-12 lines are additional text lines, 13-82 lines are the multipart / alternative segment, including two subsets: 13-30 lines are plain text, 32-79 lines are hypertext.</p> <p>In Example 3, 20-21 lines are additional text lines, 22-3127 lines are Multipart / Mixed type segments, including 3 subsets: 22-171 lines are Multipart / Related segment, 173-1688 lines and 1690-3125 lines It is two attachments. The Multipart / Related section contains two subsets: 27-61 lines are Multipart / Alternative segments, 63-169 rows are an embedded resource (picture). The Multipart / Alternative segment includes two subsets: 31-48 lines are pure text body, 40-59 lines are hypertext.</p> <p>Example 1 Only a texture of plain text is actually a special case in the Multipart hierarchy. If you don't want to avoid it, it is fully compliant with the MIME spirit.</p> <p>Date: Thu, 18 APR 2002 09:32:45 0800</p> <p>From: <bhw98@sina.com></p> <p>TO: <bhwang@jlonline.com></p> <p>Subject: Test</p> <p>MIME-VERSION: 1.0</p> <p>Content-type: multipart / alternative; boundary = "{[^_^)]}"</p> <p>- {[(^_^)]}</p> <p>Content-Type: Text / Plain; Charset = "ISO-8859-1"</p> <p>Content-Transfer-Encoding: 7bit</p> <p>This is a simple mail.</p> <p>- {[^ _ ^)]} -</p> <p>Q Which common domains is in the email header and segment?</p> <p>A In the email header, there are many domain names that are used along RFC 822, and MIME has also increased. Common standard domain names and meanings</p> <p>Domain Name Meaning Adder RECEIVED Transport Path Parts Mail Server Return-Path Reply Address Target Mail Server Delivered-To Send Address Target Mail Server Reply-To Reply Address Mail Created FROM sender Address Mail creator TO Recipient Address Mail creator CC CCD address message creator BCC Dedicated Address Mail Created Date Date Date and Time Mail Creation Subject Theme Mail Created MIME-ID Message Id Message Mime-VersionMime version message creation The coded-transfer-encoding content of Content-Type content is not standard, custom domain names, such as X-MAILER, X-MSMail-Priority, etc. It is usually understood that their significance can be understood when receiving and sending mail is the same program.</p> <p>In the section, there are substantially the following domains.</p> <p>Domain Nomination Content-Type Segment Type of CONTENT-TRANSFER-ENCODING Segment Transport Coding Method The Content-Disposition Segment Schedule The CONTENT-ID CONTENT-LOCATION segment location (path) Content-Base segment Base location</p> <p>In addition to the value, there is also a parameter. The value and parameters, the parameters and parameters are separated by ";"; The parameter name and the parameter values ​​are separated by "=". As the 28-29 line of Example 3, the value of the Content-Type field is "Multipart / Alternative", and there is a parameter Boundary, the value is "---- = _ nextpart_002_007c_01c3115f.80dfc5e0". Another example 3st line, the value of the Content-Disposition domain is "attachment", and there is a parameter filename, the value is "readme.doc".</p> <p>Q Content-Type and what forms of their parameters?</p> <p>A Content-Type is all in the form of "primary type / subtype". The main type has Text, Image, Audio, Video, Application, Multipart, Message, etc., which represent text, pictures, audio, video, applications, segments, messages, etc. Each primary type may have multiple sub-types, such as the TEXT type contains Plain, HTML, XML, CSS type. With the primary type and subtypes of X-beginning, the type of customization is also expressed, and it has not officially registered to IANA, but most of them have agreed. If Application / X-Zip-Compressed is a Zip file type. In Windows, "HKEY_CLASS_ROOT / MIME / DATABASE / Content Type" listed in the registry, listed in most known Content-Type except Multipart.</p> <p>With regard to the form of parameters, there are many additional regulations in RFC, and some allow for several parameters, more common</p> <p>Main Type Parameter Name Meaning TextCharset Character Set ImageName Name ApplicationName Name MultipartBoundary Border</p> <p>The character set can also be seen in the "HKEY_CLASS_ROOT / MIME / DATABASE / CHARSET" of the Windows Registry.</p> <p>Q Content-Transfer-Encoding What are you? What is the character?</p> <p>A Content-Transfer-Encoding has several Base64, Quoted-Printable, 7bit, 8bit, Binary, etc. Among them, 7 bit is the default encoding method. The email source code is initially designed to all be printed in the form of a printed ASCII code. Non-ASCII code text or data to encode into required format, as three examples above. Base64, Quoted-Printable is the most widely encoded method in non-English countries. The binary method only has symbolic meaning without any practical value. Base64 encodes the input string or a segment of data into only {'A' - 'Z', 'A' - 'Z', '0' - '9', ' ', '/'} 64 characters Strings, '=' is used to fill. The method of its encoding is to take the input data stream each time you take 6 bit, use this 6 bit value (0-63) as an index to check the table, and output the corresponding character. In this way, each 3 bytes are encoded to 4 characters (3 × 8 → 4 × 6); filled with '=' by dissatisfaction with 4 characters. Some occasions, "=? CHARSET? B? Xxxxxxxxx =" indicates that xxxxxxxx is Base64 encoding, and the original character set is Charset. Such as Example 3 Chapter 7 "=? GB2312? B? WLBATRXEZEZOWNCG ==? =" Is made from Simplified Chinese "Bluternity". Directly encoded directly in the section, the time is appropriate, and MIME recommends up to 76 characters per line. As the 1697-3125 line of Example 3 is a zip file base64 encoding.</p> <p>QuoteD-printable encodes according to the input string or byte range, if you do not need to encode characters, output directly; value. Some situations, "=? Charset? Q? Xxxxxxxxx? =" Indicates that xxxxxxxx is quoted-printable encoding, and the original character set is Charset. Directly encoded in the segment, right time to go online, additional output 1 '=' before the wrap. As 44-59 lines of Example 3, it is the quoted-printable encoding of HTML text. The 45th line "= C7 = E7 = C0 = CA" is "sunny", because "Qing" GB2312 code is C7E7, "Lang" GB2312 code is C0CA. On the end of the line 48, 53, 57, only solitary '=', indicating that this is a soft back to the encoding, not the original textured.</p> <p>In recent years, many domestic mail servers have supported 8bit, so only mails transmitted in China, especially in the mail head, can directly use 8bit encoding, do not process the Chinese characters. If the email is going abroad or is old, press BASE64 or QuoteD-Printable coding.</p> <p>Q What is embedded resources? What do it have?</p> <p>A embedded resources are also a lighting point of MIME, which makes the email content are lively and colorful. You can define some sections, animations, sounds or even CSS styles, and scripts associated with the text within the Multipart / Related framework of the message. Usually in the HTML text, use the hyperlink to the embedded resource. As in Example 3, HTML body 53-54 line, decoded</p> <p><Body background = CID: 007901C311C $ 72B978A0 $ 0100007f @ bluesky bgcolor = # fffff></p> <p>It pointed out that the picture of $ 72B978A0 $ 0100007F @ bluesky is also a super link (CID: XXXXXXXX). The 64-169 line is such an embedded resource. In addition to contact with the Content-ID, there is another common form: use ordinary super connections and content-location. E.g:</p> <p>In the body of HTML,</p> <p>... ...</p> <p><Img src = "http://www.dangdang.com/images/all/anti_joyo_dm_book.gif"></p> <p>... ...</p> <p><Img src = "http://www.dangdang.com/dd2001/getiMage_small.asp?id=486341"></p> <p>... ...</p> <p>Corresponding embedded resources are</p> <p>Content-type: image / gif; name = "Anti_JOYO_DM_BOOK.GIF"</p> <p>Content-Transfer-Encoding: Base64</p> <p>Content-location: http://www.dangdang.com/images/all/anti_joyo_dm_book.gif</p> <p>... ...</p> <p>Content-type: Application / OCTET-stream; Name = "getImage_small.asp? Id = 486341"</p> <p>Content-Transfer-Encoding: Base64</p> <p>Content-location: http://www.dangdang.com/dd2001/getiMage_small.asp?id=486341</p> <p>... ...</p> <p>In addition,</p> <p>Content-location: http://www.dangdang.com/images/all/anti_joyo_dm_book.gif</p> <p>versus</p> <p>Content-location: Anti_JOYO_DM_BOOK.GIF</p> <p>Content-base: http://www.dangdang.com/images/All/</p> <p>It is equivalent.</p> <p>Q Mail virus uses attachments and embedded resources to spread?</p> <p>A some mail attachments may have a virus and is easy to understand. Attachment is a document after all, it is also preventive, not easy to open. But inline resources are accessible when browsing the content of the message. If there is a virus or malicious code, you don't know anything. As the NIMDA virus that has been popular in the world's two years, the functional source code is as follows:</p> <p>MIME-VERSION: 1.0</p> <p>Content-type: Multipart / Related;</p> <p>TYPE = "Multipart / Alternative";</p> <p>Boundary = "==== _ ABC1234567890DEF _ ===="</p> <p>- ==== _ ABC1234567890DEF _ ====</p> <p>Content-Type: Multipart / Alternative;</p> <p>Boundary = "==== _ ABC0987654321DEF _ ===="</p> <p>- ==== _ ABC0987654321DEF _ ====</p> <p>Content-Type: Text / HTML;</p> <p>Charset = "ISO-8859-1"</p> <p>Content-Transfer-Encoding: 7bit</p> <p><Html> <head> </ head> <body bgcolor = # ffffff></p> <p><iframe src = CID: EA4DMGBP9P Height = 0 width = 0></p> <p></ iframe> </ body> </ html></p> <p>- ==== _ ABC0987654321DEF _ ==== -</p> <p>- ==== _ ABC1234567890DEF _ ====</p> <p>Content-type: Audio / X-WAV; Name = "Readme.exe"</p> <p>Content-Transfer-Encoding: Base64</p> <p>Content-id: <ea4dmgbp9p></p> <p>Sign</p> <p>AAAA2AAAA4FUG4ATANNIBGBTM0HVGHPCYBWCM9NCMFTIGNHBM5VDCBIZSBYDW4GAW4GRE9TIG1V</p> <p>ZguudQ0kjaaaaaaaaaa11cfvcbvpphg1tzxxtu88e6pcphw1tzyzqku8dbvppjmqszxytu88cbvo</p> <p>... ... ... ...</p> <p>AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA =</p> <p>- ==== _ ABC1234567890DEF _ ====</p> <p>It embeds an executable as a resource into a frame-like page, but declares that this executable code is a waveform sound type. Since the Microsoft IE (version 5.0 and below) has a major security vulnerability, there is no check whether the content-type extension is matched, so it is easily deceived, causing this "Readme when it is easy to swindle. ", the machine is infected with the virus. The poisonous machine uses the address book to send poisoned mail to others, one pass ten, ten pass hundred, Nimda worms.</p> <p>Throughout history, the virus is just out of time, but there is no one can continue to ravage. Nimda, SARS is also the case.曰: "How difficult is the Bang, Zhong Zhicheng City", also: "Non-Dynasty will fall, the city spirit is forever", I believe that we can win "SARS"!</p> <p>The virus library upgrade is carried out after the new virus butt, do not excessively depend on anti-virus software. A good habit is to close the email preview feature, or set a preview plain text section, first view the mail source, confident that the virus is suspected to open. Emperor's mail from a super text of the stranger, especially Never open accessories directly in the mail client software.</p> <p>Q Some spam take the way to hide the sender, how to trace them from?</p> <p>A From the above mail header domain name table, you can see that the creator of the message can master the content of most domains, but the resced isotactic is automatically added by the servers at all levels. The sender is a whirling. Spam generally uses group-issued software to send, the mail header from the FROM domain (sender address) can be arbitrarily forged, even written into a recipient address (have received the spam, angry when I have received myself,?). Check the ReceiveD Domain (Transfer Path) chain to find a real source. The received statement added by each server is in the first, so the bottom RECEIVED contains the SMTP or HTTP server used by the sender, and the original gateway external IP address. The basic format of the Receive statement is: from a by B. A is the sender, b is the recipient. E.g:</p> <p>Received: (qmail 45304 invoked from network network); 4 May 2003 17:05:47 -0000</p> <p>Received: from unknown (Helo Bjapp9.163.net) (202.108.255.197)</p> <p>BY 202.106.182.244 with smtp; 4 May 2003 17:05:47 -0000</p> <p>Received: from localhost (localhost [127.0.0.1])</p> <p>By bjapp9.163.net (postfix) with SMTP ID E1C761D84C631</p> <p>For <bhw98@sina.com>; MON, 5 May 2003 01:07:26 0800 (CST)</p> <p>Received: from fanyingxxxx@tom.com (unknown [211.99.162.194])</p> <p>By bjapp9.163.net (coremail) with smtp id ogeaam1itt7mnalc.1</p> <p>For <bhw98@sina.com>; mon, 05 May 2003 01:07:26 0800 (CST)</p> <p>It is not difficult to see from the above example, the transmission path of the message is: 211.99.162.194 → BJAPP9.163.NET (Coremail 202.108.255.197?) → BJAPP9.163.NET (Postfix, 202.108.255.197?) → 202.106.182.244 . The sender's mailbox fanyingxxxx@tom.com is not necessarily listed.</p> <p>The localhost [127.0.0.1] of this example means software installed on the BJAPP9.163.NET installed.</p> <p>[related resources]</p> <p>RFC / STD document: Internet FAQ Archives BHW98 column: http://www.9cbs.net/develop/author/netauthor/bhw98/</p> <p>First release: 2003-05-16 Last revision: 2003-05-16</p></div><div class="text-center mt-3 text-grey"> 转载请注明原文地址:https://www.9cbs.com/read-23669.html</div><div class="plugin d-flex justify-content-center mt-3"></div><hr><div class="row"><div class="col-lg-12 text-muted mt-2"><i class="icon-tags mr-2"></i><span class="badge border border-secondary mr-2"><h2 class="h6 mb-0 small"><a class="text-secondary" href="tag-2.html">9cbs</a></h2></span></div></div></div></div><div class="card card-postlist border-white shadow"><div class="card-body"><div class="card-title"><div class="d-flex justify-content-between"><div><b>New Post</b>(<span class="posts">0</span>) </div><div></div></div></div><ul class="postlist list-unstyled"> </ul></div></div><div class="d-none threadlist"><input type="checkbox" name="modtid" value="23669" checked /></div></div></div></div></div><footer class="text-muted small bg-dark py-4 mt-3" id="footer"><div class="container"><div class="row"><div class="col">CopyRight © 2020 All Rights Reserved </div><div class="col text-right">Processed: <b>0.035</b>, SQL: <b>9</b></div></div></div></footer><script src="./lang/en-us/lang.js?2.2.0"></script><script src="view/js/jquery.min.js?2.2.0"></script><script src="view/js/popper.min.js?2.2.0"></script><script src="view/js/bootstrap.min.js?2.2.0"></script><script src="view/js/xiuno.js?2.2.0"></script><script src="view/js/bootstrap-plugin.js?2.2.0"></script><script src="view/js/async.min.js?2.2.0"></script><script src="view/js/form.js?2.2.0"></script><script> var debug = DEBUG = 0; var url_rewrite_on = 1; var url_path = './'; var forumarr = {"1":"Tech"}; var fid = 1; var uid = 0; var gid = 0; xn.options.water_image_url = 'view/img/water-small.png'; </script><script src="view/js/wellcms.js?2.2.0"></script><a class="scroll-to-top rounded" href="javascript:void(0);"><i class="icon-angle-up"></i></a><a class="scroll-to-bottom rounded" href="javascript:void(0);" style="display: inline;"><i class="icon-angle-down"></i></a></body></html><script> var forum_url = 'list-1.html'; var safe_token = 'll4f7g2DHj41te8n5fI987j66VcQGho2VE2y2QTsowtGmwT7IN_2B7bryIl3Rj97HvCos6xkLtSTSW28FsBF_2B0lg_3D_3D'; var body = $('body'); body.on('submit', '#form', function() { var jthis = $(this); var jsubmit = jthis.find('#submit'); jthis.reset(); jsubmit.button('loading'); var postdata = jthis.serializeObject(); $.xpost(jthis.attr('action'), postdata, function(code, message) { if(code == 0) { location.reload(); } else { $.alert(message); jsubmit.button('reset'); } }); return false; }); function resize_image() { var jmessagelist = $('div.message'); var first_width = jmessagelist.width(); jmessagelist.each(function() { var jdiv = $(this); var maxwidth = jdiv.attr('isfirst') ? first_width : jdiv.width(); var jmessage_width = Math.min(jdiv.width(), maxwidth); jdiv.find('img, embed, iframe, video').each(function() { var jimg = $(this); var img_width = this.org_width; var img_height = this.org_height; if(!img_width) { var img_width = jimg.attr('width'); var img_height = jimg.attr('height'); this.org_width = img_width; this.org_height = img_height; } if(img_width > jmessage_width) { if(this.tagName == 'IMG') { jimg.width(jmessage_width); jimg.css('height', 'auto'); jimg.css('cursor', 'pointer'); jimg.on('click', function() { }); } else { jimg.width(jmessage_width); var height = (img_height / img_width) * jimg.width(); jimg.height(height); } } }); }); } function resize_table() { $('div.message').each(function() { var jdiv = $(this); jdiv.find('table').addClass('table').wrap('<div class="table-responsive"></div>'); }); } $(function() { resize_image(); resize_table(); $(window).on('resize', resize_image); }); var jmessage = $('#message'); jmessage.on('focus', function() {if(jmessage.t) { clearTimeout(jmessage.t); jmessage.t = null; } jmessage.css('height', '6rem'); }); jmessage.on('blur', function() {jmessage.t = setTimeout(function() { jmessage.css('height', '2.5rem');}, 1000); }); $('#nav li[data-active="fid-1"]').addClass('active'); </script>