CC address of the associated message.
Received date of the associated message.
Sent Date of the associated message.
Flag, whether the info is changed and requires save to disk. Compare with CamelMessageInfo:folder-flagged
Bit-or of #CamelMessageFlags.
Flag, whether the info is changed and requires save to the destination store/server. This is different from the CamelMessageInfo:dirty, which takes care of the local information only.
From address of the associated message.
Headers of the associated message. Can be %NULL.
Encoded Message-ID of the associated message as a guint64 number, partial MD5 sum. The value can be cast to #CamelSummaryMessageID.
Mailing list address of the associated message.
Body preview of the associated message. Can be %NULL.
Encoded In-Reply-To and References headers of the associated message as an array of guint64 numbers, partial MD5 sums. Each value can be cast to #CamelSummaryMessageID.
Size of the associated message.
Subject of the associated message.
The #CamelFolderSummary to which the message info belongs, or %NULL. It can be set only during construction of the object.
To address of the associated message.
A unique ID of the message in its folder.
User flags for the associated message. Can be %NULL. Unlike user-tags, which can contain various values, the user-flags can only be set or not.
User-defined headers of the associated message. Can be %NULL.
User tags for the associated message. Can be %NULL. Unlike user-flags, which can be set or not, the user-tags can contain various values.
Flag, whether the info is currently aborting notifications. It is used to avoid unnecessary 'folder-flagged' and 'dirty' flags changes and also to avoid associated folder's "changed" signal. f