<feed xmlns='http://www.w3.org/2005/Atom'>
<title>leap_mail.git/changes/bug_7244_fix_nested_multipart, branch 0.4.0rc2</title>
<subtitle>[leap_mail] 
</subtitle>
<link rel='alternate' type='text/html' href='https://leap.se/git/leap_mail.git/'/>
<entry>
<title>[pkg] fold in changes</title>
<updated>2015-08-26T21:09:22+00:00</updated>
<author>
<name>Ivan Alejandro</name>
<email>ivanalejandro0@gmail.com</email>
</author>
<published>2015-08-26T21:09:22+00:00</published>
<link rel='alternate' type='text/html' href='https://leap.se/git/leap_mail.git/commit/?id=43c920f38d1c114e9044d2da15d4a05d5faab79d'/>
<id>43c920f38d1c114e9044d2da15d4a05d5faab79d</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>[bug] fix the rendering of nested multipart</title>
<updated>2015-07-13T15:55:30+00:00</updated>
<author>
<name>Kali Kaneko</name>
<email>kali@leap.se</email>
</author>
<published>2015-07-08T16:47:04+00:00</published>
<link rel='alternate' type='text/html' href='https://leap.se/git/leap_mail.git/commit/?id=221a168e07a5d8ff32573c80ab2cad54d03d3038'/>
<id>221a168e07a5d8ff32573c80ab2cad54d03d3038</id>
<content type='text'>
This commit fix a very simplistic and until now broken handling of
nested multipart that went undetected due to the structure of the mails
used in tests until now.  Incidentally, the way that Mail.app structures
attachments made this bug noticeable.

There was also an off-by-one indexing error when retrieving the subpart
message for a given subpart.

Be aware that the current implementation will only handle correctly 2
levels of multipart nesting. Extending beyond in a more generic way will
need further work.

Closes: #7244
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This commit fix a very simplistic and until now broken handling of
nested multipart that went undetected due to the structure of the mails
used in tests until now.  Incidentally, the way that Mail.app structures
attachments made this bug noticeable.

There was also an off-by-one indexing error when retrieving the subpart
message for a given subpart.

Be aware that the current implementation will only handle correctly 2
levels of multipart nesting. Extending beyond in a more generic way will
need further work.

Closes: #7244
</pre>
</div>
</content>
</entry>
</feed>
