Hi,
On Thu, 2018-11-01 at 12:56 -0400, Dr. John H. Lauterbach wrote:
> concurrent connections are always set to "1".
aha, okay, I see.
> evolution does not allows TLS when the server wants STARTTLS or the
> reverse.
The STARTTLS and TLS operate on different ports usually. But you are
On Thu, 2018-11-01 at 17:26 +0100, Milan Crha via evolution-list wrote:
> Hi,
> On Thu, 2018-11-01 at 11:02 -0400, Dr. John H. Lauterbach wrote:
> Evolution has a problem.
> I'd not call it Evolution problem, the server rejects the credentials,not
> Evolution. I doubt Evolution garbles your
Hi,
On Thu, 2018-11-01 at 11:02 -0400, Dr. John H. Lauterbach wrote:
> Evolution has a problem.
I'd not call it Evolution problem, the server rejects the credentials,
not Evolution. I doubt Evolution garbles your credentials anyhow when
you enable the other account/s. It's not the case
Thank you, Milan. I would NOT have posted the output of CAMEL_DEBUG=imapx:io
evolution UNLESS I had first verfied login credentials.
Adding the second imapx account causes the first (and working) account to have
an authentication failure.
In addition, all AUTHENTICATION TYPES were verified
On Thu, 2018-11-01 at 10:12 -0400, Dr. John H. Lauterbach wrote:
> [imapx:A] I/O: 'A00103 LOGIN ...'
> [imapx:A] I/O: 'A00103 NO [AUTHENTICATIONFAILED] Authentication failed.'
Hi,
all login attempts end like the above. It's what the server returned,
it doesn't like your credentials
RE: $ CAMEL_DEBUG=imapx:io evolution
Thank you for the suggestion. Please note that all the imapx accounts work fine
together on MS Outlook 365. imapx accounts that have worked fine at various
times in the past, aren't working now. Only imapx account now that is working
is on servers owned by
