Sending mail using an alias address

[DanielB]

Hi,

I have setup like this :

premium account -> user@domian.com

This account also recieves mail for lets say info@domain.com, sales@domain.com and support@domain.com. Those aliases are configured via Scalix. I have setup some rules to sort incoming mail into different folders of the user@domain.com account and I configured access rights so that user1@domain.com and user2@domain.com can access the subfolders of user@domain.com. So far so good. However, my customer also wants to send mail using these alias addresses. If I turn on the Sender header function for user@domain.com and setup delegates I can send mail as user@domain.com as user1@domain.com. However, I can not use the configured aliases as the sender address. Scalix tells me I have insufficient access rights to send as user sales@domain.com. I suppose that's because sales@domain.com is not an account but just an alias. I could configure seperate accounts I guess, but that would use licenses + I would have to open tons of additional mailboxes in Outlook which isnt exactly pretty.

How can I make this work ?

Thanks.

[craig]

Outlook does not support "send as" in MAPI mode

[jedwards-locked-out]

Actually, you cannot send as in any mode because Scalix doesn't have the functionality because they can't figure it out. Why else would they ignore attempts to get them to do it? Thay're still fumbling and hacking through someone elses code.

[florian]

jedwards,

if you like the product that we provide so little, why do you actually bother to spend time on this forum?

Indeed, Outlook running against Exchange has this same limitation as well, therefore it is a functional limitation in Outlook that we can't easily work around. If you put one of your SMTP aliases into the from field in both Scalix and Exchange, this gets normalized into your primary email address.

There are 3rd-party products available that you can install on the Exchange server to rewrite the address, but it's not a client side functionality. I've never sat down to figure the same out for Scalix, but as sendmail can rewrite addresses, you can do the same thing here.

The workaround - that's possible in both Scalix and Exchange - is to create a secondary user account, give the user delegate rights and then have him send from the alternative mailbox.

We're keeping track of the issue and should future versions of Outlook make it easier to address this, we'll be on track and continue hacking our code to do so.

We're potentially looking into providing the send-as-alias functionality in SWA - as we control our own UI there, that should be possible. I cannot give you a timeline for this.

Cheers,
Florian.