Search results for "Postorius" - Mailman-users

KeyError: 'subject_prefix'

by Stephen J. Turnbull

Torge Riedel writes: > today I had the following error in my inbox: > > KeyError: 'subject_prefix' > AttributeError: 'MailingList' object has no attribute > 'subject_prefix' This isn't very helpful. Does this happen for all lists? A particular list? How long have you been running this version of Mailman 3 (time since last update)? Is there anything in the logs from Mailman core (this error is coming from the client side of the REST API module)? > I checked the database, Which database? It looks to me like subject_prefix is declared in both Mailman core and HyperKitty (I haven't checked Postorius). I'm not real familiar with this code, so it could be that eventually everything boils down to REST calls to Mailmman core, but it looks like Django's database is involved for HyperKitty. > there is a column "subject_prefix", so I feel it is something in > the code causing the error. Sure, but what? We eventually see this: > File "/opt/mailman/web/venv/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 112, in call > error_msg, response, None) > urllib.error.HTTPError: HTTP Error 500: <html> > <head> > <title>Internal Server Error</title> > </head> > <body> > <h1><p>Internal Server Error</p></h1> > > </body> > </html> which is mailmanclient passing on the REST API's report that Mailman core is very confused. There should be a log message from core for this.

4 years, 8 months

Re: Migrating mailman3 to latest ubuntu lts

by Helio Loureiro

Hi, And here we have it: (venv) mailman@new=server ~ (v3.3.9)> mailman-web migrate System check identified some issues: WARNINGS: account.EmailAddress: (models.W036) MariaDB does not support unique constraints with conditions. HINT: A constraint won't be created. Silence this warning if you don't care about it. account.EmailAddress: (models.W043) MariaDB does not support indexes on expressions. HINT: An index won't be created. Silence this warning if you don't care about it. Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: Applying account.0004_alter_emailaddress_drop_unique_email... OK Applying account.0005_emailaddress_idx_upper_email... OK Applying admin.0003_logentry_add_action_flag_choices... OK Applying auth.0009_alter_user_last_name_max_length... OK Applying auth.0010_alter_group_name_max_length... OK Applying auth.0011_update_proxy_permissions... OK Applying auth.0012_alter_user_first_name_max_length... OK Applying django_mailman3.0003_sessions... OK Applying django_q.0010_auto_20200610_0856... OK Applying django_q.0011_auto_20200628_1055... OK Applying django_q.0012_auto_20200702_1608... OK Applying django_q.0013_task_attempt_count... OK Applying django_q.0014_schedule_cluster... OK Applying hyperkitty.0016_auto_20180309_0056... OK tl;dr: it was the database. So the django was spitting out absolutely horrible traceback errors to diagnose the issue. I modified the code to print the query and then raise exception (what is expected from an error, not only "I just failed, sorry do whatever"). Then I got the query and tried manually. And it failed. (venv) mailman@new-server ~ (v3.3.9)> mailman-web migrate System check identified some issues: WARNINGS: account.EmailAddress: (models.W036) MariaDB does not support unique constraints with conditions. HINT: A constraint won't be created. Silence this warning if you don't care about it. account.EmailAddress: (models.W043) MariaDB does not support indexes on expressions. HINT: An index won't be created. Silence this warning if you don't care about it. Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: Applying account.0004_alter_emailaddress_drop_unique_email...Error running query: b'*ALTER** TABLE `account_emailaddress` DROP INDEX `email`'* Traceback (most recent call last): File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 89, in _execute return self.cursor.execute(sql, params) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/mysql/base.py", line 75, in execute return self.cursor.execute(query, args) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/cursors.py", line 179, in execute res = self._query(mogrified_query) [...] (venv) mailman@new-server ~ (v3.3.9) [0|1]> mysql -umailman3web -p -h localhost mailman3web Enter password: Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 32 Server version: 10.6.12-MariaDB-0ubuntu0.22.04.1 Ubuntu 22.04 Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [mailman3web]> *ALTER TABLE `account_emailaddress` DROP INDEX `email`;* ERROR 2013 (HY000): Lost connection to server during query MariaDB [mailman3web]> *ALTER TABLE `account_emailaddress` DROP INDEX `email`;* ERROR 2006 (HY000): Server has gone away No connection. Trying to reconnect... Connection id: 32 Current database: mailman3web ERROR 2013 (HY000): Lost connection to server during query So I looked to the mysql error logs and searched Internet for the issue. It recommended to run a "mysql_upgrade", which failed with another error: root@seliius26224 /e/mailman3# mysql_upgrade -u root --force Phase 1/7: Checking and upgrading mysql database Processing databases mysql mysql.column_stats OK mysql.columns_priv OK mysql.db OK mysql.engine_cost Error : Table 'mysql.engine_cost' doesn't exist status : Operation failed mysql.event OK mysql.func OK [...] sys.x$wait_classes_global_by_avg_latency OK sys.x$wait_classes_global_by_latency OK sys.x$waits_by_host_by_latency OK sys.x$waits_by_user_by_latency OK sys.x$waits_global_by_latency OK Phase 4/7: Running 'mysql_fix_privilege_tables' ERROR 1932 (42S02) at line 477: Table 'mysql.innodb_index_stats' doesn't exist in engine FATAL ERROR: Upgrade failed I searched again the Internet and found a fix: https://stackoverflow.com/questions/37856155/mysql-upgrade-failed-innodb-ta… Now migration is progressing. Thanks for all the patience and support. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Tue, 19 Dec 2023 at 15:23, Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/19/23 3:11 AM, Helio Loureiro wrote: > > Hi, > > > > No luck :( > > > > (venv) mailman@new-server ~ (v3.3.9)> *pip install -U > > django-allauth==0.58.0* > > You need to install django-allauth<0.58.0 as in > ``` > pip install django-allauth\<0.58 > ``` > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to helio(a)loureiro.eng.br >

1 year, 7 months

Re: Invalid FilterAction: discard. Treating as discard

by Mark Sapiro

On 5/7/19 6:19 AM, Henrik Rasmussen wrote: > Having set the Filter content to Yes - regardless of other setting in the "Alter Messages" tab, make a HTML message come out empty. I can replicate this on my test list. I don't understand the question? Are you asking why the log contains "invalid FilterAction: discard. Treating as discard"? If so, that's a bug. See <https://gitlab.com/mailman/mailman/issues/592>. If you are asking why the message is empty after filtering and discarded, It is presumably because it is a text/html message as opposed to a multipart/alternative message with text/plain and text/html alternative parts. > I have tried debugging by changing each setting one-by-one and sending the user's mail, but no change makes the mail come out with a content. However setting "Filter content" to "no" makes the mail come out okay. There are list attributes filter_types and pass_types (also filter_extensions and pass_extensions, but those probably aren't relevant here) which affect this and which aren't exposed in Postorius. See <https://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/filterin…> for more info of content filtering. Presumably, the combination of filter_types and pass_types is not allowing text/html. You need to examine these settings in mailman shell, e.g. list(m.pass_types) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

Re: Problem with digests not being sent daily

by Mark Sapiro

On 6/21/24 22:04, Mark wrote: > > At ~04:50 I posted an email to the list. The message was delivered to > members and archived. > > Nothing showed up in /opt/mailman/mm/var/lists/<LISTID> Probably because (in Postorius) Settings->Digest->Enable Digests is No > Then, as "mailman", I ran "mailman digests --periodic" manually and got > the same error (as expected since there is nothing there) ... > > $ /opt/mailman/venv/bin/mailman digests --periodic > Traceback (most recent call last): ... > FileNotFoundError: [Errno 2] No such file or directory: > '/opt/mailman/mm/var/lists/<LISTID>/digest.mmdf' -> > '/opt/mailman/mm/var/lists/<LISTID>/digest.6.3.mmdf' This error should not occur if there is no digests.mmdf. It only does occur because you have set Digest size threshold to 0 under the assumption that 0 means unlimited which it doesn't. If you don't want digests sent on size, you need to set Digest size threshold to a very large number. I've created https://gitlab.com/mailman/mailman/-/issues/1158 to avoid throwing the exception, but setting the threshold to 0 is still wrong as it will cause a digest to be sent on every post. If the Enable Digests setting is Yes, then the lack of digests needs more investigation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

Re: Bulk update of members' moderation settings

by Mark Sapiro

On 11/18/21 12:37 PM, Alex King via Mailman-users wrote: > I imported a list from mailman 2.1 using > https://docs.mailman3.org/en/latest/migration.html. > > It happens that emergency moderation was set on the mailman 2.1 list, > and this has resulted in all members having Moderation set to Hold. I > now want to change that to Default Processing for all members. > > Is there a way to achieve that in bulk without clicking through the > members options for each member in Postorius? I don't understand how this happened. The mailman 2.1 list's emergency setting should hsave been imported as the emergency setting of the Mailman 3 list and should not affect individual member's moderation at all. However, to set the moderation action for all members of a list to default processing You can do something like this in mailman shell ``` bin/mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> from mailman.interfaces.action import Action >>> for member in m.members.members: ... member.moderation_action = Action.defer ... >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

Re: MM2 to MM3 Archives Loading

by Alain D D Williams

On Wed, Dec 04, 2024 at 08:45:02PM -0000, Joshua Bushe wrote: > This link is an example you sent earlier: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/ > > This link is above is the page where i can't see any of my lists outputs on my mailman3 gui. All i visually see is three loading icons spinning. Also, mark said it will only show threads with post in the last 30 days. so i made a test list and made a new thread and still the problem persists. Still see the three loading icons spinning. I've manually added the test list and also did it through the gui. Same outcome. This is one of the things that I had few problems with. The command that I used was: # su - list -s /usr/bin/bash -c 'python3 /usr/share/mailman3-web/manage.py hyperkitty_import -l senate(a)mm-test.phcomp.co.uk /tmp/senate.mbox' • This was on a Debian system, installed via apt-get • /tmp/senate.mbox needs to be readable by the user list • Done after the list had been created via postorius, then I ran: # su - list -s /usr/bin/bash -c 'mailman --run-as-root import21 senate(a)mm-test.phcomp.co.uk /tmp/senate.pck' -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

8 months

Re: Installing mailman 3

by Rafael Mora

Why isn't it sending emails? What do you think? El mar., 1 ago. 2017 a las 16:34, Abhilash Raj (<raj.abhilash1(a)gmail.com>) escribió: > > > > On Tue, Aug 1, 2017, at 02:29 PM, Rafael Mora wrote: > > Hello Abhilash, > > I have this in my settings.py file: > > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'localhost' > EMAIL_PORT = 25 > #EMAIL_HOST_USER = 'mailing(a)labbrands.com' > #EMAIL_HOST_PASSWORD = '******' > > > This looks good to me. > > > What should I use in user and password?? Does Django use postfix to send > the email??? > > > I think you don't need a password and username as long as your postfix is > configured to relay local emails without authentication (which it is by > default if you installed from distro packages and if you haven't changed > the settings). > > > Thanks > > > > > El mar., 1 ago. 2017 a las 16:20, Abhilash Raj (<raj.abhilash1(a)gmail.com>) > escribió: > > Hi, > > > > On Tue, Aug 1, 2017, at 02:11 PM, Rafael Mora wrote: > > It's ok now, but still I can't make it send the confirmation email > > > > This is from mailman.log: > > > > > > [mailman@localhost logs]$ tail -f mailman.log > > Aug 01 15:59:18 2017 (2327) lmtp runner started. > > Aug 01 15:59:18 2017 (2333) virgin runner started. > > Aug 01 15:59:18 2017 (2332) retry runner started. > > Aug 01 15:59:18 2017 (2330) pipeline runner started. > > Aug 01 15:59:18 2017 (2325) command runner started. > > Aug 01 15:59:19 2017 (2328) nntp runner started. > > Aug 01 15:59:19 2017 (2326) in runner started. > > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET > > /3.0/lists?count=0&page=1&advertised=true HTTP/1.1" 200 90 > > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET > > /3.0/lists?count=10&page=1&advertised=true HTTP/1.1" 200 90 > > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/domains HTTP/1.1" 200 > > 90 > > > > > > > > > > What should I do? > > If you are talking about Account confirmation emails, they usually are > sent out from Django and not Mailman Core itself. > > To configure Django you need to edit the `settings.py` file, wherever > that is one your installation. If you are following the guide mentioned > at http://docs.mailman3.org/en/latest/prodsetup.html, it should be at > `mailman-suite/mailman-suite_project/settings.py`. > > To configure your Django to send emails, have a look at > > http://docs.mailman3.org/en/latest/config-web.html#setting-up-email-required > . > > That documentation page has pretty much everything you need in order to > have a running Web Frontend, please go through it and make sure you have > everything configured. > > Finally, the actual emails from Mailing lists are supposed to be handled > by Core. You need to configure Postorius & Mailman both to communicate. > The settings are mentioned > http://docs.mailman3.org/en/latest/config-core.html#configuring-mta > here. > > > Hope that helps! > > > > > > > > > > > > > > > El mar., 1 ago. 2017 a las 15:36, Mark Sapiro (<mark(a)msapiro.net>) > > escribió: > > > > > On 8/1/17 1:14 PM, Rafael Mora wrote: > > > > > > > > Why does it say Address already in use? > > > > > > > > > Because you are starting lm tp runner and it's already running. > > > > > > Do 'mailman stop'. Then ensure no Mailman processes are running. kill > > > any if necessary. Then do 'mailman start'. > > > > > > -- > > > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > > > San Francisco Bay Area, California better use your sense - B. Dylan > > > _______________________________________________ > > > Mailman-users mailing list > > > mailman-users(a)mailman3.org > > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > > -- > > > > Atentamente / Best Regards > > > > Ing. Rafael Mora > > _______________________________________________ > > Mailman-users mailing list > > mailman-users(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > -- > thanks, > Abhilash Raj > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > -- > > Atentamente / Best Regards > > Ing. Rafael Mora > > > -- > thanks, > Abhilash Raj > > -- Atentamente / Best Regards Ing. Rafael Mora

8 years

Re: Mailman 3 installation from latest Debian packages

by Andreas Barth

* Brian Carpenter (brian_carpenter(a)emwd.com) [210212 19:05]: > On 2/12/21 7:49 AM, Matthew Blissett wrote: > >I found > >https://lists.gem5.org/archives/list/gem5-announce@gem5.org/ which > >is running the same version, but presumably not using these Debian > >packages as the Javascript is slightly different. > > > >Could this be a problem with the Debian packaging, or perhaps my > >configuration -- which is very close to the defaults (i.e. Mailman > >and Apache configuration generated by dpkg). > > > >Has anyone set up a working installation using these packages? > > The above reference URL is actually one of our clients running on > one of our Mailman 3 shared servers. Mailman 3/Postorius/Hyperkitty > were all installed using a virtual environment via pip. I don't use > packages at all for our Mailman 3 installations. Sorry I was too fast deleting the original mail, so replying here instead. I used the Debian packages as my original mailman configuration but migrated then to mailman based on git. Still using the configuration settings from the debian packages (e.g. content of mailman3-web.cfg). So yes, the debian packages worked fine for me with just the defaults. (However, I would strongly recommend to use postgres and not sqlite as the database, as sqlite is unfit for production, and migration is not really easily possible, but that's not related to Debian.) Regards, Andi

4 years, 5 months

Error in mailman3 debian package, python error

by Lars Schimmer

Hi! Mailman Core Version GNU Mailman 3.2.1 (La Villa Strangiato) Mailman Core API Version 3.0 Mailman Core Python Version 3.7.3 (default, Apr 3 2019, 05:39:12) [GCC 8.3.0] Since yesterday our mailman3 (debian package) throws this error: Internal Server Error: /mailman3/hyperkitty/api/mailman/archive OperationalError at /hyperkitty/api/mailman/archive (1366, "Incorrect string value: '\\xF0\\x9F\\x8D\\x8E' for column `mailman3web`.`hyperkitty_email`.`subject` at row 1") Request Method: POST Request URL: http://localhost/mailman3/hyperkitty/api/mailman/archive?key=zMxTGlteq4tqkL… Django Version: 1.11.22 Python Executable: /usr/bin/uwsgi-core Python Version: 3.7.3 Python Path: ['.', '', '/usr/lib/python37.zip', '/usr/lib/python3.7', '/usr/lib/python3.7/lib-dynload', '/usr/local/lib/python3.7/dist-packages', '/usr/lib/python3/dist-packages'] Server time: Wed, 7 Aug 2019 08:03:47 +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/db/backends/utils.py" in execute 64. return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/mysql/base.py" in execute 101. return self.cursor.execute(query, args) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in execute 250. self.errorhandler(self, exc, value) File "/usr/lib/python3/dist-packages/MySQLdb/connections.py" in defaulterrorhandler 50. raise errorvalue File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in execute 247. res = self._query(query) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in _query 411. rowcount = self._do_query(q) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in _do_query 374. db.query(q) File "/usr/lib/python3/dist-packages/MySQLdb/connections.py" in query 292. _mysql.connection.query(self, query) The above exception ((1366, "Incorrect string value: '\\xF0\\x9F\\x8D\\x8E' for column `mailman3web`.`hyperkitty_email`.`subject` at row 1")) was the direct cause of the following exception: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 41. response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 187. response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 185. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/decorators/http.py" in inner 40. return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mailman.py" in _decorator 69. return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/decorators/csrf.py" in wrapped_view 58. return view_func(*args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mailman.py" in archive 115. add_to_list(mlist_fqdn, msg) File "/usr/lib/python3/dist-packages/hyperkitty/lib/incoming.py" in add_to_list 151. email.save() File "/usr/lib/python3/dist-packages/django/db/models/base.py" in save 808. force_update=force_update, update_fields=update_fields) File "/usr/lib/python3/dist-packages/django/db/models/base.py" in save_base 838. updated = self._save_table(raw, cls, force_insert, force_update, using, update_fields) File "/usr/lib/python3/dist-packages/django/db/models/base.py" in _save_table 924. result = self._do_insert(cls._base_manager, using, fields, update_pk, raw) File "/usr/lib/python3/dist-packages/django/db/models/base.py" in _do_insert 963. using=using, raw=raw) File "/usr/lib/python3/dist-packages/django/db/models/manager.py" in manager_method 85. return getattr(self.get_queryset(), name)(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/db/models/query.py" in _insert 1079. return query.get_compiler(using=using).execute_sql(return_id) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py" in execute_sql 1112. cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py" in execute 64. return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/utils.py" in __exit__ 94. six.reraise(dj_exc_type, dj_exc_value, traceback) File "/usr/lib/python3/dist-packages/django/utils/six.py" in reraise 685. raise value.with_traceback(tb) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py" in execute 64. return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/mysql/base.py" in execute 101. return self.cursor.execute(query, args) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in execute 250. self.errorhandler(self, exc, value) File "/usr/lib/python3/dist-packages/MySQLdb/connections.py" in defaulterrorhandler 50. raise errorvalue File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in execute 247. res = self._query(query) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in _query 411. rowcount = self._do_query(q) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in _do_query 374. db.query(q) File "/usr/lib/python3/dist-packages/MySQLdb/connections.py" in query 292. _mysql.connection.query(self, query) Exception Type: OperationalError at /hyperkitty/api/mailman/archive Exception Value: (1366, "Incorrect string value: '\\xF0\\x9F\\x8D\\x8E' for column `mailman3web`.`hyperkitty_email`.`subject` at row 1") Request information: USER: AnonymousUser Has anyone a idea what went wrong or howto fix it? MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

5 years, 11 months

Fwd: Problems after Upgrade

by Jeff

Update on this. I fixed the problem logging in to the web interface by changing several instances of smart_text to smart_str. I also notice that I errored in my message below by saying the replaced text was “search_text”. It was actually “smart_text”. I believe my "site-packages/compressor” library was not updated correctly because I had to make many manual changes to get things to work. I still have the problem "mailman-web compress” listed below. However, I was able to login to the web interface and approve messages. > Begin forwarded message: > > From: Jeff <mm3(a)steele.com> > Subject: Problems after Upgrade > Date: October 30, 2022 at 3:24:21 PM EDT > To: mailman-users(a)mailman3.org > > Hello, > > I tried to upgrade to the latest mailman3 version using the following command: > > pip install -U mailman postorius django-mailman3 hyperkitty mailman-web mailmanclient > > There didn’t appear to be any problems with this step and I’ve since run it again a few times and only see that the requirements have been satisfied. > > When first running the command: > > mailman-web migrate > > I received several errors dealing with search_text in the package compressor (at least that’s as best as I remember, I wasn’t taking notes). I fixed these manually by changing it to search_str. Eventually "mailman-web migrate” started working and has subsequently worked. > > When I run the command: > > mailman-web compress > > I get the following error: > > traceback (most recent call last): > File "bin/mailman-web", line 8, in <module> > sys.exit(main()) > File "/usr/local/mailman3/lib64/python3.8/site-packages/mailman_web/manage.py", line 37, in main > execute_from_command_line(sys.argv) > File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line > utility.execute() > File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/__init__.py", line 440, in execute > self.fetch_command(subcommand).run_from_argv(self.argv) > File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/__init__.py", line 279, in fetch_command > klass = load_command_class(app_name, subcommand) > File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/__init__.py", line 49, in load_command_class > return module.Command() > File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/base.py", line 274, in __init__ > raise TypeError("requires_system_checks must be a list or tuple.") > TypeError: requires_system_checks must be a list or tuple. > > I have not been able to fix this and would appreciate any assistance. > > When I run the command: > > bin/mailman-web collectstatic > > It asks me yes or no continue and when I enter “yes” it displays the following which I assume means it worked: > > 372 static files copied to '/usr/local/mailman3/web/static', 38 unmodified > > > Starting mailman3 seems to work by the status message shows the following: > > systemctl status -l mailman3 > ... > Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: return function(args[0], config.db.store, *args[1:], **kws) > Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: File "/usr/local/mailman3/lib64/python3.8/site-packages/mailman/model/bounce.py", line 259, in send_warnings_and_remove > Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: self._send_warnings() > Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: File "/usr/local/mailman3/lib64/python3.8/site-packages/mailman/database/transaction.py", line 85, in wrapper > Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: return function(args[0], config.db.store, *args[1:], **kws) > Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: File "/usr/local/mailman3/lib64/python3.8/site-packages/mailman/model/bounce.py", line 310, in _send_warnings > Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: member.address, > Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: File "/usr/local/mailman3/lib64/python3.8/site-packages/mailman/model/member.py", line 121, in address > Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: return (self._user.preferred_address > Oct 30 14:51:03 mailhost.steele.com mailman[3521451]: AttributeError: 'NoneType' object has no attribute 'preferred_address' > lines 13-35/35 (END) > > I have been receiving admin requests to approve messages. But, I can’t approve them because of the following issue: > > Starting mailman-web seems to work as expected with no errors. However, when I try to login to the web interface, I get a HTML page with the following error: > > init__() got an unexpected keyword argument 'providing_args' > Request Method: GET > Request URL: http://lists.crestwood-dc.org/accounts/login/?next=/mailman3/lists/crestwoo… > Django Version: 4.1.2 > Exception Type: TypeError > Exception Value: > __init__() got an unexpected keyword argument 'providing_args' > Exception Location: /usr/local/mailman3/lib64/python3.8/site-packages/compressor/signals.py, line 4, in <module> > Raised during: allauth.account.views.LoginView > Python Executable: /usr/local/mailman3/bin/uwsgi > Python Version: 3.8.13 > > As a result, I cannot login and approve posts. > > I would greatly appreciate any assistance with these issue. > > Thanks much! >

2 years, 9 months

Mailman-users search results for query "Postorius"