On Fri, 2014-04-18 at 14:47 +0200, Milan Crha wrote:
> On Thu, 2014-04-17 at 10:12 -0400, dfc wrote:
> > [imapx:A] Starting command (active=1,) A0 LOGIN...
> > [imapx:A] camel_imapx_write: 'LOGIN...'
> > [imapx:A] camel_imapx_read: buffer is 'A0 NO failed: Could not
> > connect to server'
>
On Fri, 2014-04-18 at 14:47 +0200, Milan Crha wrote:
> On Thu, 2014-04-17 at 10:12 -0400, dfc wrote:
> > [imapx:A] Starting command (active=1,) A0 LOGIN...
> > [imapx:A] camel_imapx_write: 'LOGIN...'
> > [imapx:A] camel_imapx_read: buffer is 'A0 NO failed: Could not
> > connect to server'
>
On Thu, 2014-04-17 at 10:12 -0400, dfc wrote:
> [imapx:A] Starting command (active=1,) A0 LOGIN...
> [imapx:A] camel_imapx_write: 'LOGIN...'
> [imapx:A] camel_imapx_read: buffer is 'A0 NO failed: Could not
> connect to server'
Hi,
interesting, at least to me, from the above snippet
> This is for Evolution 3.10.4 under F20
>
> So a couple of questions: does an imap conversation carry information
> about the need to update certificates?
Not really. Depending on how you connect (i.e. if you use SSL to a
dedicated port) then the SSL exchange is before IMAP gets started so
the
On 04/17/2014 10:12 AM, dfc wrote:
Sometime after our university probably updated/fixed
SSL issues associated with Heartbleed
my imap connection via evolution ceased to work and
I haven't been able to retrieve email. IT
more or less waives it off as an issue
for "an unsupported email client".
He
Sometime after our university probably updated/fixed
SSL issues associated with Heartbleed
my imap connection via evolution ceased to work and
I haven't been able to retrieve email. IT
more or less waives it off as an issue
for "an unsupported email client".
Here is the client side view:
[imapx:
