Contents

FIXES

recent fixes based on importing results into evolution

1. was running into some issue with base64 encoded message/rfc822 attachments displaying
   as empty. encoding them as plain solved the issue (odd).

2. problem with a large percentage of emails, not displaying as mime. turned out to be
   all received from blackberry. further, turned out there was 2 content-type headers,
	 "Content-Type", which I add, and "Content-type". normally my override works, but I
	 need to handle it case insensitvely it would appear. more tricky, whats the story
	 with these. fixing that will probably fix that whole class of issues there.
	 evolution was renaming my second content type as X-Invalid-Content-Type or something.

3. another interesting one. had content-transfer-encoding set in the transport message
   headers. it was set to base64. i didn't override that, so evolution "decoded" my
	 plaintext message into complete garbage.
	 fix - delete content-transfer-encoding.

4. added content-location and content-id output in the mime handling of attachments
   to get some inline html/image mails to work properly.
   further, the containing mime content-type must be multipart/related, not multipart/mixed,
	 at least for evolution, in order for the images to appear inline.
   could still improve in this area. if someone drags and drops in an image, it may
	 be inline in the rtf version, but exchanges generates crappy html such that the image
	 doesn't display inline. maybe i should correct the html output in these cases as i'm
	 throwing away the rtf version.

5. note you may need wingdings installed. i had a lot of L and J appear in messages from
   outlook users. turns out its smilies in wingdings. i think its only if word is used
	 as email editor and has autotext messing things up.

6. still unsure about how to do my "\r" handling.

Version data entries

4 entries across 4 versions & 1 rubygems

Version	Path
ruby-msg-1.2.17.2	FIXES
ruby-msg-1.2.17.1	FIXES
ruby-msg-1.2.17	FIXES
ruby-msg-1.2.17.3	FIXES