yet another sendmail configuration problem - OpenSuSE 10.1

[michael.jeier]

Thanks! But I did it a little bit different: I just used some sendmail.mc, which I found on the internet. I think it's basically the same as using the linux.mc. I had to customize it though. The thing that was missing is the authinfo Feature, which consequently then added the right entries to the sendmail.cf. I'll clean that mess up now and try to see if I can merge the new entries into my old sendmail.cf.
Btw, I can send now via the ISP's smtp, BUT I did not run omsendin (yet). So, there's absolutely no Scalix specific stuff in the sendmail.cf, but it works anyway I'm wondering if I SHOULD run the omsendin then. There might be some drawbacks, when those Scalix entries are missing. I'll see.

[btisdall]

You should definitely run omsendin asap - depending on your precise scalix setup you'll have varying degrees of broken-ness otherwise.

[florian]

on suse, there is an additional level of warning. SuSE by default does not use a straightforward .mc mechanism; it actually has SuSEconfig that generates .mc and .cf from /etc/sysconfig/mail and /etc/sysconfig/sendmail. My experience is that one should not try to tweak suse's mechanism too much, but rather modify those files, run the config file generation and only then start tweaking manually....

--f.

[michael.jeier]

Aww, I thought I was nearly done with that problem.
Thanks for the comments!! I'll definitely run omsendin then. I'll also take a final look at the config files of SuSE (I think I did that already), but I think one cannot set the authorization to a SMTP server there (this is quite simply a bug in SuSE). I'll let you know...

[jaime.pinto]

I just realized I may have been downloading from the wrong area (or the wrong software):

I followed the "Editions: Free 60-Day Trial" path after requesting a trial license a few minutes ago. I got a name and password and was prompted to download 'scalix-11.0.4-GA-enterprise-redhat-intel.tgz'. That was obvious enough.

But as an existing customer I could not find a downloading area for me (no notification email with name/password received yet). So a few weeks back I went to the only place I could get something: the community area. From there my last download was 'scalix-11.0.4-GA-core-rhel4-intel.tar'

Are scalix-11.0.4-GA-enterprise-redhat-intel.tgz and scalix-11.0.4-GA-core-rhel4-intel.tar the same?

In any case I think there is room for improvement. I am not all that smart, I admit, but we have some money. Please do something for somebody like me.

Jaime

[florian]

It is fundamentally the same software, just a different packaging:

- the core package only has one distro (rhel4 in your case), while the enterprise packaging is by family (rhel3,rhel4 and fc5)
- the enterprise package comes with the outlook connector, while for community/core this is a separate download file
- the enterprise package has some bits that are not available for community edition (active directory extensions, attachment text extractors)

But again, the rpms that exist in both packages ARE the same bits.

I didn't know that you were already a commercial customer - when did you buy? Can you ping me via email and I shall find out why you didn't receive the update/download notifications (the last, for 11.0.4, should have been sent out on 05/03).

Final question - is this related to the rest of this thread??

Florian.

[michael.jeier]

That was completely offtopic, so I skip on the last two threads, but I'm glad that you have some money, while not being so smart, Jamie. Good for you!

OK, so when I ran "omsendin" my smtp customizations were gone. I don't blame Scalix for that, it probably uses the internal SuSE configuration. This configuration (/etc/sysconfig/mail and /etc/sysconfig/sendmail, or via YAST) seems not sufficient enough to configure a smarthost with authentication.The sendmail documentation says that with "customisations you cannot achieve". (see http://www.sendmail.org/faq/section5.html#5.3.2.1)

So, here's what I changed in the sendmail.cf-file:
- Add

Code: Select all

#####  $Id: authinfo.m4,v 1.9 2002/06/27 23:23:57 gshapiro Exp $  #####

somewhere between

Code: Select all

#####  $Id: use_ct_file.m4,v 8.11 2001/08/26 20:58:57 gshapiro Exp $  #####

and

Code: Select all

 #####  $Id: no_default_msa.m4,v 8.2 2001/02/14 05:03:22 gshapiro Exp $  #####

on top of the file.
- above the "options" (look for similar entries), add the following

Code: Select all

# authinfo list database: contains info for authentication as client
Kauthinfo hash -o /etc/mail/auth/auth-info.db

- edit the smart host entry like this:

Code: Select all

# "Smart" relay host (may be null)
DSsmtp.myisp.adress

- uncomment the authentication mechanisms

Code: Select all

# list of authentication mechanisms
O AuthMechanisms=EXTERNAL GSSAPI DIGEST-MD5 CRAM-MD5 LOGIN PLAIN

- edit the authinfo rule like this:

Code: Select all

######################################################################
###  authinfo: lookup authinfo in the access map
###
###   Parameters:
###      $1: {server_name}
###      $2: {server_addr}
######################################################################
Sauthinfo
R$*      $: <$(authinfo AuthInfo:$&{server_name} $: ? $)>
R<?>      $: <$(authinfo AuthInfo:$&{server_addr} $: ? $)>
R<?>      $: <$(authinfo AuthInfo: $: ? $)>
R<?>      $@ no            no authinfo available
R<$*>      $# $1

This is like using the following in the sendmail.mc:

Code: Select all

  define(`SMART_HOST',`smtp.myisp.adress')dnl
  define(`confAUTH_MECHANISMS', `EXTERNAL GSSAPI DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl
  FEATURE(`authinfo',`hash /etc/mail/auth/auth-info')dnl


This assumes that you have made a database containing the client information at /etc/mail/auth/auth-info.db (see http://www.scalix.com/wiki/index.php?title=HowTos/MTA_Integration under section "Smarthost configuration" ," Setting up a Smarthost with sendmail").

Finally, to keep your configuration save from SuSE you add to the top of /sbin/conf.d/SuSEconfig.sendmail:

Code: Select all

# do not run this configuration to keep the sendmail SMTP customizations
exit


Hopefully, sendmail is all set now. Let's see how much fun the SSL configuration will be...

[florian]

Michael,

glad that this works for you and agree that the config file structure for some OS components (including the MTAs) in SuSE is somewhat awkward for anything that goes beyond the most straightforward usecase. Your changes look very logical to me. As a side remark, it is possible to tell yast not to update sendmail.cf through an official configuration option, this can be found in /etc/sysconfig/mail:

Code: Select all

# If you don't want to let SuSEconfig generate your
# configuration file, set this to no
#
MAIL_CREATE_CONFIG="no"

And I actually believe omsendin sets this automatically when we run it. I hope it does. .

So, your 'hack' to prevent suseconfig from doing anything *should* not strictly be necessary unless I am missing anything.

To close up on the other sub-thread, I have found Jaime's customer record in the meantime and added him as a contact to receive new version notification updates; this was simply a mixup in email addresses - so just to be clear, commercial Scalix customers will get immediate notification and full download information when a new or updated version becomes available.

Cheers,
Florian.