Mark Sapiro wrote:

...

ERROR 2021-05-24 16:22:22,895 1648 django.security.DisallowedHost Invalid HTTP_HOST header: 'tgc_mailman_web:8000'. The domain name provided is not valid according to RFC 1034/1035. WARNING 2021-05-24 16:22:22,896 1648 django.request Bad Request: /postorius/api/templates/list/homepage.gruppe.tgcamberg1848.de/list:member:regular:footer It appears you created the new template with Postorius, but there is an issue for Postorius templates. Possibly your Django setting for POSTORIUS_TEMPLATE_BASE_URL needs to be adjusted. Obviously I have a problem with the hostname. I set [code] POSTORIUS_TEMPLATE_BASE_URL=http://tgc_mailman_web:8000 [/code] where tgc_mailman_web is my container name. This URL ist stored in the DB-table "template" for the name=list:member:regular:footer. A call to my fqdn or to localhost [code] wget http://localhost:8000/postorius/api/templates/list/homepage.gruppe.tgcamberg... [/code] will return the footer itself - this works fine. Therefore, should i set POSTORIUS_TEMPLATE_BASE_URL to http://localhost:8000? If that works, yes.

Hi Mark,

thanks for your reply and excuse my delay. I was very busy in the last weeks but made some tests. Newly created templates with POSTORIUS_TEMPLATE_BASE_URL=http://localhost:8000 did not work. I changed it to my fqdn - at the moment I am able to access the template via this URl (e.G. http://lists.example.de:8000/postorius/api/templates/list/homepage.lists.exa...). But if I try to send an email I got the following error:

Jul 09 16:00:37 2021 (27) Uncaught runner exception: HTTPConnectionPool(host='lists.example.de', port=8000): Max retries exceeded with url: /postorius/api/templates/list/homepage.lists.example.de/list:admin:action:post (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused')) Jul 09 16:00:37 2021 (27) Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/urllib3/connection.py", line 159, in _new_conn conn = connection.create_connection( File "/usr/lib/python3.8/site-packages/urllib3/util/connection.py", line 84, in create_connection raise err File "/usr/lib/python3.8/site-packages/urllib3/util/connection.py", line 74, in create_connection sock.connect(sa) ConnectionRefusedError: [Errno 111] Connection refused

During handling of the above exception, another exception occurred:

Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", line 670, in urlopen httplib_response = self._make_request( File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", line 392, in _make_request conn.request(method, url, **httplib_request_kw) File "/usr/lib/python3.8/http/client.py", line 1255, in request self._send_request(method, url, body, headers, encode_chunked) File "/usr/lib/python3.8/http/client.py", line 1301, in _send_request self.endheaders(body, encode_chunked=encode_chunked) File "/usr/lib/python3.8/http/client.py", line 1250, in endheaders self._send_output(message_body, encode_chunked=encode_chunked) File "/usr/lib/python3.8/http/client.py", line 1010, in _send_output self.send(msg) File "/usr/lib/python3.8/http/client.py", line 950, in send self.connect() File "/usr/lib/python3.8/site-packages/urllib3/connection.py", line 187, in connect conn = self._new_conn() File "/usr/lib/python3.8/site-packages/urllib3/connection.py", line 171, in _new_conn raise NewConnectionError( urllib3.exceptions.NewConnectionError: : Failed to establish a new connection: [Errno 111] Connection refused

During handling of the above exception, another exception occurred:

Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/requests/adapters.py", line 439, in send resp = conn.urlopen( File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", line 724, in urlopen retries = retries.increment( File "/usr/lib/python3.8/site-packages/urllib3/util/retry.py", line 439, in increment raise MaxRetryError(_pool, url, error or ResponseError(cause)) urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='lists.example.de', port=8000): Max retries exceeded with url: /postorius/api/templates/list/lists.example.de/list:admin:action:post (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3.8/site-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3.8/site-packages/mailman/runners/incoming.py", line 79, in _dispose process(mlist, msg, msgdata, start_chain) File "/usr/lib/python3.8/site-packages/mailman/core/chains.py", line 79, in process link.function(mlist, msg, msgdata) File "/usr/lib/python3.8/site-packages/mailman/chains/hold.py", line 232, in _process template = getUtility(ITemplateLoader).get( File "/usr/lib/python3.8/site-packages/mailman/model/template.py", line 188, in get contents = getUtility(ITemplateManager).get( File "/usr/lib/python3.8/site-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3.8/site-packages/mailman/model/template.py", line 110, in get contents = protocols.get(actual_uri, **auth) File "/usr/lib/python3.8/site-packages/mailman/utilities/protocols.py", line 38, in get response = requests.get(url, timeout=REQUEST_TIMEOUT, **kws) File "/usr/lib/python3.8/site-packages/requests/api.py", line 76, in get return request('get', url, params=params, **kwargs) File "/usr/lib/python3.8/site-packages/requests/api.py", line 61, in request return session.request(method=method, url=url, **kwargs) File "/usr/lib/python3.8/site-packages/requests/sessions.py", line 530, in request resp = self.send(prep, **send_kwargs) File "/usr/lib/python3.8/site-packages/requests/sessions.py", line 643, in send r = adapter.send(request, **kwargs) File "/usr/lib/python3.8/site-packages/requests/adapters.py", line 516, in send raise ConnectionError(e, request=request) requests.exceptions.ConnectionError: HTTPConnectionPool(host='lists.example.de', port=8000): Max retries exceeded with url: /postorius/api/templates/list/lists.example.de/list:admin:action:post (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused'))

I set POSTORIUS_TEMPLATE_BASE_URL=lists.example.de:8000 and I have no idea, why the connection is refused. Do you see any configuration error d or have another idea?

Best regards, chrclaus

christopher.claus@tgcamberg1848.de writes:

Hi together,

does anybody has an idea for the problem "ConnectionRefusedError: [Errno 111] Connection refused"?

Does this have anything to do with the subject?

As for ideas, no, no ideas without more information. Like what is trying to connect to what and why, is this a new install or a sudden change in a working install, if the latter, were there other changes to the system (OS or package upgrade), etc.

Hi Abhilash,

excuse my delay, i was out-of-order in the last weeks.

You want the URL at which Postorius (postorius) is available from Core (mailman-core container). The default for that in the container images is set to http://mailman-web:8000. Does that not work for you? I changed the container-names (but not the hostnames) an probably i set the POSTORIUS_TEMPLATE_BASE_URL to the container-name and not to the hostname.

If you want to verify, you want to exec into the Core’s container (docker exec -it mailman-core bash) and see if you can curl the URL from inside there. If you are using the default docker-compose-postorius.yaml then there is a /etc/hosts entry created by docker for the mailman-web container, hence http://mailman-web:8000 works there (but it won’t work on the host, since docker doesn’t modify the host’s /etc/hosts). I modified the compose-file since i have a separate container for a database and i use a seperate network for all my other container. The consequence was, that i do not have a fix subnet. I tried to change all occurences of ip-adresses to hostnames. Therefore i stripped these parts in the compose-file. Currently, there is not entry for mailman-web in the hosts file of mailman-core. I did not find any place in your config and scripts, were this file is written. At which place, this should be done? An interesting point: mailman_core has an entry to itself (with own ip) in /etc/hosts and mailman_web also. I think, this is not correct, isnt it? But nevertheless a curl of the URL from core to web works without error message.

There might also be a bug in play here which would cause such connection refused errors when subscribing/unsubscribing when there was a template configured for the list. Is that the case for you or are you seeing always when trying to send the email (which would imply that the Web container simply isn’t reachable from Core). I thought about the situation, that all my lists where migrated from mailman 2. Many of the have footer- and header-messages, automatic replies which are not shown in the template section of the list. Is a recreation in mailman3 a good option in this situation?

Best regards, chrclaus

Hi Abhilash, Hi Mark,

I upgraded my docker-image to maxking/docker-mailman 0.4.1 and reset my whole configuration. After applying my individual config-items step-by-step I got no errors anymore. Probably I have had a misconfiguration by trying to switch from IP-addresses to hostnames in docker-image v0.3. Thank you for the update of the docker-image to v0.4 - good job!

Best regards, chrclaus

Peter Münster writes:

On Mon, May 24 2021, Mark Sapiro wrote:

...

var/templates/site/de/list:member:generic:footer.txt

Note "de" in the above.

I have created an empty file /var/lib/mailman/templates/site/en/list:member:generic:footer.txt

Do you really mean "en"? If the user's primary language setting is de, I presume

/var/lib/mailman/templates/site/de/list:member:generic:footer.txt

will override

/var/lib/mailman/templates/site/en/list:member:generic:footer.txt

Steve

Peter Münster writes:

On Wed, Aug 31 2022, Stephen J. Turnbull wrote:

...

Do you really mean "en"?

Yes. Since this is the only file under the templates-directory, it should be used according to https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n....

Or do I misunderstand something?

No, I was just making sure because Mark's message that you quoted mentioned "de", and you have an umlaut in your name. Come to think of it, I'm not even sure Mark was replying to you, but for what it's worth that was my thought process. :-)

I'm not very familiar with Django's handling of such files, but my understanding is that many files are collected from various places using manage.py's collectstatic command. I don't remember whether these templates are among them.

That's the only thing I can think of offhand. If that's not it, I'll try to get back to this on Saturday.

Steve

Peter Münster writes:

On Thu, Sep 01 2022, Stephen J. Turnbull wrote:

...

I'm not very familiar with Django's handling of such files,

I don't think, that Django is involved here.

Ah, you're right. My GSoC student is working on Postorius so I have Django on the brain.

My language setting is "fr", so I've copied templates/site/en templates/site/fr and now it works.

So no real problem, but the question remains: why did it not work with "en"?

The template to be used is determined by the language setting of the user, or the default if the user is anonymous. You have to repeat the process with all of the templates that might be used on your system due to users' language settings. Presumably it *would* have worked for any user whose language setting was "en". But if you do have "de" users, you'll need to replace the "de" template as well.

If you mean that you switched your language setting to "en" or have an "en" user, and tested it, we can take a look at it, but as I understand the situation, you have a "fr" setting so you saw the "fr" template.

Steve

Peter Münster writes:

If the "final fallback" as mentioned in https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n.... worked, that would be a good feature. Only one template in templates/site/en and everything works as expected, independently of any language settings.

But that's not the way it works. If I understand correctly, you're referring to the overriding site-specific templates, but in fact there is always the fallback of the builtin template. I don't see how this can work any other way. The Mailman project is fortunate to have a team of translators handling all the default templates. They need to stay for many, if not the great majority, of sites. For example, on my site, I have to support English, Japanese, and Chinese. I can do the first two myself, but except for trivial cases like "suppress footer with empty template file", I definitely want to fall back to the default Chinese even if I've added site-specific or clarifying wording to the English and Japanese. If you think this kind of use case is really important (and I can imagine many other similar use cases, I just think they're too rare to justify even more complexity in the I18N algorithm), you could file an issue, requesting an "LC_ALL-like" override pseudo-language, such that if that template is set, all languages use it.

Note, I've already figured out how to do this. I think it would do less good (save you a few "cp <template file> ../fr" copies) than harm (confuse people reading the docs who don't have a use case). All you need to do is convince at least one of the active core (me, Mark, Abhilash) that it's a good idea and I'll implement.

For reference, from src/mailman/utilities/i18n.py:

The <language> path component is variable, and described below.

* The list-specific language directory
  $template_dir/lists/<mlist.list_id>/<language>
  $template_dir/lists/<mlist.fqdn_listname>/<language> (deprecated)

* The domain-specific language directory
  $template_dir/domains/<mlist.mail_host>/<language>

* The site-wide language directory
  $template_dir/site/<language>

-------------------------------- HERE --------------------------------
* The template directory within the mailman source tree
  <source_dir>/templates/<language>
----------------------------------------------------------------------

The <language> path component is calculated as follows, in this order:

* The `language` parameter if given
* `mlist.preferred_language` if given
* The server's default language
* English ('en')

On 9/1/22 03:19, Peter Münster wrote:

My language setting is "fr", so I've copied templates/site/en templates/site/fr and now it works.

So no real problem, but the question remains: why did it not work with "en"?

Because of https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n.... which you referenced previously

     After all those paths are searched, the final fallback is the English
     template within the Mailman source tree.

I.e. the final fallback is to the English template in the source tree, not to a list, domain or site specific English template in Mailman's config.TEMPLATE_DIR.

-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan