Re: potential pop3d memory leakage (2.1.16)

2004-03-25 Thread Michael Loftis
Also proxyd.c ignores servername:, I've got a few other patches going against mine but right at the top of cmdloop() (line 1427 my file which is probably wrong) we have a gethostname and a hostname variable isntead of using the common config_servername. Not bad bug, just inconsistent. Thanks f

Re: potential pop3d memory leakage (2.1.16)

2004-03-25 Thread Ken Murchison
Michael Loftis wrote: First I realise that 2.1.16 is 'dead tree' now, however inside of openinbox popd_msg is xmalloc-ed but as far as I can tell NEVER free'd anywhere and is then leaked between sessions. Can anyone confirm this? You are correct. Its been around for a while. Here's the f

potential pop3d memory leakage (2.1.16)

2004-03-25 Thread Michael Loftis
First I realise that 2.1.16 is 'dead tree' now, however inside of openinbox popd_msg is xmalloc-ed but as far as I can tell NEVER free'd anywhere and is then leaked between sessions. Can anyone confirm this? -- GPG/PGP --> 0xE736BD7E 5144 6A2D 977A 6651 DFBE 1462 E351 88B9 E736 BD7E --- H