Re: New username@DOMAIN breaks Evolution-Exchange connector's LDAP authentication

From: DeckerEgo (john.ellis_at_gmail.com)
Date: 11/17/04 

Date: 17 Nov 2004 07:01:49 -0800

Nope. Still broken.

jtellis@alumni.indiana.edu (John T. Ellis) wrote in message news:<42ab0e9d.0411161829.2f30c730@posting.google.com>...
> This is largely going on the research I've done so far, let me know if
> I've made any illogical jumps...
>
> Evolution 2 now requires users that need to specify a domain to do so
> with the format username@DOMAIN, instead of the previous allowed
> format
> of DOMAIN\username. This works fine for calendaring, mail and tasks
> but
> breaks the LDAP authentication mechanism for some Global Address List
> servers.
>
> For example, say you migrate from an earlier pre-Active Directory
> server
> for your address list, WINS and Exchange (i.e. Exchange 5.5).
> According
> to some Microsoft knowledge base articles I've read, the newly
> converted
> Active Directory server will still do authentication in the
> DOMAIN\username format _instead_ of the allowed username@DOMAIN
> format.
>
> Normally this isn't a problem - unless you submit your username and
> domain as a single concatenated string (i.e. logging into an LDAP
> directory). I ran the Exchange connector in debug mode and noticed
> that each time the connector attempted to authenticate to the Global
> Address List server it was denied.
>
> Things worked just peachy with Evolution 1.4 - but things are broken
> in 2. The only change is the username@DOMAIN format for my username
> versus the earlier DOMAIN\username format. If the connector was
> repaired so that the DOMAIN\username format was allowed again, LDAP
> authentication would probably work fine.
>
> http://bugzilla.ximian.com/show_bug.cgi?id=66926 lists a possible
> patch... I'll try re-compiling.

Relevant Pages

  • Re: Exchange 2007 Send Connector problem with Internal email address
    ... I am trying to send email from ..NET application, and I can embed user authentication in the app. ... The SMTP server requires a secure connection or the client was not authenticated. ... setup a Receive Connector with appropriate permissions. ... I can send email out of all internet email addresses with the send connector ...
    (microsoft.public.exchange.setup)
  • Re: I want to use MailMarshal as edge
    ... "Integrated Windows Authentication" checked?" ... You configured the send connector to send through an exchange server (with ... Remove authentication from the send connector and you should be fine. ... Send connector is forwarding to both dns name and ip of smarthost. ...
    (microsoft.public.exchange.setup)
  • Re: How to allow emails to relay through Exchange 2007
    ... If you've setup a Connector for unauthenticated relaying, and allowed the IP address of the sending host to connect, the host should be able to relay. ... I still can't get the emails that are generated from the other server to get through... ... 'Inbound authentication failed with error LogonDenied for Receive connector Default EXCHANGE. ...
    (microsoft.public.exchange.setup)
  • Re: I want to use MailMarshal as edge
    ... You configured the send connector to send through an exchange server? ... Remove authentication from the send connector and you should be fine. ...
    (microsoft.public.exchange.setup)
  • Re: Out going mail problem
    ... If Outlook is configured for POP3 accounts then I do not use authentication ... for SMTP(before exchange server). ... > How sure are you that your ISP's SMTP server does not require ... > Authentication of the SmallBusiness SMTP connector (or the connector you ...
    (microsoft.public.windows.server.sbs)