Walter Dnes <waltdnes <at> waltdnes.org> writes:
> > So, I am using Claws Mail that downloads e-mails from several > > google mail accounts (all are mine :) and about once or twice > > in a month get into the situation when Claws asks me to verify > > and change the google certificates, first in one direction and > > soon after that (usually during the next downloading of my e-mails) > > - in another. > > I suspect that it is google that makes something wrong here. > > What do you think? > The 2 servers probably have different certificates, which is why you > get this behaviour. I suggest going into "apk mode" and putting an > entry into your hosts file <G>, like... > 173.194.192.108 pop.gmail.com > This will force your system to always use the same server, and avoid > the re-validation every time you hit the other server from the one you > used the previous time. Clusters & Clouds are the sort answer. Everybody (big) is now racing to deploy services; often as if a single IP or dns record or domain name, yet underneath is a cluster of many, many machines. The security is, well, let's just say evolving to be kind. I have no idea about your particular situation; but I've been reading up on cluster and cloud for months now, so here are a few links you might find interesting. Hopefully that illuminate that services that are traditionally single machine bound, are now on top of clusters of machines; and that is a hack-a-day-patch-away scenario that is very fast moving. YMMV [1,2,3]. Mesos is the cluster technology that I follow (or at least try to). I'm trying to get a full set of codes and mesos into the portage tree. If nothing else, folks can use (3+) old machines to build a cluster to see where we are all moving to (clouds and cluster), like it or not, imho. hth, James [1] https://mesosphere.github.io/mesos-dns/docs/tutorial-gce.html [2] https://github.com/mesosphere/mesos-dns [3] https://github.com/Banno/vagrant-mesos [4] http://radar.oreilly.com/2014/01/apache-mesos-open-source-datacenter-computing.html
