Scalix Forums

Is there a way to have ALL email go to an email gateway by default? Including the email that will ultimately be handled by the local SCALIX server.

Do you mean ALL mail as in:
-the mail sent by the mailclients of the Scalix server
-the mail coming from the internet, destined for a domain hosted by the Scalix server
-the mail sent by the Scalix Web Access clients

Because the first two are relatively easy to implement. For the mailcliets, just configure them to use the gateway as SMTP server. For the internet mails, just point your MX records to your mailgateway.
The third is a bit tricky though, as there is no option in scalix to force the SWA clients to use a different SMTP server than the Scalix server AFAIK.

Ofcourse it's possible to add an option in smtpd.cfg saying SMTPFILTER=TRUE, that should give you the possibility of configuring senmail and sendmail-milter. But I can't tell you anything on how that works, since I chose to run mail mailgateway on a different machine with postfix (wich I prefer over sendmail)

As I probably won't have to tell you, adding a mailfitering gateway between the internet and your mailserver requires some delicate relay configuration, as it is really easy to accidently create an open relay this way. I have configured it this way:
-The mailgateway only acceps mail for the domains hosted by the scalix server OR coming from the local (internal) network.
-The Scalix server only accepts mail from the local networks OR from roaming users on the internet when they have authenticated.

My mailclients use the Scalix server as SMTP, because in my situation, scanning of internal mail is not required.

What I am mainly looking to do is have all email by SCALIX users sent through the email gateway. At the moment I am in the process of migrating people over to SCALIX. Until I do I can not send email to those users who are not moved over yet because it drops into SCALIX.

This is fairly easy to do. Just make sure that there is a DNS that resolves to the old mail server for the domain's MX. You can test that with dig:
dig mx mydomain.com

The DNS records are not an issue here, the SCALIX server is setup to handle email in the domain that I am slowly migrating. I have an email gateway running postfix out in front that at the moment is using a transport to redirect only my email to the SCALIX server. This works fine, the issue comes up if I want to send an email to another user in the same domain from a SCALIX client (web client or outlook) whose account has been setup inside SCALIX but is not active. SCALIX sees that there is a valid local account and directs the email to SCALIX. What I would like to do is direct all email to the gateway so that only my email ends up in SCAlIX.

Thanks

so you want your Scalix server to forward al mail destined for adresses of a domain that it serves, but of wich it does not serve the actual address, to another server (your "old" mailserver??
If that's the case, then your Scalix server has to resolve your "old" mailserver as the secondary MX. It will then forward any mail for that domain wich it couldn't deliver locally, to that domain.
Anyway, why don't you consider bulkadding all the users into your Scalix server and then setting up an IMAPsync wich synchronises the mailboxes on the two servers?

I think what you need to do is just add forwarding addresses for the Scalix users you have not yet migrated.

Say you have scalix.domain.com and legacy.domain.com, simply put in a forwarding address for user@scalix.com.com to point to user@legacy.domain.com.

Cheers,

Sascha.

ScalixSupport wrote:I think what you need to do is just add forwarding addresses for the Scalix users you have not yet migrated.

Yes, this is a possibility. But if you have a lot of users, setting up a temporary DNS that resolves the MX to the old mailserver is so much easier.

Maybe. We do provide tools like ommigu to ease the migration and mass update the directory with forwarding addresses.

Sascha.

Maybe I am not explaining what I am trying to accomplish correctly. All inbound email is handled by a
server running Postfix. At the moment only my email is being forwarded along to the SCALIX server by using Postfix's transport option. The problem I run into is when I want to send an email to someone else in the company from a client talking to SCALIX. All of the accounts have been setup in SCALIX but only mine is actively being used. If I send an email to someone who has a valid account in SCALIX, then the email will go to that account in SCALIX. What I would like is to have the email go to the email gateway rather than SCALIX handling it internally.

Thanks

Hi. You'll need to create a redirect rule for each of the users. The easiest way to do this is with sxaa which is located in the admin_resource_kit subdirectory of the tarball. There's a readme file which details it's usage.

Thanks,
Rachel

What you need to know is that scalix does not own a domain. If a scalix user sends an email to another user having the same domain but not beeing a scalix user, then the email is handed off to sendmail. Sendmail will then check for the MX of the domain and if you set up your DNS correctly it will resolve to your old mailserver and your email ends up there, like you want to.

As long as you're not using Outlook + Connector as your Scalix MUA, wouldn't (as someone already pointed out) simply specifying your Postfix box as the smtp server in Thunderbird/whatever or in the config for SWA accomplish what you're trying to achieve?

Postscript: just changed the value of 'smtpServer' in /etc/opt/scalix/webmail/partner.xml and was able to relay through the Postfix box on my LAN.

ggreenaway

The answer to you question is explained by Rachel 4 posts back. Use sxaa from the admin resource kit (ARK) and setup forwards from the Scalix user to the corresponding SMTP address on your production servers.

AussieOwner wrote:ggreenaway

The answer to you question is explained by Rachel 4 posts back. Use sxaa from the admin resource kit (ARK) and setup forwards from the Scalix user to the corresponding SMTP address on your production servers.

Hi, I'd like to understand why this is the best solution in this particular case, because for every further user or batch of users ggreenaway wants to add to the test scalix box he'll have to redo the forward (shouldn't that be redirect?) rules only to ultimately delete all of them when his scalix server enters production.

Just curious.