hi! not sure whether you want to consider this a bug or not, but in fetchmail 5.9.14 i get a problem connecting to one specific pop3 server (the others work fine), where calling STSL terminates the connection. i can replicate the behaviour using telnet on port 110 on that server, so it's really a server bug, but it annoys the hell out of me, and i can hardly change the server. i have a patch that introduces a 'nostls' flag you can use with some servers. i should warn that i'm not 100% sure that my patch doesn't destroy anything, but for my setup it works fine (1 server uses the STLS command, one i switch it off for and two don't list it in their CAPAbilities). the thing probably also applies to non-ppc versions, but i didn't check. have fun. i'll submit this to the fetchmail people, maybe they'll introduce it.
Created attachment 4641 [details, diff] patch to introduce the 'nostls' flag see original bug post
have you tried fetchmail-6.1.0 which is currently unmasked in portage?
hello again! erm, when i got the problem i tried to emerge the build but it said it was still masked... haven't tried since then. i suppose i could use ebuild to merge it. will try tomorrow.
emerge rsync emerge fetchmail When you do an rsync... you should find the new fetchmail unmasked
hi again! the new fetchmail wasn't unmasked on my system (at least emerge fetchmail built 5.9.14), but i built the new one with ebuild merge. as i suspected, it has the same problems (i.e. 6.1.0). i'm still using my patched 5.9.14 now... i'll write the people hosting the mailserver in question, maybe it's a known bug there... hopefully.
6.1.1 has been relased into portage. Not to bore you with the same question again, but can you let me know if this new version fixes the problem?
hi! yeah, same problems. i posted my patch on the fetchmail-friends mailinglist, but to no avail (didn't appear in the archives...) the patch works well enough on the 6.1.1 tree, but i'll include a new patch here, in case you're interested. have fun, jens
Created attachment 4972 [details, diff] same patch, but for 6.1.1
Have you gotten any responses from fetchmail maintainers regarding your patch?
hello. no, i'm sad to say that there was no response so far.
And now fetchmail-6.1.2 is available with supposedly some TLS fixes... again... it work for you? any response regarding your patch?
And of course... a new version has been released again. Please let me know if 6.2.1 works or contains your workaround :) The sad part of this story is that on the fetchmail site he welcomes code additions to fetchmail. You would think that the least you would get is a response...
db fix
sorry for not answering so long, my net access was limited. yes, 6.2.2 does fix my problem, though it does not seem to be my patch that fixes it. *shrugs* as long as it works... :)
hi! i know it's been some time, but i'd like to add a little something... i've recently updated my system, again with the same bug. a quick check (after a few days of little email traffic) confirmed that fetchmail had been downgraded to 5.9.14 again - 6.2.2 works fine on my ppc, and i'd like to propose that it at least goes ~ppc take care, jens
