On Thu, 1 Oct 1998, Robert W. Canary wrote:
> Hi,
>
> Steve Cassidy wrote:
> >
> > I'm having a mail problem. I get my mail with fetchmail onto my laptop which
> > forwards it using smtp to my local maildrop. Linuxconf has stuck some
> > anti-spam lines into sendmail.cf which seem to be resulting in my losing
> > messages due to the 'junk' not being there, here are two error messages:
> >
> > Sep 29 08:46:06 sputnik sendmail[11570]: IAA11570: SYSERR(root): Unknown
> > ruleset junk
> >
> > Sep 28 16:08:51 sputnik sendmail[10831]: NOQUEUE: SYSERR(steve):
> > /etc/sendmail.cf: line 216: readcf: map junk: class dbm not
> > available
> >
> > Deselecting the anti-spam option doesn't seem to remove these lines from
> > sendmail.cf, the junk map file is there but empty. I've resorted to disabling
> > mailconf and hand editing sendmail.cf to try to remove the references to junk,
> > I can't seem to find an archived sendmail.cf from pre-linuxconf.
> >
> > Apart from this problem the mailconf setup is great, it was doing just what I
> > wanted. Any help appreciated.
> >
>
> I don't know how to help you on this, but I would like for the module
> writers to take note of this situation. linuxconf *should not* be
> allowed to put option/configurations into a system setup, without the
> SysAdmin
> knowing about it. linuxconf modules *should* give the ability to edit
> blocks of
> a configuration file, and even tag them to tell linuxconf modules to
> leave them alone.
> :-)
sendmail.cf is really a file apart. While in a sens, it is a config file,
it is very complicate to parse and update. Most tools (all) generate the
file based on other information. Linuxconf does the same.
For other config file, linuxconf just edit the file and let you see the
feature. Changing them in linuxconf or in an editor is about the same.
Linuxconf does not generate or set various flags without you knowing about
it. So tagging a section of a file is not relevant. Except for
sendmail.cf, you are allowed to work with an editor and then with
linuxconf and then with the editor without problem. This has always been a
spec of linuxconf.
As for sendmail.cf, when linuxconf replace a sendmail.cf which was not
written by itself, it prompts the admin with a pretty large popup. If you
do a single change in sendmail.cf after that, linuxconf will notice as it
keeps a MD5 checksum of the file it generated. The popup will show up
again.
Linuxconf does that only for sendmail.cf. For other config file, there is
no point as linuxconf reads it and write it, even trying to preserve
comments and ordering as much as possible.
--------------------------------------------------------
Jacques Gelinas ([EMAIL PROTECTED])
Linuxconf: The ultimate administration system for Linux.
see http://www.solucorp.qc.ca/linuxconf
new developments: remote GUI admin, multiple machines admin, wu-ftpd
---
You are currently subscribed to linuxconf as: [[email protected]]
To unsubscribe, forward this message to [EMAIL PROTECTED]