http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5531
------- Additional Comments From [EMAIL PROTECTED] 2007-06-22 09:36 ------- Created an attachment (id=4016) --> (http://issues.apache.org/SpamAssassin/attachment.cgi?id=4016&action=view) fix ok, here's a fix. It adds a new API, transport_cleanup() -- named to match the existing message_cleanup(). I couldn't think of a better way to do this than to add a new API, unfortunately. :( Since it's a new API, I added a #define so that callers could tell if it exists or not; I also recommend we do not add this to 3.2.x, instead keeping it for 3.3.0. (the amount of RAM leaked is pretty trivial, and unlikely to affect anyone not using libspamc repeatedly in one process.) I'll check it into trunk once the 3.2.x queue clears out... ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
