After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 329371 - user name in the format "username@domain name" doesn't work
user name in the format "username@domain name" doesn't work
Status: RESOLVED FIXED
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.5.x
Other Linux
: Normal normal
: 2.7
Assigned To: Connector Maintainer
Ximian Connector QA
: 337498 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-01-31 17:13 UTC by Ryan P Skadberg
Modified: 2006-04-19 06:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch for supporting username@domainame format usernames (3.99 KB, patch)
2006-04-12 10:01 UTC, Sushma Rai
none Details | Review
Patch (5.59 KB, patch)
2006-04-17 12:54 UTC, Sushma Rai
none Details | Review
Patch -> slightly different than the previous patch. (6.26 KB, patch)
2006-04-18 10:07 UTC, Sushma Rai
committed Details | Review

Description Ryan P Skadberg 2006-01-31 17:13:59 UTC
When I try to access my exchange mail, using verbose debug, I see this:

CamelException.set(0x965fe38, 3, 'Cancelled')
CamelException.set(0x965fe38, 3, 'Cancelled')
Thread b5428ba0 >
Get folder info(0x8bbba00:exchange://rskadber%40company.com;auth=Basic@webmail.company.com/, '<null>') =
< b5428ba0 >


Tasks and Calendar seem to work just fine, it seems to just be mail I am having issues accessing.

This is with 2.5.9.0 of connector, 2.5.90 and 1.5.90 of eds and evo.
Comment 1 Sushma Rai 2006-02-02 07:53:50 UTC
Is the the first time you are using or did you upgrade to 
2.5.90 from the older version?

What is your user name, that you have entered in account setup wizard?
looks like you have entered username@domain as user name.
Make sure that you enter the user name and OWA url as you
enter for Outlook Web Access.




Comment 2 Ryan P Skadberg 2006-02-03 17:12:57 UTC
This was an upgrade, it was working 100% fine up until the upgrade.
Comment 3 Ryan P Skadberg 2006-02-03 17:13:56 UTC
Upgrade was from 2.5.5 (or so) to 2.5.90
Comment 4 Sushma Rai 2006-02-04 04:35:55 UTC
You didn't answer the username related question.

Well, can you delete and re-create the account and see if it works?
Comment 5 Ryan P Skadberg 2006-02-04 04:58:22 UTC
Yes, that is how I enter things for OWA, so it is correct.  As I said, was working fine with 2.5.5, suddently broke with 2.5.90.

It looks like this may be a Fedora Rawhide specific issue with an updated LDAP.  I filed a bug here:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=179975

In RH's BZ.  Will let you know what the update on that is, once I get one from Dave.
Comment 6 Ryan P Skadberg 2006-03-02 14:23:54 UTC
This does not seem to be a Redhat issue (it continued to 2.5.92.

Here's what I see:

Calendar and Tasks seems to work fine.

When I try and open the > which shows my exchange mail, I get this on the command line:

CamelException.set(0xb2f7908, 3, 'Cancelled')
CamelException.set(0xb2f7908, 3, 'Cancelled')
Thread b1161ba0 >
Get folder info(0x9ee0c50:exchange://rskadber%40egenera.com;auth=Basic@webaccess.egenera.com/, '<null>') =
< b1161ba0 >

When I do this, I see nothing in my E2K_DEBUG=5 session of evolution-exchange, so it seems like Evolution isn't even sending anything to evolution-exchange to try and get its mail.

I'm thinking maybe it has to do with the way my Exchange server gets usernames, which is username@company.com, instead of something like DOMAIN\username.

I also noticed that the Authenticate button in the create new exchange account GUI doesn't seem to show anything good or bad.
Comment 7 Ryan P Skadberg 2006-03-02 14:24:28 UTC
Upping this to major, as it is blocking me from using evolution.
Comment 8 Sushma Rai 2006-03-03 05:41:36 UTC
Ryan,
Can you create another unix user and try to use Evolution as that 
user, and create the account?
If authentiation fails when u try to create the account, 
please run "evolution" setting E2K_DEBUG=4 and get the traces.

Comment 9 Ryan P Skadberg 2006-03-03 15:06:52 UTC
So, this gets more interesting.  I created a brand new unix user, logged in, and started evo.  Registered the Exchange account (got a failure when I mistyped the URL and attempted to auth in the account creation, so that seems fine).  Then, when Evolution started, I got an error saying it couldn't connect to the backend.  Strange, so I restarted (after a force-shutdown).  When I tried to restart, I got the following on the command line:

** (evolution:2998): CRITICAL **: e2k_global_catalog_lookup: assertion `E2K_IS_GLOBAL_CATALOG (gc)' failed

(evolution:2998): camel-WARNING **: camel_exception_get_id called with NULL parameter.

(evolution:2998): evolution-mail-WARNING **: Error occurred while existing dialogue active:
Could not connect to Evolution Exchange backend process: No such file or directory


--------

So, I tried starting the exchange process by its hand and I still got this error.  So, something funky is going on here.

Does evolution try to start this process and if so, where is the location defined?

Any other ideas of things to try?
Comment 10 Ryan P Skadberg 2006-03-03 15:11:17 UTC
So, on my main account (where this problem all started), I am seeing this:

** (evolution:4193): WARNING **: LDAP authentication failed (0x31)

Any ideas of what that error might be?  It seems to only happen when I have Exchange on, so this could be part of the issue.
Comment 11 Sushma Rai 2006-03-04 05:53:48 UTC
On the new account, 
have you provided the Global Catalog server details, while setting up
an account? 
Also, in that account, kill evo, eds and exchange-storage, bonobo-activation-server processes, 
set BONOBO_ACTIVATION_PATH=<your prefix>/lib/bonobo/servers
and start evolution. If again you see the error 
"Could not connect to Evolution Exchange backend process:" try to
run evolution-exchange-storage process on the seperate console and try.

looking at the "LDAP authentication failed" error, i think yor global catalog server name is wrong, or it is not accessible? 
Comment 12 Ryan P Skadberg 2006-03-04 14:58:25 UTC
OK, I seem to have the same exact issues on a new account as I do on an old one.  Calendar and Tasks work and Mail doesn't.  It seems to come back to the error:

(evolution:2998): evolution-mail-WARNING **: Error occurred while existing
dialogue active:
Could not connect to Evolution Exchange backend process: No such file or
directory

So, something is set wrong.  As this only happens in Mail, it seems like somewhere something is setting this incorrectly.  I looked at the bonobo servers and seems like it is set right in there.  Any ideas of where else to look?
Comment 13 Void Main 2006-03-20 20:02:42 UTC
I just upgraded from Fedora Core 4 to Fedora Core 5 and now I am having the exact same problem. I submitted a bug report with Red Hat:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=185990

Evolution versions:
evolution-data-server-1.5.92-1
evolution-connector-2.5.92-1
evolution-2.6.0-1
evolution-webcal-2.4.1-3.2
Comment 14 Void Main 2006-03-20 22:52:34 UTC
I figured out my problem. In the older Evolution I had to use "username@domain.com" as my userid. After upgrading I had to use just my username (without the domain). Works like a champ now!
Comment 15 Ryan P Skadberg 2006-03-21 00:50:14 UTC
Thanks Void, this seems to have fixed it for me.

Developers - when was this change made and how did noone know about it? :)
Comment 16 Sushma Rai 2006-03-21 07:50:26 UTC
See comment #1. username@domain was not working in 2.0 to 2.4 and now it is handled, but looks like some bug. changing the summary.

Comment 17 Void Main 2006-03-21 15:39:15 UTC
Sushma, I think it was your comment that made me try to use just the "username". It would appear to me that you have the versions reversed though. With Fedora Core 4 (evo connector 2.2.2) I was using "username@domain" and with Fedora Core 5 (evo connector 2.5.92) I have to use just "username". It did spark me to play with the username though and I thank you for that!
Comment 18 Sushma Rai 2006-04-07 10:51:51 UTC
*** Bug 337498 has been marked as a duplicate of this bug. ***
Comment 19 Sushma Rai 2006-04-12 10:01:48 UTC
Created attachment 63296 [details] [review]
Patch for supporting username@domainame format usernames
Comment 20 Sushma Rai 2006-04-17 04:38:42 UTC
From the bug #335561, some server require username to be in the 
from of e-mail id. So the proper fix would be during account creation
first trying authentication user e-mail id as user name and 
on failure extracting the usernmae form e-mail id and trying it out.
Comment 21 Sushma Rai 2006-04-17 12:54:34 UTC
Created attachment 63701 [details] [review]
Patch
Comment 22 Sushma Rai 2006-04-18 10:07:58 UTC
Created attachment 63785 [details] [review]
Patch -> slightly different than the previous patch.

Avoids asking for password twice, if the username is not in the from of email ID and, authentication fails.
Comment 23 Sushma Rai 2006-04-19 06:54:57 UTC
Committed to CVS head. 
Ryan P Skadberg , Void Main, Can you please verify this?
Evolution 2.7.1 will have this fix.