On Sat, Oct 23, 2010 at 09:08:52AM -0600, Joseph wrote:
> On 10/23/10 08:53, Harry Strongburg wrote:
>> On Sat, Oct 23, 2010 at 12:15:23AM -0600, Joseph wrote:
>>> fetchmail: socket error while fetching from
>>> syscon...@gmail.com@pop.gmail.com
>> Silly mistake there! :)
>>
>> Fetchmail 'user' requires you do NOT have a domain-name added onto it.
>> The domain-name is supplied at the "poll" argument.
>>
>> Have fun.
>
> I've removed the domain name, now the line looks like:
> poll pop.gmail.com with proto POP3 and options no dns user 'syscon780'
> password 'xxxxxxxxxxxx' options ssl sslcertpath /home/joseph/.mutt/cert/
I have had this working for ages and I do not have time to think about
it, but I have the equivalent of syscon...@gmail.com, not syscon780 or
syscon...@gmail.com@pop.gmail.com. I also have sslcertck after ssl. I do
not know whether that would help.
> but it still complains, certificate not trusted.
>
> fetchmail: This means that the root signing certificate (issued for
> /C=US/O=Google Inc/CN=Google Internet Authority) is not in the trusted
> CA certificate locations, or that c_rehash needs to be run on the
> certificate directory. For details, please see the documentation of
> --sslcertpath and --sslcertfile in the manual page.
> fetchmail: Server certificate verification error: certificate not trusted
> fetchmail: Warning: the connection is insecure, continuing anyways. (Better
> use --sslcertck!)
>
> --
> Joseph
--
If a thing's worth doing, it is worth doing badly.
-- G.K. Chesterton
Brian Salter-Duke (Brian Duke) Email: b_duke(AT)bigpond(DOT)net(DOT)au
