Re: [opensuse-factory] New Tumbleweed snapshot 20180320 released!
As I understand these warnings are because of postfix version update (3.2.4 -> 3.3.0) * The postconf command now warns about unknown parameter names in a Postfix database configuration file. As with other unknown parameter names, these warnings can help to find typos early. How I can turn these warnings off? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi,
As I understand these warnings are because of postfix version update (3.2.4 ->> 3.3.0)
* The postconf command now warns about unknown parameter names in a Postfix database configuration file. As with other unknown parameter names, these warnings can help to find typos early.
How I can turn these warnings off?
remove the unknown parameters? Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
I can't. All these parameters are required (dbname, password, username, hosts etc) And as I said before, whole mail system works, only warnings on Postfix startup.
As I understand these warnings are because of postfix version update (3.2.4 ->> 3.3.0)
* The postconf command now warns about unknown parameter names in a Postfix database configuration file. As with other unknown parameter names, these warnings can help to find typos early.
How I can turn these warnings off?
remove the unknown parameters? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Argo,
I can't. All these parameters are required (dbname, password, username, hosts etc) And as I said before, whole mail system works, only warnings on Postfix startup.
postconf -m | grep mysql gives a result? And how did you specify this lookup table in main.cf?
As I understand these warnings are because of postfix version update (3.2.4 ->>> 3.3.0)
Maybe, mabe not. [...] Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi! postconf -m | grep mysql gives me output mysql In main.cf there are: virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf, mysql:/etc/postfix/mysql_virtual_mailbox_domainaliases_maps.cf virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_maps.cf, mysql:/etc/postfix/mysql_virtual_alias_domainaliases_maps.cf virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_domains_maps.cf smtpd_sender_login_maps = mysql:/etc/postfix/mysql_virtual_sender_login_maps.cf Argo
I can't. All these parameters are required (dbname, password, username, hosts etc) And as I said before, whole mail system works, only warnings on Postfix startup.
postconf -m | grep mysql gives a result? And how did you specify this lookup table in main.cf?
As I understand these warnings are because of postfix version update (3.2.4 ->>> 3.3.0)
Maybe, mabe not. [...] Bye. Michael. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Argo,
Hi!
postconf -m | grep mysql gives me output mysql
In main.cf there are: virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf, mysql:/etc/postfix/mysql_virtual_mailbox_domainaliases_maps.cf virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_maps.cf, mysql:/etc/postfix/mysql_virtual_alias_domainaliases_maps.cf virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_domains_maps.cf smtpd_sender_login_maps = mysql:/etc/postfix/mysql_virtual_sender_login_maps.cf
Argo
last idea: Run postmap again for all of the mysql maps. But I suspect this would help. strings $( which postconf ) | grep <any mysql param> does not return anything. strings $( which postconf ) | grep mysql gives "mysql", though. Maybe a bug in postconf? Wrong build? Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
The subject of your email is not what your email is about. "Re: [opensuse-factory] New Tumbleweed snapshot 20180320 released!" This subject line is about a new TW snapshot...interesting to most [opensuse-factory] subscribers. Your email is not that. As requested in every TW snapshot release messages: "When you reply to report some issues, make sure to change the subject. It is not helpful to keep the release announcement subject in a thread while discussing a specific problem." Not only is it not helpful. It's irritating to some people. Makes people less inclined to read your message and possibly help sort out your problem. On 03/29/2018 12:23 PM, Michael Hirmke wrote:
Hi Argo,
Hi!
postconf -m | grep mysql gives me output mysql
In main.cf there are: virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf, mysql:/etc/postfix/mysql_virtual_mailbox_domainaliases_maps.cf virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_maps.cf, mysql:/etc/postfix/mysql_virtual_alias_domainaliases_maps.cf virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_domains_maps.cf smtpd_sender_login_maps = mysql:/etc/postfix/mysql_virtual_sender_login_maps.cf
Argo
last idea:
Run postmap again for all of the mysql maps.
But I suspect this would help.
strings $( which postconf ) | grep <any mysql param>
does not return anything.
strings $( which postconf ) | grep mysql
gives "mysql", though.
Maybe a bug in postconf? Wrong build?
Bye. Michael.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
The subject of your email is not what your email is about. "Re: [opensuse-factory] New Tumbleweed snapshot 20180320 released!" This subject line is about a new TW snapshot...interesting to most [opensuse-factory] subscribers.
Your email is not that.
As requested in every TW snapshot release messages: "When you reply to report some issues, make sure to change the subject. It is not helpful to keep the release announcement subject in a thread while discussing a specific problem."
Not only is it not helpful. It's irritating to some people. Makes people less inclined to read your message and possibly help sort out your problem.
why do you shoot on me? I'm not the original poster. Do you want me to change his subject? Why don't you tell him? Nevertheless I changed the subject for my latest reply. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 03/29/2018 01:50 PM, Michael Hirmke wrote:
The subject of your email is not what your email is about. "Re: [opensuse-factory] New Tumbleweed snapshot 20180320 released!" This subject line is about a new TW snapshot...interesting to most [opensuse-factory] subscribers.
Your email is not that.
As requested in every TW snapshot release messages: "When you reply to report some issues, make sure to change the subject. It is not helpful to keep the release announcement subject in a thread while discussing a specific problem."
Not only is it not helpful. It's irritating to some people. Makes people less inclined to read your message and possibly help sort out your problem.
why do you shoot on me? I'm not the original poster. Do you want me to change his subject? Why don't you tell him?
I posted to the list, not to you. Consequently, he _was_ told. Several people have commented on this faux pas that continues to appear. This is not a problem for me. Upon realizing that yet another person has not followed instructions, I usually delete the message unless it's pertinent to me. And then trying to find it again with its automated TW snapshot release message is difficult. So in many ways this oversight is not helpful, and potentially detrimental to the person and to the list. Yes, I want you to change the subject. Many people want to help as you have done, Michael. Changing the subject line makes your help more useful. In addition, I know first hand how it is when my machine doesn't work. At such times, I'm not inclined to read the fine print. I apologize for irritating if that happened. After a couple of people complained of the issue, I realized that my ignoring these messages just helps keep it in place. Thank you for being willing to help solve a problem.
Nevertheless I changed the subject for my latest reply.
Thank you for doing that. It is more helpful than the non-descriptive TW release message. Carl -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Carl, [...]
why do you shoot on me? I'm not the original poster. Do you want me to change his subject? Why don't you tell him?
I posted to the list, not to you. Consequently, he _was_ told. Several
Of course he could read it, but you answered directly on my message. Shouldn't you have answered the original message? Perhaps just nitpicking, but it was really irritating. [...]
Carl
bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 03/30/2018 01:58 AM, Michael Hirmke wrote:
Hi Carl,
[...]
why do you shoot on me? I'm not the original poster. Do you want me to change his subject? Why don't you tell him?
I posted to the list, not to you. Consequently, he _was_ told. Several
Of course he could read it, but you answered directly on my message. Shouldn't you have answered the original message? Perhaps just nitpicking, but it was really irritating.
Yes, it would have been the right thing to do; I had already deleted the original message. It may seem that I answered directly to you; I didn't. Your message came from the mailing list. My reply went to the mailing list...after I had just read several complaints and suggestions for how to automate rejecting such mistaken messages...and realizing that my inaction was part of the problem. The subject: "My computer won't fill in the right subject line for me" addresses the first person's message. It also relates to the hundreds of similar messages that are distracting and irritating. I have a filter for the messages from Dominique Leuenberger with the New TW Release subject. When someone does not comply with the request "make sure to change the subject", "it is not helpful". That suggestion is in _every New TW Snapshot Release message_. As near as I can determine, the practice of including that request started with: [opensuse-factory] New Tumbleweed snapshot 20160724 released! Tue, Jul 26, 2016 at 10:53 PM (PST) I don't understand what you want. I already apologized for being an irritant. My closest friends say it's one of my better traits. Carl
[...]
Carl
bye. Michael.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Carl, [...]
I don't understand what you want. I already apologized for being an
perhaps I couldn't express it better (I'm not a native speaker). I don't need any apology, I just wanted to understand.
irritant. My closest friends say it's one of my better traits.
:)
Carl
Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi! Maybe you are right about wrong build or something, because Webmin Postfix module shows Postfix version 3.2.4 not 3.3.0 as it should be. Argo Hi Argo, last idea: Run postmap again for all of the mysql maps. But I suspect this would help. strings $( which postconf ) | grep <any mysql param> does not return anything. strings $( which postconf ) | grep mysql gives "mysql", though. Maybe a bug in postconf? Wrong build? Bye. Michael. -- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Argo,
Hi!
Maybe you are right about wrong build or something, because Webmin Postfix module shows Postfix version 3.2.4 not 3.3.0 as it should be.
no, I have definitley postfix 3.3.0 and *my* postconf doesn't contain these strings. So it might be a problem with postconf from postfix 3.3.0.
Argo
Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Michael Hirmke wrote:
Hi Argo,
Hi!
postconf -m | grep mysql gives me output mysql
In main.cf there are: virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf, mysql:/etc/postfix/mysql_virtual_mailbox_domainaliases_maps.cf virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_maps.cf, mysql:/etc/postfix/mysql_virtual_alias_domainaliases_maps.cf virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_domains_maps.cf smtpd_sender_login_maps = mysql:/etc/postfix/mysql_virtual_sender_login_maps.cf
Argo
last idea:
Run postmap again for all of the mysql maps.
Just fyi, they're not database files that need hasing, they're textual config files.
Maybe a bug in postconf? Wrong build?
May be someting like that, yes. -- Per Jessen, Zürich (4.4°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, [...]
last idea:
Run postmap again for all of the mysql maps.
Just fyi, they're not database files that need hasing, they're textual config files.
oops, I don't use mysql for postfix, but I thought they are maps as many of the other postfix config files. Thx for clarification.
Maybe a bug in postconf? Wrong build?
May be someting like that, yes.
Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Michael Hirmke wrote:
Hi,
As I understand these warnings are because of postfix version update (3.2.4 ->> 3.3.0)
* The postconf command now warns about unknown parameter names in a Postfix database configuration file. As with other unknown parameter names, these warnings can help to find typos early.
How I can turn these warnings off?
remove the unknown parameters?
They are neither unknown nor unused, that's the point - a postfix mysql config needs e.g. "dbname" and "password". -- Per Jessen, Zürich (5.3°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Ok, I understand, but what have changed? Everything worked fine and without warnings before this (3.2.4 -> 3.3.0) update. It works now also, but on Postfix startup there are warnings. I can't find any documentation about the changes in postfix 3.3.0 mysql syntax or options. Argo
Hi,
As I understand these warnings are because of postfix version update (3.2.4 ->> 3.3.0)
* The postconf command now warns about unknown parameter names in a Postfix database configuration file. As with other unknown parameter names, these warnings can help to find typos early.
How I can turn these warnings off?
remove the unknown parameters?
They are neither unknown nor unused, that's the point - a postfix mysql config needs e.g. "dbname" and "password". -- Per Jessen, Zürich (5.3°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op donderdag 29 maart 2018 11:08:26 CEST schreef Argo Sieger:
Ok, I understand, but what have changed? Everything worked fine and without warnings before this (3.2.4 -> 3.3.0) update. It works now also, but on Postfix startup there are warnings. I can't find any documentation about the changes in postfix 3.3.0 mysql syntax or options.
Argo
Hi,
As I understand these warnings are because of postfix version update (3.2.4
->> 3.3.0)
* The postconf command now warns about unknown parameter names in a Postfix database configuration file. As with other unknown parameter names, these warnings can help to find typos early.
How I can turn these warnings off?
remove the unknown parameters?
They are neither unknown nor unused, that's the point - a postfix mysql config needs e.g. "dbname" and "password".
-- Per Jessen, Zürich (5.3°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland.
Try to 'grep' on the cf files, you may have double entries somehow. -- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
There is no double entries in mysql_xxx_maps.cf Already checked. Op donderdag 29 maart 2018 11:08:26 CEST schreef Argo Sieger:
Ok, I understand, but what have changed? Everything worked fine and without warnings before this (3.2.4 -> 3.3.0) update. It works now also, but on Postfix startup there are warnings. I can't find any documentation about the changes in postfix 3.3.0 mysql syntax or options.
Argo
Hi,
As I understand these warnings are because of postfix version update (3.2.4
->> 3.3.0)
* The postconf command now warns about unknown parameter names in a Postfix database configuration file. As with other unknown parameter names, these warnings can help to find typos early.
How I can turn these warnings off?
remove the unknown parameters?
They are neither unknown nor unused, that's the point - a postfix mysql config needs e.g. "dbname" and "password".
-- Per Jessen, Zürich (5.3°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland.
Try to 'grep' on the cf files, you may have double entries somehow. -- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
Argo Sieger -
Carl Symons -
Knurpht ＠ openSUSE -
mh＠mike.franken.de -
Per Jessen