Search results for "Postorius" - Mailman-users

Re: spanish localization

by Victoriano Giralt

On Fri, 2021-02-12 at 09:04 +0100, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > 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. Actually, I was going to ask these same questions, because I dedicated some hours to get the Spanish translation nearly finished, it was kind of a "spiritual" need for me, being the person that seeded the efforts for Mailman i18n support back in the late '90s :-) :-) > 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. I got this very same error, and was also confused, as manage.py runs at the project level, not application level. > I'm lost. Do not feel bad, Guillermo, an old time pythonist with message translations experience, that uses i18n for some of his applications, is also dazzled and confused :-) Confused-with-translations-ly, Victoriano. -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

3 years, 9 months

Mailman3 is wrongly display name a list member

by Stephen J. Turnbull

Allan Hansen writes: > When I subscribe 'A' <a(a)foo.com>, Mailman3 changes it to 'B' > <a(a)foo.com>. If I recall correctly, this issue occurs because Subscription objects have no display name attribute, but User and Address objects do. First, the advice part: > What can I do to help this member? Unfortunately the mailman command line utility doesn't seem to allow changing the display name. The REST interface does, though. I think just starting Python 3 on the Mailman host as the Mailman user (we recommend "mailman" but Debian prefers "list", YMMV) and typing >>> from mailman.testing.documentation import dump_json >>> dump_json('http://localhost:8001/3.1/addresses/a@foo.com', ... method='PATCH', data={'display_name': 'A'}) should do what you want. Note the numbers "8001" (Mailman core's REST port) and "3.1" (the API version) may be different on your system, I'm assuming the default install of a recent Mailman release. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for information about accessing the REST API and https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for a few more details on the update process. On to the rants, if you care. > I went into Django and added the name 'B' to the subscriber's > account (the name was empty). > > I then unsubscribed <a(a)foo.com> from the lists and resubscribed 'A' > <a(a)foo.com>. > > The subscription again lists as 'B' <a(a)foo.com>. Does the user need to have different display names for different addresses? (I don't think it's possible to have different display names for the same address on different lists because there's no display name at all for Subscription objects.) If the answer is "no", the correct thing to do is to set the desired display name on the user's account. If the answer is "yes", there doesn't seem to be any way to do this with current Postorius/HyperKitty. Postorius doesn't expose the display name anywhere that I can see, and HyperKitty only manages the account's "real name". > This brings up a previous discussion of display names on this list, > but I have not been able to find any solution to the need to change > Mailman3's display names for a subscriber. It is beyond weird that > unsubscribing, setting the account display name and resubscribing > the member fishes back up the old and wrong display name. Unless you explained what you did incorrectly this is not weird, it's the expected result. You set "B" in the account, that's what's going to show up as the display name. It is not obvious that a new subscription should change an existing display name for a user or an address, given that there is no way to set a list-specific display name. It could go either way, and for the user I would definitely not change it, for the address I tend to agree that a new subscription should not change the address's display name. I agree that it's weird that neither Postorius nor HyperKitty seems to expose a way to set Address display names, though. If you want a new subscription to set the display name for an address, the workaround would be to delete the address, then reconfirm the address, and resubscribe the address to all the relevant lists.

2 years, 10 months

Re: mail host choices when creating a new list

by Andrew Hodder

Abhilash, I'm not sure what you're referring to, there's no "web hosts" in the admin panel and I already added the "mail hosts" there (of the four added, only the first one shows up in the postorius drop down). Sincerely, Andrew Hodder Systems Administrator Support Operations, Afilias E-mail: drew(a)afilias.info Phone: +1 416.673.4164 Fax: +1 416.646.1541 On Tue, Oct 24, 2017 at 3:08 PM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > Hi Andrew, > > On Tue, Oct 24, 2017, at 11:58 AM, Andrew Hodder wrote: > > Hi! > > > > So, I'm trying to create a new list and pick one of the other mail > > domains > > we have configured (from the django admin panel), yet in the "Create New > > List" page in postorius, I see only a single option (the first domain > > we'd > > added/set as the default) in the drop-down under "Mail Host". Am I > > missing > > somewhere else I need to add alternative mail domains to? Thanks in > > advance! > > Yes, you can add new 'Web Hosts' from the Django's Admin console > (admin/django_mailman3/maildomain/). Note that you need to be a > superuser to do this. > > > -- > Abhilash Raj > maxking(a)asynchronous.in >

7 years, 1 month

Re: [Django] ERROR (EXTERNAL IP): Service Unavailable

by Mark Sapiro

On 2/22/21 5:47 PM, dancab(a)caltech.edu wrote: > I've imported a list from Mailman2 and had the owner send a message for testing purposes. > > His message are moderated per the list configuration. The message is delivered to Mailman3 and shows that it's being held. > > However if we attempt to view the message in Postorius web UI then an error is thrown. Can you see the message in the held messages view and only get the error when you click the message, or can you not see the held messages view at all? Is it only this list that has an issue? Can you visit other pages for this list? > In the web interface the error is simply "Mailman REST API not available. Please start Mailman core." > > But Mailman Core is running and we can do other functions just fine. Our superuser account receives a much more detailed message with the subject below. > > [Django] ERROR (EXTERNAL IP): Service Unavailable: /postorius/lists/cpa-announcement.caltech.edu/held_messages > > Does "Service Unavailable" mean I'm missing something in the configuration? Possibly, but I don't think so. What is the Traceback from the message Django sends to the server admin? -- 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: Apache+mod_wsgi issue

by Odhiambo Washington

On Sat, Dec 24, 2022 at 9:40 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/24/22 00:00, Odhiambo Washington wrote: > > > > These are my files: > > 1. urls.py > > <CUT > > > from django.conf.urls import include > > from django.urls import re_path > > from django.contrib import admin > > from django.urls import reverse_lazy > > from django.views.generic import RedirectView > > > > urlpatterns = [ > > re_path(r'^$', RedirectView.as_view( > > url=reverse_lazy('list_index'), > > permanent=True)), > > re_path(r'^postorius/', include('postorius.urls')), > > re_path(r'^hyperkitty/', include('hyperkitty.urls')), > > re_path(r'', include('django_mailman3.urls')), > > re_path(r'^accounts/', include('allauth.urls')), > > # Django admin > > re_path(r'^admin/', admin.site.urls), > > re_path(r'^mailman3/', include('postorius.urls')), > > re_path(r'^archives/', include('hyperkitty.urls')), > > ] > > </CUT> > > > You don't need all of those. ^postorius/ and ^mailman3/ are two > different ways to access Postorius, and ^hyperkitty/ and ^archives/ are > two different ways to access HypereKitty. You only need one of each, but > having both is OK. > That urls.py was picked from https://wiki.list.org/DOC/Mailman%203%20installation%20experience. Maybe that page needs some edits/revision now? > 2. apache.conf > > <CUT> > > ... > > Alias /static "/opt/mailman/mm/static" > > <Directory "/opt/mailman/mm/static"> > > Require all granted > > </Directory> > > # WSGIScriptAlias /mailman3 /opt/mailman/mm/wsgi.py > > # WSGIScriptAlias /accounts /opt/mailman/mm/wsgi.py > > # WSGIScriptAlias /admin /opt/mailman/mm/wsgi.py > > # WSGIScriptAlias /archives /opt/mailman/mm/wsgi.py > > # WSGIScriptAlias /user-profile /opt/mailman/mm/wsgi.py > > # WSGIScriptAlias /hyperkitty /opt/mailman/mm/wsgi.py > > # WSGIScriptAlias /postorius /opt/mailman/mm/wsgi.py > > WSGIScriptAlias / /opt/mailman/mm/wsgi.py > > > This will send every http request to mod_wsgi except for requests to > /static. This is OK if there are no other web sites on this server and > the only http requests are for Django related things. > This is just a virtual host. There are other websites on the server. ... > > I have tested with creating all those commented out aliases and that > ended > > up still giving me /mailman3/mailman3/* which I did not > > like, although everything appeared to work. > > I then ended up with only "WSGIScriptAlias / /opt/mailman/mm/wsgi.py" > > and now when I type https://mm3-lists.kictanet.or.ke I end > > up at https://mm3-lists.kictanet.or.ke/mailman3/lists/. Of course > something > > has appended "/mailman3" > > So this has resulted in all URLs having /mailman3/ appended, except for > the > > /archives link. > > > How about https://mm3-lists.kictanet.or.ke/user_profile/ ? > I have uncommented the line "WSGIScriptAlias /user-profile /opt/mailman/mm/wsgi.py", I don't see any definition for it in urls.py as well. Perhaps that's the issue? When I uncomment /user-profile, I end up with an ugly URL: https://mm3-lists.kictanet.or.ke/user-profile/user-profile/ So instead of aliasing the /user-profile, I have decided to add another definition to urls.py: re_path(r'^user-profile/', include('allauth.urls')), Which I think gives me a cleaner URL: https://mm3-lists.kictanet.or.ke/user-profile/login/?next=/user-profile/ I also had to alias /accounts, which then brings me to: https://mm3-lists.kictanet.or.ke/accounts/mailman3/lists/ - which I believe is fine because one gets the option to either login or signup. And I think that "/account" and "/user-profile" are synonymous. > Now my question is about what could be adding the /mailman3. Is it > possible > > that I installed something out of the ordinary? > > > It's a mod_wsgi thing. I haven't used mod_wsgi for Mailman for some time > (I now use gunicorn on all the sites I manage), but when I did I think I > had > WSGIScriptAlias /mm3 /opt/mailman/mm/wsgi.py > > and all the URLs were like https://example.com/mm3/mailman3/..., > https://example.com/mm3/archives/..., etc. > I already had gunicorn working too, but I just need to also figure out this mod_wsgi. I will stop bothering about the /mailman3 being appended, as long as it serves the required purpose. Thank you for all the help. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

1 year, 11 months

Re: List description as sender

by Henrik Rasmussen

It is the description in the Settings -> List Identity -> Description that is used in the list overview https://list.example.com/postorius/lists/ and also as the "From:" in the mails sent to the subscribers. I try to keep the descriptions as short as possible, and I don't consider "Newsletter to the members of the Anthropology Society" a long message, when displayed in https://list.example.com/postorius/lists/, but when the description is displayed as From: in mails, I agree it is a long description. On lists.mailman3.org, the description "General list for Mailman 3 users and others interested in Mailman 3" is also short, but when used as From: it is fairly long. -----Oprindelig meddelelse----- From: Mailman-users is an infrequent newsletter sent to list administrators <mailman-users(a)lists.example.com> Sent: 14. september 2018 13:20 To: mailman-users(a)lists.example.com Subject: Test 201809141319 [cid:image001.png@01D44E6C.A57045A0] -- Henrik Rasmussen <her(a)adm.ku.dk<mailto:her@adm.ku.dk>> University of Copenhagen, Danmark -----Oprindelig meddelelse----- Fra: Mark Sapiro <mark(a)msapiro.net> Sendt: 14. september 2018 17:36 Til: mailman-users(a)mailman3.org Emne: [MM3-users] Re: List description as sender On 09/14/2018 05:35 AM, Henrik Rasmussen wrote: > When receiving a mail from Mailman 3, the From: User name is the description of the list, like From: Long desription of the list for all members of certain project <project(a)lists.example.com<mailto:project@lists.example.com>>. > > Starting to get old, I recall something about a discussion we once had on http://mail.python.org/pipermail/mailman-users/, but I don't recall the reason for this and I can't find the discussion, so it might be something I dreamed. Specifically what messages are you talking about? The only case I see offhand where the From: is as you describe is in posts from an anonymous list. In any case, the list description is described in Postorius as "This description is used when the mailing list is listed with other mailing lists, or in headers, and so forth. It should be as succinct as you can get it, while still identifying what the list is." I.e., it shouldn't be a long description. -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@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<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

6 years, 2 months

Re: installing a new instance of mm3

by Christian Stalberg

mailman.log is showing this: ERROR 2021-10-18 22:19:12,385 616 django.security.DisallowedHost Invalid HTTP_HOST header: 'subdomain.domain.tld'. You may need to add 'subdomain.domain.tld' to ALLOWED_HOSTS. ERROR 2021-10-18 23:01:15,318 616 django.security.DisallowedHost Invalid HTTP_HOST header: '192.168.0.1'. You may need to add '192.168.0.1' to ALLOWED_HOSTS. Where do those entries go? -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, October 22, 2021 11:44 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: installing a new instance of mm3 On 10/22/21 6:37 AM, Christian Stalberg via Mailman-users wrote: > Is this document that Brian Carpenter wrote still valid? > > https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 As Steve said, it should be. > Brian installed my instance. Now its broken. My lists are down. I'm > getting nowhere with diagnostics and troubleshooting (which was easier > with mailman 2). What's broken? Postorius, Hyperkitty, mail delivery, all of them? Do you find any clues in the logs at /opt/mailman/mm/var/logs/? Particularly mailman.log for core and mailmansuite.log for Postorius and Hyperkitty. We will try to help if we have information to help identify the problem. -- 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/

3 years, 1 month

more about spanish translations

by Guillermo Hernandez (Oldno7)

I've just made a test creating a user in postorius to change an address that already has a suscription (from mailman 2.1). It's a test address with the digest enabled to be aware from any problem in the digest sending messages (e.g. I had to change all digest addresses to mime whe I did the migration from 2.1) The fact is that I cannot find from which template or Weblate term chains it could be from, and the address confirmation email is a language mix in spanish and english. I copy it down. I would like to translate it all, but as said, I cannot find where to do it. I wonder if it's comes from another package as allauth or something like this. Here is the mail: Subject: =?utf-8?q?=5Bescepticos=2Ees=5D_Por_favor_confirmar_direcci=C3=B3n_de_correo?= =?utf-8?q?_electr=C3=B3nico?= From: postorius(a)XXXXXXXXXXX.es To: XXXXXXXX(a)gmail.com Date: Fri, 19 Feb 2021 10:26:26 -0000 Message-ID: <161373038620.5080.16387108004007982309(a)XXXXXXX.es> X-Spam-Status: No, score=-1.0 required=8.0 tests=ALL_TRUSTED=-1,URIBL_BLOCKED=0.001 <dns:XXXXXXXXX.es> [172.67.131.28, 104.21.3.190] <dns:XXXXXXXXXX.es?type=MX> [0 XXXXXXXXXXXX.es.] autolearn=unavailable autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on XXXXXXXXXXX.es Hello from XXXXXXXXXXX.es! You're receiving this e-mail because user XXXXXXXXXX(a)gmail.com has given your e-mail address to register an account on XXXXXXXXXXXXXXX.es. To confirm this is correct, go to https://XXXXXXXXXXX.es/mailman3/accounts/confirm-email/MTM:1lD2zR:3GpALYKI1… Muchas gracias por usar XXXXXXXXXX.es! XXXXXXXXXXX.es

3 years, 9 months

Re: django-mailman3 update causing errors

by Simon Hanna

On 05/01/2018 10:35 PM, Darren Smith wrote: > Hello, > > In attempting to update our mailman3/postorius/hyperkitty installation, I > have run into an error after upgrading the django-mailman3 project. > > Our webui is being run through supervisord. The command being run is this: > > /<path>/mailman3/conda/envs/mailman3_ext/bin/waitress-serve > --listen=localhost:8787 webui.wsgi:application > > The error I'm getting is pretty long, but most of it appears to be usage > instructions. Here are what I believe to be the pertinent parts: > > > > Error: Bad module 'webui.wsgi' > > Usage: > > waitress-serve [OPTS] MODULE:OBJECT > <lots and lots of usage instructions> > > There was an exception (ImportError) importing your module. > > It had these arguments: > 1. No module named error > > > > Any thoughts on why updating django-mailman3 would cause this? I'm not sure what exactly you upgraded to what version, so it's only a guess.. Did you by chance upgrade django? Using outdated middleware settings caused similar errors. Can you check that you are adhering to the settings that are used in the example_projects of Postorius and Hyperkitty? Try to start mailman using the builtin server (./manage.py runserver) and see what that tells you. Also please mention what versions you are using and show us your settings.py (hide passwords and stuff...)

6 years, 6 months

Re: "Cannot connect to SMTP server localhost on port 25"

by Mark Sapiro

On 9/22/19 2:11 AM, Manos Pitsidianakis wrote: > > mailman3 tries to get the template I've set via the mailman suite > interface but it assumes it is hosted locally: > 'http://localhost:8000/mailman3/api/templates/list/meli-announce.meli.delive…' > In my setup, they are separate machines. I can't find any way to change > this in the configuration. Also, can't the same template be loaded from > the master's localhost:8001 api? See <https://mailman.readthedocs.io/en/latest/build/lib/mailman/rest/docs/templa…>. There are other ways to set the URI for a template which will work in your case. When you set a template via Postorius, it sets the URI for that template to point to itself to return what it set. In your case, this URI points to localhost which is Postorius' localhost, but it is set in core and core's localhost is a different machine so it doesn't work. You could file an issue at <https://gitlab.com/mailman/postorius/issues> about this. > Haven't fiddled with python for some time, why is this exception catched > by "except socket.error"? Is it a subclass of > requests.exceptions.ConnectionError? The other way around. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

Mailman-users search results for query "Postorius"