Civileme <[EMAIL PROTECTED]> writes:
> > Yes, /etc/postfix/main.cf was read as broken by webmin-0.80 apparently
> > because the hostname wasn't loaded into the file--just left for a default
> > which may not have been read correctly by webmin.
uh?
on my configuration, the "myhostname" parameter is commented (preceded by
a "#") and it works fine..
> > I set up a test sequence.
> >
> > 1. touch /etc/postfix/webmin
> AAAACCCKKK!!! /etc/postfix/main.cf I need some strong coffee!
> > 2. put the hostname in and clear the #
> > 3. do 2 plus the next general parameter
> > *
> > *
> > *
> >
> > Anyway, after going back to webmin having performed step 2 and a sync, the
> > whole configuration presented itself for modification. Prior to that, it
> > had said the config file had errors and I must edit it by hand.. Setp 3
> > was never necessary to be perform.
When the config file has errors, the postfix-webmin module cannot do
anything..:
You deserve one little explanation on that issue: when "postfix check"
fails, it verifies that it is connected to a terminal, and if not, doesn't
send the failing parameters; so I can't present the errors in the Webmin
interface. We got a headache with Francis on this problem, but can't seem
to be able to fix it from the Webmin side; (I don't want to patch Postfix
for that).
To clarify: the initial config file was containing the error? or you did
modify it?
--
Guillaume Cottenceau
