Search results for "2021" - Mailman-users

Re: Message-Footer after migrating to Mailman3

by christopher.claus＠tgcamberg1848.de

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.ex…) 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('<urllib3.connection.HTTPConnection object at 0x7fe80eaaec40>: 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: <urllib3.connection.HTTPConnection object at 0x7fe80eaaec40>: 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('<urllib3.connection.HTTPConnection object at 0x7fe80eaaec40>: 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('<urllib3.connection.HTTPConnection object at 0x7fe80eaaec40>: 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

3 years, 11 months

Re: problems installing mailman3 under gentoo and upgrading mailman2 to mailman3

by John Covici

On Sat, 13 Mar 2021 05:42:53 -0500, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > On 13/3/21 9:44, John Covici wrote: > > On Sat, 13 Mar 2021 03:25:41 -0500, > > Guillermo Hernandez (Oldno7) via Mailman-users wrote: > >> On 13/3/21 8:53, John Covici wrote: > >>>> We recommend installing Mailman and the web components in a virtualenv, > >>>> but it is not a requirement. We also suggest that postgresql is a better > >>>> choice than MariaDB. > >>>> > >>> I sort of am installing from source, gentoo installs from source. No > >>> one on the gentoo users mailing list seems to be able to help me, > >>> except to tell me to use a different mailing list mechanism called > >>> mlmmj. > >>> > >> From the perspective of someone who was in the same place (but > >> installing in a FreeBSD S.O.), I would recommend you to follow > >> the "virtualenv" guide but without executing the "env" > >> commands. It will produce a system wide mailman3 installation but > >> it will work (as it is for me since a few moths ago) > >> > >> I writed down a step by step path of my installation and it could > >> be of your interest (maybe you have to locate and install some > >> packages by different name, but I think it will be not much > >> difference). It could provide you a overall view of all the > >> processes implied. > >> > >> I'ts here: https://forums.FreeBSD.org/threads/mailman-3.61050/post-488128 > > Thanks, by the env commands you mean the creation and activation > > commands? > > I mean the part when you activate the virtualenv (Virtualenv > setup & activate virtualenv) in > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > > The servers in which I was migrating from mailman2 were jailed > servers and I didn't want to add more virtualization layers (and > I read some articles documenting problems using virtualenv in > FreeBSD) so, I prefered to install all of it system wide as it > was before with mailman2. > > > > > I will certainly look at your thread. > > Now one thing came up while trying to create the database, I got a traceback complaining about a revision error because gentoo had a slightly different version (3.3.2) instead of 3.3.3 using pip. When I upgrade mailman, am I going to have to do something to the database as well and why should the database have some kind of reference to the mailman version? -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

4 years, 3 months

Re: problem with postorius initial setup

by John Covici

On Tue, 16 Mar 2021 12:14:36 -0400, Stephen J. Turnbull wrote: > > John Covici writes: > > > Hi. I am trying to setup postorius, but I have run into a problem. I > > am using the example project, except I am using postgresql instead of > > sqlite3. I ran python manage.py migrate which was successful. > > > > On running the development server I get: > > Exception in thread django-main-thread: > > Traceback (most recent call last): > > File > > "/usr/lib/python3.8/site-packages/django/utils/module_loading.py", > > line 20, in import_string > > return getattr(module, class_name) > > AttributeError: module 'postorius.middleware' has no attribute > > 'APICountingMiddleware' > > This appears to be another version mismatch. The > APICountingMiddleware appears to be a debugging or development > instrumentation tool. It was added on 2021-02-28, so it's very > recent. Somehow your Postorius settings.py is newer than your > Postorius middleware.py. I would guess you have checked out or pip'ed > a very recent version of Postorius but the example_project is picking > up an older version, possibly from the Gentoo package. Why that could > happen depends on whether you've set up a venv for the up-to-date > Postorius, whether it's active, and so on. I think I know what is happening, but not how to fix. The example_project which the docs told me to get is from the postorius git which is, of course, recent, whereas the postorius I have from the gentoo package is 1.3.3, which is not that old, but maybe not up to the git version. Should I be using the git version? -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

4 years, 3 months

Re: Internal Server Error: /mailman/accounts/fedora/login/

by matthew＠alberti.us

Kilian, It looks like someone (or a bot) is trying to login using Fedora as the authentication plugin; but that plugin is not configured. You probably want to disable/comment out the Fedora plugin INSTALLED_APPS section in the settings_local.py file. - Matt Alberti -----Original Message----- From: Kilian Kilger <kkilger(a)gmail.com> Sent: Friday, September 17, 2021 12:24 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Internal Server Error: /mailman/accounts/fedora/login/ Hi mailing list, I own a mailman box. I regularily (many times a day) get mail with an internal server error. I am using Debian and the included mailman3-full package. I guess someone tries to hack my instance. But I don't understand why this leads to the internal server error. I am also wondering why the request URL is /mailman/accounts/fedora/login, as I am using Debian (understandable if the request happens via an outside trigger). I have no clue about the internal workings of mailman though. I use Debian 11 bullseye and thus version 3.3.3. I can trigger the internal server error by myself by visiting the request URL. Despite these emails the instance seems to work fine. Best regards, Kilian. Internal Server Error: /mailman/accounts/fedora/login/ TypeError at /accounts/fedora/login/ _openid_consumer() missing 2 required positional arguments: 'provider' and 'endpoint' Request Method: GET Request URL: <URL>/mailman/accounts/fedora/login/?process=login&next=/mailman/accounts/pa ssword/reset/ Django Version: 2.2.24 Python Executable: /usr/bin/uwsgi-core Python Version: 3.9.2 Python Path: ['.', '', '/usr/lib/python39.zip', '/usr/lib/python3.9', '/usr/lib/python3.9/lib-dynload', '/usr/local/lib/python3.9/dist-packages', '/usr/lib/python3/dist-packages', '/usr/lib/python3.9/dist-packages'] Server time: Fr, 17 Sep 2021 06:12:57 +0000 Installed Applications: ('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 34. response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 115. response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 113. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py" in view 71. return self.dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py" in dispatch 97. return handler(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django_mailman3/lib/auth/fedora/views.py" in get 56. return self.post(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django_mailman3/lib/auth/fedora/views.py" in post 67. client = _openid_consumer(request) Exception Type: TypeError at /accounts/fedora/login/ Exception Value: _openid_consumer() missing 2 required positional arguments: 'provider' and 'endpoint' Request information: USER: AnonymousUser _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 9 months

Re: at the finish line of mailman3 docker, but can't sign in.

by John Covici

It was in https://asynchronous.in/docker-mailman On Sun, 01 Aug 2021 16:55:11 -0400, Abhilash Raj wrote: > > > > On Sun, Aug 1, 2021, at 1:52 PM, John Covici wrote: > > I am finding some missing documentation in the section on configuring > > mailman-web, it refers to a file > > https://asynchronous.in/docker-mailman/web/ which does not exist. > > Try https://asynchronous.in/docker-mailman/web.html > > Can you point me where you saw the original URL so I can update it? > > > > > > > > On Sat, 31 Jul 2021 21:21:24 -0400, > > John Covici wrote: > > > > > > OK, thanks a lot -- if anyone here can help with proper config for > > > those, that would be great. I do have a web server, but its apache > > > rather than mginx and I am not sure how to properly translate. Also, > > > doing a separate container for an mta which would just talk to > > > mailman would get around the sendmail situation I have, although > > > there may be a decent way to do that as well. I guess the hard part > > > is to tie the multiple containers together. > > > > > > > > > On Sat, 31 Jul 2021 17:56:15 -0400, > > > Abhilash Raj wrote: > > > > > > > > > > > > > > > > On Sat, Jul 31, 2021, at 3:56 AM, John Covici wrote: > > > > > I have a couple of questions about the container, if its OK. > > > > > > > > Sure it is :) > > > > > > > > > > > > > > First, it says to run you create the directory > > > > > /opt/mailman/mailman-core and /opt/mailman/mailman-web and then do the > > > > > git clone. What directory should the git clone be in? > > > > > > > > You can do clone anywhere you can run commands from. There aren't any files in the repository that you'd be directly using. You'll just be relying on the docker-compose.yaml file from the repo (or one of the other compose files if you choose to use a different database) unless you are going to build the container images on your own instead of using the published ones. > > > > > > > > I just do it in my home directory of the user I am running commands as. /opt/mailman could be a good option too. > > > > > > > > > A couple of more questions -- is there a way to install the web server > > > > > and the mta in the container, this way I could make the whole thing > > > > > be independent of my host configs? > > > > > > > > You probably don’t want to install mta and webserver in the Mailman containers, you want to add separate containers for them and make Mailman containers talk to them. This will let you keep the container for each component separate and it is just easier to manager. > > > > > > > > You would need to add appropriate containers for webserver and mta in the docker-compose.yaml file and figure out the configuration on how to tie them to Mailman. The Mailman container images repo doesn’t provide such a configuration, but there are folks in the channel who have done it and you should be able to find them in this list’s archives. > > > > > > > > > > > > > > On Fri, 30 Jul 2021 16:04:48 -0400, > > > > > bob B wrote: > > > > > > > > > > > > is this the info you need for the container version > > > > > > > > > > > > [root@..... docker-mailman]# docker ps > > > > > > CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES > > > > > > 30af82ac9315 maxking/mailman-web:0.3 "docker-entrypoint.s…" 2 hours ago Up 2 hours 127.0.0.1:8000->8000/tcp, 127.0.0.1:8080->8080/tcp mailman-web > > > > > > cd01a99cf908 maxking/mailman-core:0.3 "docker-entrypoint.s…" 2 hours ago Up 2 hours 127.0.0.1:8001->8001/tcp, 127.0.0.1:8024->8024/tcp mailman-core > > > > > > 77fe89ced9e8 postgres:9.6-alpine "docker-entrypoint.s…" 2 hours ago Up 2 hours 5432/tcp dockermailman_database_1 > > > > > > > > > > > > > > > > > > for smtp host > > > > > > ------------ > > > > > > cat /opt/mailman/web/settings_local.py > > > > > > #allowed_hosts = ['127.0.0.1', 'localhost','HOST.DOMAIN.org'] > > > > > > #ALLOWED_HOSTS = ['127.0.0.1', 'localhost','HOST.DOMAIN.org'] > > > > > > ALLOWED_HOSTS = ['*'] > > > > > > DEBUG = True > > > > > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > > > > > > EMAIL_HOST = 'smtp.example.com' > > > > > > EMAIL_PORT = 25 > > > > > > --------------------------- > > > > > > cat /opt/mailman/core/mailman-extra.cfg > > > > > > # mailman-extra.cfg > > > > > > > > > > > > [mta] > > > > > > incoming: mailman.mta.postfix.LMTP > > > > > > outgoing: mailman.mta.deliver.deliver > > > > > > # mailman-core hostname or IP from the Postfix server > > > > > > lmtp_host: localhost > > > > > > lmtp_port: 8024 > > > > > > # Postfix server's hostname or IP from mailman-core > > > > > > smtp_host: smtp.example.com > > > > > > smtp_port: 25 > > > > > > configuration: /etc/postfix-mailman.cfg > > > > > > [mailman] > > > > > > # This address is the "site owner" address. Certain messages which must be > > > > > > # delivered to a human, but which can't be delivered to a list owner (e.g. a > > > > > > # bounce from a list owner), will be sent to this address. It should point to > > > > > > # a human. > > > > > > site_owner: my_real_email_is_in_the_file.com > > > > > > __________________________________ > > > > > > > > > > > > My docker most machine /etc/postfix/main.cf has > > > > > > > > > > > > transport_maps = > > > > > > regexp:/opt/mailman/core/var/data/postfix_lmtp > > > > > > local_recipient_maps = > > > > > > regexp:/opt/mailman/core/var/data/postfix_lmtp > > > > > > relay_domains = > > > > > > regexp:/opt/mailman/core/var/data/postfix_domains > > > > > > > > > > > > > > > > > > # Support the default VERP delimiter. > > > > > > recipient_delimiter = + > > > > > > unknown_local_recipient_reject_code = 550 > > > > > > owner_request_special = no > > > > > > > > > > > > ------------------------------ > > > > > > > > > > > > > > > > > > > > > > > > is that correct? I leave them set to smtp.example.com because the will send out via the docker host machine, and so i ONLY have my actual outbound server listed in /etc/postfix/main.cf on the docker host machine, or do i need to replace smtp.example.com with our outbound server? > > > > > > > > > > > > > > > > > > Also, If I want to blow away everything away (databse etcc) and rebuild it... what are those steps? > > > > > > _______________________________________________ > > > > > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > > > > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > > > > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > > > > > > > > > > > > > -- > > > > > Your life is like a penny. You're going to lose it. The question is: > > > > > How do > > > > > you spend it? > > > > > > > > > > John Covici wb2una > > > > > covici(a)ccs.covici.com > > > > > _______________________________________________ > > > > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > > > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > > > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > > > > > > > > > > > > > > -- > > > > thanks, > > > > Abhilash Raj (maxking) > > > > > > > > > > -- > > > Your life is like a penny. You're going to lose it. The question is: > > > How do > > > you spend it? > > > > > > John Covici wb2una > > > covici(a)ccs.covici.com > > > _______________________________________________ > > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > -- > > Your life is like a penny. You're going to lose it. The question is: > > How do > > you spend it? > > > > John Covici wb2una > > covici(a)ccs.covici.com > > > > > -- > thanks, > Abhilash Raj (maxking) > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

3 years, 11 months

Re: Struggle on upgrading mailman3-web to new version - Not Found: /mailman//

by Stefan Bauer

Hi Eggert, thank you for your input. Unfortunately that did not work. After changing the line ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ to ProxyPass /mailman unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ and restarted apache2, still a similar behavior when accessing https://my.mailinglistserver.local/mailman/postorius/lists/ Page not found (404) Request Method: GET Request URL: https://mmy.mailinglistserver.local/mailma//postorius/lists/ What i find strange is that the URL is mangled. The 'n' from mailman is missing and now there is a second slash. This all must happen inside the uwsgi-container as my request is modified. Not Found: /mailma// [pid: 1346851|app: 0|req: 28/28] 10.254.253.13 () {52 vars in 827 bytes} [Mon Oct 25 17:47:21 2021] HEAD /mailman/ => generated 2773 bytes in 4 msecs (HTTP/1.1 404) 5 headers in 155 bytes (1 switches on core 1) Am Mo., 25. Okt. 2021 um 17:19 Uhr schrieb Eggert Ehmke via Mailman-users < mailman-users(a)mailman3.org>: > Hello Stefan, > > I had the same problem. While I did not find the reason for this strange > behavior, I found a workaround. I changed the lines in the apache vhost > file > like this: > > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > ProxyPass /mailman unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > </IfModule> > > Note I only changed the single ProxyPass line from mailman3 to mailman. > The > url to access the web gui also changes like this: > > https://my.mailinglistserver.local/mailman/postorius/lists/ > > This works for me, tell us your success. Would be nice when the problem > could > be solved finally, this happened to a few people. > > Cheers, Eggert > > Am Montag, 25. Oktober 2021, 10:45:50 CEST schrieb Stefan Bauer: > > Dear Users, > > > > I recently upraded mailman3 from Ubuntu 18 to 20. After accessing the > > web-interface via > > > > https://my.mailinglistserver.local/mailman3/postorius/lists/ > > > > I receive > > > > Not Found: /mailman//postorius/lists/ > > [pid: 1346851|app: 0|req: 4/4] 10.254.253.12 () {70 vars in 1369 bytes} > > [Mon Oct 25 10:39:59 2021] GET /mailman3/postorius/lists/ => generated > 2821 > > bytes in 12 msecs (HTTP/1.1 404) 5 headers in 155 bytes (1 switches on > core > > 1) > > > > Where does the wrong path come from (mailman vs. mailman3) > > > > After enabling Debug, i see in the browser the following: > > > > > > Page not found (404) > > Request Method: GET > > Request URL: > https://my.mailinglistserver.local/mailman//postorius/lists/ > > > > Using the URLconf defined in urls, Django tried these URL patterns, in > this > > order: > > > > ^$ > > ^postorius/ > > ^hyperkitty/ > > ^user-profile/delete$ [name='mm_user_account_delete'] > > ^user-profile/$ [name='mm_user_profile'] > > ^accounts/ > > ^admin/ > > > > The current path, /postorius/lists/, didn't match any of these. > > > > You're seeing this error because you have DEBUG = True in your Django > > settings file. Change that to False, and Django will display a standard > 404 > > page. > > > > My apache configuration is very simply: > > > > # more /etc/apache2/conf-enabled/mailman3.conf > > Alias /mailman3/favicon.ico > > /var/lib/mailman3/web/static/postorius/img/favicon.ico > > Alias /mailman3/static /var/lib/mailman3/web/static > > > > <Directory "/var/lib/mailman3/web/static"> > > Require all granted > > </Directory> > > > > <IfModule mod_proxy_uwsgi.c> > > ProxyPass /mailman3/favicon.ico ! > > ProxyPass /mailman3/static ! > > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > > </IfModule> > > > > I dont see where the path gets traversed in the wrong way. Any help is > > greatly appreciated. > > > > thank you. > > > > Stefan > > _______________________________________________ > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 8 months

ham-confirm+3ee85b006eeb5897ca6f53b093cb063672f6a784@example.com

by Jörg Klein

I want add some subscribers. When the I get this error message: I have no address ham-request(a)example.com. Do I need for every mailing list more as the mailing list email address? Final-Recipient: rfc822; ham-request(a)example.com Action: failed Status: 5.0.0 Remote-MTA: dns; mx0.example.com. (80.237.138.5, the server for the domain example.com.) Diagnostic-Code: smtp; 550 Address invalid (ID:550:1:1 (mi015.mc1.hosteurope.de)) Last-Attempt-Date: Wed, 17 Feb 2021 01:13:18 -0800 (PST)

4 years, 4 months

Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by peter＠chubb.wattle.id.au

>>>>> "David" == David Partain via Mailman-users <mailman-users(a)mailman3.org> writes: David> On Tue, 2021-03-02 at 20:07 +0000, David Partain via David> Mailman-users wrote: >> On Tue, 2021-03-02 at 19:56 +0000, David Partain via Mailman-users >> wrote: >> >> I assume this is because /usr/share/mailman3-web/manage.py, which >> has: >> >> '#!/usr/bin/env python' >> >> resolves to Python 2.7.17. You may want to install python-is-python3 to make /usr/bin/python python3 PeterC

4 years, 4 months

Re: statistics monitoring for Mailman3

by Seth Seeger

On Mon, Mar 15, 2021, at 11:32 AM, Seth Seeger wrote: > > > On Mar 12, 2021, at 12:10 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > > > > You inspired me. See <https://www.msapiro.net/scripts/smtp_report>. > > I get the following error: > > File "./smtp_report", line 44 > print(f' {lname}: {tot}') > ^ > SyntaxError: invalid syntax > > I'm running python3 (3.5.3), and I'm afraid I don't know enough python > to know what's wrong. My wife fixed it! f-strings don't show up until Python 3.6. She rewrote the two print statements as: print(' ' + lname + ': ' + str(tot)) Seth

4 years, 3 months

Re: changing the main template for subscriptions and more

by Mark Sapiro

On June 21, 2021 10:03:50 AM CDT, "Jens Günther" <jens.guenther(a)posteo.de> wrote: > >How can I change the template for all the lists (respectively >maildomains/webdomains) so that I don't have to do this manually for >all >lists? To set a template as default for all lists and domains, put it in Mailman's var/templates/site/LC directory. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

4 years

Mailman-users search results for query "2021"