Search results for "Postorius" - Mailman-users

Re: How to store additional information about lists?

by Mark Sapiro

On 5/25/21 12:28 AM, Stephen J. Turnbull wrote: > Andreas Barth writes: > > > private: hand-selected people, think about e.g. board or steering > > committees internal discussions. Of course, the archive (if there is > > any) should be restricted to the actual members. Posting to these > > lists is currently not restricted, so no derivation needed from the > > current set in postorius. > > This is already possible by requiring admin approval, or by setting > the ban list to something that matches everything like "^.". The ban list can't be used in this way. A banned address can't be subscribed by any means including admin action. And even if an admin temporarily removes the ban, subscribes the address and then restores the ban, the now banned member can't post. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

Re: Posterious membership listing for non-owner/moderators?

by Mark Sapiro

On 3/11/21 4:58 AM, Duane Raymond wrote: > Hi, > > I'm configuring my new mailman3 lists and one option I wish to use is a membership listing (which list members can opt-in/out of via their preferences). The only problem is, via the web interface (Posterious / Hyperkitty) I can't find that listing when logged in as an ordinary member. Am I missing something or is this not built in yet? > > I have my test list setting under List Identity -> Members List Visibility set to "Only mailinglist members", but all I can find in terms of members is the side-listing of posters to the list/thread. > > (as usual before asking the question I explored a lot and searched the archives/documentation). Maybe you should also check issues. This is <https://gitlab.com/mailman/postorius/-/issues/369> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

Re: Hyperkitty performance problem

by Odhiambo Washington

On Fri, Nov 22, 2024 at 9:59 AM Tobias Diekershoff <tobiasd(a)fsfe.org> wrote: > Hey all, > > so far we could not find the reason behind the problem. However while > reviewing the installation process one one our team mentioned that he > read the installation instructions for Hyperkitty different then the > rest of the team. > > Are Mailman3/Postorius and Hyperkitty supposed to run in separated > databases, or are they supposed to use the same database? > > Thanks in advance for clarification! > Tobias > The official documentation specifies two DBs - one for Mailman Core and the other for Mailmanweb. As far as I know, there are no conflicts in the tables so you could use the same DB for both. -- 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]

1 year, 3 months

Re: Outgoing messages fro Mailman fails DMARC

by Henrik Rasmussen

> On 04/10/2018 06:53 PM, Mark Sapiro wrote: > > I'm not sure I understand what you are saying. Mailman's (both 2 and 3) > DMARC mitigations allow modifying the outgoing message in some or all > cases so the From: domain is the list's domain so the message won't be > dealt with by the recipient MTA according to the original From: domain's > DMARC policy. > > See <https://wiki.list.org/DEV/DMARC>;. Also, > <https://wiki.list.org/x/17891458> may be of interest. Thanks you for the links. According to https://wiki.list.org/DEV/DMARC the MM3 list setting "DMARC mitigation action" (which actually say "Replace From: with list address" in Postorius) should change the From: header. This doesn't seem to work if I don't also set "DMARC Mitigate unconditionally" to Yes, but does if I do. Where do I change defaults for all lists, instead of a per list change in settings/dmarc_mitigations ? Henrik Rasmussen

7 years, 10 months

Can't Start Mailman3 Core on Fresh Install

by Mail Person

Hi Everyone. I'm installing Mailman3 on a Ubunu 18.03 server using MySQL as the backend. After installing using the mailman3-full package and configuring it, I'm getting the following error when trying to start the mailman3 service: l 21 04:28:44 eps mailman3[81963]: packet.raise_for_error() Jul 21 04:28:44 eps mailman3[81963]: File "/usr/local/lib/python3.8/dist-packages/pymysql/protocol.py", line 221, in raise_for_error Jul 21 04:28:44 eps mailman3[81963]: err.raise_mysql_exception(self._data) Jul 21 04:28:44 eps mailman3[81963]: File "/usr/local/lib/python3.8/dist-packages/pymysql/err.py", line 143, in raise_mysql_exception Jul 21 04:28:44 eps mailman3[81963]: raise errorclass(errno, errval) Jul 21 04:28:44 eps mailman3[81963]: sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) (1045, "Access denied for user 'mailman3'@'127.0.0.1' (using password: YES)") Jul 21 04:28:44 eps mailman3[81963]: (Background on this error at: http://sqlalche.me/e/e3q8) I'm not sure why the access issue is happening. Mailman3-web is running fine and I can see the site at mailman3/postorius/lists (but it says Page Not Found).

3 years, 7 months

Re: Source Installation Assistance

by Brian Carpenter

The first thing is my server environment: Debian 10 Postgres for the database Nginx for the webserver I was able to create the virtual environment, install Mailman core and I have the Django installed and the project setup. I have Postorius and Hyperkitty setup. Everything is looking good. The problem I am having is when I am trying to migrate the data into the Postgres database. The migration process worked fine with SQLite but I decided to go with Postgres. Here is what I have in the settings.py for the database: DATABASES = { 'default': { 'ENGINE': 'django.db.backends.postgresql_psycopg2', 'NAME': '*************', 'USER': '**********', 'PASSWORD': '************', 'HOST': 'localhost', 'PORT': '', } When I run python manage.py migrate, I get the following exception: Applying hyperkitty.0007_allauth_20160808_1604...Traceback (most recent call last): File "/opt/mailman/mailman-web/mailman_venv/lib/python3.7/site-packages/django/db/backends/utils.py", line 82, in _execute return self.cursor.execute(sql) psycopg2.errors.InFailedSqlTransaction: current transaction is aborted, commands ignored until end of transaction block The above exception was the direct cause of the following exception: Traceback (most recent call last): File "manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/opt/mailman/mailman-web/mailman_venv/lib/python3.7/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line utility.execute() File "/opt/mailman/mailman-web/mailman_venv/lib/python3.7/site-packages/django/core/management/__init__.py", line 375, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/opt/mailman/mailman-web/mailman_venv/lib/python3.7/site-packages/django/core/management/base.py", line 323, in run_from_argv self.execute(*args, **cmd_options) File "/opt/mailman/mailman-web/mailman_venv/lib/python3.7/site-packages/django/core/management/base.py", line 364, in execute output = self.handle(*args, **options) File "/opt/mailman/mailman-web/mailman_venv/lib/python3.7/site-packages/django/core/management/base.py", line 83, in wrapped res = handle_func(*args, **kwargs) File "/opt/mailman/mailman-web/mailman_venv/lib/python3.7/site-packages/django/core/management/commands/migrate.py", line 234, in handle fake_initial=fake_initial, File "/opt/mailman/mailman-web/mailman_venv/lib/python3.7/site-packages/django/db/migrations/executor.py", line 117, in migrate state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial) File "/opt/mailman/mailman-web/mailman_venv/lib/python3.7/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial) File "/opt/mailman/mailman-web/mailman_venv/lib/python3.7/site-packages/django/db/migrations/executor.py", line 246, in apply_migration self.record_migration(migration) File "/opt/mailman/mailman-web/mailman_venv/lib/python3.7/site-packages/django/db/migrations/executor.py", line 261, in record_migration self.recorder.record_applied(migration.app_label, migration.name) File "/opt/mailman/mailman-web/mailman_venv/lib/python3.7/site-packages/django/db/migrations/recorder.py", line 82, in record_applied self.ensure_schema() File "/opt/mailman/mailman-web/mailman_venv/lib/python3.7/site-packages/django/db/migrations/recorder.py", line 62, in ensure_schema if self.has_table(): File "/opt/mailman/mailman-web/mailman_venv/lib/python3.7/site-packages/django/db/migrations/recorder.py", line 56, in has_table return self.Migration._meta.db_table in self.connection.introspection.table_names(self.connection.cursor()) File "/opt/mailman/mailman-web/mailman_venv/lib/python3.7/site-packages/django/db/backends/base/introspection.py", line 48, in table_names return get_names(cursor) File "/opt/mailman/mailman-web/mailman_venv/lib/python3.7/site-packages/django/db/backends/base/introspection.py", line 43, in get_names return sorted(ti.name for ti in self.get_table_list(cursor) File "/opt/mailman/mailman-web/mailman_venv/lib/python3.7/site-packages/django/db/backends/postgresql/introspection.py", line 52, in get_table_list """.format('c.relispartition' if self.connection.features.supports_table_partitions else 'FALSE')) File "/opt/mailman/mailman-web/mailman_venv/lib/python3.7/site-packages/django/db/backends/utils.py", line 99, in execute return super().execute(sql, params) File "/opt/mailman/mailman-web/mailman_venv/lib/python3.7/site-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/opt/mailman/mailman-web/mailman_venv/lib/python3.7/site-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers return executor(sql, params, many, context) File "/opt/mailman/mailman-web/mailman_venv/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/opt/mailman/mailman-web/mailman_venv/lib/python3.7/site-packages/django/db/utils.py", line 89, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/opt/mailman/mailman-web/mailman_venv/lib/python3.7/site-packages/django/db/backends/utils.py", line 82, in _execute return self.cursor.execute(sql) django.db.utils.InternalError: current transaction is aborted, commands ignored until end of transaction block So at this point I am stuck. Brian

6 years, 4 months

Change the default value for the General Archive Policy

by Markus Grandpré

Dear list, currently, when I create a new mailing list with MM3 the value for "Archive policy" is always set to "Public archives". I'd like to change the default value for "Archive policy" to "Do not archive this list". How can I do this? In Debian 12 I find in </usr/lib/python3/dist-packages/postorius/forms/list_forms.py>: mlist_properties = ['archivers'] archive_policy_choices = ( ('public', _('Public archives')), ('private', _('Private archives')), ('never', _('Do not archive this list')), ) archive_rendering_mode_choices = ( ('text', _('Plain text')), ('markdown', _('Markdown text')), ) archive_policy = forms.ChoiceField( choices=archive_policy_choices, widget=forms.RadioSelect, label=_('Archive policy'), help_text=_('Policy for archiving messages for this list'), ) but have no idea how to change the settings here. Your help is very appreciated. Best regards, Markus Grandpré -- Markus Grandpré Universität Konstanz Kommunikations-, Informations- und Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur Sachgebiet Diensteadministration Tel: ++49 7531 88 4342

8 months, 1 week

SOLVED (was: compress failed...)

by Guillermo Hernandez (Oldno7)

El 30/10/22 a las 12:22, Guillermo Hernandez (Oldno7) via Mailman-users escribió: > > El 28/10/22 a las 9:18, Guillermo Hernandez (Oldno7) via Mailman-users > escribió: >> >> El 27/10/22 a las 21:39, Mark Sapiro escribió: >>>> After that the compress part showed errors... but the postorius web >>>> maintenance was working well except for the CSRF error >>>> verification. I will trace the compress errors and will try to find >>>> the problem later. >>> >>> >>> Do you have `COMPRESS_ENABLED = True` in your settings? If that's >>> not the issue, it may be in the settings for COMPRESS_PRECOMPILERS >> >> While I'm tracing the problem out, this is the configuration I had >> working and the error it shows after upgrade: >> >> <------- snip of settings.py> >> >> # >> COMPRESS_PRECOMPILERS = ( >> ('text/less', 'lessc {infile} {outfile}'), >> ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), >> ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), >> ) >> # On a production setup, setting COMPRESS_OFFLINE to True will bring a >> # significant performance improvement, as CSS files will not need to be >> # recompiled on each requests. It means running an additional "compress" >> # management command after each code upgrade. >> # >> http://django-compressor.readthedocs.io/en/latest/usage/#offline-compression >> #### activo compresion 18/12/20 >> COMPRESS_OFFLINE = True >> ###COMPRESS_OFFLINE = False >> <---------- end snip> >> >> And below is the error it shows: >> >> /usr/local/mailman3 # su -m mailman3 -c "python3 manage.py compress" >> Traceback (most recent call last): >> File "/usr/local/mailman3/manage.py", line 10, in <module> >> execute_from_command_line(sys.argv) >> File >> "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", >> line 446, in execute_from_command_line >> utility.execute() >> File >> "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", >> line 440, in execute >> self.fetch_command(subcommand).run_from_argv(self.argv) >> File >> "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", >> line 279, in fetch_command >> klass = load_command_class(app_name, subcommand) >> File >> "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", >> line 49, in load_command_class >> return module.Command() >> File >> "/usr/local/lib/python3.9/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. >> >> > After searching around, I've got a hint of what can be happening. It > seems a variable has changed in Django 4.1 its nature from boolean to > a tuple > > https://github.com/painless-software/django-probes/issues/24 > > I've upgraded another server with mailman3 lists, with the same config > listed above, and it shows the same error in the "compress" part. I'm > not sure where to set the requires_system_checks variable as in one of > the comments of the link, and as it doesn't seems to break anything > more, I will wait for more info before trying to avoid it. I'm sure it > will have some repercusion on the performance, but I'll have to live > with it. > > > Thanks again for your supporting advices. I did a pip install --upgrade --force-reinstall Django==4.0.8 downgrading Django from 4.1 and now a su -m mailman3 -c "python3 manage.py compress" worked without pain. > >> >> >> >> >> -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

3 years, 4 months

Re: Link another address

by Quanah Gibson-Mount

--On Tuesday, May 19, 2020 1:13 AM +0000 Brian Carpenter <brian_carpenter(a)emwd.com> wrote: > I am thinking about incorporating the following Postorius/Django account > feature into Affinity: > > Other emails: (no other email) Link another address > > However I cannot think of a serious real-world need for this. What are > the developers' reasoning behind this? Was this feature highly demanded > by Mailman 3 users? Just trying to find out what I am missing here. Here's one use case: I've worked on an open source project for nearly 20 years. Over the course of those years, I've had a variety of different email addresses. The nice thing about being able to link all of them together under my single user ID is that I can find every email I've ever sent to the project lists, regardless of what my address was at the time. Regards, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

5 years, 9 months

Re: Error downloading CSV for 1,300 members

by Odhiambo Washington

An alternative is to just use the CLI to get the list. Afterall, all you need is the addresses, or no? On Thu, Feb 23, 2023, 21:46 Jose Bernal <jbernal.web.dev(a)gmail.com> wrote: > Any suggestions on troubleshooting downloading a modest-size CSV file for a > list with 1,300 members? Clicking "CSV Export" on smaller lists works > fine, but on this larger list I get this error in mailman-web.log: > > Thu Feb 23 10:03:32 2023 - uwsgi_response_write_body_do(): Broken pipe > [core/writer.c line 429] during GET /mailman3/postorius/lists/ > members.list.ocdla.org/csv_view/ (172.31.54.89) > OSError: write error > > > --------------------- > José Bernal > Web/Application Engineer > Cell 541-228-8481 > jbernal.web.dev(a)gmail.com > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to odhiambo(a)gmail.com >

3 years

Mailman-users search results for query "Postorius"