Search results for "Postorius" - Mailman-users

Re: Installing mailman 3

by Abhilash Raj

When you set DEBUG=False, Django doesn't serve static files because of which you see only text and no styles. http://docs.mailman3.org/en/latest/pre-installation-guide.html#django-stati… If you do set DEBUG=False, you need to serve the static pages somehow. Alternatively in you case, you can remove the part of the `settings.py` which changes the Emailbackend when `DEBUG=False` so that you don't have to worry about serving static files and still send out emails. On Wed, Aug 2, 2017, at 09:46 AM, Rafael Mora wrote: > For testing purpose I turned back to false the DEBUG var and everything > started working fine with HyperKitty > > I don't understand... this is the trace when I click Login from Postorius > to HyperKitty > > [02/Aug/2017 16:43:42] "GET /postorius/lists/ HTTP/1.1" 200 3645 > [02/Aug/2017 16:43:48] "GET /accounts/login/?next=/postorius/lists/ > HTTP/1.1" 200 10950 > [02/Aug/2017 16:43:49] "GET /static/CACHE/css/hyperkitty.2f591b4e31fe.css > HTTP/1.1" 200 156657 > > > What should I check? > > > > > > > > > El mié., 2 ago. 2017 a las 10:56, Mark Sapiro (<mark(a)msapiro.net>) > escribió: > > > On 08/02/2017 07:55 AM, Rafael Mora wrote: > > > HyperKitty is looking for some files in /static/CACHE/... but it doesn't > > > find them: > > > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" > > > 404 107 > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" > > > 404 107 > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css HTTP/1.1" > > > 404 107 > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > > 404 > > > 105 > > > [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > > 404 > > > 105 > > > > > > > > > Should I run any command to activate the CACHE dir? > > > > > > You need to ensure you have a working sass compiler. As I said at > > < > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > >, > > See the third bullet under > > <http://docs.list.org/en/latest/prodsetup.html#dependencies>. > > > > Then you need to run commands like > > > > django-admin collectstatic --clear > > django-admin compress > > > > > > -- > > 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

9 years, 1 month

Re: Postorius claims 2 messages held when there are none - out of sync

by Mark Sapiro

On 6/26/23 11:53 AM, Ken Alker wrote: > > Is the var/messages hierarchy also where all the archived emails are > stored for future viewing via the web interface? No. They are stored in the hyperkitty_email and hyperkitty_attachment tables in the database. >> Also, there is a long thread at >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/threa >> d/UWCUQYU7Q5X5LWNII57ZZ4DDXE4DEFX7/ and maybe others that might be >> relevant. > > I have never used the mailman shell before, but based on the referenced > thread I learned to do this (note that the thread also taught me how to > rewrite it to narrow down to just the list with issues so I didn't > delete held messages in other lists, if my case): > > for verification: > > venv) mailman@speedy:~/web/logs$ mailman shell -l > sbarc-list(a)lists.netlojix.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 sbarc-list(a)lists.netlojix.com mailing list > >>> requests = IListRequests(m) > >>> first = True > >>> for request in requests.held_requests: > ... key, data = requests.get_request(request.id) > ... if first: > ... first = False > ... print(m.list_id) > ... print (f"""\ > ... Sender: {data['_mod_sender']} > ... Subject: {data['_mod_subject']} > ... Date: {data['_mod_hold_date']} > ... Reason: {data['_mod_reason']} > ... """) > ... > and then to delete the two messages: > > (venv) mailman@speedy:~/web/logs$ mailman shell -l > sbarc-list(a)lists.netlojix.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 sbarc-list(a)lists.netlojix.com mailing list > >>> requests = IListRequests(m) > >>> first = True > >>> for request in requests.held_requests: > ... key, data = requests.get_request(request.id) > ... if first: > ... first = False > ... print(m.list_id) > ... print(f'request id: {request.id}, deleting') > ... requests.delete_request(request.id) > ... > sbarc-list.lists.netlojix.com > request id: 27, deleting > request id: 28, deleting > >>> > > The result of this, however, was that the web interface still claimed I > had two held messages. I wasn't sure if there was some cron-type > "sweeper" process I had to wait to auto-run or if I had to manually do > something to create an update. I then realized that the sample script > had a ' >>> commit ()" ' at the end, which I'd missed. So, I re-entered > the script (but it didn't spit out that it deleted anything this time) > and got an error when I did the commit. Was this in the same `mailman shell` interaction or a new one? What was the error? > So, I figured the messages HAD > been delete and the commit wasn't really necessary. When I went back to > the web interface, the number of held messages was at 0 and I no longer > get the original error when clicking on "Held messages", so my issue is > solved. But this does leave me with some educational questions: > > 1) Did I affect something somehow with my "commit", or was there a job > that cleaned things up (if so, what job)? I'm not sure of the sequence of events, but I think you probably looked in Postorius before you quit `mailman shell` and then you quit `mailman shell` with ctrl-D which did an implicit commit. > 2) Is the "commit" even necessary (I saw it in someone else's script in > the thread)? It is necessary to explicitly commit() or quit with ctrl-D to actually update the database. > 3) Is there a way to save a script and then execute it via shell rather > than typing it in every time (it appears from the examples that people > are typing them in every time, which is super tedious; I didn't paste > for fear of doing something damaging, but maybe that would work)? Yes, you can save a script in the bin/ directory in your venv and run it with `mailman shell -r`. See `mailman shell --details`. > 4) Are the request.id's of the messages dynamic/changing, or are they > fixed for life? I thought I'd delete based on exact request.id without > looping but I was afraid maybe they were changing over time and that > this wouldn't be a good idea. Might be nice to know for the future. The request.id is constant for that request object. The request object is fixed for a specific held message request. I.e., a specific held message's request object and its request.id and other attributes are fixed until that request is handled. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

Error when click on mailing list: An error occurred while processing your request.

by adam.heathcote＠utas.edu.au

Hey there, We have a Mailman3 server with quite a few lists all running with no issues. Recently I imported a list from our old Mailman 2 server which went fine. I attempted to remove the current owner and add myself but now when clicking on the list, Postorius shows: An error occurred while processing your request. The output of /opt/mailman/web/logs/mailmanweb.log is here: ERROR 2024-07-09 17:11:33,371 2795 django.request Internal Server Error: /mailman3/lists/net-ops.list.utas.edu.au/ Traceback (most recent call last): File "/opt/mailman/venv/lib64/python3.9/site-packages/django/core/handlers/exception.py", line 56, in inner response = get_response(request) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/core/handlers/base.py", line 197, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/views/generic/base.py", line 103, in view return self.dispatch(request, *args, **kwargs) File "/opt/mailman/venv/lib64/python3.9/site-packages/postorius/views/generic.py", line 76, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/views/generic/base.py", line 142, in dispatch return handler(request, *args, **kwargs) File "/opt/mailman/venv/lib64/python3.9/site-packages/postorius/views/list.py", line 411, in get return render(request, 'postorius/lists/summary.html', data) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/shortcuts.py", line 24, in render content = loader.render_to_string(template_name, context, request, using=using) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/loader.py", line 62, in render_to_string return template.render(context, request) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/backends/django.py", line 61, in render return self.template.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 175, in render return self._render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/loader_tags.py", line 157, in render return compiled_parent._render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/loader_tags.py", line 63, in render result = block.nodelist.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/defaulttags.py", line 321, in render return nodelist.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/defaulttags.py", line 52, in render output = self.nodelist.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) TypeError: sequence item 1: expected str instance, NoneType found I've tried removing it and reimporting it to no avail. Is there anything I can besides manually creating it and adding the members and owners from the old server? Cheers

2 years, 2 months

Re: Dealing with confirmation requests for unsubscribes

by Mark Sapiro

On 11/18/20 7:41 AM, Brian Carpenter wrote: > Hello List, > > I ran into the following issue for some mailman 3 lists that I am hosting: > > https://gitlab.com/mailman/mailman/-/issues/768 > > Since there is no way for a list owner to deal with a moderation request > for an unsubscription task, I assume I need to do something via the > command line. This is where I need some help with. How do I deal with > these moderation requests that are unable to be reviewed in an admin gui > (Postorius/Affinity)? mailman shell -l list(a)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 test.msapiro.net mailing list This >>> list(getUtility(IPendings).find(mlist=m, pend_type='unsubscription', token_owner=TokenOwner.moderator)) will return something like [('a8df55f557b5718505280d2613937e25a3109252', {'type': 'unsubscription', 'list_id': 'list.example.com', 'email': 'user(a)example.com', 'display_name': 'Mark S', 'when': '2020-11-18T22:56:53', 'token_owner': 'moderator'})] What you want is the token, in this case 'a8df55f557b5718505280d2613937e25a3109252' Then do >>> ISubscriptionManager(m).confirm('a8df55f557b5718505280d2613937e25a3109252') which will return (None, <TokenOwner.no_one: 0>, None) and finally: >>> commit() > I do recommend removing such choices for Postorius for Member policy. I > will be doing this for Affinity until issue 768 is resolved. The correct thing to do is fix <https://gitlab.com/mailman/mailman/-/issues/768>. We almost certainly will do that rather than remove the moderate and confirm then moderate unsubscription policies. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

Re: confirm-email: error NoReverseMatc

by Peter Münster

On Wed, Jan 31 2018, Simon Hanna wrote: > It's complaining about an empty url used for reversing. Do you mind sharing > your settings.py file? we don't need the secret key and logins for stuff, so > you can mask those. the rest should be ok to make public. Ok, here are the settings (mainly from mailman-suite): --8<---------------cut here---------------start------------->8--- import os BASE_DIR = os.path.dirname(os.path.abspath(__file__)) SECRET_KEY = 'xxx' DEBUG = False ADMINS = ( ('Mailman Suite Admin', 'root@localhost'), ) ALLOWED_HOSTS = [ "localhost", # Archiving API from Mailman, keep it. "x1", "x2", ] MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = 'x' MAILMAN_REST_API_PASS = 'y' MAILMAN_ARCHIVER_KEY = 'z' MAILMAN_ARCHIVER_FROM = ('127.0.0.1') INSTALLED_APPS = ( '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', 'paintstore', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', ) MIDDLEWARE_CLASSES = ( 'django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.auth.middleware.SessionAuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware', ) ROOT_URLCONF = 'urls' TEMPLATES = [ { 'BACKEND': 'django.template.backends.django.DjangoTemplates', 'DIRS': [], 'APP_DIRS': True, 'OPTIONS': { 'context_processors': [ 'django.template.context_processors.debug', 'django.template.context_processors.i18n', 'django.template.context_processors.media', 'django.template.context_processors.static', 'django.template.context_processors.tz', 'django.template.context_processors.csrf', 'django.template.context_processors.request', 'django.contrib.auth.context_processors.auth', 'django.contrib.messages.context_processors.messages', 'django_mailman3.context_processors.common', 'hyperkitty.context_processors.common', 'postorius.context_processors.postorius', ], }, }, ] WSGI_APPLICATION = 'wsgi.application' DATABASES = { 'default': { 'ENGINE': 'django.db.backends.sqlite3', 'NAME': os.path.join(BASE_DIR, 'db/mailman.db'), } } AUTH_PASSWORD_VALIDATORS = [ { 'NAME': 'django.contrib.auth.password_validation.UserAttributeSimilarityValidator', }, { 'NAME': 'django.contrib.auth.password_validation.MinimumLengthValidator', }, { 'NAME': 'django.contrib.auth.password_validation.CommonPasswordValidator', }, { 'NAME': 'django.contrib.auth.password_validation.NumericPasswordValidator', }, ] LANGUAGE_CODE = 'fr' TIME_ZONE = 'Europe/Paris' USE_I18N = True USE_L10N = True USE_TZ = True STATIC_ROOT = os.path.join(BASE_DIR, 'static') STATIC_URL = '/static/' STATICFILES_DIRS = ( ) STATICFILES_FINDERS = ( 'django.contrib.staticfiles.finders.FileSystemFinder', 'django.contrib.staticfiles.finders.AppDirectoriesFinder', 'compressor.finders.CompressorFinder', ) SESSION_SERIALIZER = 'django.contrib.sessions.serializers.PickleSerializer' LOGIN_URL = 'account_login' LOGIN_REDIRECT_URL = '' LOGOUT_URL = 'account_logout' DEFAULT_FROM_EMAIL = 'abc' SERVER_EMAIL = 'abc' from django.contrib.messages import constants as messages # flake8: noqa MESSAGE_TAGS = { messages.ERROR: 'danger' } AUTHENTICATION_BACKENDS = ( 'django.contrib.auth.backends.ModelBackend', 'allauth.account.auth_backends.AuthenticationBackend', ) ACCOUNT_AUTHENTICATION_METHOD = "username_email" ACCOUNT_EMAIL_REQUIRED = True ACCOUNT_EMAIL_VERIFICATION = "mandatory" ACCOUNT_LOGIN_ON_EMAIL_CONFIRMATION = True ACCOUNT_LOGIN_ON_PASSWORD_RESET = True ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https" ACCOUNT_UNIQUE_EMAIL = True SOCIALACCOUNT_PROVIDERS = { 'openid': { 'SERVERS': [ dict(id='yahoo', name='Yahoo', openid_url='http://me.yahoo.com'), ], }, 'google': { 'SCOPE': ['profile', 'email'], 'AUTH_PARAMS': {'access_type': 'online'}, }, 'facebook': { 'METHOD': 'oauth2', 'SCOPE': ['email'], 'FIELDS': [ 'email', 'name', 'first_name', 'last_name', 'locale', 'timezone', ], 'VERSION': 'v2.4', }, } COMPRESS_PRECOMPILERS = ( ('text/less', 'lessc {infile} {outfile}'), ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), ) COMPRESS_OFFLINE = True HAYSTACK_CONNECTIONS = { 'default': { 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', 'PATH': os.path.join(BASE_DIR, "fulltext_index"), }, } REST_FRAMEWORK = { 'DEFAULT_FILTER_BACKENDS': ( 'rest_framework.filters.OrderingFilter', ), } Q_CLUSTER = { 'timeout': 300, 'save_limit': 100, 'orm': 'default', } LOGGING = { 'version': 1, 'disable_existing_loggers': False, 'filters': { 'require_debug_false': { '()': 'django.utils.log.RequireDebugFalse' } }, 'handlers': { 'mail_admins': { 'level': 'ERROR', 'filters': ['require_debug_false'], 'class': 'django.utils.log.AdminEmailHandler' }, 'file':{ 'level': 'INFO', #'class': 'logging.handlers.RotatingFileHandler', 'class': 'logging.handlers.WatchedFileHandler', 'filename': os.path.join(BASE_DIR, 'logs', 'mailman.log'), 'formatter': 'verbose', }, 'console': { 'class': 'logging.StreamHandler', 'formatter': 'simple', }, }, 'loggers': { 'django.request': { 'handlers': ['mail_admins', 'file'], 'level': 'ERROR', 'propagate': True, }, 'django': { 'handlers': ['file'], 'level': 'ERROR', 'propagate': True, }, 'hyperkitty': { 'handlers': ['file'], 'level': 'DEBUG', 'propagate': True, }, 'postorius': { 'handlers': ['console', 'file'], 'level': 'INFO', }, }, 'formatters': { 'verbose': { 'format': '%(levelname)s %(asctime)s %(process)d %(name)s %(message)s' }, 'simple': { 'format': '%(levelname)s %(message)s' }, }, } if DEBUG == True: EMAIL_BACKEND = 'django.core.mail.backends.filebased.EmailBackend' EMAIL_FILE_PATH = os.path.join(BASE_DIR, 'emails') FILTER_VHOST = True try: from settings_local import * except ImportError: pass --8<---------------cut here---------------end--------------->8--- -- Peter

8 years, 7 months

Re: Apache shows No Lists

by ceo＠sartrack.nz

Thanks; There has never been a 'Mailman' user. I do have a www-data user (all Apache2 data' and there is a 'list' user. I may have run the import fuction as root, but I then used chown() to set the directory tree /var/lib/mailman3/* to user 'list'. So I upgraded Debian 10 to Debian 11. This also upgraded Apache2 I assume, but I kept the original (single) config file. I then installed the whole Mailman3 package with 'apt'. I may also have installed additional missing bits afterwards, as I think it was not complete. I initially tried to use MariaDB but the installation failed completly because it never asked for the MariaDB root password, and as a result of that everyting else failed too. Then I un-installed 5 times, and then I finally went for the 'default' database system. I then edited the file with the recommended settings for Mailman3: 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> So clearly Apache2 manages to access the data supplied by Postorius because it sees the lists (at least the empty ones). -What user should the whole system running under: 'list'? of 'www-data'? - Is there anything else I should tell Apache2? Now I tried to use "django-admin createsuperuser". This also fails because of this error: ImportError: cannot import name 'force_text' from 'django.utils.encoding' (/usr/local/lib/python3.9/dist-packages/django/utils/encoding.py) And I cannot find where this 'force_text' is called from. It must be removed as it is too old.

3 years, 4 months

Re: Mailman3 throws 500 error (unicode encode) when loading held messages in Postorius

by Mark Sapiro

On 8/27/20 5:44 PM, Simon Handfield via Mailman-users wrote: > > Traceback (most recent call last): > File "/usr/lib/python3.6/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 214, in __call__ > return super().__call__(environ, start_response) > File "falcon/api.py", line 215, in falcon.api.API.__call__ (falcon/api.c:2872) > File "falcon/api.py", line 189, in falcon.api.API.__call__ (falcon/api.c:2419) > File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 167, in on_get > resource = self._make_collection(request) > File "/usr/lib/python3/dist-packages/mailman/rest/helpers.py", line 159, in _make_collection > for resource in collection] > File "/usr/lib/python3/dist-packages/mailman/rest/helpers.py", line 159, in <listcomp> > for resource in collection] > File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 157, in _resource_as_dict > resource = self._make_resource(request.id) > File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 78, in _make_resource > resource['msg'] = msg.as_string() > File "/usr/lib/python3.6/email/message.py", line 158, in as_string > g.flatten(self, unixfrom=unixfrom) > File "/usr/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/lib/python3.6/email/generator.py", line 181, in _write > self._dispatch(msg) > File "/usr/lib/python3.6/email/generator.py", line 214, in _dispatch > meth(msg) > File "/usr/lib/python3.6/email/generator.py", line 272, in _handle_multipart > g.flatten(part, unixfrom=False, linesep=self._NL) > File "/usr/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/lib/python3.6/email/generator.py", line 181, in _write > self._dispatch(msg) > File "/usr/lib/python3.6/email/generator.py", line 214, in _dispatch > meth(msg) > File "/usr/lib/python3.6/email/generator.py", line 243, in _handle_text > msg.set_payload(payload, charset) > File "/usr/lib/python3.6/email/message.py", line 315, in set_payload > payload = payload.encode(charset.output_charset) > UnicodeEncodeError: 'ascii' codec can't encode characters in position 8-9: ordinal not in range(128) > > I'm sorry if this is a query that's answered already but I have not been able to find matching thread that seems to relate to my error. Sorry for not answering earlier and for not being able to devote more time to this now as I'm going away within the hour, but this looks as if the message is somehow defective. Basically, the message can't be flattened by its as_string() method because of unicode issues. This can occur because of non-ascii characters is the message headers or in body parts explicitly or implicitly declared as ascii. We have had workarounds for this for some time, but I don't think they are in 3.1.1, See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/email/message.…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

Re: Listing/Exporting member list error: Mailman REST API not available. Please start Mailman core.

by Abhilash Raj

On Mon, Feb 17, 2020, at 2:24 PM, Daniel Armengod wrote: > Can confirm the problem is reproducible on mailman 3.3.0 installed via PIP. > > Postorius hangs on exporting CSV subscribers [1] (~6k in this case), > with error "Mailman REST API not available. Please start Mailman core" > (which is otherwise running fine). > > mailman3.log also shows WORKER TIMEOUT log entry, exactly the same as > OP's message. > > > You can add a new |gunicorn.cfg| next to your |mailman.cfg| and add > > the additional options. > For further reference if anyone reads this thread, see [2]. > > I had to look that up to figure out where the file name "gunicorn.cfg" > came from. It's not immediately obvious to the reader why a file named > "guincorn.cfg" should be specially interpreted by mailman3. There are several 3rd party libraries/CLIs that collectively makes Mailman Core work. Each of which, have their own configs and Mailman does not wrap each of their configs in it's own, a design decision made by the initial authors which I agree with. Wrapping 3rd party tool's configs in Mailman's configs only makes the job of maintaining much harder. > > The suggested fix - increasing timeout of worker process - did work > perfectly for me. Thanks :) > > Regards, > Daniel > > [1] http://www.<redacted>.org/postorius/lists/<redacted>/csv_view/ > [2] > https://mailman.readthedocs.io/en/latest/src/mailman/runners/docs/rest.html… > > _______________________________________________ > 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)

6 years, 7 months

User with abo to list can not set to another moderation flag

by Stephen J. Turnbull

Chris via Mailman-users writes: > I've one weird problem. I've some lists and a user which is a > moderator on both lists. I don't understand how the moderator role is relevant. > Steps to reproduce > > Postorius -> Users -> search for the user to change -> manage > Both Lists are shown > Moderarion Flag on a newer List was changed from standard to accept -> > On the older list I've tried from Standard to Accept -> click on > the button to accept changes result in reverting to "standard" (the > setting which I want to change). I don't think the moderator role or the presence of multiple lists is related; that page appears to be just broken. Here's another recipe: 1. I went to a site I maintain 2. returned to the top page 3. clicked on a list 4. clicked manage on a user (in both cases, just the one closest to the mouse ponter, no systematic idea) 5. clicked on the moderation option (which was List Default), selected Accept, clicked Update => option remained Accept 6. clicked on the moderation option (still Accept), selected List Default, clicked Update => option reverted to Accept 7. clicked on the moderation option (still Accept), selected Hold, clicked Update => option remained Hold. I tried a few different things, but the pattern was consistent: I could change the option to any value except List Default. Issue https://gitlab.com/mailman/postorius/-/issues/623 You wrote in a followup that > Another way works > List -> users ->(members) -> select User > and in User Settings changing moderation works. and I can confirm that this does work on my instance. Steve

1 year, 7 months

Re: Guidance Request: Migrating Existing Mailman 3 Installation to Docker-Based Deployment

by Washington Odhiambo

On Fri, Apr 10, 2026 at 6:04 PM Prasanth Nair <prasanth.nair(a)linaro.org> wrote: > Hi all, > > I am currently running a Mailman 3 setup on a standalone server and > planning to migrate it to a Docker-based deployment using the official > Docker Mailman images. I would appreciate your guidance on the recommended > approach for this migration. > > *Current (existing) setup:* > > - Mailman Core: 3.3.5 > - Postorius: 1.3.6 > - HyperKitty: 1.3.5 > - PostgreSQL: 12.22 (Ubuntu) > - Host-based installation (non-Docker) > - Postfix used as the MTA > - Active mailing lists with members and archives > - Apache reverse proxy in front > > *Target (new) setup:* > > - Docker-based Mailman 3 (mailman-core, mailman-web, PostgreSQL > containers) > - Based on the official Docker Mailman repository > - Postfix as the MTA > - Apache reverse proxy in front > > I would like to migrate the following components safely: > > - Mailing lists and their configurations > - Subscribers and roles > - HyperKitty archives > - Postorius/web data (users, preferences, etc.) > > I have a few specific questions: > > 1. What is the recommended migration approach from a host-based Mailman > 3 installation to the Docker-based setup? > 2. Is it safe to directly restore the PostgreSQL databases into the > Docker environment, or is there a preferred migration method? > 3. Are there any version compatibility considerations when migrating > from Mailman Core 3.3.5 / Postorius 1.3.6 / HyperKitty 1.3.5 to the > versions used in the current Docker images? > 4. How to migrate archives? > 5. The official Docker Compose file references `postgres:12-alpine`. Is > it recommended to stay on PostgreSQL 12 for compatibility, or is it > supported to use a newer PostgreSQL version (for example, PostgreSQL 18) > with the Docker Mailman setup? > 6. Are there any common pitfalls or best practices you would recommend > for ensuring a smooth migration? > > > Any guidance or documentation you can provide would be greatly appreciated. > > Thank you for your time and support. > Hello Prasanth, How about you just test the installation on Docker and migration and see the results. You could even use a higher version of postgres in your container since MM3 supports it. My test machine has PostgreSQL 17 and MM3 running. Since the test migration is non-destructive, you could do it, fail, drop the volumes, do it again until you have it working. And you take notes in the process. I asked Uncle Google for "migrate mailman3 from bare metal to docker" and the AI response at the top seemed quite close to what it should be. Scare the fear away and just do the testing on some VM. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

5 months, 1 week

Mailman-users search results for query "Postorius"