altering sendmail may render scalix unusable?

[TCWardrobe]

Hi!

I am used to exim, so please bare with me

Basically I just want to enable a smarthost to let the scalix testing get to the next stage, external mailing. I think I know what I have to do (searched the forum and google and found what I've searched) but I am a bit confused about how I actually "touch" the config files of sendmail without killing scalix.

1.) where is sendmail.mc? the config sendmail.cf itself states I should not edit this file, I should edit sendmail.mc. find / locate did not find it so I assume I have to generate it somehow. I've seen some reference to m4 as the microprocessor for the configfile but I am a bit afraid I don't get it right. Tips?

2.) I don't get it exactly how scalix is integrated into the system, or how deep. I have played around with kolab some time ago and I hope scalix is not even remotely compareable to that! So... how deep is your love^Wintegration?

[kanderson]

You should be fine to edit the .cf, just make a copy of it first.

Scalix directly modifies the .cf because it's the only fine which will FOR SURE be there for configuring Sendmail. As you've seen, the m4 might be, but it might not.

If you do generate a new cf from an m4, be sure to run omsendin to reinsert the Scalix specific pieces.

What are you trying to change?

Kev.

[TCWardrobe]

You should be fine to edit the .cf, just make a copy of it first.

I must admit I'm a debianer for reasons! In the past as I played around with SuSE and edited .confs diectly, yast (or SuSEConfig) somehow destroyed time by time such directly edited systems or left some services unusable. There were other issues why I went to debian and why I didn't choose FC for this case but that would go beyond the scope of this, surely
The bottom line is I don't feel comfortable with a SuSE system so I was a bit afraid of editing the files directly. But I did that already yesterday (at least it is testsystem) and I went on testing successfully.

What are you trying to change?

Kev.

Basically I try to enable internet-wide mailing, nothing more. This works by now, even if the configuration and tweaks I had to make look a bit dreadful... but as long as it works *shrug*

A bit in detail. The testsystem lives inside a working production network, with some subnets (through VPNs and local ones). The scalix server is accessable from everywhere. Scalix resides inside a remote VPN-subnet, the smarthost inside the main office-subnet. This smarthost (running exim4 on Debian) gets all mails with fetchmail, does spamdetection/tagging and delivers them to users maildirs, relays incoming mails dependent on the from:-header to another smarthost with the correct credentials needed for every mailaccount at the not-local mailservice provider where domain.com is hosted and finally offers the mails via an imapd back to the users. Maybe more of a mailhub as a smarthost though... just realised
So local (local as in including all subnets) clients dump there mail from user@domain.com to this smarthost, this one bothers with the smtp-auth. Right now scalix looks just like an ordinary client to this local smarthost and mail is sent to the rest of the world. Mail from the internet does not get to scalix so far (I have to rethink how I want to integrate fetchmail here without interfering with the users as long as this is just a testsetup).

.oO( what was the question again? *g* )

so, what do I want to change... turning this SuSE box into a debian box would be a great start!

No, no real questions related to smarthost foo left by now, even if I am open-minded if someone has comments and suggestions on my setup. Also I am not sure if I want to migrate all the mailstuff from the smarthost to the scalix server when scalix is used prductively... but I think no one can help me with it right now