I’m running postfix on Tumbleweed. I configured the mysql plugin to certain data to a database so PostfixAdmin can pick them up.
Since several weeks, when I check the journal for user postfix I see unused parameters for every line in the mySQL config lines:
This used to work without errors. So I figure something has changed perhaps within Postfix, but all I can find regarding this subject are the same settings I already have.
Well, at some point I made a backup of /etc/postfix, deleted the directory and forced a reinstall. Actually I copied main.cf and master.cf from /var/adm/backup/postfix/, installed yast2 e-mail-server and everything was fine again.
Perhaps re-running mysql_secure_installation might fix your problem (It’s the install script that configures your mariadb/mysql security configuration).
The following web page I created describes what it is, and if you wish to create a HereDoc to standardize your configuration (Like your current situation, re-apply what you configured before, or if you’re installing and maintain a farm to apply the same settings to all).
I’ll checkout what you both said, although, I don’t believe in reinstalling and than hoping the problem goes away. That doesn’t sound very logical to me. Especially when keeping the main and master files which most likely contain the wrong setting to begin with. Also, I didn’t configure postfix with yast.
It worked, and it stopped working without me touching it. So changes must have come with an update (guess).
I checked mariaDB. Settings are still there. All accounts work, other products connecting to a db are working also.
I can log in with my ‘superuser’ from the cli.
Also, if it was the database, you would get log in errors I think. Now it is clearly a Postfix error saying it just doesn’t understand the parameters.
The same problem here.
It started after Postfix update ftom 3.2.x to version 3.3.0 and I have not found a solution to get rid of these warnings.
Basically, everything works, only the log file is full of these warnings.
And warnings come when starting Postfix.
Has anyone found the cause of these warnings?
Now the second bugzilla link tsu2 provided is exactly the problem I have. Yes it offers no solution, they do suspect it is just visual yet still working. This I can confirm. The problem is that your logs are flooding with these errors from time to time.