obsolete version number in TODO

[Rboylan]

Got email-2.4.3.tar.gz from the latest cvs. It
includes a TODO file, with the following notation:
- We should support RFC 2231. Oleg Broytmann has
patches to add this support, so we'll look into it for
email-1.3.

Since this is email-2.4, I presume either its been done
or the version number needs to change.

This is a low-priority item. I figured I mention it,
since I saw it.

[http://sourceforge.net/tracker/index.php?func=detail&aid=700140&group_id=103&atid=100103]

[Barry Warsaw (barry)]

Bugs and patches on the email package probably belong better
on the Python or mimelib projects. But in any event, I've
updated the TODO list. Thanks!

[Rboylan (rboylan)]

I just did a cvs update and looked at email-2.5b1 in there.
 The TODO still refers to email-1.3. (21-Mar-2003).

Out of curiosity, where do python and mimelilb bugs go?

[Barry Warsaw (barry)]

I'll bet you're looking at the maintenance branch. I still
have to backport the trunk changes to the maint branch.

Python bugs should go in the Python project trackers.
mimelib bugs should probably go there too, or in the
standalone mimelib project. If you submit email package bug
reports in the Python project, be sure to assign them to me.