Erik, without either debugging info of a leak detector, or bare necessities to reproduce the situation per the FAQ <http://www.fetchmail.info/fetchmail-FAQ.html#G3>, there is no chance this can ever be fixed. (This does not rule out a lucky coincidence, but such a coincidence might happen in a few years, or never.)
While the memory stats might hint to a leak, more info is required, and I propose to also provide information from lsof -c fetchmail (run as root). I will personally also not investigate bugs in 6.3.18, but only in 6.3.22 -- I might be willing to look at bug reports that pinpoint the location in a code excerpt, however. It all hinges on a way for me to reproduce the problem, or someone to send a patch and/or a good explanation how the leak would show up. Sorry. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
