-
Notifications
You must be signed in to change notification settings - Fork 5
Message format
This is known to be along the lines of
CMD <TrID> <parameters> <payload size>\n
<header name>: <header value>\n
[...more headers...]\n
\n
<payload body>
The payload body often itself constitutes a headers-and-body construct.
<TrID> is a transaction ID; outlook.com uses numbers for this. If it's set to something nonzero in a message sent by the client, the server will acknowledge the message by means of a response--possibly one that is otherwise a noop--that has the same transaction ID. If the server sends an unsolicited message, the transaction ID is zero.
Contains a cookie. After receiving this header, all subsequent messages sent by the client must contain a Registration header whose value is the same as the value of the last received Set-Registration.
See above.
The current time according to the server, formatted as a Unix timestamp.
Looks like some sort of hex value.