Search results for "2021" - Mailman-users

Not sure which part of Mailman 3 is generating this exception

by Philip Colmer

I've found the following exception in "mailman.log": [28/Sep/2021:11:17:18 +0000] "GET /3.1/lists/test(a)mm3.lavasoftware.org HTTP/1.1" 200 374 "-" "GNU Mailman REST client v3.3.3" 2021-09-28 11:17:18 [FALCON] [ERROR] GET /3.1/lists/test(a)mm3.lavasoftware.org/config => Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1276, in _execute_context self.dialect.do_execute( File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 608, in do_execute cursor.execute(statement, parameters) psycopg2.OperationalError: SSL error: sslv3 alert bad record mac The above exception was the direct cause of the following exception: Traceback (most recent call last): File "falcon/app.py", line 361, in falcon.app.App.__call__ File "/opt/mailman/venv/lib/python3.8/site-packages/mailman/rest/listconf.py", line 282, in on_get value = getter.get(self._mlist, attribute) File "/opt/mailman/venv/lib/python3.8/site-packages/mailman/rest/helpers.py", line 228, in get value = list(value) File "/opt/mailman/venv/lib/python3.8/site-packages/mailman/model/mailinglist.py", line 348, in filter_types for content_filter in results: File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/orm/query.py", line 3535, in __iter__ return self._execute_and_instances(context) File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/orm/query.py", line 3560, in _execute_and_instances result = conn.execute(querycontext.statement, self._params) File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1011, in execute return meth(self, multiparams, params) File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/sql/elements.py", line 298, in _execute_on_connection return connection._execute_clauseelement(self, multiparams, params) File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1124, in _execute_clauseelement ret = self._execute_context( File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1316, in _execute_context self._handle_dbapi_exception( File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1510, in _handle_dbapi_exception util.raise_( File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/util/compat.py", line 182, in raise_ raise exception File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1276, in _execute_context self.dialect.do_execute( File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 608, in do_execute cursor.execute(statement, parameters) sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) SSL error: sslv3 alert bad record mac [SQL: SELECT contentfilter.id AS contentfilter_id, contentfilter.mailing_list_id AS contentfilter_mailing_list_id, contentfilter.filter_type AS contentfilter_filter_type, contentfilter.filter_pattern AS contentfilter_filter_pattern FROM contentfilter WHERE %(param_1)s = contentfilter.mailing_list_id AND contentfilter.filter_type = %(filter_type_1)s] [parameters: {'param_1': 1, 'filter_type_1': 0}] (Background on this error at: http://sqlalche.me/e/13/e3q8) [2021-09-28 11:17:18 +0000] [2076] [ERROR] Error handling request /3.1/lists/test(a)mm3.lavasoftware.org/config Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.8/site-packages/gunicorn/workers/sync.py", line 136, in handle self.handle_request(listener, req, client, addr) File "/opt/mailman/venv/lib/python3.8/site-packages/gunicorn/workers/sync.py", line 179, in handle_request respiter = self.wsgi(environ, resp.start_response) File "/opt/mailman/venv/lib/python3.8/site-packages/mailman/database/transaction.py", line 51, in wrapper config.db.commit() File "/opt/mailman/venv/lib/python3.8/site-packages/mailman/database/base.py", line 52, in commit self.store.commit() File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/orm/session.py", line 1046, in commit self.transaction.commit() File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/orm/session.py", line 508, in commit t[1].commit() File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1762, in commit self._do_commit() File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1793, in _do_commit self.connection._commit_impl() File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 773, in _commit_impl self._handle_dbapi_exception(e, None, None, None, None) File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1514, in _handle_dbapi_exception util.raise_(exc_info[1], with_traceback=exc_info[2]) File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/util/compat.py", line 182, in raise_ raise exception File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 771, in _commit_impl self.engine.dialect.do_commit(self.connection) File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 392, in connection self._handle_dbapi_exception(e, None, None, None, None) File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1514, in _handle_dbapi_exception util.raise_(exc_info[1], with_traceback=exc_info[2]) File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/util/compat.py", line 182, in raise_ raise exception File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 390, in connection return self._revalidate_connection() File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 469, in _revalidate_connection raise exc.InvalidRequestError( sqlalchemy.exc.InvalidRequestError: Can't reconnect until invalid transaction is rolled back I'm happy to report it as an issue against the appropriate part on GitLab but it isn't entirely clear to me which part of the suite is causing this. I think it is Core but I'm not absolutely sure. Philip

3 years, 9 months

Re: List creation error

by Brian Carpenter

Odhiambo Washington wrote: > On Wed, 6 Jan 2021 at 15:36, Andreas Barth aba(a)ayous.org wrote: > > > > Odhiambo Washington (odhiambo(a)gmail.com) [210106 12:12]:PS: I could probably have caused the error with some weird operation I > > did: > > Initially when postorius comes up, it has the domain - example.com > > http://example.com. I am not sure > > where it gets this. > > > > > > example.com is the default domain from django. Renaming that via the > > django (e.g. mailman3/admin/sites/site/1/change/ ) worked for me quite > > well (without touching anything in the database by hand). > > Hi Andi, > I could be missing something still... > > At what juncture during the installation do you do this renaming? > Where is this directory? On my setup, I have no such directory - but I > could be missing something in the install process, maybe.. > > root@debian10:/opt/mailman# pwd > /opt/mailmanroot@debian10:/opt/mailman# find . -type d -name sites > ./mm/venv/lib/python3.7/site-packages/jedi/third_party/django-stubs/django-stubs/contrib/sites > ./mm/venv/lib/python3.7/site-packages/django/contrib/sites > Do you find anything amiss with this HOWTO - > https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 ?? I > find > the guide rather straight and clear. That is my work in progress and thank you for the compliment. > It's the one I am following - almost to the letter - except for the fact > that I am using Apache+mod_wsgi+MySQL+Exim instead. > I have configs in place by the time I run 'mailman info' portion. But then > again, when I run this command, I don't like what it prints because I see > some reference to sqlite. Can you paste what the mailman info output is and the contents of your mailman.cfg file? > As it is, I believe my problem lies elsewhere, not possible to solve with > your rename option. To get rid of example.com, I log into Django, create a new site using the main list domain and note the site id. I then edit the settings_local.py file and change the SITE_ID setting to the new site id of the main list domain. You will need to restart mailman and qcluster I believe after making that change.

4 years, 6 months

Mailman3 stopped working after Upgrade to Ubuntu 21.04

by Thomas Möhle

Hey, I have set up mailman3 with mailman3-web on my mailserver and after upgrading to Ubuntu 21.04 my setup stopped working. I can see repeating log entries of mailman trying to reach something within hyperkitty and getting an error. The same constant repeating cycle of log entries is visible in my log files. I have attached my config files as well as the logfiles for mailman3 and mailman-web. As you can see, I'm not really getting many errors, yet within 5 seconds there are almost 2000 lines of log entries where mailman tries to reach something within hyperkitty over and over and over again. One thing I did to create an error message is start up both services, then edit a test list, that I created, in the web interface. This is the error you can find in the logs then: ERROR 2021-08-07 12:50:26,932 2343625 postorius Un-handled exception: HTTP Error 404: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/postorius/views/generic.py", line 74, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 97, in dispatch return handler(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/postorius/views/list.py", line 301, in get primary_email = set_preferred(request.user, mm_user) File "/usr/lib/python3/dist-packages/postorius/utils.py", line 77, in set_preferred mm_user.preferred_address = primary_email.email File "/usr/lib/python3/dist-packages/mailmanclient/restobjects/user.py", line 57, in __setattr__ super(User, self).__setattr__(name, value) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py", line 131, in __setattr__ return super(RESTObject, self).__setattr__(name, value) File "/usr/lib/python3/dist-packages/mailmanclient/restobjects/user.py", line 145, in preferred_address response, content = self._connection.call(url, {'email': email}) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 127, in call raise HTTPError(url, response.status_code, urllib.error.HTTPError: HTTP Error 404: WARNING 2021-08-07 12:50:26,938 2343625 django.request Not Found: /mailman3/postorius/lists/test.lists.example.com/ Can anyone here help me debug this? I'm working on this problem for days now and can't seem to find a solution. Thanks so much in advance, Thomas

3 years, 11 months

Re: Problem updating mailman

by Odhiambo Washington

On Sun, 24 Jan 2021 at 00:46, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/23/21 2:56 AM, Odhiambo Washington wrote: > > I am getting this error after I did a git pull and build. > > > > (venv) [mailman3@gw ~/git]$ /opt/mailman/mm/bin/mailman-post-update > > + '[' False == False ']' > > + mkdir -p /opt/mailman/mm/static > > + /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput > > --verbosity 0 > > +* /opt/mailman/mm/bin/django-admin compress* > > CommandError: An error occurred during rendering > > > /opt/mailman/mm/venv/lib/python3.7/site-packages/HyperKitty-1.3.4rc2-py3.7.egg/hyperkitty/templates/hyperkitty/404.html: > > /usr/local/lib/ruby/site_ruby/2.7/rubygems/dependency.rb:311:in > `to_specs': > > Could not find 'sass-listen' (~> 4.0.0) among 4 total gem(s) > ... > > > Ruby-sass is no longer supported. Please see the Sass compiler section > at > <https://docs.mailman3.org/en/latest/install/virtualenv.html#dependencies > >. > I uninstalled rubygem-sass from the OS. I don't remember consciously installing that because it was never in the guide I followed (which is your own writeup). But I still have a problem: (venv) [mailman3@gw ~/mm]$ /opt/mailman/mm/bin/mailman-post-update + '[' False == False ']' + mkdir -p /opt/mailman/mm/static + /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput --verbosity 0 + /opt/mailman/mm/bin/django-admin compress CommandError: An error occurred during rendering /opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3-1.3.5-py3.7.egg/django_mailman3/templates/socialaccount/signup.html: */bin/sh: sass: not found* pip3 install sass fails: ..... ERROR: Command errored out with exit status 1: /opt/mailman/mm/venv/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-vnlujru1/sass_15812b8baa1b405c8130edb21a4f4316/setup.py'"'"'; __file__='"'"'/tmp/pip-install-vnlujru1/sass_15812b8baa1b405c8130edb21a4f4316/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-_f8rgww1/install-record.txt --single-version-externally-managed --compile --install-headers /opt/mailman/mm/venv/include/site/python3.7/sass Check the logs for full command output. The complete failure text is at https://pastebin.ubuntu.com/p/tsB2CCNrQG/ Maybe it's time to blow up everything in the virtualenv and start over because I am not sure what caused this. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

4 years, 5 months

Re: Unable to retrieve <800 members of Mailman list through Curl command

by Abhilash Raj

Hi, thanks, Abhilash Raj On Wed, Jan 20, 2021 at 17:58, Shashikanth Komandoor <shashikanth.komandoor(a)gmail.com> wrote: > Hi Team, > > I am currently running Mailman 3 with version 3.3.1 and in > built > postfix version 2.10.1-6 on RHEL 7.5 with PostgreSQL 11.7 version with > default values. I am almost running 2000 lists with 128 GB RAM and 24 > Cores > on a single VM and on which all the mailman 3 components are running. > > It is observed for most of the lists having members more > than > 500 is displaying "Mailman REST API not available. Please restart > Mailman > Core" message on the postorius window and on running the CURL command > over > REST API of Mailman it is reaching the time limit 30 seconds and > showing > the below error. This is a known issue with the Members API. You can use pagination[1] to get the list of Members in batches instead of all in a single request. I'd say a page size of 200~ should be fine, but you should try out on your server and adjust the size. [1]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… You can also use the command line to run `mailman members ant.example.com` to get a list of Members for the list. Abhilash > > > > *curl: (52) Empty reply from serverNo JSON object could be decoded* > > The same behavior is observed on browsing the held > messages for > few lists either through the browser or through CURL and REST API. > > How to resolve this issue ? What other details I can > provide to > make you get an idea ? > -- > Thanks & Regards, > Shashi Kanth.K > 9052671936 > > > > > <<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…>> > Virus-free. > www.avast.com <http://www.avast.com/> > <<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…>> > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > <mailto:mailman-users@mailman3.org> > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > <mailto:mailman-users-leave@mailman3.org> > <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>

4 years, 5 months

Re: subscribing to any list is not possible

by r.woithe＠callassoftware.com

Hello again, cause of testing with the new installation, the mailman log file gives me an error: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman/app/workflow.py", line 69, in __next__ return step() File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", line 331, in _step_send_confirmation self._set_token(TokenOwner.subscriber) File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", line 157, in _set_token self.token = pendings.add(pendable, timedelta(days=3650)) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3/dist-packages/mailman/model/pending.py", line 91, in add token = token_factory.new() File "/usr/lib/python3/dist-packages/mailman/utilities/uid.py", line 79, in new return self._next_unpredictable_id() File "/usr/lib/python3/dist-packages/mailman/utilities/uid.py", line 155, in _next_unpredictable_id x = random.random() + right_now % 1.0 + time.clock() % 1.0 AttributeError: module 'time' has no attribute 'clock' Jan 13 09:23:29 2021 (1263) REST request handler error: Traceback (most recent call last): File "/usr/lib/python3.8/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 218, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 248, in falcon.api.API.__call__ File "falcon/api.py", line 244, in falcon.api.API.__call__ File "/usr/lib/python3/dist-packages/mailman/rest/members.py", line 262, in on_post token, token_owner, member = registrar.register( File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", line 520, in register list(workflow) File "/usr/lib/python3/dist-packages/mailman/app/workflow.py", line 69, in __next__ return step() File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", line 331, in _step_send_confirmation self._set_token(TokenOwner.subscriber) File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", line 157, in _set_token self.token = pendings.add(pendable, timedelta(days=3650)) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3/dist-packages/mailman/model/pending.py", line 91, in add token = token_factory.new() File "/usr/lib/python3/dist-packages/mailman/utilities/uid.py", line 79, in new return self._next_unpredictable_id() File "/usr/lib/python3/dist-packages/mailman/utilities/uid.py", line 155, in _next_unpredictable_id x = random.random() + right_now % 1.0 + time.clock() % 1.0 AttributeError: module 'time' has no attribute 'clock' i found this: This bug has been already fixed in upstream: https://gitlab.com/mailman/mailman/-/commit/ea05bdd0f74ba06d85adad1f7d190a6… i will try to patch it.

4 years, 5 months

Re: [Django] ERROR (EXTERNAL IP): Service Unavailable

by dancab＠caltech.edu

Thanks, I'm copying what seems like the relevant info from mailman.log below. Sorry, I totally missed that log existed! There's very little time delay from the moment I click to view the held messages and receiving the API error. There is a non-zero count in the badge for the Held Messages tab. It shows "1" as expected. [25/Feb/2021:09:28:14 -0800] "GET /3.1/lists/cpa-announcement(a)caltech.edu/held?count=0&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.2" [2021-02-25 09:28:14 -0800] [462] [ERROR] Socket error processing request. Traceback (most recent call last): File "/opt/mailmanve/lib64/python3.6/site-packages/gunicorn/workers/sync.py", line 134, in handle self.handle_request(listener, req, client, addr) File "/opt/mailmanve/lib64/python3.6/site-packages/gunicorn/workers/sync.py", line 190, in handle_request util.reraise(*sys.exc_info()) File "/opt/mailmanve/lib64/python3.6/site-packages/gunicorn/util.py", line 625, in reraise raise value File "/opt/mailmanve/lib64/python3.6/site-packages/gunicorn/workers/sync.py", line 175, in handle_request respiter = self.wsgi(environ, resp.start_response) File "/opt/mailmanve/lib64/python3.6/site-packages/mailman/database/transaction.py", line 50, in wrapper 18,1 Top raise value File "/opt/mailmanve/lib64/python3.6/site-packages/gunicorn/workers/sync.py", line 175, in handle_request respiter = self.wsgi(environ, resp.start_response) File "/opt/mailmanve/lib64/python3.6/site-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/opt/mailmanve/lib64/python3.6/site-packages/mailman/rest/wsgiapp.py", line 193, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 274, in falcon.api.API.__call__ File "falcon/api.py", line 269, in falcon.api.API.__call__ File "/opt/mailmanve/lib64/python3.6/site-packages/mailman/rest/post_moderation.py", line 174, in on_get resource = self._make_collection(request) File "/opt/mailmanve/lib64/python3.6/site-packages/mailman/rest/helpers.py", line 182, in _make_collection entries = [as_dict(resource) for resource in collection] File "/opt/mailmanve/lib64/python3.6/site-packages/mailman/rest/helpers.py", line 182, in <listcomp> entries = [as_dict(resource) for resource in collection] File "/opt/mailmanve/lib64/python3.6/site-packages/mailman/rest/post_moderation.py", line 164, in _resource_as_dict resource = self._make_resource(request.id) File "/opt/mailmanve/lib64/python3.6/site-packages/mailman/rest/post_moderation.py", line 76, in _make_resource msg = getUtility(IMessageStore).get_message_by_id(key) File "/opt/mailmanve/lib64/python3.6/site-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/opt/mailmanve/lib64/python3.6/site-packages/mailman/model/messagestore.py", line 103, in get_message_by_id return self._get_message(row) File "/opt/mailmanve/lib64/python3.6/site-packages/mailman/model/messagestore.py", line 95, in _get_message with open(path, 'rb') as fp: FileNotFoundError: [Errno 2] No such file or directory: '/var/tmp/mailman/messages/XC/DU/XCDUNGGCTVSN7RGCW5F3WXM5T2WEHCCJ'

4 years, 4 months

Re: error changed after restart

by Guillermo Hernandez (Oldno7)

On 6/2/21 21:19, Abhilash Raj wrote: > > > On Sat, Feb 6, 2021 at 19:44, Guillermo Hernandez (Oldno7) via > Mailman-users <mailman-users(a)mailman3.org> wrote: >> On 6/2/21 18:08, Abhilash Raj wrote: >> >> On Sat, Feb 6, 2021, at 3:04 AM, Guillermo Hernandez (Oldno7) via >> Mailman-users wrote: >> >> I restarted de server and the error changed. Now the log >> shows "KeyError: 'subscription_mode'": >> >> Did you also restart Mailman Core after the upgrade? >> >> Yes, indeed: I stopped mailman core and all the processes related. >> Did the upgrades. Started all again. Find the errors in the web user >> interface. Stopped all again. Looked for errors in the log. Restarted >> the complete server. Found the second error that this second mail is >> about to. It happens when, in the main page that shows all the lists >> you click to see one of them. It seems to me that it has been >> database structure changes in django that the upgrade is not aware... >> but it's a very long shot from my side. > `subscription_mode` was added in Mailman Core 3.3.2 and it is actually > a derived atrribute and not stored in Database. Mailman's API should be > returning this attribute for each Member, but for some reason it seems > to me like it isn't doing that even though do have Mailman 3.3.3 running > like you said. > If you have Curl installed, can you send me the output of: > $ curl -u <user>:<pass> http://localhost:8001/3.1/members?count=5&page=1 This is the output you asked for (it's the same you can see when you try to interact with one list): /usr/local/mailman3 # curl -u XXXXXX:XXXXXX http://localhost:8001/3.1/members?count=5&page=1 /usr/local/mailman3 # <html> <head> <title>Internal Server Error</title> </head> <body> <h1><p>Internal Server Error</p></h1> </body> </html> No log entry has been produced... TIA. > It should ideally return an output that looks something like shown > here[1]. You > can put the username/password of Core's API server in the above command. > [1]: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > > Abhilash >> I'm using sqlite as django database and mysql for mailman. >> >> ERROR 2021-02-06 11:47:49,015 26798 django.request Internal >> Server Error: >> /mailman3/mailman3/lists/name_and_domain.of.the.list >> Traceback (most recent call last): File >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >> line 119, in __getattr__ return self._get(name) File >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >> line 86, in _get raise KeyError(key) KeyError: >> 'subscription_mode' During handling of the above exception, >> another exception occurred: Traceback (most recent call >> last): File >> "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py", >> line 34, in inner response = get_response(request) File >> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", >> line 115, in _get_response response = >> self.process_exception_by_middleware(e, request) File >> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", >> line 113, in _get_response response = >> wrapped_callback(request, *callback_args, **callback_kwargs) >> File >> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", >> line 71, in view return self.dispatch(request, *args, >> **kwargs) File >> "/usr/local/lib/python3.7/site-packages/postorius/views/generic.py", >> line 74, in dispatch return super(MailingListView, >> self).dispatch(request, *args, **kwargs) File >> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", >> line 97, in dispatch return handler(request, *args, >> **kwargs) File >> "/usr/local/lib/python3.7/site-packages/postorius/views/list.py", >> line 295, in get member.subscription_mode == File >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >> line 124, in __getattr__ self.__class__.__name__, name)) >> AttributeError: 'Member' object has no attribute >> 'subscription_mode' *********************** some info about >> the installed versions via pip list: pip list | grep django >> django-allauth 0.44.0 >> django-appconf 1.0.4 >> django-compressor 2.4 >> django-extensions 3.1.0 >> django-gravatar2 1.4.4 >> django-haystack 3.0 >> django-mailman3 1.3.5 >> django-picklefield 3.0.1 >> django-q 1.3.4 >> djangorestframework 3.12.2 pip list | grep mailman >> django-mailman3 1.3.5 >> mailman 3.3.3 >> mailman-hyperkitty 1.1.0 >> mailmanclient 3.3.2 pip list | grep postorius >> postorius 1.3.4 On 6/2/21 11:12, >> Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> I've just upgrade mailman 3 installation following Mr. >> Sapiro advice: did a pip install --upgrade >> django-mailman3 hyperkitty mailman mailmanclient >> mailman-hyperkitty postorius I did a "python3 manage.py >> migrate" after, too. And all seemed to run well. All the >> lists showed in postorius via web, but when I try to >> accesss into one of them the browser shows an error. In >> the log you can see: *-*-*-*-*-*-* Traceback (most recent >> call last): File >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >> line 119, in __getattr__ return self._get(name) >> File >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >> line 86, in _get raise KeyError(key) KeyError: >> 'get_requests_count' .. (And after all the traceback >> lines) AttributeError: 'MailingList' object has no >> attribute 'get_requests_count' *-*-*-*-*-*-*-* The lists >> seem to be distributing messeages well.. but I cannot >> acces via web administration (django/postorius) Can >> anyone point me in the right direction to solve this, >> please? _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> <mailto:mailman-users@mailman3.org> To unsubscribe send >> an email to mailman-users-leave(a)mailman3.org >> <mailto:mailman-users-leave@mailman3.org> >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/> >> >> >> _______________________________________________ Mailman-users >> mailing list -- mailman-users(a)mailman3.org >> <mailto:mailman-users@mailman3.org> To unsubscribe send an >> email to mailman-users-leave(a)mailman3.org >> <mailto:mailman-users-leave@mailman3.org> >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/> >> >> >> _______________________________________________ Mailman-users mailing >> list -- mailman-users(a)mailman3.org >> <mailto:mailman-users@mailman3.org> To unsubscribe send an email to >> mailman-users-leave(a)mailman3.org >> <mailto:mailman-users-leave@mailman3.org> >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/>

4 years, 5 months

Re: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Abhilash Raj

On Thu, Feb 25, 2021, at 3:55 PM, Brian Carpenter wrote: > https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 Thanks Brian, this looks quite comprehensive in the details. The only thing I am a bit concerned about is granting sudo privileges to the Mailman user. It really shouldn't have sudo given that Mailman and Django are supposed to run as mailman user. Any compromise of the Django application will provide the attacker root on the machine. On Thu, Feb 25, 2021, at 3:55 PM, Brian Carpenter wrote: > I have finished my how-to install Mailman 3 on Debian 10 completed to > the point where you can use it to get a fully functional Mailman 3 > environment up and running. This is a comprehensive guide that walks you > through installing EVERYTHING (currently!) that Mailman 3 needs to run. > It also makes updating Mailman 3/Postorius/Hyperkitty very easy. I have > not added the update directions yet but will very soon. I also plan on > adding a section on setting up DKIM and Xapian with Mailman 3. > > I hope this helps those who wish to get a Mailman 3 server up and > running quickly and brings a sense of sanity to the confusion regarding > the various documentation out there concerning the installation of > Mailman 3/Postorius/Hyperkitty. I intend to add a How-to for Ubuntu 20 > at some point. This really does remind me of https://xkcd.com/927/. Is there a specific reason that you chose to go with an entirely new doc rather than helping to improve the existing one? Several parts of it (at least the ones that official guide covers) seems similar to me and is duplicate information that at least two people are going to spend time writing and maintaining in future. Is it something about the contribution process to the official documentation that makes it hard for people to contribute? Most of the pages at docs.mailman3.org or come from this[1] repo and use Sphinx to build and REsT formatting (.rst). [1]: https://gitlab.com/mailman/mailman-suite-doc I am just trying to understand how can we lower the barrier for community members to help contribute to existing docs instead of them having to create new ones. Specifically around installation, since that tends to get stale often when depedent packages change or a new dependency is added that breaks the installation. -- thanks, Abhilash Raj (maxking)

4 years, 4 months

Re: Unable to get mailman3 working on Ubuntu 20.04 LTS

by Abhilash Raj

> On Oct 27, 2021, at 4:51 PM, Shawn Heisey <mailman(a)elyograg.org> wrote: > > On 10/26/2021 11:43 AM, Michael Heseltine wrote: >> after upgrading an older server to Ubuntu 20.04, I tried to first upgrade my old mailman 2 installation to mailman 3. I've been on it for three weeks now, but unable to get anything working. I have long forgone the idea of upgrading and thus purged everything from mailman2 on my machine, and installed and removed mailman3 several times to no avail. > > I just ran into a lot of trouble myself getting the Ubuntu packages working. And I got the same advice you did from this mailing list -- don't try to install it that way. > > My first attempt at installing it without using packages was the virtualenv method. After beating my head against that for a few hours and not making any progress at all, I gave up. > > I now have the docker install fully functional, and imported my list configurations from data I saved from an ancient mailman2 install. It was giving me grief too when I first installed it, but I managed to work through each of the problems. One of the issues was a basic networking problem -- mailman in the container wasn't able to talk to Postfix on the host. Rebooting the host cleared that up. Side note: There are no details in the docker instructions about how to upgrade the containers to newer versions. Easy upgrades was a big reason why I wanted to use the Ubuntu packages. Upgrading other packages has always been pretty straightforward. The instructions are basically in the issue description, pending move to a documentation page: https://github.com/maxking/docker-mailman/issues/293 If you are upgrading the latest 0.4.x release from 0.3.x, you also want to look at https://asynchronous.in/docker-mailman/news/#upgrading-to-040-release > > I'm using Apache, not nginx. It was already installed, and I know more about configuring it than nginx. It wasn't too difficult to set up Apache to proxy over to uwsgi running in the web container. I had to work out the config myself ... the docker instructions only have a config example for nginx. If you can send a PR for the config you set up for Apache in Github, or just an issue, I can include it in the docs :-) -- thanks, Abhilash Raj (maxking)

3 years, 8 months

Mailman-users search results for query "2021"