hi,

yesterday i upgraded to 10.2 from 10.1 slackware. everything seems ok
expected i found my fetchmail stoped working.

blow is my fetchmail configuration:

poll pop.gmail.com with proto POP3 and options no dns
user 'myname@gmail.com' with pass "mypassword" is 'narke' here
options ssl sslcertck sslcertpath '/home/narke/.certs'
keep
smtphost localhost

blow is error messages:

fetchmail: Warning: server certificate verification: unable to get
local issuer certificate
2901:error:14090086:SSL
routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify
failed:s3_clnt.c:844:
fetchmail: SSL connection failed.

so, i gues there might be ssl which stop running. but i can not recall
how i set up the fetchmail to using ssl.

could anyone help me? thanks.


-
woody

On 17 Dec 2005 00:58:27 -0800, Steven Woody Cried: Read These Runes!:
......>
> poll pop.gmail.com with proto POP3 and options no dns
> user 'myname@gmail.com' with pass "mypassword" is 'narke' here
> options ssl sslcertck sslcertpath '/home/narke/.certs'
> keep
> smtphost localhost

Here ssl keep works properly. Try it without the sslcertck sslcertpath
'/home/narke/.certs' entries.

HTH

Thorn
--
Ed Sullivan will be around as long as someone else has talent.
-- Fred Allen

I think the Fetchmail Slackware package doesn't have the ssl option....
I had this trouble once, and I got the source code and compiled with an
special option..... you can see with ./configure --help

Thorn The Mannamavi wrote:
> On 17 Dec 2005 00:58:27 -0800, Steven Woody Cried: Read These Runes!:
> .....>
> > poll pop.gmail.com with proto POP3 and options no dns
> > user 'myname@gmail.com' with pass "mypassword" is 'narke' here
> > options ssl sslcertck sslcertpath '/home/narke/.certs'
> > keep
> > smtphost localhost
>
> Here ssl keep works properly. Try it without the sslcertck sslcertpath
> '/home/narke/.certs' entries.
>
> HTH
>
> Thorn
> --
> Ed Sullivan will be around as long as someone else has talent.
> -- Fred Allen

yes, after removed 'sslcertck' and 'sslcertpath' options, it works
normally. and, today i found the error came from that google have
changed its certification vendor ( from Thawte to Equifax ). i don't
know what are security implies of removing sslcert option. will that
leak my email password to public?

thanks.

On 18 Dec 2005 04:28:12 -0800, Steven Woody Cried: Read These Runes!:
>
> Thorn The Mannamavi wrote:
>> On 17 Dec 2005 00:58:27 -0800, Steven Woody Cried: Read These Runes!:
>> .....>
>> > poll pop.gmail.com with proto POP3 and options no dns
>> > user 'myname@gmail.com' with pass "mypassword" is 'narke' here
>> > options ssl sslcertck sslcertpath '/home/narke/.certs'
>> > keep
>> > smtphost localhost
>>
>> Here ssl keep works properly. Try it without the sslcertck sslcertpath
>> '/home/narke/.certs' entries.
>>
>> HTH
>>
>> Thorn
>> --
>> Ed Sullivan will be around as long as someone else has talent.
>> -- Fred Allen
>
> yes, after removed 'sslcertck' and 'sslcertpath' options, it works
> normally. and, today i found the error came from that google have
> changed its certification vendor ( from Thawte to Equifax ). i don't
> know what are security implies of removing sslcert option. will that
> leak my email password to public?

Why? It's an ssl connection. But if you need proof just put a sniffer on
your network interface. You'll see all is encrypted.

Thorn
--
Acid -- better living through chemistry.

Thorn The Mannamavi wrote:
> On 18 Dec 2005 04:28:12 -0800, Steven Woody Cried: Read These Runes!:
> >
> > Thorn The Mannamavi wrote:
> >> On 17 Dec 2005 00:58:27 -0800, Steven Woody Cried: Read These Runes!:
> >> .....>
> >> > poll pop.gmail.com with proto POP3 and options no dns
> >> > user 'myname@gmail.com' with pass "mypassword" is 'narke' here
> >> > options ssl sslcertck sslcertpath '/home/narke/.certs'
> >> > keep
> >> > smtphost localhost
> >>
> >> Here ssl keep works properly. Try it without the sslcertck sslcertpath
> >> '/home/narke/.certs' entries.
> >>
> >> HTH
> >>
> >> Thorn
> >> --
> >> Ed Sullivan will be around as long as someone else has talent.
> >> -- Fred Allen
> >
> > yes, after removed 'sslcertck' and 'sslcertpath' options, it works
> > normally. and, today i found the error came from that google have
> > changed its certification vendor ( from Thawte to Equifax ). i don't
> > know what are security implies of removing sslcert option. will that
> > leak my email password to public?
>
> Why? It's an ssl connection. But if you need proof just put a sniffer on
> your network interface. You'll see all is encrypted.
>

i did use 'ssl' option, i just truned off 'sslcertck' option to make it
work.

Roberto Lauretti wrote:
> I think the Fetchmail Slackware package doesn't have the ssl option....
> I had this trouble once, and I got the source code and compiled with an
> special option..... you can see with ./configure --help

i don't think so, Roberto. ldd `which fetchmail` will print a line
contains libssl.so