See METHODS in Mail::Reporter
Option | Defined in | Default |
---|---|---|
body | Mail::Message | undef |
body_type | Mail::Box::Message | |
cache_body | <false> | |
cache_head | <false> | |
cache_labels | <false> | |
deleted | Mail::Message | <false> |
field_type | Mail::Message | undef |
folder | Mail::Box::Message | <required> |
head | Mail::Message | undef |
head_type | Mail::Message | |
labels | Mail::Message | {} |
log | Mail::Reporter |
|
messageId | Mail::Message | undef |
modified | Mail::Message | <false> |
size | Mail::Box::Message | undef |
trace | Mail::Reporter |
|
trusted | Mail::Message | <false> |
unique | Mail::Box::Net::Message | <unique string> |
write_labels | <true> |
Returns the size of this message. If the message is still on the remote server, IMAP is used to ask for the size. When the message is already loaded onto the local system, the size of the parsed message is taken. These sizes can differ because the difference in line-ending representation.
With only one argument, the value related to $label is returned. With more that one argument, the list is interpreted a label-value PAIRS to be set.
The IMAP protocol defines its own names for the labels, which must be set imediately to inform other IMAP clients which may have the same folder open. But that can be changed with new(write_labels). Some labels are translated to the corresponding IMAP system labels.
Use the IMAP's UID FETCH IMAP
command to get some data about this
message. The $info request is passed to Mail::Box::IMAP4::fetch().
Without $info, ALL
information is retrieved and returned as a HASH.
Write all delayed information, like label changes, to the server. This is done under force, so should even be done for folders opened without write-access. This method is called indirectly by a Mail::Box::write() or Mail::Box::close().
The $imap argument is a Mail::IMAPClient which has the right folder already selected.
Writing changes to the remote folder is not without hassle: IMAP4 (or is it only manual Mail::IMAPClient doesn't support replacing header or body. Therefore, when either of them change, the whole message is rewritten to the server (which is supported), and the original flagged for deletion.