Re: Found error in docker-container
Hi Alex,
On Wed, Jul 5, 2017, at 03:21 AM, Alexander Klotz wrote:
Hi,
one of our developers wanted to point out an error he found in mailman 3.1, docker container maxking/mailman-core-0.1
The entries in /opt/mailman/core/var/data/postfix_lmtp are not set correctly, example:
/^testlist@mailman\.example\.com$/ lmtp:[172.19.199.2# IP Address of mailman-core container]:8024
this actually should look like this:
/^testlist@mailman\.example\.com$/ lmtp:[172.19.199.2]:8024
Can you send a copy of your Mailman configuration that you added at
/opt/mailman/core/mailman-extra.cfg
?
I think this is mostly because the configuration parser doesn't understand the in-line comments. So, if you are using the configuration exactly as it is mentioned in the documentation, it could be the cause of this problem.
Solution to that would be to just remove all the in-line comments.
[mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 172.19.199.2 # IP Address of mailman-core container lmtp_port: 8024 smtp_host: 172.19.199.1 # IP Address of host where postfix is. smtp_port: 25 configuration: /etc/postfix-mailman.cfg
Like the two comments seen in the configuration above.
I will update the documentation too so that others don't get caught in something like this.
Thanks!
-- thanks, Abhilash Raj
Hi Abhilash,
Can you send a copy of your Mailman configuration that you added at
/opt/mailman/core/mailman-extra.cfg
?
Here it is:
[mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 172.19.199.2 lmtp_port: 8024 smtp_host: 172.19.199.1 smtp_port: 25 configuration: /etc/postfix-mailman.cfg
Regards, Alex
Hi,
unfortunately I have to get back to this topic, since there's still a problem. We already removed the comments as you suggested, but we still have to make manual corrections when creating a new list, because the alias information is safed incorrectly in the tables of the postfix host. There is a port indication with a "]" in the comments, but it is incomplete. The proper address has to be inserted here.
Regards, Alex
On Wed, Jul 5, 2017, at 03:21 AM, Alexander Klotz wrote:
Hi,
one of our developers wanted to point out an error he found in mailman 3.1, docker container maxking/mailman-core-0.1
The entries in /opt/mailman/core/var/data/postfix_lmtp are not set correctly, example:
/^testlist@mailman\.example\.com$/ lmtp:[172.19.199.2# IP Address of mailman-core container]:8024
this actually should look like this:
/^testlist@mailman\.example\.com$/ lmtp:[172.19.199.2]:8024
Can you send a copy of your Mailman configuration that you added at
/opt/mailman/core/mailman-extra.cfg
?I think this is mostly because the configuration parser doesn't understand the in-line comments. So, if you are using the configuration exactly as it is mentioned in the documentation, it could be the cause of this problem.
Solution to that would be to just remove all the in-line comments.
[mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 172.19.199.2 # IP Address of mailman-core container lmtp_port: 8024 smtp_host: 172.19.199.1 # IP Address of host where postfix is. smtp_port: 25 configuration: /etc/postfix-mailman.cfg
Like the two comments seen in the configuration above.
I will update the documentation too so that others don't get caught in something like this.
Thanks!
-- Mit freundlichen Grüßen, Alexander Klotz
(redaktion kulturserver)
mailto:alexk@kulturserver.de
Stiftung kulturserver.de gGmbH
Lothringerstraße 23 D-52062 Aachen http://ggmbh.kulturserver.de
Geschäftsführer: Wolfgang Knauff
Amtsgericht Aachen* *Handelsregister-Nr.:B 10515 Umsatzsteuer-Identifikations-Nr.:DE DE 230868040
Hi Alex,
On Mon, Jul 17, 2017, at 06:32 AM, Alexander Klotz wrote:
Hi,
unfortunately I have to get back to this topic, since there's still a problem. We already removed the comments as you suggested, but we still have to make manual corrections when creating a new list, because the alias information is safed incorrectly in the tables of the postfix host. There is a port indication with a "]" in the comments, but it is incomplete. The proper address has to be inserted here.
Let me do some testing before I answer this, so I will get back to you with some better answers than "it should not be happening".
Regards, Alex
On Wed, Jul 5, 2017, at 03:21 AM, Alexander Klotz wrote:
Hi,
one of our developers wanted to point out an error he found in mailman 3.1, docker container maxking/mailman-core-0.1
The entries in /opt/mailman/core/var/data/postfix_lmtp are not set correctly, example:
/^testlist@mailman\.example\.com$/ lmtp:[172.19.199.2# IP Address of mailman-core container]:8024
this actually should look like this:
/^testlist@mailman\.example\.com$/ lmtp:[172.19.199.2]:8024
Can you send a copy of your Mailman configuration that you added at
/opt/mailman/core/mailman-extra.cfg
?I think this is mostly because the configuration parser doesn't understand the in-line comments. So, if you are using the configuration exactly as it is mentioned in the documentation, it could be the cause of this problem.
Solution to that would be to just remove all the in-line comments.
[mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 172.19.199.2 # IP Address of mailman-core container lmtp_port: 8024 smtp_host: 172.19.199.1 # IP Address of host where postfix is. smtp_port: 25 configuration: /etc/postfix-mailman.cfg
Like the two comments seen in the configuration above.
I will update the documentation too so that others don't get caught in something like this.
Thanks!
-- Mit freundlichen Grüßen, Alexander Klotz
(redaktion kulturserver)
mailto:alexk@kulturserver.de
Stiftung kulturserver.de gGmbH
Lothringerstraße 23 D-52062 Aachen http://ggmbh.kulturserver.de
Geschäftsführer: Wolfgang Knauff
Amtsgericht Aachen* *Handelsregister-Nr.:B 10515 Umsatzsteuer-Identifikations-Nr.:DE DE 230868040
-- thanks, Abhilash Raj
Hi Alex,
On Mon, Jul 17, 2017, at 06:32 AM, Alexander Klotz wrote:
Hi,
unfortunately I have to get back to this topic, since there's still a problem. We already removed the comments as you suggested, but we still have to make manual corrections when creating a new list, because the alias information is safed incorrectly in the tables of the postfix host. There is a port indication with a "]" in the comments, but it is incomplete. The proper address has to be inserted here.
Unfortunately, I am not able to replicate this problem in my setup.
[mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 172.19.199.2 lmtp_port: 8024 configuration: /etc/postfix-mailman.cfg
I have just this configuration for LMTP and it seems to generate correct required LMTP transport files for me.
I also tried running postfix and made it read this file and things seem to be working.
Can you try running a fresh new image and see if the problem still persists?
$ docker rm -f mailman-core $ docker-compose create mailman-core $ docker-compose up -d mailman-core
Unless the old configuration with comments is cached somewhere, I can't imagine why Core is generating wrong maps.
Also, can you check if the mailman is using correct configuration?
$ docker exec -it mailman-core mailman conf
This should print all the configuration, maybe you can grep to see everything related to mta is there as you'd expect?
Hope it helps!
Regards, Alex
On Wed, Jul 5, 2017, at 03:21 AM, Alexander Klotz wrote:
Hi,
one of our developers wanted to point out an error he found in mailman 3.1, docker container maxking/mailman-core-0.1
The entries in /opt/mailman/core/var/data/postfix_lmtp are not set correctly, example:
/^testlist@mailman\.example\.com$/ lmtp:[172.19.199.2# IP Address of mailman-core container]:8024
this actually should look like this:
/^testlist@mailman\.example\.com$/ lmtp:[172.19.199.2]:8024
Can you send a copy of your Mailman configuration that you added at
/opt/mailman/core/mailman-extra.cfg
?I think this is mostly because the configuration parser doesn't understand the in-line comments. So, if you are using the configuration exactly as it is mentioned in the documentation, it could be the cause of this problem.
Solution to that would be to just remove all the in-line comments.
[mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 172.19.199.2 # IP Address of mailman-core container lmtp_port: 8024 smtp_host: 172.19.199.1 # IP Address of host where postfix is. smtp_port: 25 configuration: /etc/postfix-mailman.cfg
Like the two comments seen in the configuration above.
I will update the documentation too so that others don't get caught in something like this.
Thanks!
-- Mit freundlichen Grüßen, Alexander Klotz
(redaktion kulturserver)
mailto:alexk@kulturserver.de
Stiftung kulturserver.de gGmbH
Lothringerstraße 23 D-52062 Aachen http://ggmbh.kulturserver.de
Geschäftsführer: Wolfgang Knauff
Amtsgericht Aachen* *Handelsregister-Nr.:B 10515 Umsatzsteuer-Identifikations-Nr.:DE DE 230868040
-- thanks, Abhilash Raj
participants (2)
-
Abhilash Raj
-
Alexander Klotz