请选择 进入手机版 | 继续访问电脑版

AdvertCN - 广告中国

 找回密码
 立即注册

QQ登录

只需一步,快速开始

 谷歌+Bing+TT+MSN官方代理 
⚡️按条S5代理⚡️静态⚡️独享⚡️5G⚡️最干净<Wifi住宅+5G移动>IP代理泰国仓储,本土仓发货2-3元/单
指纹浏览器,就用AdsPower谷歌/FB/Bing/Yahoo代理商开户7200W全球动态不重复住宅IP代理全球优质流量,选TrafficStars
出售Facebook,友缘号,FB广告号,insFB/TT/KW 加白开户比Adplexity还好用的Spy工具ADPLEXITY + ADVERTCN
FB不限额广告号MediaGo+Taboola+Ob开户百度国际MediaGo⚡️让产品狂奔全球百度国际,高点击转化,快速放量
百度国际MediaGo,独家原生流量虚拟信用卡+独立站收款行业首创新型指纹Cloak, 谷歌奇效!BINOM TRACKER 60% OFF!
Kookeey⚡️100%独享⚡️原生住宅IP⚡5000W动态住宅全场8折⚡全球虚拟卡, 支持U充值谷歌/Outbrain/Taboola⚡️一键开户
FB极速下户/白名单/不收费Affiliate站外引流服务⚡️极速出单免账户投放 FB 广告(送项目)2024做什么 - Media buy 项目库
免费黑五教程(持续更新、欢迎交流)Facebook 批量上广告Facebook账号1块一个各种主页、账单户、BM户(优势)
⚡️个人户,bm户不限额,账单户Adsterra 的CPA/CPM/CPC 网站流量在线注册美国/英国/香港等海外公司EU KETO/CBD - Jumbleberry
【YouTube】油管获利号交易平台三不限/账单户/BM不限额/直播主页FB二三解1元/个9Proxy ⚡️ $0.04/IP, 无限带宽
最佳Health和Beauty联盟广告位出租全球低价纯净住宅/移动IP-免费试用广告代投, 东南亚物流, 虚拟信用卡
VMLogin指纹浏览器+多账号防关联   
查看: 2737|回复: 0

邮件服务器搭建 (5) 如何回复信件

[复制链接]

8

主题

7

广告币

28

积分

初级会员

Rank: 2

积分
28

社区QQ达人

发表于 2014-12-7 16:53:07 | 显示全部楼层 |阅读模式
adsterra
本帖最后由 一生有你 于 2014-12-9 01:25 编辑

上一篇是手工telnet取信,各类语言都有自己的imap库,了解了协议,基本就没问题了
下面问题来了,如何回复一个邮件。
回复一个邮件和普通发信有什么区别?
下面是详细解释  转载的。
不想多说,说白了就一句话,发信和回复就差三个信头!

Threading: Message-ID, References, In-Reply-ToOften a message is a response to a previous message. The parent of a response is the message that it responds to.
The parent may have been a response to yet another message. There can also be other messages with the same parent, with the same grandparent, etc. A collection of messages with a common ancestor is usually called a thread.
Readers can use Message-ID and References to see the structure of a thread.
Message identifiersIn theory a message identifier is tokenizable; it contains a < token, an encoded address, and a > token. Two examples:     <[email protected] >     <"16913 Tue Apr  9 14:24:59 1996"@bnr.ca>I recommend against using quoted strings, spaces, tabs, or comments inside message identifiers; there is no reason for identifiers to contain user-interface fluff.Note that the Internet mail address encoded in a message identifier is usually not an address that can receive mail.
Message-IDThe value of a Message-ID field is a message identifier. For example:     Message-ID: <[email protected]>The Internet mail address encoded in Message-ID is required to be a unique worldwide identifier for this message.
It is the writer's responsibility to obtain authorization from the owner of the domain used in Message-ID. It is up to the owner to decide how to allocate a different box part for each new message.
822bis says that the domain used in Message-ID ``SHOULD be the domain name of the host on which it was created.'' However, in reality, many dialup hosts don't have domain names, and many hosts behind firewalls don't have public domain names. Some organizations have set aside banks of Message-ID names that do not refer to hosts.
Any message that starts or continues a thread needs a Message-ID. Not all messages contain Message-ID; for example, bounce messages from qmail do not contain Message-ID, and the Bell Labs upas mailer never creates Message-ID.
Security and reliability issuesIn practice, Message-IDs are not necessarily unique. For example, Internet Mail Service 5.0.1457.3 reportedly copies Message-ID into a bounce message from the message being bounced; and Microsoft Internet Mail reportedly uses the same Message-ID for every message. Furthermore, from a security perspective, an attacker can easily forge a message with a duplicate Message-ID.This means that it is neither secure nor reliable to discard a message with the same Message-ID as a previous message. If you want to discard duplicates, you should compute a cryptographic hash of each message.
ReferencesIn theory the value of a References field is tokenizable, consisting of a series of words and message identifiers.
In practice, References has nothing other than the message identifiers, each preceded by exactly one space, all on one line:
     References: <[email protected]> <[email protected]> <[email protected]> <[email protected]>This is the USENET References syntax. Writers should follow the same format.Writers use References to indicate that a message has a parent. The last identifier in References identifies the parent. The first identifier in References identifies the first article in the same thread. There may be more identifiers in References, with grandparents preceding parents, etc. (The basic idea is that a writer should copy References from the parent and append the parent's Message-ID. However, if there are more than about ten identifiers listed, the writer should eliminate the second one.)
In-Reply-ToThe value of an In-Reply-To field is tokenizable, consisting of a series of words and message identifiers.
According to 822, In-Reply-To lists parents, and References lists ``other correspondence.'' Some MUAs do in fact put parents into In-Reply-To. However, very few readers are able to parse the complicated syntax of In-Reply-To specified by 822, let alone the syntactically incorrect fields that show up in practice:
     In-Reply-To: Your message of 10 Jan 1998 20:22:41 -0000       (WRONG)The USENET References syntax, as described above, has been much more successful than the 822 In-Reply-To, thanks to its simplicity. I recommend that writers support References as described above. 822bis recommends generating In-Reply-To as well as References; however, I don't know if there are any readers that understand In-Reply-To without also understanding References. There are some writers that generate In-Reply-To without References; I recommend that, for backwards compatibility, readers look for identifiers in In-Reply-To and append them to References if they are not already included in References.

评分

参与人数 1广告币 +1 收起 理由
lwbing + 1 赞一个!

查看全部评分

相关帖子
回复

使用道具 举报

您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

关于我们|联系我们|DMCA|广告服务|小黑屋|手机版|Archiver|Github|网站地图|AdvertCN

GMT+8, 2024-3-29 01:16 , Processed in 0.046070 second(s), 14 queries , Gzip On, MemCache On.

Copyright © 2001-2023, AdvertCN

Proudly Operating in Hong Kong.

快速回复 返回顶部 返回列表