Ok, found a way to validate this theory. I took the message that was failing and simply added "charset=us-ascii" to the Content-Type: line like this...
Content-Type: text/plain; charset=us-ascii
Verified that direct connection to the imap port returns the ("charset" "us-ascii") in the bodystructure response. Then tested with wm5 and was able to see the email. In this case, I am able to modify the mime header manually but that is not possible with clients and even if it is, most clients default to not specifying the charset option. All other imap server implementations I've seen default to us-ascii if there is nothing specified. I think it is reasonable to expect your server to do the same. I will check to see if this is required as part of the rfc but it seems like an easy thing to fix. |