/
385.txt
99 lines (61 loc) · 2.32 KB
/
385.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
* 歴史
[FIG[
* RFC 724
[PRE[
<extension-field> ::= "In-Reply-To" ":" <reference-list>
|...
<reference-list> ::= <null>
| <reference-item>
| <reference-item> "," <reference-list>
<reference-item> ::= <phrase>
| <mach-host-phrase>
<mach-host-phrase>::= "<" <host-phrase> ">"
]PRE]
** b. In-Reply-To:
The contents of this field identify previous correspondence
which this message answers. If message identifiers are used
in this field, they should be enclosed in angle brackets (<>).
** 例
- In-Reply-to: <some string at SHOST>
]FIG]
[FIG[
* RFC 733
optional-field =
[PRE[
...
/ "In-Reply-To"":" #(phrase / mach-id)
/...
]PRE]
** 2. In-Reply-To
The contents of this field identify previous correspondence which
this message answers. Note that if message identifiers are used
in this field, they must use the mach-id specification format.
** 例
- In-Reply-To: <some string at SHOST>
* RFC 822
[PRE[
optional-field =
...
/ "In-Reply-To" ":" *(phrase / msg-id)
/...
]PRE]
** 4.6.2. IN-REPLY-TO
The contents of this field identify previous correspondence
which this message answers. Note that if message identifiers
are used in this field, they must use the msg-id
specification format.
** 例
- In-Reply-To: <some.string@DBM.Group>, George's message
** C.3.5. IN-REPLY-TO
The field-body is no longer a comma-separated list, although a
sequence is still permitted.
]FIG]
** RFC 2822
[[RFC2822の3.6.4]]参照。
[PRE[
obs-in-reply-to = "In-Reply-To" *WSP ":" *(phrase / msg-id) CRLF
]PRE]
* 関連
[2] [CODE(822)@en[[[References:]]]] 欄も参照。
* メモ
[1] なんとなく [CODE(822)[[[Reply-To]]]] 欄との関係を期待したくなるところですが、あんまり関係ないです。 [CODE(822)[In-Reply-To]] は''そのメッセージが返信する、元メッセージ''を示し、 [CODE(822)[Reply-To]] は''そのメッセージを受け取った人が返信する時に使って欲しい宛先''が示されます。