Proposed changes to mailutils

[clay caragianes]

I believe this is how I submit proposed changes to mailutils, but
please correct me if I am not.

There are two changes they are both for issues I've run across
regarding multipart messages.

The first change is to boundary definitions that begin with a space or
spaces before the quotes or valid characters in the boundary
definition.
example:
boundary= "--some--boundary";
This doesn't parse correctly and causes issues when viewing the email
because mailutils doesn't correctly get the boundary definition for
the email. The change in mime.c looks for white spaces and strips them
out before attempting to read the boundary definition.

The second change is to support emails that have no ending boundary to
the last part of the message. I have run into a lot of messages that
are not spam and do not contain a end boundary to the last part of the
message. The change to the code assumes that the end boundary is the
end of the file if it does not find a end boundary.

I don't believe these changes are RFC compliant but there is enough
email like this that I receive that warrants these changes. I don't
know if you want to add it to the code base, offer it as a possible
patch, or do nothing at all.


There was 1 file changed: mailbox/mime.c
I have included it attached as text and as a diff as well as both the
diff and text in a zip file.




_______________________________________________
Bug-mailutils mailing list
Bug-mailutils@...
http://lists.gnu.org/mailman/listinfo/bug-mailutils