Search results for "Postorius" - Mailman-users

Re: Member Issue Discovered

by Brian Carpenter

On 10/29/20 11:26 AM, Mark Sapiro wrote: > On 10/29/20 5:17 AM, Brian Carpenter wrote: >> On 10/29/20 4:27 AM, Alex Schuilenburg via Mailman-users wrote: >>> On 29/10/2020 01:57, Brian Carpenter wrote: >>>> With Mailman 3, every list owner has the ability to remove a reply in >>>> a thread, a complete thread, and even the entire archives. That is a >>>> welcome difference from MM2 in my opinion. >>> A very welcome difference, only I don't see this option in the web >>> interface of my debian 3.2.1 installation. Is this a shell only >>> option, 3.3 feature or configuration option I have missed? >> It is not a shell option. It can be done via Hyperkitty but I am not >> sure when that feature showed up. > > Actually, with current HyperKitty, only site admins can remove messages > or threads or the archive. The ability for list owners to do it is > <https://gitlab.com/mailman/hyperkitty/-/issues/261>. Thanks Mark. To clarify more, we have this ability for List owners with our own custom admin interface (Affinity). I thought Postorius had that. When I checked out Postorius, I was indeed logged in as server owner. Sorry for the incorrect info. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 10 months

Re: Error -- postorius Un-handled exception

by Odhiambo Washington

On Sun, Jan 28, 2024 at 11:26 AM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Odhiambo Washington writes: > > > The issue you're dealing with in that case is this change in > > PostgreSQL-15 discussed in this blog: > > > https://www.cybertec-postgresql.com/en/error-permission-denied-schema-publi… > > Thank you for the reference! > > If you have a Mailman-only host, with a Mailman-only PostgreSQL, or > The Cabal of equally responsible maintainers are the only people who > work on the Postgres cluster, the two approaches are basically > equivalent. > > My take is that the default "right thing" is to transfer ownership of > the 'mailman' database to the 'mailman' user, and use "GRANT ALL ON > SCHEMA public TO fred" in the case that you don't want to give "sudo > mailman" to Fred. > > Rationale: I believe there are a number of things that the 'postgres' > user can do that other users cannot, and you probably don't want > random contractors or new volunteers to have those privileges. On the > principlee that 'postgres' should only do those things that only > 'postgres' can do, you want to make the 'mailman' user the owner of > the 'mailman' database (and 'mailmanweb' too if you go that route). > Then if you have a user 'fred' who may be working on both mailman and > non-mailman databases in a session, then instead of giving sudo > mailman to Fred, 'mailman' can grant all on schema public in mailman > to 'fred'. > > It's a really fine difference, and probably will matter to almost > nobody running Mailman 3. I do think > > user 'mailman' owns the 'mailman' database > > is conceptually simpler than > > user 'postgres owns the 'mailman' database and 'mailman' has ALL > privilege on the PUBLIC schema > > Right? > Right! That makes more sense. -- 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]

2 years, 7 months

Re: spanish localization

by Guillermo Hernandez (Oldno7)

On 11/2/21 20:15, Mark Sapiro wrote: > On 2/11/21 3:47 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> I contributed in january to translate to spanish all the items left in >> Mailman Core, Django-mailman, HyperKitty and Postorius via Weblate. I >> thought they will be used in the next upgrade, but I cannot see any >> improvement and there are many words untranslated. > > The Spanish translations for Mailman core and HyperKitty are currently > completely up to date with weblate. django-mailman3 differs in one > string that was translated on Feb 10 and hasn't yet been merged. > Postorius also differs in a few places from the Feb 10 version that > hasn't yet been merged. Ok. Thanks for checking it. I put my little contribution in Weblate and I like that it could be used by anyone. > Other than that, the translations should be good. > > >> Is there any way to upgrade the .po files in order to get the last >> translation? > > For the web UI you need to run the django management `compilemessages` > command. I tried to run this using the same command as I did for the "collectstatic" (that solved all my previous problems for the upgrade) and "migrate" runs but it shows me an error: su -m mailman3 -c "python3 manage.py compilemessages" CommandError: This script should be run from the Django Git checkout or your project or app tree, or with the settings module specified. if I try with --settings param (for I missunderstood the error message) it shows the same: su -m mailman3 -c "python3 manage.py compilemessages --settings settings" CommandError: This script should be run from the Django Git checkout or your project or app tree, or with the settings module specified. I tried to find any doc regarding the use of the "compilemessages" command but I couldn't As far as I can see (I runned it with -h parm) this had to be related to the main python module, but I cannot understand why the pip upgrade did not do the job. I'm lost. Can you, please, point me in the right direction? > For Mailman core you need to run > ``` > cd mailman/messages/es/LC_MESSAGES > msgfmt -o mailman.mo mailman.po > ``` > to compile the mailman.po file for gettext. >

5 years, 7 months

Re: Finding a user to delete them

by Stephen J. Turnbull

Brian Carpenter writes: > I do think List Admins would want an interface to help "manage" a > user account on behalf of a user then what is currently available > in Postorius. Oh, no question about that whatsoever. I'm quite surprised that this facility isn't present yet. (I rarely make mistakes in mass subscribe and the defaults work fine for my subscribers -- or they make their own changes -- so I can't recall ever encountering this need.) I wonder if in Mailman 3 where user profiles exist and are clearly *not* subject to control by *list* admins in the same way that subscriptions are, and in this day of GDPR etc if maybe we need to restrict admin access to various user properties. This sounds like a rather difficult design problem. > I don't see this functionality built into Mailman 3 nowhere near > the extent that Mailman 2 has. Web interfaces are supposed :-( to be easy enough for Great-Grandma to use, so I imagine the designers didn't think much admin intervention would be needed. > My approach with Affinity is definite leaning very heavy on the > needs of list admins atm. Perhaps that's a good division of responsibility between Postorius and Affinity dev processes. Something to think about. Steve

6 years, 6 months

Re: Upgrading mailman 3 venv installation

by Mark Sapiro

On 9/29/21 10:52 AM, Morris Jones wrote: > > In my virtual environment, I ran `pip list -o` and got a significant > list. I noticed that all of the mailman packages seemed to be "Type > sdist" and the framework packages "Type wheel". (Dunno what "Type" means > in this context.) Type is the package type. sdist is a source distribution. wheel is a form of binary distribution. Older forms are egg and bdist. > So I tried `pip list -o | grep sdist` and got a smaller list: > > (venv) mailman@mail:~$ pip list -o | grep sdist > atpublic 2.1.1 2.3 sdist > django-allauth 0.43.0 0.45.0 sdist > django-mailman3 1.3.4 1.3.7 sdist > flufl.i18n 3.1.3 3.2 sdist > flufl.lock 5.0.3 6.0 sdist > HyperKitty 1.3.3 1.3.4 sdist > lazr.config 2.2.2 2.2.3 sdist > mailman 3.3.2 3.3.5 sdist > mailmanclient 3.3.1 3.3.3 sdist > mysqlclient 2.0.1 2.0.3 sdist > postorius 1.3.3 1.3.6 sdist > > Is this a reasonable list of the packages that I should update? Several of those are dependencies. The packages you should upgrade are mailman, postorius, hyperkitty, django-mailman3 and mailmanclient. Dependencies will be upgraded as required. If a dependency is not upgraded, the older version should work. -- 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: Outgoing messages fro Mailman fails DMARC

by Mark Sapiro

On 04/19/2018 03:22 AM, Henrik Rasmussen wrote: > > 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. If DMARC Mitigate unconditionally is No, DMARC mitigation action will only be applied if the original From: domain publishes a DMARC policy of quarantine or reject. If the action is not being applied in this case, there is some issue in looking up the DMARC policy for the domain. Possibly, dnspython is not available or there is some other issue with this. In any case, errors should be logged in Mailman's log. > Where do I change defaults for all lists, instead of a per list change in settings/dmarc_mitigations ? You need to do this with list styles. See <http://mailman.readthedocs.io/en/latest/src/mailman/styles/docs/styles.html>. At present, Postorius doesn't allow specifying a style when creating a list, so you may need to modify mailman/src/mailman/styles/base.py. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 5 months

Re: Mailman3-web/Postorius behind Lighttpd

by Mark Sapiro

On 2/16/22 10:00, Élodie BOSSIER via Mailman-users wrote: > > I'm using Mailman 3.3.3 (Tom Sawyer) on Debian Bullseye 11.2 from > packages : When you install Debian packages, your primary support resource is Debian. ... > I can access from localhost to http://127.0.0.1:8000/ which move me > correctly to http://127.0.0.1:8000/postorius/lists/ and all seem to be > correct. > > But 127.0.0.1:8000 listen only in localhost : > #netstat -tanpu | grep 8000 > tcp 0 0 127.0.0.1:8000 0.0.0.0:* LISTEN > 626175/python3 Which is as it should be. > So I try to use my lighttpd as proxy as recommanded with this config : > > >> scgi.protocol = "uwsgi" >> scgi.server = ( >> "/" => (( "host" => "127.0.0.1", "port" => 8000, "check-local" => >> "disable" )), >> ) > > but it's return me a "502 Bad Gateway". I don't know anything about lighttpd, but the fact that you can access http://127.0.0.1:8000/ from localhost and that seems to work suggests that you shouldn't be using uwsgi protocol, but just a straight http proxy. See https://redmine.lighttpd.net/projects/lighttpd/wiki/HowToPythonWSGI#lighttp… and https://redmine.lighttpd.net/projects/lighttpd/wiki/Docs_ModProxy -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

Internal Server Error, Need 2 values to unpack in for loop; got 1

by Elias Rudberg

Hello! I am using mailman3 (version 3.3.8) and it mostly works fine, but sometimes (usually several times every day) the error below appears. Any suggestions for what could be done about this? Should it be considered a bug in Django, so not a mailman3 problem, or does it indicate something wrong with mailman3 itself? Best regards, Elias Here is what the error message looks like: ------------------------------------------- [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/postorius/lists/ Internal Server Error: /mailman3/postorius/lists/ ValueError at /postorius/lists/ Need 2 values to unpack in for loop; got 1. [...] Django Version: 3.2.19 [...] Python Version: 3.11.2 [...] Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 47, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/postorius/views/list.py", line 1145, in list_index return render( File "/usr/lib/python3/dist-packages/django/shortcuts.py", line 19, in render content = loader.render_to_string(template_name, context, request, using=using) File "/usr/lib/python3/dist-packages/django/template/loader.py", line 62, in render_to_string return template.render(context, request) File "/usr/lib/python3/dist-packages/django/template/backends/django.py", line 61, in render return self.template.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 170, in render return self._render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 162, in _render return self.nodelist.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 938, in render bit = node.render_annotated(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 905, in render_annotated return self.render(context) File "/usr/lib/python3/dist-packages/django/template/loader_tags.py", line 150, in render return compiled_parent._render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 162, in _render return self.nodelist.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 938, in render bit = node.render_annotated(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 905, in render_annotated return self.render(context) File "/usr/lib/python3/dist-packages/django/template/loader_tags.py", line 62, in render result = block.nodelist.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 938, in render bit = node.render_annotated(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 905, in render_annotated return self.render(context) File "/usr/lib/python3/dist-packages/django/template/defaulttags.py", line 315, in render return nodelist.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 938, in render bit = node.render_annotated(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 905, in render_annotated return self.render(context) File "/usr/lib/python3/dist-packages/django/template/defaulttags.py", line 315, in render return nodelist.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 938, in render bit = node.render_annotated(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 905, in render_annotated return self.render(context) File "/usr/lib/python3/dist-packages/django/template/library.py", line 234, in render return t.render(new_context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 172, in render return self._render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 162, in _render return self.nodelist.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 938, in render bit = node.render_annotated(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 905, in render_annotated return self.render(context) File "/usr/lib/python3/dist-packages/django/template/defaulttags.py", line 203, in render raise ValueError( Exception Type: ValueError at /postorius/lists/ Exception Value: Need 2 values to unpack in for loop; got 1. Request information: USER: AnonymousUser [...] -------------------------------------------

2 years, 2 months

Re: Weird startup problem after upgrade

by Mark Sapiro

On 12/2/22 08:21, Odhiambo Washington wrote: > I am facing an odd situation in which MM3 doesn't start successfully on > reboot, but I can start it manually. > This is a venv install. > This started after I did an upgrade (pip install --upgrade mailman > postorius hyperkitty mailman-hyperkitty) followed by the requisite > collectstatic|compress|compilemessages|migrate > post-update commands. Was the venv activated when you ran pip? You should also include django-mailman3 and mailmanclient in the packages to be upgraded although they are dependencies and "should" upgrade anyway. Also, at least one person has noted that --force-reinstall was required to get all dependencies upgraded <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > Secondly, it appears that the upgrade did NOT change the versions for the > upgraded components - postorius=1.3.6, hyperkitty=1.3.5, > Mailman Core Version=3.3.5. I was expecting the version to all bump up to > the latest. What does `pip freeze` in the venv show for versions? > Thanks in advance for any insights into what could be causing this. How do you start it manually? `mailman start` or `systemctl start mailman3`? What's the content of /etc/systemd/system/mailman3.service? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

Re: Extracting mailing list users

by Mark Sapiro

On 1/2/23 07:06, Jan Eden via Mailman-users wrote: > On 2023-01-02 14:36, Eggert Ehmke via Mailman-users wrote: > >> Thank you, that worked! Now all my addresses are clean. >> >> Still, don't you think this should be possible via Postorius, or by some mailman cli command, like >> mailman rename_member <old> <new> Yes, it should be possible to change the display name for an address via Postorius. See https://gitlab.com/mailman/postorius/-/issues/451. >> It happened I had still the patched cli_members.py where I had both the old and new line active: >> print(formataddr((address.display_name, address.original_email)), file=outfp) >> print(f'{address.display_name} <{address.original_email}>', file=outfp) >> The first (old) line still produces the output with utf-8 codes. Is this to be expected? > > I would assume the original line outputs the QP-escaped names, to be > used in an email header. Yes. The original `formataddr((address.display_name, address.original_email))` creates the format `display name <email>` suitable for use in an email header. Thus, if the display name contains non-ascii, it is RFC 2047 encoded. The encoding may be quoted-printable or base64 depending on which is shorter. -- 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

Mailman-users search results for query "Postorius"