Re: [Evolution] SSL Heartbleed Patch Causes Evolution to Fail

[Marc Hurst <marc hurst independentgeo com>]

Thank you all for responding. I know very little about networks. I'm a 
user, not an IT specialist; so I sincerely appreciate your help.

Pete: Until now, under account settings->security No Encription was 
selected. I changed it to SSL. Tried to Send and Receive, successfully 
received the first 10 messages, then, after a very long pause, dialog 
box text says "Failed on message 11". Dialog box does not close (or 
maybe I didn't waited long enough). After several minutes, I attemped to 
close Evo. Evo did not respond to Close. Minimized it. Several minutes 
later I noticed that it did eventually close.

--Marc


On 04/12/2014 11:40 AM, Pete Biggs wrote:
> On Fri, 2014-04-11 at 19:37 -0400, Marc Hurst wrote:
> > Yesterday, my ISP applied an SSL Patch for "the heartbleed problem".
> > Although I am not using SSL, the patch caused Evolution to fail on all 3
> > of my computers.
> If you aren't using SSL, then no matter what patch they apply to their
> servers, it's not going to matter to you!  Are you sure you aren't using
> SSL? (And the "STARTTLS" configuration *is* SSL.)  And if you aren't
> using SSL, and your ISP provides it, then you really, really should do
> so.
>
> If you *are* using some form of encrypted communication, your ISP would
> have changed their encryption keys at the same time, could it be
> something to do with that?
>
> > I press "Send and Receive", A dialog box says "Receiving message 1 of
> > XXX". After a very long wait, eventually I Evolution gives an error
> > message "Failed to receive message xxxxxxxxxxxxx: Unknown reason."
> You need to run Evolution from the command line, possibly with debugging
> turned on, to see what is actually happening.  We can't really tell you
> what debugging variables to use since you haven't said what version of
> Evolution or what type of account you are talking about.
>
> P.