Scalix Forums

Hello-

I have a mail gateway already in production doing antivirus/spam filtering. I have scalix setup now and want to continue using my gateway and just have scalix relay all mail to my existing gateway. What config file would i use to relay all outgoing mail through my existing gateway?

Hi Joe,

You can edit your sendmail.mc file and change:



to be:



then rebuild your sendmail.cf file. If you do this, you need to run omsendin to get the Scalix routines put back in. Or you can just edit your sendmail.cf file and change:



to be:



and then restart sendmail.

Thanks,
Rachel

Didnt realize scalix was just using sendmail for the MTA. Super easy change. Thanks!

But this doesn't work if the user you are trying to send mail to exists in the Scalix directory. I'm trying to do the same thing to gear up for a tiered cut over, and I need every piece of mail that is sent from the Scalix server to go out to my mail relay first.

What else needs to be done here?

No, of course that wouldn't work if the users exist in the Scalix directory as Scalix would attempt to deliver to their Scalix mailbox. In that case, you would need to create redirect rules for each of the users that haven't migrated over yet. You can use sxaa (see the admin_resource_kit subdirectory in the Scalix tarball) to create these redirect rules.

Thanks,
Rachel

Hi,
This thread may be a bit old, but I have the same issue.
However I have lots of users and I was hoping that there was a global config file that could be edited to do the same as the smart host relay for local users?

btw. Im useing Scalix 11

Thanks
Tony D

Would fetchmail on the non-Scalix server work? That would allow you to pull the message off of Scalix, and deliver it to the old server. As people are migrated, just remove them from the fetchmailrc file.

Kev.

No, that wouldn't be something I would be looking at for a production server.
Cant Scalix be configured in a similar same way that sendmail has been configured to use a smart host?

You aren't sending mail anywhere though. Sendmail wouldn't deal with it any differently.

A smarthost is like specifying a route. It's the next step to find where a message should eventually be delivered. In the case you're talking about, the message should be delivered to the machine it's already on, therefore, it just gets delivered.

This is exactly the same as trying to traceroute localhost (or 127.0.0.1) through some gateway.

Even if you specified it, it wouldn't be used because there is no reason to use it. The message is already at the the place it needs to arrive for delivery.


I've used fetchmail before on production servers, and it works extremely well.