Please describe the problem:
The problem can be duplicated.  When using an Active Directory password with
special characters, trying to set up an exchange server account in evolution
fails as the authenticate phase.  We tried close to one dozen different
passwords with a controlled varying number of special characters in the active
directory password.  The chosen active directory passwords were alphanumeric
length of 8 with an initial value of 5 special characters (Pa55w0rd!+$^*) and
then subsequent less special characters down to one (Pa55w0rd!).  With each of
the password variations using special characters, the authenticate phase failed
every time when setting up the exchange server account.  The final part of the
test used several passwords without special characters.  During this testing
phase, the authenticate phase completed successfully every time.

Steps to reproduce:
1. Log onto an Active Directory domain controller and create a user and
associate a new password with one special character
2. Attempt to create a new exchange server account in evolution 
3. Authenticate phase should fail


Actual results:
The authenticate phase failed every time when using special characters in active
directory passwords.

Expected results:
I would expect that the authenticate phase would succeed.

Does this happen every time?
yes

Other information:
This circumvents password complexity requirements as active directory users are
required to create passwords that are alphanumeric with a minimum of one special
character.  Since evolution did not succeed in the authenticate phase, this
forces users to downgrade to alphanumeric passwords with no special characters.
 Potential security issue.