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