| 1 |
On Thu, 2 Apr 2015 15:57:20 +0000 (UTC) James <wireless@×××××××××××.com> wrote: |
| 2 |
|
| 3 |
> Walter Dnes <waltdnes <at> waltdnes.org> writes: |
| 4 |
> |
| 5 |
> |
| 6 |
> > > So, I am using Claws Mail that downloads e-mails from several |
| 7 |
> > > google mail accounts (all are mine :) and about once or twice |
| 8 |
> > > in a month get into the situation when Claws asks me to verify |
| 9 |
> > > and change the google certificates, first in one direction and |
| 10 |
> > > soon after that (usually during the next downloading of my e-mails) |
| 11 |
> > > - in another. |
| 12 |
> |
| 13 |
> > > I suspect that it is google that makes something wrong here. |
| 14 |
> > > What do you think? |
| 15 |
> |
| 16 |
> > The 2 servers probably have different certificates, which is why you |
| 17 |
> > get this behaviour. I suggest going into "apk mode" and putting an |
| 18 |
> > entry into your hosts file <G>, like... |
| 19 |
> |
| 20 |
> > 173.194.192.108 pop.gmail.com |
| 21 |
> |
| 22 |
> > This will force your system to always use the same server, and avoid |
| 23 |
> > the re-validation every time you hit the other server from the one you |
| 24 |
> > used the previous time. |
| 25 |
> |
| 26 |
> |
| 27 |
> Clusters & Clouds are |
| 28 |
|
| 29 |
the cause of problems. :) |
| 30 |
|
| 31 |
But thank you for the links. I will look at them later. |
| 32 |
|
| 33 |
> the sort answer. Everybody (big) is now racing to |
| 34 |
> deploy services; often as if a single IP or dns record or domain name, |
| 35 |
> yet underneath is a cluster of many, many machines. The security is, |
| 36 |
> well, let's just say evolving to be kind. I have no idea about your |
| 37 |
> particular situation; but I've been reading up on cluster and cloud |
| 38 |
> for months now, so here are a few links you might find interesting. |
| 39 |
> Hopefully that illuminate that services that are traditionally single |
| 40 |
> machine bound, are now on top of clusters of machines; and that is |
| 41 |
> a hack-a-day-patch-away scenario that is very fast moving. YMMV [1,2,3]. |
| 42 |
> |
| 43 |
> |
| 44 |
> Mesos is the cluster technology that I follow (or at least try to). |
| 45 |
> I'm trying to get a full set of codes and mesos into the portage tree. |
| 46 |
> If nothing else, folks can use (3+) old machines to build a cluster |
| 47 |
> to see where we are all moving to (clouds and cluster), like it or not, |
| 48 |
> imho. |
| 49 |
> |
| 50 |
> |
| 51 |
> hth, |
| 52 |
> James |
| 53 |
> |
| 54 |
> [1] https://mesosphere.github.io/mesos-dns/docs/tutorial-gce.html |
| 55 |
> |
| 56 |
> [2] https://github.com/mesosphere/mesos-dns |
| 57 |
> |
| 58 |
> [3] https://github.com/Banno/vagrant-mesos |
| 59 |
> |
| 60 |
> [4] |
| 61 |
> http://radar.oreilly.com/2014/01/apache-mesos-open-source-datacenter-computing.html |
| 62 |
> |
| 63 |
> |
| 64 |
> |
| 65 |
> |
| 66 |
> |
Archives