On Saturday 05 August 2006 21:21, Beech Rintoul wrote:
> Yes that's all set up. I'm wondering if the recent update of openssl broke
> something.
That's quite possible. You could try deinstalling it and going back to the
base ssl.
TAke a look at /usr/ports/UPGRADING, at 20060108 there is a mess
On Saturday 05 August 2006 18:09, Donald J. O'Neill wrote:
> On Saturday 05 August 2006 20:59, Beech Rintoul wrote:
> > Thanks for the suggestion, but that didn't help. There seems to be a
> > problem regarding secure login, as the rest of my insecure pop3 logins
> > work. This all started after my
On Saturday 05 August 2006 20:59, Beech Rintoul wrote:
> Thanks for the suggestion, but that didn't help. There seems to be a
> problem regarding secure login, as the rest of my insecure pop3 logins
> work. This all started after my last -current update.
>
> Beech
Gmail uses ssl, do you have that
On Saturday 05 August 2006 17:16, Donald J. O'Neill wrote:
> On Saturday 05 August 2006 18:49, Beech Rintoul wrote:
> > I just started getting the following error while trying to login to
> > gmail:
> >
> > The process for the pop3s://pop.gmail.com protocol died unexpectedly.
> >
> > I'm running Fr
On Saturday 05 August 2006 18:49, Beech Rintoul wrote:
> I just started getting the following error while trying to login to gmail:
>
> The process for the pop3s://pop.gmail.com protocol died unexpectedly.
>
> I'm running FreeBSD 7.0-CURRENT with the kde ports all up to date. I've
> double checked
I just started getting the following error while trying to login to gmail:
The process for the pop3s://pop.gmail.com protocol died unexpectedly.
I'm running FreeBSD 7.0-CURRENT with the kde ports all up to date. I've double
checked the configs and they are correct. I can log into pop3 on gmail f
