diff options
author | Philipp Korber <p.korber@1aim.com> | 2018-11-16 15:46:43 +0100 |
---|---|---|
committer | Philipp Korber <p.korber@1aim.com> | 2018-11-16 15:46:43 +0100 |
commit | 652d6f0ffeee7302a2cb51059bef75d8b0bb50be (patch) | |
tree | c3851592642938172f280f7428d43e08b0fe2cbe /headers/doc | |
parent | 0947fe8996149fe20a6d47a793f9555790eb2eae (diff) |
refactor: merged sources of mail-headers,mail-internals,mail-core, mail
Originally it was palaned to do a merge with `--allow-unrelated-history`
but this can not be doesn as `mail-core` has a "invalid" history which
has a merge conflict **with itself**. So even rewinding the history on
a empty repo is not possible.
Instead the code was directly coppied over losing history.
But the history is still available in the different
`history-backup-*` branches. It is just that the past history
is decoupled from the current history.
Diffstat (limited to 'headers/doc')
-rw-r--r-- | headers/doc/list_of_headers.txt | 78 |
1 files changed, 78 insertions, 0 deletions
diff --git a/headers/doc/list_of_headers.txt b/headers/doc/list_of_headers.txt new file mode 100644 index 0000000..7cf1666 --- /dev/null +++ b/headers/doc/list_of_headers.txt @@ -0,0 +1,78 @@ +-- FIXME AsciiString => HeaderName +-- NOT HERE Content-Header-Extension |AsciiString | Unstructured|, +-- NOT HERE Other |AsciiString | Unstructured|, + +RFC | Name | Rust-Type | Comment +------|---------------------------|-------------------|---------------------------- +5322 | | | RFC 5322 obsoletes RFC 822 + | Date | DateTime | + | From | MailboxList | + | Sender | Mailbox | + | Reply-To | MailboxList | + | To | MailboxList | + | Cc | MailboxList | + | Bcc | OptMailboxList | + | Message-ID | MessageID | + | In-Reply-To | MessageIDList | + | References | MessageIDList | + | Subject | Unstructured | + | Comments | Unstructured | + | Keywords | PhraseList | + | Resent-Date | DateTime | + | Resent-From | MailboxList | + | Resent-Sender | Mailbox | + | Resent-To | MailboxList | + | Resent-Cc | MailboxList | + | Resent-Bcc | OptMailboxList | + | Resent-Msg-ID | MessageID | + | Return-Path | Path | + | Received | ReceivedToken | +------|---------------------------|-------------------|--------------------------- +2045 | Content-Type | Mime | + | Content-ID | MessageID | + | Content-Transfer-Encoding | TransferEncoding | + | Content-Description | Unstructured | the rfc states it is TEXT, but referes to RFC822 + | | | in RFC5322 there is no longer TEXT, it was replaced + | | | by Unstructured +------|---------------------------|-------------------|--------------------------- +2183 | | | proposed standard (obsoltets rfc 1806) + | Content-Disposition | Disposition | +------|---------------------------|-------------------|--------------------------- + + + +------ "others" ---- +-- e.g. see https://www.cs.tut.fi/~jkorpela/headers.html +--Delivered-To |loop detection| +--User-Agent |client software used by orginator| +--Abuse-Reports-To |inserted by some servers| +--X-Envelop-From |Mailbox| |sender in the envelop copied into the body| +--X-Envelop-To |Mailbox| |again envelop information moved into body| +--X-Remote-Addr |from html| +-- +------Proposed Standard---- +--RFC 1766 +-- Content-Language |LanguageTag| +--RFC 1864 +-- Content-MD5 |Base64| +-- +------Experimental-------- +--RFC 1806 |attachment of inline| +-- Content-Disposition |Dispositions| +--RFC 1327 & 1911 +-- Importance +-- Sensitivity +--RFC 1154 & 1505 +-- Encoding +-- +------Not Standad ------ +--RFC 1036 +-- FollowupTo |??MessageID| +--RFC 1036 |count of lines| +-- Lines |usize| +--RFC ???? +-- Status |U/R/O/D/N| |should NEVER EVER be generate for a mail to send, use by some mail delivery systems INTERNAL ONLY| +-- +-- +------Not Standard Discouraged---- +--ContentLength |usize| |do never generate content length header in a mail you send, it's a HTTP think|
\ No newline at end of file |