More than one domain on same Scalix Server?

[Valerion]

I know there is no link between a mailnode and a domain name, but what is the difference between the domain name that you assign to a mailnode, and the domain name that you can add in the SAC under Administration (local domains)?

The list you add in SAC under Administration populates the domain dropdown list when you add an email address to a user. The domain attached to a mailnode is used to auto-generate a default email address for a user on the mailnode (usually at creation).

Currently, our server (exim) recieves email for three different domains. I would like to replace it with Scalix, I can do this by adding mailnodes and alternate addresses to an account; but the problem is sending from three different accounts. What are my options here? Three Scalix instances? Or have Scalix handle one domain, and leave the other three to exim?

I would really like to consolidate all this into one Scalix system if possible. Any setup that can provide this kind of functionality? I don't need all mail to be accessible from one location (ie, I am satisfied if people will have to login to three different SWA locations). I would like the Outlook integration to work on the primary domain, and then have people maybe add their alternate accounts under different Outlook profiles.

I've got a similar setup here, where I have 2 different roles in 2 different organisational units, and of course, two email addressses. Since I didn't want the two to mix, I created two different mailboxes.

In SWA I log in to either the one or the other and use that (pending delegation being implemented in SWA), while in Outlook I have both mailboxes set up as different profiles. The primary one (the one I use the most) is a delegate of the secondary mailbox and also has rights to send on behalf of the second mailbox. For me this works well. I use delegation to send all my mails, then move the sent emails manually to the other mailbox's Sent Items.

[e1kosau]

hi i want to be able to send outside under a different domain. I want to temporarily use xyz.com domain to test the server and eventually will shift to our corporate ABC.COM domain. I will have users in xyz.com to be the same in ABC.COM domain once I deploy the email server in production.

I want to have the origin domain for all my emails to have a XYZ.COM domain and shift to the CORPORATE domain ABC.COM when on production. How do I achieve this??

[felipegeek]

Again rehashing what has been said by others in different ways. Please adapt to this need in the next version of Scalix.

User has multiple email addresses on a single account but all mail looks like it was sent to the primary mailbox address so the originiating address ends up lost to the end user.
Example: Send an email to user@maindomain.com, also CC user@2nddomain.com and user@3rddomain.com. At the recipient side it the user receives one email with the basic headers showing the user as 'user@maindomain.com' in the To and CC lines. The detailed header shows the email as 'for <user@2nddomain.com>'. Can this be changed so that the reciepient Scalix user knows which address the incoming message was really sent to?

This leads me to the next issue - Sending/replying as another address. It would be very helpful to be able to send/reply as any of the addresses configured in the Scalix server for a given user. I saw a previous post from a Scalix rep that mentioned corporate customer's generally not wanting users to send mail as other accounts, which makes sense from an external/personal account perspective. This is so users can't add their POP3/IMAP/Hotmail accounts to Outlook and do direct personal email from the corporate email client/server.

What Scalix ought to be able to do is allow the appearance of approved domains the Scalix admin would have added to the server and assigned to a user. Case in point, I have a client with 8 domains (8 related business) and about 15 employees. Each employee works for 2-4 of these companies and has addreses for the respective domains. They need to have multiple addresses (and the appearance of those addresses) without the headache of multiple mailbox accounts with separate logins. The Outlook groupware functionality is also a requirement because of the collaboration these 15 people have amongst themselves with regards to scheduling and contacts. Having to add multiple profiles to Outlook or login to separate SWA sessions is a kludgy and generally inefficient use of groupware and email tools.

This is obviously a major sticking point for many of your users. The restrictive 'one domain' view is very 1990's MS Exchange thinking before multiple domains routinely became associated with an enterprise.

I look forward to a solution.

Best regards,
-felipe

[florian]

Felipe,

the issue has been brought up many times and we certainly appreciate the need behind this. However, in some situations we're bound by what the email client provides us with.

having tested this with Outlook, it seems that it's not possible to do the selection of sender address you're describing; I've tested Outlook's behaviour with Exchange 2003 (not some old version!) and it's just the same - the server always converts whatever FROM address you use to your identity's primary address. The only way to have different senders is multiple mailboxes and delegate access, sending on behalf.

Obviously, we could come up with a solution in SWA; at this point we're hesitant to do that because we would like all our client applications (incl. Outlook!) to behave in a consistent manner.

Opening up discussion here - would a partial solution, for SWA only - be a real solution or more pain than pleasure?

Thx,
Florian.