Search results for "Postorius" - Mailman-users

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, 5 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, 6 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, 5 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, 8 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, 7 months

Re: Mailman and Mailman-web databases

by Odhiambo Washington

On Wed, Apr 5, 2023 at 12:31 PM Andrew Hodgson <andrew(a)hodgson.io> wrote: > Hi. > > Just come out of a bit of a server reorg where I followed the new > instructions to get Mailman3 up and running with Mailman-web. > > Virtualenv Installation - Mailman Suite 3.3 documentation (list.org)< > https://docs.list.org/en/latest/install/virtualenv.html> > > In these instructions we are using 2 databases for the Mailman and Django > components. I guess it doesn't harm anything to have just one database for > both but wondered whether it was a good idea to split eventually? > Nice question. The thing is, Mailman Core doesn't know about the existence of any web interface (Postorius & Hyperkitty). I believe that is the reason why the databases are split in the documentation. Someone can decide NOT to install Postorius and Hyperkitty. If one decides to have everything centrally, then I see no harm in using the same database. I have sites using the same database for both, and others that are split. It's cosmetic, I think. I will let the experts have their say. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

3 years, 4 months

Assistance with mailman3

by ayen＠afilias.info

Hi all I'm pretty new to mailman but been trying to install mailman 3 and been running into issues, following the documentation at http://docs.mailman3.org/en/latest/prodsetup.html installed Python 3.6, nginx, ruby-sass then with pip installed whoosh mailman-hyperkitty postorius hyperkitty mailman tried to start mailman core, symlinked master and runner -> /usr/bin/ (otherwise it wouldn't run) mailman core starts but when I hit the api url I get this in the logs File "/usr/local/lib/python3.6/dist-packages/mailman-3.2.2-py3.6.egg/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/usr/local/lib/python3.6/dist-packages/mailman-3.2.2-py3.6.egg/mailman/rest/wsgiapp.py", line 218, in __call__ return super().__call__(environ, start_response) File "/usr/local/lib/python3.6/dist-packages/falcon/api.py", line 248, in __call__ responder, params, resource, req.uri_template = self._get_responder(req) File "/usr/local/lib/python3.6/dist-packages/falcon/api.py", line 664, in _get_responder route = self._router_search(path, req=req) TypeError: find() got an unexpected keyword argument 'req' Mar 13 10:54:44 2019 (17273) 127.0.0.1 - - "GET /3.1/ HTTP/1.1" 500 59 and on frontend "A server error occurred. Please contact the administrator." that leads to my gnu not working and throwing keyerrors for postorius. I'm using a clean install of ubuntu 18.04 but have also tried to install on centos 7 with no success. Are there any missing dependencies or steps that I've missed any assistance would be appreciated. Andy

7 years, 4 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

Re: Is it possible to add non-members in regex format in Mailman 3 ?

by Mark Sapiro

On 6/16/20 7:09 AM, Shashikanth Komandoor wrote: > > But in mailman 3, I am not allowed to add the non members in > the regex format. Of course it is allowing me to add individual mail ids > and give permissions. But I want to add a non-member which may be something > like the entire cisco.com domain on which I want to set the rule. You cannot add a non-member with a regexp email, but the legacy *_these_nonmembers list attributes still exist in Mailman core and accept regexps. These settings are exposed in Postorius 1.3.3+ under Settings -> Message Acceptance. With older Postorius, you ned to set these directly in core, e.g. with `mailman shell` as in $ 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 >>> m.accept_these_nonmembers [] >>> m.accept_these_nonmembers = ['^.*[.(a)]good\.domain$'] >>> m.accept_these_nonmembers ['^.*[.(a)]good\\.domain$'] >>> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

Re: integrating mm3 with postfix / lmtp

by Fabian A. Santiago

On October 25, 2017 9:13:20 PM EDT, Mark Sapiro <mark(a)msapiro.net> wrote: >On 10/25/2017 05:41 PM, Fabian A. Santiago wrote: >> >> No to the domains part and I think virtual alias maps is needed: >> >> mail postfix/trivial-rewrite[19445]: warning: do not list domain xxx >in BOTH virtual_mailbox_domains and relay_domains >> Oct 25 20:39:19 mail postfix/trivial-rewrite[19445]: warning: do not >list domain xxx in BOTH virtual_mailbox_domains and relay_domains >> Oct 25 20:39:19 mail postfix/submission/smtpd[19441]: NOQUEUE: >reject: RCPT from >pool-108-53-239-102.nwrknj.fios.verizon.net[108.53.239.102]: 550 5.1.1 ><test123@xxx>: Recipient address rejected: User unknown in virtual >mailbox table; from=<fsantiago@xxx> to=<test123@xxx> proto=ESMTP >helo=<[10.0.0.29]> > >(above slightly sanitized for return to the list) > >The issue here is your list domain cannot be a virtual_mailbox_domain >or >a virtual_alias_domain. > >I have the same issue on mail.python.org where we have both Mailman 2 >and Mailman 3 lists @python.org. and python.org is a >virtual_alias_domain. > >I have a group of MRs for a branch that implements "alias_domains" to >deal with this. > >Basically it works by creating another (virtual_alias_maps) >postfix_vmap >mapping to map list addresses @python.org to addresses @x.python.org. >Then the postfix_domains and postfix_lmtp maps have the x.python.org >domain and there is a patch to mailman/runners/lmtp.py to map the >x.python.org domain back to python.org. > >The various MRs are ><https://gitlab.com/mailman/mailman/merge_requests/202> for the core, ><https://gitlab.com/mailman/mailmanclient/merge_requests/18> for the >REST bindings used by Postorius and ><https://gitlab.com/mailman/postorius/merge_requests/186> to be able to >set an alias_domain via Postorius. > >That's not all implemented at mail.python.org. What's there is the >basic >Postfix config, a bash script the generate the new mappings from the >old >and a simple patch to mailman/runners/lmtp.py. > >So, the bottom line is it can be done and it's in process, but it won't >really be supported until Mailman 3.2. In the mean time, you just need >to have a separate domain for your lists that isn't a virtual_*_domain. Ok thanks. At least I have a clear answer now. Any ETA on 3.2 in mind yet? -- Thanks, Fabian S. OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

8 years, 9 months

Mailman-users search results for query "Postorius"