I am profoundly disappointed to discover that the mail client configuration instructions - for Mozilla at least - don't mention PORTS at all. When I couldn't get Thunderbird to retrieve Gmail through PopFile? I suspected that there was something additional to do in Account Manager beyond what the instructions say, since I knew that knew that PopFile? uses only port 110 as a downstream connection to clients; how could leaving the assigned port for an account set to 995 possibly work?!

It doesn't, of course, but the instructions don't bother AT ALL to explain that the port MUST ALWAYS be set to 110 and then further explain the necessary syntax for communicating to PopFile? what port to actually use for the upstream connection to the server. NOT A WORD Is said about ports or SSL or the syntax required to implement it. It's been many years since I last used PopFile?, and in the meantime virtually every mail provider has transitioned to use of secure connections that use ports other than 110. That's years of opportunity for someone to have revised the documentation, but instead it's still mired in a temporal distortion from 2005.

I had to discover that necessary syntax by accident in a "SSL problem with POPFile 1.1.2" post here in these forums, as I was preparing to ask for help resolving the log error I observed (pop3: 626: IO::Socket::INET or IO::Socket::SSL gets an error: IO::Socket::INET: connect: timeout). I knew the syntax would be something like what I found in that post, but why did I have to stumble upon it there? Why isn't it documented with the mail client configuration?

I don't seem to be allowed to correct this damning omission myself; considering how poorly the documentation is being maintained by whatever exists of a PopFile? Inner Circle, that documentation desperately needs some Wikipedia-style inclusiveness.