Application IDs with length 1 are handled properly
Setting the address to "mms://" throws IllegalArgumentException instead
of a RuntimeException.
Clarifications about the reply mechanism added in section Internal settings.
getTimestamp() method returns the timestamp
set by the network when applied to a received message and it returns always
null when applied to a sent message
There are no additional constraints for the contentLocation parameter
of a MessagePart, other than containing only US-ASCII
characters
Fix provided for handling Java MMSs with no priority or normal priority. Such MMSs were discarded in the earlier release.