i got the info from the internet, that the aliases are read from the aliases.db
since this is not updated when saving aliases with webmin the mails are not delivered correctly.
there should always be send "newaliases" after each aliases-saving to update aliases.db
cheers
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That message comes from Postfix, but it is completely harmless (assuming that your email is actually being delivered to aliases properly).
i'm not sure.
i got the info from the internet, that the aliases are read from the aliases.db
since this is not updated when saving aliases with webmin the mails are not delivered correctly.
there should always be send "newaliases" after each aliases-saving to update aliases.db
cheers
looking on the internet they say you have always to sne a:
newaliases
after changing anything in the aliases setup to update the aliases.db.
it seems that webmit does not send this message after saving changings.
atleast, if i send this manually afterwards, the error does not come.
cheers
Actually, Webmin already runs the "newaliases" command after each update to the aliases list.
so may be something is broken there.
atleast it works only if i do this manually each time afterwards.
is there a way to verify if this command is beeing sent?
cheers
hi again,
could it be my configuration visible in the attached img,
that i always get this error after saving aliases?
if so would i need to use option two, say insert the hash:/etc/aliases in the second line?
thanks for advice,
in fact it's not very clear to me <bg></bg>
cheers
My apologies - I found a case where Webmin is doing this wrong, causing the newaliases command to fail. I will fix this in the next release.
Thanks