IMAP BODYSTRUCTURE decoding assumes Content-Type parameter ordering

[octo]

The decoding logic for the IMAP BODYSTRUCTURE response makes a bad assumption about the ordering of the Content-Type parameters. This issue manifests when decoding a text section, and the assumption is that the "CHARSET" parameter will be the first parameter. This is not always the case, which can lead to decoding problems.

For example, the charset will not be correctly parsed from the following:

Content-Type: text/plain;
	format=flowed;
	charset="windows-1251";
	delsp=yes

Parameter parsing needs to be order-independent, and issues like this have already been fixed elsewhere in the IMAP parser.

[octo]

Fixed in 1.0.4