Ldap address book and Scalix

[ausyvr]

Does anyone know what how Scalix reads the email address from a Open Ldap address book?

When i connect my clients to the ldap directory for address look up, it connects fine, you can create a new message type in a partial name and hit the 'Check Names' icon. The To: field will complete with the name/email etc. BUT when you send the email a few seconds later you receive an error

Code: Select all

The address type supported by this service provider

When you do a 'Find" for a user, then select the Email Address tab, you see the users full email address with SMTP:usernmame@anywherebuthere.com
Me thinks Scalix does not remove the SMTP: before sending the email out causing the error.

Note: The LDAP Address directory was working flawlessly before we moved some users to Scalix.

Thanks

[ausyvr]

Has anyone else ran into the issue i posted earlier? Guys from Scalix?

There has to be a fix somewhere! Please?

To add to this problem, we have a user who set up a second POP account from an external domain. The setup and testing of the account works fine.

EXCEPT when the user receives an email from this external POP account, the 'From' field displays the internal address..which is totally pointless.
My theory is that Scalix is grabbing the user from the Scalix System Directory in Outlook which displays the internal address always as username@scalix.com

Two accounts set up for one user:
username@scalix.com
external@domain.com

Mail from both accounts is delivered into the same inbox etc

To send mail from secondary account in Outlook :
New -> Accounts and select which account you want to send from.
Type out the email and hit 'send'

Email is delivered fine but with the From being username@scalix.com not external@domain.com

One final issue is Receiving email sent to this account. The Outlook Send/Receive Progress reports:

Code: Select all

 task mail.domain.net - Receiving reported error (0x80040102): The request operation can not be performed on this account

Is there a fix for this, a work around? Where I a work its considered a major issue.

It seems Scalix always looks at the SYSTEM Address book for users. This will be fine when we have fully moved over Scalix but until then its a problem. [/code]