Evolution will not authenticate on Exchange

Forgot to add, this is the error message I keep getting over and over:

e-data-server-ui-Message: Key file does not have key 'exchange:__rci%5cmichael.carpenter;<email address hidden>com_'
e-data-server-ui-Message: Key file does not have key 'exchange:__rci%5cmichael.carpenter;<email address hidden>com_' in group 'Passwords-Exchange'

I have this same problem.

I've had evolution and exchange working for quite some time now on Gutsy, but upon upgrading to Hardy it stopped working.

We use HTTPS (only) for OWA at our company.

I get the same error as above.

I've tried setting the OWA URL to:

https://email.company.com/
https://email.company.com/exchange
https://email.company.com/exchange/username

And I've tried setting the username to:

username
DOMAIN\username
DOMAIN/username
<email address hidden>

Nothing seems to work.

I've pretty much attempted all of those options as well. It just refuses to work. Starting to drive me crazy because I know it was working before!

Same thing here. Just installed Hardy today and cannot get Evo to work with exchange keep getting the failed url error. My debug log looks similar to yours. We to are also using https and not http. This was working in 7.10.

I've had some success by creating a new exchange account, suggesting the problem may be caused by some artefact of upgrading the evolution instance. After creating a new account and restarting evo, I could see messages on the exchange server again. Did crash after that, but nothing to suggest it was particularly exchange-related.

Wish I could say I had the same luck. I still can't create an account. It fails even when trying to set up a new account.

Mine was a fresh install and hasn't worked once. Still trying to figure this out, tried creating a IMAP connection and was able to get mail. Then tried changing it from IMAP to Exchange on the account but Evo crashed. Restart and it tries to connect but never really gets any further. No lovin... :(

Still hacking looking for resolution.

Posted this in another bug I think is similar or dup.

https://bugs.launchpad.net/ubuntu/+source/evolution-exchange/+bug/209438

Turned on some debug. E2k_Debug=4 doesn't produce anything.

Evolution Exchange Storage up and running
E2K_DEBUG=4
> GET /exchange/jarosenf/ HTTP/1.1
> Soup-Debug-Timestamp: 1207362670
> Soup-Debug: SoupSessionSync 1 (0x80df8b8), SoupMessage 1 (0x80b0900), SoupSocket 1 (0x80eb608)
> Host: email.XXXXXX.com
> Accept-Language: en-US, en
> User-Agent: Evolution/2.22.0

But Camel_Debug=all produces some errors.

>CamelException.set(0x83a21ac, 2, 'Could not authenticate to server. (Password incorrect?)
>
>')
>Thread b5830b90 >
>Get folder info(0x836ca88:exchange://XXXXX%5cjarosenf;<email address hidden>/, '<null>') =
>< b5830b90 >
>CamelException.set(0x85abb84, 2, 'Could not authenticate to server. (Password incorrect?)

The password is correct as I use it everyday logging into other corp resources.

Still fails even with latest evolution updates....

still fails even with release candidate april 21

Mine fails as well with this error:

Could not connect to server .

Make sure the URL is correct and try again.

It's STILL a problem! I upgraded from 7.10 to 8.04 on Apr 30th, and the Evolution Exchange plugin is now broken. I've been using the Exchange plugin for Evolution with issue since 6.04.

My errors:

e-data-server-ui-Message: Key file does not have key 'exchange:__fcpsedu%5ctdeboeser;auth_Basic@151.188.17.145_'

(evolution:10336): camel-CRITICAL **: camel_object_is: assertion `o != NULL' failed

(evolution:10336): camel-CRITICAL **: camel_object_ref: assertion `CAMEL_IS_OBJECT(o)' failed

e-data-server-ui-Message: Key file does not have key 'exchange:__fcpsedu%5ctdeboeser;auth_Basic@151.188.17.145_'
e-data-server-ui-Message: Key file does not have key 'exchange:__fcpsedu%5ctdeboeser;auth_Basic@151.188.17.145_'
...

I have the same problem here. But I think I know why this is happening, at least in my case.

Here is a part of the log produced by the Evolution:

> GET /exchange HTTP/1.1
> Soup-Debug-Timestamp: 1210055753
> Soup-Debug: SoupSessionSync 1 (0x8b4dc10), SoupMessage 2 (0x846e418), SoupSocket 2 (0x8e12940)
> Host: mail.company.com
> Authorization: NTLM TlRMTVNTUAABAAAABoIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMAAAAAAAAAAwAAAA
> User-Agent: Evolution/2.22.1

< HTTP/1.1 302 Moved Temporarily
< Soup-Debug-Timestamp: 1210055754
< Soup-Debug: SoupMessage 2 (0x846e418)
< Location: https://mail.company.com/exchweb/bin/auth/owalogon.asp?url=https://mail.company.com/exchange&reason=0&replaceCurrent=1
< Set-Cookie: sessionid=; path=/; expires=Thu, 01-Jan-1970 00:00:00 GMT
< Set-Cookie: cadata=; path=/; expires=Thu, 01-Jan-1970 00:00:00 GMT
< Connection: close
< Content-Length: 0

> GET /exchweb/bin/auth/owalogon.asp?url=https://mail.company.com/exchange&reason=0&replaceCurrent=1 HTTP/1.1
> Soup-Debug-Timestamp: 1210055755
> Soup-Debug: SoupSessionSync 1 (0x8b4dc10), SoupMessage 2 (0x846e418), SoupSocket 3 (0x8e12b38), restarted
> Host: mail.company.com
> User-Agent: Evolution/2.22.1
> Authorization: NTLM TlRMTVNTUAABAAAABoIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMAAAAAAAAAAwAAAA

< HTTP/1.1 200 OK
< Soup-Debug-Timestamp: 1210055757
< Soup-Debug: SoupMessage 2 (0x846e418)
< Cache-Control: no-cache
< Pragma: no-cache
< Content-Length: 8349
< Content-Type: text/html; charset=utf-8
< Expires: -1
< Server: Microsoft-IIS/6.0
< X-Powered-By: ASP.NET
< X-AspNet-Version: 2.0.50727
< X-OWA-Version: 8.1.240.5
< Date: Tue, 06 May 2008 06:37:17 GMT
** (evolution:19205): WARNING **: Invalid uri 'owaauth.dll'

(evolution:19205): libsoup-CRITICAL **: soup_message_set_request: assertion `SOUP_IS_MESSAGE (msg)' failed
e-data-server-ui-Message: Key file does not have key 'exchange:__qliu;<email address hidden>com_' in group 'Passwords-Exchange'

From this, I can see evolution got an invalid URI 'owaauth.dll'. Such URI is the used as the POST URI of a form-based authentication of OWA. Here is the HTML code from the OWA authentication page:

<form action="owaauth.dll" method="POST" name="logonForm" autocomplete="off">
<input type="hidden" name="destination" value="https://mail.company.com/exchange">
<input type="hidden" name="flags" value="0">
<input type="hidden" name="forcedownlevel" value="0">

Our company uses a customized HTML page as the form-based authentication page. Here, the action URI is a relative URI containing only "owaauth.dll". It is relative to "https://mail.company.com/exchweb/bin/auth/owalogon.asp?url=https://mail.company.com/exchange&reason=0&replaceCurrent=1". So the actual absolute URI should be "https://mail.company.com/exchweb/bin/auth/owaauth.dll". Firefox and Internet Explorer both have the correct behavior, while evolution-exchange connector thought "owaauth.dll" is an absolute URI (though in most cases, it is an absolute URI like "/exchweb/bin/auth/owaauth.dll").

The fix should be parsing the POST URIs per standard like Firefox and IE do.

I'm suprised to see the importance hasn't been set. No one cares about it? For people like me who love to use Ubuntu at work it's a real problem! Could somebody set a higher priority on this bug?

Yeah, i got the same bugs error, exactly, only workaround i found .. is using IMAP and for some lucky reason that works, but i really hope this bug can be fixed ASAP.

I know it does not really help but while googling on the subject two weeks ago, I found that *someone* (a developer) had posted a blog comment about the same symptom. The comment was about a mix of library versions that, when linked with Evo, would lead to the issue. Overall, special care had to be taken with the _exact_ lib versions.

I forgot to log the URL and can't find it back but I would suggest checking with the evo developers to know which exact libraries (version) evo depends on.

SOLVED:

actually to get around this issue a coworker of mine found out that if you create an entry in the /etc/hosts file mapping the ip of your the exchange server to the hostname of the server it actually was looking for it worked.

in my case anyways when it would try to authenticate it would be fine, but when actually connecting to the exchange server it was trying a different server, so not sure if this would be a bug or something to do with our setup.

I think the solution is related to your specific environment and I am suspecting you have something different than others. I took sniffer traces and could see evolution was connecting to the right server. TCP starts but after the client sends the first HELLO, the server resets the connection. The debugs are the same as in this bug report but the network behavior is the same as in #209438.

Eventually, I think that Bug #209438, #207723 and #225986 are actually the same (duplicates).

wow thats pretty intersting.. ill have to load up wireshark and see what goes in the packets also, i had a default install of 7.10 and updated packages of evolution, and im now using 804 and latest evolution. and everything is working 100% email, GAB, calendar.

Now this is also interesting. I thought evo 2.22 (what this bug relates to) was only in Hardy (8.04) -- were you running evo 2.22 in Gutsy ? I see that a number of people managed to fix the problem by running exchange-connector-setup-2.22 manually instead of declaring the Exchange server in Evo's preferences. This does not help everyone and certainly not my case.

Now: did you set up exchange in 7.10 (what evo release) then upgrade to 8.04 or did you setup the account from scratch in 8.04 ?

I was actually running 7.10 earlier , and had the same issue, i rebuilt 8.04 from scratch, only thing i kept was my /home .. so what is going on with your problem??

your home still contains the .goncf/ and .evolution/ directories. Have you tried moving these away and see if you can reconfigure the Exchange server from scratch ? Make sure you keep a copy, though :)

For your case, I mostly suspect that the Exchange server name is resolved by WINS on other users computers (assuming other users use Outlook etc. on Windows) while your DNS accepts the same name but resolves to a different address.

In my case, everything worked well in 7.10. I installed 8.04 from scratch, not even keeping my home directory. I am now unable to set up an exchange account. I hit the exact same problem as described in the case ("Key file does not have key ...") and the SSL woes described in bug #207723. I am sure evo tries to reach the proper server as checked with a sniffer.

This bug is really about users migrating from 7.10 (working) to 8.04 (not working). I do see people who claim 8.04 works for them and I am very curious what the difference is.

Qi Liu's analysis is also interesting but I do not think my company uses a customize page on OWA (looks pretty bland); I wonder about others.

Same here. Apple Mail is perfectly able to authenticate, but Evo says that there's an "Unknown Error" and demands me to check my settings (username, password, url) which are correct.

I stumbled upon this problem this morning.

I have 2 systems running, one with 7.10 and the other one with 8.04. Now I needed to configure evolution on my 8.04 system and had the same issue, that it was coming back over and over again with the password prompt. No inbox available either, nothing.

I took the easy way out by forcing a downgrade of evolution-exchange while the 'not working' mail profile was still in evolution. I launched it and cause of dependency mismatches, nothing was available either. After that I decided just to wait for a solution, search a bit on the net for possible solutions (nowhere to be found, unless you build it yourself it seems)

Cause of the dependency issues, normal updates won't work either anymore. So I did an 'apt-get -f install' which causes the evolution-exchange to update to the current version again.

I launched evolution again to configure another account and discovered, that miraculously the exchange profile was working!

I'm not into linux/C(++)/apt yet, but maybe there is a conversion issue, together with creating a new empty exchange profile over here.

Could someone test this 'work-around' over here?

1) leave the not working exchange profile in your current version of evolution
2) download evolution-exchange_2.12.0-0ubuntu1_amd64.deb (or the i386 alternative if you're running 32 bit) from http://packages.ubuntu.com/gutsy/evolution-exchange
3) close evolution and install the package by: apt-get --force-all -i evolution-exchange_2.12.0-0ubuntu1_(architecture-you-have).deb
4) fire up evolution and see the profile is in there, but without any folders in it (this part I forgot but I might have tried work off / online again to force an authentication, which is almost at the bottom of the file menu)
5) close evolution
6) run apt-get -f install again to recover from dependency issues
7) fire up evolution

For me, upgrading to Intrepid alpha was the fix.

I can confirm this bug on my fully updated Ubuntu 8.04.1

I tried to setup a new exchange account from scratch, but cannot authenticate against my corporate 2003 Exchange server (using HTTPS)

Console logging:
evolution-shell-Message: Killing old version of evolution-data-server...
e-data-server-ui-Message: Unable to find password(s) in keyring (Keyring reports: No matching results)
e-data-server-ui-Message: Key file does not have group 'Passwords-Exchange'
(evolution:8265): e-data-server-ui-WARNING **: Unable to find password(s) in keyring (Keyring reports: No matching results)
(evolution:8265): e-utils-WARNING **: No parent set, or default parent available for error dialog

Note: I seem to get redirected to /cookieauth.dll?GetLogon?url=%2FDefault.asp&reason=0/

I can confirm that this fixed about 6 updates ago

Tom de
------Original Message------
From: tom.delusinne
Sender: <email address hidden>
To: Tom De
ReplyTo: Bug 207723
Sent: Aug 5, 2008 4:30 PM
Subject: [Bug 207723] Re: Evolution will not authenticate on Exchange

I can confirm this bug on my fully updated Ubuntu 8.04.1

I tried to setup a new exchange account from scratch, but cannot
authenticate against my corporate 2003 Exchange server (using HTTPS)

Console logging:
evolution-shell-Message: Killing old version of evolution-data-server...
e-data-server-ui-Message: Unable to find password(s) in keyring (Keyring reports: No matching results)
e-data-server-ui-Message: Key file does not have group 'Passwords-Exchange'
(evolution:8265): e-data-server-ui-WARNING **: Unable to find password(s) in keyring (Keyring reports: No matching results)
(evolution:8265): e-utils-WARNING **: No parent set, or default parent available for error dialog

Note: I seem to get redirected to
/cookieauth.dll?GetLogon?url=%2FDefault.asp&reason=0/

** Changed in: evolution-exchange (Ubuntu)
       Status: New => Confirmed

--
Evolution will not authenticate on Exchange
https://bugs.launchpad.net/bugs/207723
You received this bug notification because you are a direct subscriber
of the bug.

Sent from my Verizon Wireless BlackBerry

TomDeBoeser,

What do you mean fixed 6 updates ago?
With an up-to-date Ubuntu Hardy, I still get the same error.

I think he means Intrepid updates

2008/8/6 tom.delusinne <email address hidden>:
> TomDeBoeser,
>
> What do you mean fixed 6 updates ago?
> With an up-to-date Ubuntu Hardy, I still get the same error.
>
> --
> Evolution will not authenticate on Exchange
> https://bugs.launchpad.net/bugs/207723
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Clément Lorteau
www.lorteau.fr | 06 78 57 41 94

Does anyone know if the Intrepid updates will be 'backported' to Hardy? (not sure if that's the right term). Another way of asking this is, will Hardy see these fixes or do we need to wait for Intrepid?

Mike

I think I've got the same problem as others here. I can get past the "Authentication" that is requested during creation of the Evoluation account, but then I can never actually connect.

Here is the output from the commend line. Is there some workaround until a fix comes out?

e-data-server-ui-Message: Unable to find password(s) in keyring (Keyring reports: No matching results)
e-data-server-ui-Message: Key file does not have group 'Passwords-Exchange'
e-data-server-ui-Message: Unable to find password(s) in keyring (Keyring reports: No matching results)
e-data-server-ui-Message: Key file does not have group 'Passwords-Exchange'
e-data-server-ui-Message: Unable to find password(s) in keyring (Keyring reports: No matching results)
e-data-server-ui-Message: Key file does not have group 'Passwords-Exchange'

(evolution:12902): evolution-mail-WARNING **: Error occurred while existing dialogue active:
Could not authenticate to server. (Password incorrect?)

I found out that I got redirected to /cookieauth.dll?GetLogon?url=%2FDefault.asp&reason=0/ and that this means that the Outlook server is behind an MS ISA proxy server
This was fixed in Evolution 2.12, but does apparently not work anymore...

Hi got the same probleme with 8.04 build from scratch. It is imposible o authenticate against exchange. Is there any update or fix? On the website I saw that the actual download is 2.24.0 but when I install it via apt-get I got version 2.22 from evolution and evolution-exchange.

I've not tried it, but was thinking that It may be possible to load a non-Hardy version (even live cd) and get Evolution/Exchange working. Then create a backup to be moved to the Hardy install and then restored.

I've been running Intrepid for many months now, but I still have this problem.

I know our webmail uses the ISA proxy thing.

I know I have to use a domain in front of my username.
When I don't, it spews out a lot of white lines in the terminal and takes 2 minutes to tell me it failed. (Could not connect to server. Make sure the URL is correct and try again)

When I do use the domain in front of my username (w2k\) it immediately tells me it failed, but a bit more hopeful: Could not find Exchange Web-storage system. (Should OWA run on a different path, ...)

Something that worked for me was clearing the "mailbox name" under exchange settings, and reauthenticating on that page. The auth went through fine, and it filled out the mailbox again (exactly the same way) but after a restart of evolution it worked fine.

I too have the same problem and think what Qi Liu wrote on 2008-05-06: (permalink) is accurate. Is there going to be some attempt to correct this?

I can confirm that same problem still exists SEVEN MONTHS after the first report. This is why people say Linux is not ready for primetime. Solving any Exchange client issues quickly and efficiently is the key to making inroads with the business user community. Where is the pride in ownership on this project?

I absolutely agree with Johnny Delay.
I'm using Ubuntu as a so called "business user" and it would help me convince other colleagues who are frustrated with Vista to at least consider trying Ubuntu as a secondary OS. (same as I did)
I'm also under pressure to start using the Exchange calendar (and I'm working around that by using a smartphone which has a working Exchange client).

So, Exchange support is vital to us business users that choose Ubuntu before Windows or Apple, therefore I believe that this bug is directly related to https://bugs.launchpad.net/ubuntu/+bug/1

This was working until today. It still works on my Debian Lenny machine 2.22.3.1. Stopped working with Ubuntu Intrepid machine 2.24.1. I can authenticate with the account settings dialog, but not when actually trying to get mail.

It started out with just losing connection to the exchange backend process, and now can't authenticate at all. I know it isn't the server, because it works in Firefox and Lenny.

I can confirm that this problem still exists in a fully patched 8.10 x32 install.

e-data-server-ui-Message: Unable to find password(s) in keyring (Keyring reports: No matching results)
e-data-server-ui-Message: Key file does not have group 'Passwords-Exchange'

Actually i have confirmed, that in 8.10 i can successfully connect.

--
Omar Samad

On Wed, Nov 5, 2008 at 10:08 PM, ChrisGibbs <email address hidden> wrote:
> I can confirm that this problem still exists in a fully patched 8.10 x32
> install.
>
> e-data-server-ui-Message: Unable to find password(s) in keyring (Keyring reports: No matching results)
> e-data-server-ui-Message: Key file does not have group 'Passwords-Exchange'
>
> --
> Evolution will not authenticate on Exchange
> https://bugs.launchpad.net/bugs/207723
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "evolution-exchange" source package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: evolution-exchange
>
> Hardy Heron
>
> Evolution: 2.22.0-0ubuntu2
> Evolution-Exchange: 2.22.0-0ubuntu1
>
> Problem:
> Evolution was working perfectly fine with my work Exchange OWA server before upgrading. After the upgrade it is unable to authenticate on the server at all! I have verified that the password and OWA server are correct, as I can still log on using the web interface via firefox. Thought maybe it could have been a config error, so I got rid of ~/.evolution, but now I can't even create an exchange account. Every time I attempt to go through the wizard it complains I cannot be authenticated.
>

On Wednesday 05 November 2008 10:08:29 pm ChrisGibbs wrote:
> I can confirm that this problem still exists in a fully patched 8.10 x32
> install.
>
> e-data-server-ui-Message: Unable to find password(s) in keyring (Keyring
> reports: No matching results) e-data-server-ui-Message: Key file does not
> have group 'Passwords-Exchange'

I was able to fix it by removing the account, creating a new one, and waiting
a day. Today, everything works fine again.

So what's the secret sauce to get it to work in Intrepid? I have a fresh install and as such a non-working evolution/exchange. I cannot 'delete' the account as I cannot create it.

On a different note. Does anyone have any alternatives to Evolution for Exchange calendaring? Other than OWA or outlook in a virtual environment!

Mike

Go for imap .. The exchange plugin fucked up my blackberry mail delivery
Removed all refeneces to the exchange plugin and then went with imap

Sent from my BlackBerry® wireless device

-----Original Message-----
From: Mike Phillips <email address hidden>

Date: Tue, 11 Nov 2008 01:54:52
To: <email address hidden>
Subject: [Bug 207723] Re: Evolution will not authenticate on Exchange

So what's the secret sauce to get it to work in Intrepid? I have a
fresh install and as such a non-working evolution/exchange. I cannot
'delete' the account as I cannot create it.

On a different note. Does anyone have any alternatives to Evolution for
Exchange calendaring? Other than OWA or outlook in a virtual
environment!

Mike

--
Evolution will not authenticate on Exchange
https://bugs.launchpad.net/bugs/207723
You received this bug notification because you are a direct subscriber
of the bug.

Status in “evolution-exchange” source package in Ubuntu: Confirmed

Bug description:
Binary package hint: evolution-exchange

Hardy Heron

Evolution: 2.22.0-0ubuntu2
Evolution-Exchange: 2.22.0-0ubuntu1

Problem:
Evolution was working perfectly fine with my work Exchange OWA server before upgrading. After the upgrade it is unable to authenticate on the server at all! I have verified that the password and OWA server are correct, as I can still log on using the web interface via firefox. Thought maybe it could have been a config error, so I got rid of ~/.evolution, but now I can't even create an exchange account. Every time I attempt to go through the wizard it complains I cannot be authenticated.

I've been happily using Thunderbird for IMAP email views. But I was hoping to not have to use Outlook/Smartphone/OWA for calendaring and tasks. Are you saying that IMAP can be used for access to non-email Exchange views of calendaring?

Mike

Yeah try it out I've been gettin my calendar fine through the imap plugin

Sent from my BlackBerry® wireless device

-----Original Message-----
From: Mike Phillips <email address hidden>

Date: Tue, 11 Nov 2008 02:29:44
To: <email address hidden>
Subject: [Bug 207723] Re: Evolution will not authenticate on Exchange

I've been happily using Thunderbird for IMAP email views. But I was
hoping to not have to use Outlook/Smartphone/OWA for calendaring and
tasks. Are you saying that IMAP can be used for access to non-email
Exchange views of calendaring?

Mike

--
Evolution will not authenticate on Exchange
https://bugs.launchpad.net/bugs/207723
You received this bug notification because you are a direct subscriber
of the bug.

Status in “evolution-exchange” source package in Ubuntu: Confirmed

Bug description:
Binary package hint: evolution-exchange

Hardy Heron

Evolution: 2.22.0-0ubuntu2
Evolution-Exchange: 2.22.0-0ubuntu1

Problem:
Evolution was working perfectly fine with my work Exchange OWA server before upgrading. After the upgrade it is unable to authenticate on the server at all! I have verified that the password and OWA server are correct, as I can still log on using the web interface via firefox. Thought maybe it could have been a config error, so I got rid of ~/.evolution, but now I can't even create an exchange account. Every time I attempt to go through the wizard it complains I cannot be authenticated.

On Monday 10 November 2008 8:54:52 pm Mike Phillips wrote:
> So what's the secret sauce to get it to work in Intrepid?  I have a
> fresh install and as such a non-working evolution/exchange.  I cannot
> 'delete' the account as I cannot create it.

I fixed it by creating a new account and deleting the old one. What do you
mean you can't create a new account?

On Monday 10 November 2008 9:10:47 pm mnk0 wrote:
> Go for imap .. The exchange plugin fucked up my blackberry mail delivery
> Removed all refeneces to the exchange plugin and then went with imap

I find Microsoft's non-standard implementation of IMAP on an Exchange 2003
server to be abysmal Your mileage may vary.

I'm not sure why accessing your exchange account via OWA would mess up your
blackberry delivery. That would mean webmail exchange access (OWA) would
also screw it up. If this is true, you have either a bug in your blackberry
or a misconfigured blackberry (BES) server.

OK, well maybe it was just a coincidence, but when running my
evolution 2.24.1 exchange plugin .. the messages would appear in my
inbox, and then vanish, from the server also,

--
Omar Samad

On Tue, Nov 11, 2008 at 11:23 AM, art alexion <email address hidden> wrote:
> On Monday 10 November 2008 9:10:47 pm mnk0 wrote:
>> Go for imap .. The exchange plugin fucked up my blackberry mail delivery
>> Removed all refeneces to the exchange plugin and then went with imap
>
> I find Microsoft's non-standard implementation of IMAP on an Exchange 2003
> server to be abysmal Your mileage may vary.
>
> I'm not sure why accessing your exchange account via OWA would mess up your
> blackberry delivery. That would mean webmail exchange access (OWA) would
> also screw it up. If this is true, you have either a bug in your blackberry
> or a misconfigured blackberry (BES) server.
>
> --
> Evolution will not authenticate on Exchange
> https://bugs.launchpad.net/bugs/207723
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "evolution-exchange" source package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: evolution-exchange
>
> Hardy Heron
>
> Evolution: 2.22.0-0ubuntu2
> Evolution-Exchange: 2.22.0-0ubuntu1
>
> Problem:
> Evolution was working perfectly fine with my work Exchange OWA server before upgrading. After the upgrade it is unable to authenticate on the server at all! I have verified that the password and OWA server are correct, as I can still log on using the web interface via firefox. Thought maybe it could have been a config error, so I got rid of ~/.evolution, but now I can't even create an exchange account. Every time I attempt to go through the wizard it complains I cannot be authenticated.
>

On Tuesday 11 November 2008 11:44:30 am mnk0 wrote:
> OK, well maybe it was just a coincidence, but when running my
> evolution 2.24.1 exchange plugin .. the messages would appear in my
> inbox, and then vanish, from the server also,

If that happens only intermittently, and with a few messages, it may be part
of a different bug. The messages are still on the server. If you access
them via a web interface, move them to another folder and then back, they
will reappear in your inbox.

I don't know the bug number for that one.

OH k, thanks for the tip, yeah i kinda felt that this thread went a
little off topic with that one, but intersting to know that its' been
actually reported as a bug. Ill try to reply to that thread now.

--
Omar Samad

On Tue, Nov 11, 2008 at 2:23 PM, art alexion <email address hidden> wrote:
> On Tuesday 11 November 2008 11:44:30 am mnk0 wrote:
>> OK, well maybe it was just a coincidence, but when running my
>> evolution 2.24.1 exchange plugin .. the messages would appear in my
>> inbox, and then vanish, from the server also,
>
> If that happens only intermittently, and with a few messages, it may be part
> of a different bug. The messages are still on the server. If you access
> them via a web interface, move them to another folder and then back, they
> will reappear in your inbox.
>
> I don't know the bug number for that one.
>
> --
> Evolution will not authenticate on Exchange
> https://bugs.launchpad.net/bugs/207723
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "evolution-exchange" source package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: evolution-exchange
>
> Hardy Heron
>
> Evolution: 2.22.0-0ubuntu2
> Evolution-Exchange: 2.22.0-0ubuntu1
>
> Problem:
> Evolution was working perfectly fine with my work Exchange OWA server before upgrading. After the upgrade it is unable to authenticate on the server at all! I have verified that the password and OWA server are correct, as I can still log on using the web interface via firefox. Thought maybe it could have been a config error, so I got rid of ~/.evolution, but now I can't even create an exchange account. Every time I attempt to go through the wizard it complains I cannot be authenticated.
>

I went through just about every reference I could find about this, and eventually this worked for me;

Username: domain\username (not my email address, my username)
OWA URL: https://mobile.mycompany.co.za
Mailbox: USERNAME (ie - in CAPITALS)

I spent about 3 hours trying various things, so I might have missed something else that's required, but these are the changes that made it work for me, so if it helps someone, I say pielle gert!

(PS. I think the actual "viola" moment was removing the trailing "/" from the OWA URL, but that's just a hunch....)

@Paul,

   Thanks for the tip, but unfortunately for me it did not work! :( Thanks for trying though.

I wish I had enough skills to help as most folks in my company are flipping over to Apple/Mac! That makes me sad!

Mike

It sounds like voodoo but Timothy's work around did indeed fix the problem for me, probably only temporarily though.
https://bugs.launchpad.net/ubuntu/+source/evolution-exchange/+bug/207723/comments/37

In summary, and assuming your setup worked and then mysteriously stopped working:
1. Delete your mailbox name from the Exchange
2. Authenticate

I am just trying to set it up for the first time. I have the document from my company on how to do it on evolution 2.2.2. I follow the same steps and always fail authentication. I have also tried the same voodoo suggested above with upper and lower case this and that, slashes, backslashes, et cetera. I still think what Qi Liu wrote on 2008-05-06: (permalink) is accurate.

This still fails on 2.24.2. I really do not want to go back to Windows, but IMAP is not getting the job done for me.

Is anyone actually working on this problem, or do we just share the odd success story or commiserate here?

I have heard of instances of proxy servers front ending the actual exchange servers. Some of the proxy servers:

1) Are not SSL compatible with the SSL/crypto library that evolution calls - USE HTTP instead

2) The URL: http://email.foo.com may in fact point to the front end and/or proxy and you may need to determine the actual server your mailbox is located on via some MS Exchange magic. Once you have determined this physical exchange server's address you would not use the http://email.foo.com url but rather change it to http://server-1A.foo.com (for example!)

HTH,

Mike

All access is SSL, so all URL are https for this purpose.
s
On Tue, 2008-12-02 at 19:40 +0000, Mike Phillips wrote:
> I have heard of instances of proxy servers front ending the actual
> exchange servers. Some of the proxy servers:
>
> 1) Are not SSL compatible with the SSL/crypto library that evolution
> calls - USE HTTP instead
>
> 2) The URL: http://email.foo.com may in fact point to the front end
> and/or proxy and you may need to determine the actual server your
> mailbox is located on via some MS Exchange magic. Once you have
> determined this physical exchange server's address you would not use the
> http://email.foo.com url but rather change it to http://server-
> 1A.foo.com (for example!)
>
> HTH,
>
> Mike
>

I configured mine with http and it works on Hardy

Greg wrote:
> All access is SSL, so all URL are https for this purpose.
> s
> On Tue, 2008-12-02 at 19:40 +0000, Mike Phillips wrote:
>
>> I have heard of instances of proxy servers front ending the actual
>> exchange servers. Some of the proxy servers:
>>
>> 1) Are not SSL compatible with the SSL/crypto library that evolution
>> calls - USE HTTP instead
>>
>> 2) The URL: http://email.foo.com may in fact point to the front end
>> and/or proxy and you may need to determine the actual server your
>> mailbox is located on via some MS Exchange magic. Once you have
>> determined this physical exchange server's address you would not use the
>> http://email.foo.com url but rather change it to http://server-
>> 1A.foo.com (for example!)
>>
>> HTH,
>>
>> Mike
>>
>>
>
>

Same problem here with a fully patched Intrepid.

tried all different combinations and variations.
Our exchange only offers https, ho http

Up until today when I updated my 8.10 install evolution had been working great. The only thing that changed was the 8.10 update, no configuration or account changes. This is a show stopping bug, unable to work at the moment. I am at a loss how this managed to get released or has not been corrected when you look at how long this bug has been listed here.

Done all the usual steps listed above and evolution just refuses to work. No need to list my debug info as it exactly the same as everyone has posted but I shall anyway.

e-data-server-ui-Message: Unable to find password(s) in keyring (Keyring reports: No matching results)
e-data-server-ui-Message: Key file does not have group 'Passwords-Exchange'
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:8161): DEBUG: mailto URL command: evolution %s
** (evolution:8161): DEBUG: mailto URL program: evolution
old group, new source
(evolution:8161): camel-exchange-provider-WARNING **: Unable to load Exchage summary for folder personal: no such table: personal

 Error syncing up the counts
(evolution:8161): camel-exchange-provider-WARNING **: Unable to load Exchage summary for folder personal/Deleted Messages: no such table: personal/Deleted Messages

(evolution:8161): evolution-mail-WARNING **: Failed to refresh folders: Lost connection to Evolution Exchange backend process

and so on....

My best recommendation to anyone who must use exchange features is to run windows in Virtualbox and use outlook. You could the Mac route but Entourage has it's own issues. having been a LINUX advocate sine Ygdrasil and managing large scale internet ops on LINUX that still today we can't get email right. :(

Another annoying "I got it to work but I'm not quite sure how" post:

I had the same problem this morning when I reinstalled a system with 8.10, upgraded everything and tried to set up evolution again (without just copying in the settings). As an aside, I initially googled for the keystore error, but that's actually a different bug, it just means that evolution won't store your password. It's annoying but not fatal. Other sites also recommend Thunderbird, but it doesn't do Exchange calendars, so it's not a solution to this.

So I followed the tips above, removed my username and re-authenticated, which didn't work initially. I puzzled over the username field, it seems to want a forward slash, but then the login box after that has a backslash, and the domains at my work seem to be uppercase a lot, so I tried a bit of CAPITAL/username, CAPITAL\username lowercase\username etc. No avail.

It nearly worked, as above, the actual settings screen asks you to authenticate and that appears to actually work and retrieve your mailbox name, which it could only know if it had worked, but then opening the mail account didn't work. I logged into webmail itself to make sure that was working and at the address I was putting into the settings, which it is.

So after failing a lot, here's what I think I did:
disabled the account
put in my username as CAPITAL/username
put in the webmail url (http://ukmail.<mydomain>.com/exchange/) - the trailing slash REALLY shouldn't affect this, but who knows, someone above seems to have changed that too, but the other way round. I hit authenticate and it worked, then saved it, re-enabled the check box for the account and it seemed to work. No idea why really.

So perhaps settings get cached along with the URL in evolution and not cleared properly, and that's why adding or removing a slash can suddenly make it work, if you've fixed the username or something else along the way. Pure speculation though. From all this, the Evolution Exchange connector seems to be incredibly flaky, but considering it just uses http to the web client app, it's probably something like string parsing issues making it really fragile to reconfigure.

Work appears to be using Microsoft Exchange 2003, if any absolute champion out there wants to try to fix this I can get more details and snapshots of the data being returned from the server, whatever you like.

This looks related to Bug #248705, based on some posts, specifically #14. However, I suspect that some posts are regarding different bugs, so I'd like the opener of the bug (Michael Carpenter) to confirm, please.

Looks similar. Unfortunately I can't duplicate exactly at the moment. Exchange server at work has been upgraded to 2007 and Evolution detects it as exchange 5.5 and refuses to continue. Setting the debug level does give behaviour similar to what you describe, although I'm not seeing any posts.

I see the following chain of events:

GET /owa/
401 Unauthorized
GET /owa/ (with authorization header)
302 Moved ( Location https://owaurl/owa/auth/logon.aspx?url=newowaurl )

And then Evolution complains exchange is version 5.5 and continues no further.

On Sat, 2009-01-10 at 16:56 +0000, Michael Carpenter wrote:
> Looks similar. Unfortunately I can't duplicate exactly at the moment.
> Exchange server at work has been upgraded to 2007 and Evolution detects
> it as exchange 5.5 and refuses to continue. Setting the debug level does
> give behaviour similar to what you describe, although I'm not seeing any
> posts.
>
> I see the following chain of events:
>
> GET /owa/
> 401 Unauthorized
> GET /owa/ (with authorization header)
> 302 Moved ( Location https://owaurl/owa/auth/logon.aspx?url=newowaurl )
>
> And then Evolution complains exchange is version 5.5 and continues no
> further.
>
Ah, I see. Evolution doesn't support Exchange 5.5. That's what I can
see, from poking around the source code. In that case, could someone
else confirm if it is a duplicate of #248705?
--
Chow Loong Jin

I am having the same problem on 8.10 trying to access a 2003 Exchange server on a SBS Win2k3.

I have literally tried every combination, from http://server/Exchange to https://server/Exchange to https://server/Exchange/user.name, using DOMAIN/user.name, DOMAIN\user.name and so forth.

The errors I am getting are so random I'm not even sure I should post them here. They range from not being able to authenticate to me not having a mailbox on the system.

Needless to say, OWA it works just fine using Firefox.

I'm using IMAP now which works well, but I'm a bit annoyed it's not working. I have actually used this, with the same server, a long time ago and it worked just fine.

I'm happy to post debug messages. They range from Kerberos errors to the authentication errors.

On Tue, 2009-01-20 at 19:04 +0000, Ingmar wrote:
> I am having the same problem on 8.10 trying to access a 2003 Exchange
> server on a SBS Win2k3.
>
> I have literally tried every combination, from http://server/Exchange to
> https://server/Exchange to https://server/Exchange/user.name, using
> DOMAIN/user.name, DOMAIN\user.name and so forth.
>
> The errors I am getting are so random I'm not even sure I should post
> them here. They range from not being able to authenticate to me not
> having a mailbox on the system.
>
> Needless to say, OWA it works just fine using Firefox.
>
> I'm using IMAP now which works well, but I'm a bit annoyed it's not
> working. I have actually used this, with the same server, a long time
> ago and it worked just fine.
>
> I'm happy to post debug messages. They range from Kerberos errors to the
> authentication errors.
>
Please do.
--
Chow Loong Jin

I had the same problem in fully upgraded Intrepid, including a bunch of Evolution upgrades that appeared today. But I got it to work with the help of this thread and some experimentation.

Here's my version of the voodoo:

1. Deleted the account in the Evolution Preferences dialogue and exited evolution.

2. Set up the account anew using exchange-connector-setup-2.24. The only problem here is that it asked me for the GC server, which took a little research to find, but I think this is a local issue that has existed for some time. I did not include any host name in my user name, just the plain letter-only name. The OWA address was "https://mail.mycompany.com". These values are the same as in my previous, working, Gutsy environment. Everything seemed to work fine.

3. Started Evolution. It tried to access my folders and failed, but it seemed to try harder than before. The window took some time to open, and then it kept "Scanning folders" for half a minute or so before it asked for the password again and then gave up.

4. Edited the account in the preferences, cancelling when asked for my password. On the Receiving Email tab, I noticed that the value in the OWA URL box had been garbled: it said "http" instead of "https", and my Firstname.Lastname had been appended to it. I changed it back to my old value, "http://mail.mycompany.com" (without any slash), and also cleared the Mailbox box. Then I clicked Authenticate, and gave my password when asked. The result was that my Firstname.Lastname reappeared in the Mailbox box, but the OWA URL stayed the way I typed it.

5. OK-ed my way out of the preferences (which at one point caused a freeze for about 20 seconds), exited Evolution, and restarted. Everything was fine.

Made a typo in point "4": the old value I changed back to was of course "https://mail.mycompany.com", with the s.

Thanks very much! The key point from your steps there was to run
exchange-connector-setup-2.24 from the command line, as when I tried to
follow the new account wizard from the accounts options, it wouldn't
authenticate me even though the website I entered was clearly there and
doing a normal HTTP authentication with the same password, and I tried both
plaintext and secure modes.

Even after today's fixes, the add account process is still broken, but I'm
just glad to get calendar at all. Perhaps the simplest fix is to drop in
that setup tool instead of the builtin one?

2009/1/27 avadeaux <email address hidden>

> Made a typo in point "4": the old value I changed back to was of course
> "https://mail.mycompany.com", with the s.
>
> --
> Evolution will not authenticate on Exchange
> https://bugs.launchpad.net/bugs/207723
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "evolution-exchange" source package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: evolution-exchange
>
> Hardy Heron
>
> Evolution: 2.22.0-0ubuntu2
> Evolution-Exchange: 2.22.0-0ubuntu1
>
> Problem:
> Evolution was working perfectly fine with my work Exchange OWA server
> before upgrading. After the upgrade it is unable to authenticate on the
> server at all! I have verified that the password and OWA server are correct,
> as I can still log on using the web interface via firefox. Thought maybe it
> could have been a config error, so I got rid of ~/.evolution, but now I
> can't even create an exchange account. Every time I attempt to go through
> the wizard it complains I cannot be authenticated.
>

I have tried this as well on my machine but still no luck. I am connecting to an Exchange 2007 server with form based authentication. I also have the latest and greatest updates for Evolution. When I run exchange-connector-setup-2.24, fill out my information and hit forward I get the following error;

** (exchange-connector-setup-2.24:6369): WARNING **: Invalid uri 'owaauth.dll'

** (exchange-connector-setup-2.24:6369): CRITICAL **: e2k_soup_message_new_full: assertion `msg != NULL' failed

Not sure what this means but I can't seem to get by it! I have tried several different formats of the web address and username and they either don't work or return this error. Below is the debug information;

aaron@ubuntu:/usr/bin$ E2K_DEBUG=4 exchange-connector-setup-2.24
> GET /exchange HTTP/1.1
> Soup-Debug-Timestamp: 1233074984
> Soup-Debug: SoupSessionSync 1 (0x876e940), SoupMessage 1 (0xb5101408), SoupSocket 1 (0x8771ad8)
> Host: "owa address goes heres"
> Accept-Language: en-US, en
> Authorization: NTLM TlRMTVNTUAABAAAABoIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMAAAAAAAAAAwAAAA
> User-Agent: Evolution/2.24.3

< HTTP/1.1 302 Moved Temporarily
< Soup-Debug-Timestamp: 1233074984
< Soup-Debug: SoupMessage 1 (0xb5101408)
< Location: "owa address goes heres"/exchweb/bin/auth/owalogon.asp?url="owa address goes heres"/exchange&reason=0&replaceCurrent=1
< Set-Cookie: sessionid=; path=/; expires=Thu, 01-Jan-1970 00:00:00 GMT
< Set-Cookie: cadata=; path=/; expires=Thu, 01-Jan-1970 00:00:00 GMT
< Connection: close
< Content-Length: 0

> GET /exchange HTTP/1.1
> Soup-Debug-Timestamp: 1233074984
> Soup-Debug: SoupSessionSync 1 (0x876e940), SoupMessage 2 (0xb51014b8), SoupSocket 2 (0x8771a48)
> Host: "owa address goes heres"
> Authorization: NTLM TlRMTVNTUAABAAAABoIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMAAAAAAAAAAwAAAA
> User-Agent: Evolution/2.24.3

< HTTP/1.1 302 Moved Temporarily
< Soup-Debug-Timestamp: 1233074984
< Soup-Debug: SoupMessage 2 (0xb51014b8)
< Location: "owa address goes heres"/exchweb/bin/auth/owalogon.asp?url="owa address goes heres"/exchange&reason=0&replaceCurrent=1
< Set-Cookie: sessionid=; path=/; expires=Thu, 01-Jan-1970 00:00:00 GMT
< Set-Cookie: cadata=; path=/; expires=Thu, 01-Jan-1970 00:00:00 GMT
< Connection: close
< Content-Length: 0

> GET /exchweb/bin/auth/owalogon.asp?url="owa address goes heres"/exchange&reason=0&replaceCurrent=1 HTTP/1.1
> Soup-Debug-Timestamp: 1233074984
> Soup-Debug: SoupSessionSync 1 (0x876e940), SoupMessage 2 (0xb51014b8), SoupSocket 3 (0x8771970), restarted
> Host: "owa address goes heres"
> User-Agent: Evolution/2.24.3
> Authorization: NTLM TlRMTVNTUAABAAAABoIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMAAAAAAAAAAwAAAA

< HTTP/1.1 200 OK
< Soup-Debug-Timestamp: 1233074984
< Soup-Debug: SoupMessage 2 (0xb51014b8)
< Cache-Control: no-cache
< Pragma: no-cache
< Content-Length: 8362
< Content-Type: text/html; charset=utf-8
< Expires: -1
< Server: Microsoft-IIS/6.0
< X-Powered-By: ASP.NET
< X-AspNet-Version: 2.0.50727
< X-OWA-Version: 8.1.336.0
< Date: Tue, 27 Jan 2009 16:49:44 GMT

** (exchange-connector-setup-2.24:6369): WARNING **: Invalid uri 'owaauth.dll'

** (exchange-connector-setup-2.24:6369): CRITICAL **: e2k_soup_messag...

On Tue, 2009-01-27 at 17:26 +0000, AaronDM wrote:
> I have tried this as well on my machine but still no luck. I am
> connecting to an Exchange 2007 server with form based authentication. I
> also have the latest and greatest updates for Evolution. When I run
> exchange-connector-setup-2.24, fill out my information and hit forward I
> get the following error;
>
> ** (exchange-connector-setup-2.24:6369): WARNING **: Invalid uri
> 'owaauth.dll'
Your particular bug isn't this one. It's Bug #518920. For a fix, just
head over to my PPA (http://launchpad.net/~hyperair/+archive) and grab
the debs under evolution-data-server.
--
Chow Loong Jin

I have the same issues above but with Jaunty and evolution-data-server_2.26.1.
It worked perfectly under Intrepid.

I have this on Jaunty and Evolution 2.26.1 with Exchange 2007 (no IMAP support). However, I had it working last week. I've had a couple of daily upgrades to my desktop since then, and the connection seems to have stopped working yesterday. Now I keep getting requests for password while trying to connect, and "Exchange is offline, cannot display folders" while trying to edit the account." I get repeated footer errors "Error while Scanning folders in "Exchange server <servername>."

I tried deleting and recreating the account, and got the error "The server is running Exchange 5.5. Exchange Connector supports Microsoft Exchange 2000 and 2003 only." I know the Exchange servers were upgraded to 2007 about a month ago, but again, the connection was working two days ago. I can try to find out if IT did anything different with the Exchange servers this week, but they're not too keen to support linux desktops here, so I don't know if they'll tell me anything.

Ironically, the reason I went to Jaunty was specifically for the Exchange 2007 support in Evolution 2.26.1. The outlook web access is pretty awful if you're not using IE.

On Fri, 2009-05-01 at 22:19 +0000, emdalton wrote:
> I have this on Jaunty and Evolution 2.26.1 with Exchange 2007 (no IMAP
> support). However, I had it working last week. I've had a couple of
> daily upgrades to my desktop since then, and the connection seems to
> have stopped working yesterday. Now I keep getting requests for password
> while trying to connect, and "Exchange is offline, cannot display
> folders" while trying to edit the account." I get repeated footer errors
> "Error while Scanning folders in "Exchange server <servername>."
>
> I tried deleting and recreating the account, and got the error "The
> server is running Exchange 5.5. Exchange Connector supports Microsoft
> Exchange 2000 and 2003 only." I know the Exchange servers were upgraded
> to 2007 about a month ago, but again, the connection was working two
> days ago. I can try to find out if IT did anything different with the
> Exchange servers this week, but they're not too keen to support linux
> desktops here, so I don't know if they'll tell me anything.
>
> Ironically, the reason I went to Jaunty was specifically for the
> Exchange 2007 support in Evolution 2.26.1. The outlook web access is
> pretty awful if you're not using IE.
>
The package which provides support for Exchange 2007 is evolution-mapi.
You'll also have to change the account from Exchange to MAPI account.
--
Regards,
Chow Loong Jin

evolution-mapi ... This looks like a native client. How is the issue with OWA addressed?

For what it's worth. I had problems with 8.04 and an Exchange Server 2003 (SBS), and after upgrading to Ubuntu 9.04 Desktop, everything works as expected.

Just wanted to let you know.

I confirm this error in karmik alpha 4 exchange 2003

Thanks for your report, that's something to send directly upstream at http://bugzilla.gnome.org by someone having the issue, for forwarding instructions please read http://wiki.ubuntu.com/Bugs/Upstream/GNOME, Thanks in advance.

where can i find a patch/fix? this bug is critical, not low.

evolution-exchange 2.32.2-0ubuntu3 on Ubuntu 11.04 natty amd64

Same here, fresh install of 11.04 64bit, not working....

I don't get it, Ubuntu wants to be installed in companies but so far I've had loads of problems with it. OCS was a major pain to get working with Empathy (the default chat client), it worked great with Pidgin. The exchange support is not working with Evolution (the default email client), I's surprised I can use Firefox to surf the web....

rage. how can it be low, if I have to type in passwords to 10 accounts to be able to work? same bug going on for 3 years....

In the meanwhile Ubuntu has ditched Evolution in favor of Thunderbird as default email client.
This bugreport is a farce and I personally gave up on it a couple years ago.

I think it would be more honest if bugs that are as old like this would just be closed as "won't fix" and let die.
Much better than keeping everyone's hope up for years, because clearly no one is going to fix this.

All you do need to do here in evolution is go to mail settings
Preferences - Sending Email and Receiving email - forget password
Close evolution and authenticate again