[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cobalt-users] using an mc file to configure sendmail



> I have trouble keeping track of what sendmail is doing, because the
> web interface simply changes the sendmail.cf file (as do those who
> follow the many comments on this list). On a 550, the 
> cobalt.mc file is at /usr/lib/sendmail-cf/cf/cobalt.mc.
> 
> No in order for somthing similar to work on a RaQ (550 -- maybe
> others) I needed to change the line near the top 
> from:  include(`m4/cf.m4')dnl
> to:    include(`/usr/lib/sendmail-cf/m4/cf.m4')dnl
> and this allows me to build sendmail in a local directory but in a
> standard way.
> 
> m4 /usr/lib/sendmail-cf/m4/cf.m4 ~/etc/mail/cobalt.mc > sendmail.cf
> 
> Are there any expers out there who can tell me if I can bypass the web
> face altogether, since I find this easier. Or even what the web face
> changes. Also, if anyone is using MailScanner and SpamAssasin how to
> they access sendmail. After I installed nuonces mailscanner package it
> looked like it a: completely rewrote /etc/rc.d/init.d/sendmail and b:
> created a new sendmail.cf file called sendmail.b4.mailscanner.cf.
> 
> The web inteface allows "immediate delivery" or scheduled times and
> setting a forced host name Dm. But the rest seems to be missing. Any
> ideas. I'm really just trying to track down a problem and determine if
> it is mail or dns. (I've been known to screw them both up
> simulataneously.)

Josh,

Since this is my package, let me take a moment to explain 
what is happening here.  When Cobalt release updates, they 
never take the time to modify the original cobalt.mc file.  Not 
sure why they do not, I just know that they don't. If you take 
a look at the file, you will notice that POP4SMTP and the 
mailing list section is almost missing.  Not a big, as you 
typically do NOT need to modify the sendmail.cf.  The only 
time you will, is if you want to add features to it, like Real 
Time Black Whole Lists and what not.

The "new" /etc/rc.d/init.d/sendmail is because MailScanner 
needs to loads some applications prior to loading Sendmail.  
The orginal Sendmail init script is there.  If I would have left 
it the default "MailScanner" file, the Cobalt would have run 
into issues if it ever thought Sendmail wasn't running.  It would 
start the process using the incorrect startup file.  So, to avoid 
that, I just simple renamed it.  Nothing at all wrong with that.

As far as the "sendmail.b4.mailscanner.cf" ... if you run a 
"diff" against that, and the orginal mailscanner.cf, you should 
only see that the Queue Directories has changed.  That is 
because MailScanner will barf if there is a "q1 q2 q3 q4"
directory within the actual /var/spool/ directory.  So, instead 
of having MS complain, I simple fixed sendmail from creating 
those files.

The configuration to allow Email is quite simple.  The changes 
that are in the GUI will still update the files on the system.  
What you see in the GUI is actually stored in flat files in the 
/usr/sasualito directory.

Please note, like I said ... if you use the "cobalt.mc" file, you
will break Sendmail.  I know that sounds stupid and what not
but it is the truth.  Go ahead and compile the mc into a cf file
and then run a diff against the orginal sendmail.cf (sendmail.b4)
you will see that there are a few extra lines in the orginal one
verses the one that you just created.

I hope that explains the questions that you are having, if they
do not, please contact me off list.

Thanks,
Brian

-- 
This message has been scanned for viruses and
dangerous and is believed to be clean.