Search results for "Postorius" - Mailman-users

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

5 years, 5 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...)

8 years, 3 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

6 years, 10 months

Re: Emergency moderation and clearing out a lot of held messages

by Caballero, Danny (Dan)

Thanks for some clarification. I cleared out 2800 held messages via Python shell "mailman -l" option and it took about 28 hours. Anything done via Mailman shell is a connection from Mailman core to the database, correct? Although I can't replicate that many messages via Postorius/DJango, I do see similar slowness there as well at a message per minute or more of processing. I recreated the above Mailman shell clean up via Docker container running MariaDB and noticed similar processing time for discarding held messages. That leads me to conclude that the issue isn't network related or specific to AWS RDS. I'm open to testing and switching over to Postgres if that is the straightforward solution. ---- Dan Caballero Systems Administrator Academic Computing Solutions IMSS - Caltech https://imss.caltech.edu ________________________________ From: Stephen J. Turnbull <stephenjturnbull(a)gmail.com> Sent: Friday, November 11, 2022 10:23 AM To: Caballero, Danny (Dan) <dancab(a)caltech.edu> Cc: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Emergency moderation and clearing out a lot of held messages Caballero, Danny (Dan) writes: > I don't understand. We have a single database configured for > everything. I don't recall reading anything in the set-up > documentation about using more than 1 database for Mailman3. I was trying to help localize the database request to one of the three major components: core, Postorius, HyperKitty. If you use the two- database scheme documented here: https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… knowing that database would at least identify whether the slowness is associated with core or with the web apps. The excruciating details: Conceptually, there are three separate databases: the one used by Mailman core to manage everything but authentication and archives, the one used by Django to manage authentication for HyperKitty and Postorius, and the one used by HyperKitty to manage archives. They don't share tables, and there are no name collisions for the tables so it doesn't really matter how the backend handles them. The two database configuration is not really a recommendation. I suppose the practice derives from an abundance of caution, as there are concepts like "User" that must be implemented in somewhat different ways across components (core doesn't authenticate users, while Postorius's primary function is authentication of users). I myself would worry that there might be name collisions among tables, which would cause mayhem, but that's probably excessive.

3 years, 8 months

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

by Ken Alker

--On Monday, June 26, 2023 8:24 AM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/26/23 12:01 AM, Ken Alker wrote: >> When I view a list via Postorius the "Held Messages" menu item has an >> inverse-red-"2" next to it, as if there are two held messages. There >> are, in fact, no messages in "/opt/mailman/mm/var/queue/*" (assuming the >> held messages should be in "pipeline" subdirectory). When I click on >> "Held Messages" I get "Something went wrong" followed by "HTTP Error >> 500: {"title": "500 Internal Server Error"}". How do I fix this? > > The held messages are not in any queue. They are stored in Mailman's > var/messages/ hierarchy. They can be examined with `mailman qfile` Is the var/messages hierarchy also where all the archived emails are stored for future viewing via the web interface? > 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. 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)? 2) Is the "commit" even necessary (I saw it in someone else's script in the thread)? 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)? 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. Thanks for the guidance! Ken

3 years, 1 month

Re: Fresh installation mailman3-suite via "pipx" - any experiences yet?

by Stephen J. Turnbull

Mark Sapiro writes: > > On Thu, Jan 25, 2024 at 4:43 PM Wikinaut <mail(a)tgries.de> wrote: > > > >> I recently found the "pipx" wrapper very useful and wanted to > >> ask you if this could be facilitate the fresh installation of > >> the mailman3-suite. Has anyone in the list already experiences > >> installing mailman and mailmanweg through "pipx"? > pipx apparently does create virtual environments. See > https://pipx.pypa.io/stable/comparisons/ > > The thing there that concerns me is "pipx replaces a subset of > pip's functionality; it lets you install cli applications but NOT > libraries that you import in your code." > > What does this say about the multiple dependencies that we install. I'm pretty sure it will install dependencies. I think (everything I say below is based on reading the README.md from pipx's pypa.io repo, so caveat installer) that the complexity that will arise is that (for example) a naive approach like $ pipx install mailman $ pipx install mailmanweb $ pipx install postorius $ pipx install hyperkitty will create 4 separate venvs with 3 copies of mailmanclient, 3 copies of django-mailman3, and two copies of Django. Besides the space waste, there's also the small problem that mailmanweb won't have copies of postorius and hyperkitty in its venv. :-þ pipx has an "inject" command that allows adding other packages to a venv, but I think this means that pipx has no great advantage over the standard way of installing mailman into a venv. pipx also installs stuff into the user's $HOME, specifically into ~/.local/share/pipx/venvs which I think will be kind of annoying if you need to dig into package resources. (I expect that you will still install configs into /etc/mailman3 and various data into /var/lib/mailman3/var or /opt/mailman3 or whatever without a problem.) This would only be an issue for heavy-duty customizers. This can probably be customized. One of the big advantages pipx touts is "look ma, no sudo". That's not really an advantage for system daemons, though. So bottom line is you can do it, but you'll need to study up on pipx arcana, because Mailman is a bunch of daemon it buys you very little, and the result won't look like any Mailman installation you've seen described on mailman-users or StackExchange. Steve

2 years, 6 months

Deactivate list without deleting it?

by Stephen J. Turnbull

Colin Watson writes: > Ideally, I'd like mailing lists to have a "deactivated" state in > addition to full deletion. In this state, the list would appear > nonexistent for most purposes: incoming email would be rejected, > Postorius would deny its existence, etc. [...] > Has there been any discussion of this in the past, or any advice as to > implementation strategy? I don't recall anybody discussing this. Your use case is your use case, but I think if we were going to implement this I'd probably want "partial" deactivation where the archives remain available but no mail is delivered, can't subscribe, etc. I'm also not sure I'd want Postorius to deny it ever existed. That seems rather unfriendly (again, I don't understand your use case, so that is not a comment on your requirements). So to get it into the distribution we'd need to make these things optional. (Perhaps if these options proliferate much, they could be incorporated into list "styles" so that instead of setting all the options manually, the primary use cases could be served by "intuitively" named styles.) It seems to me that dump, delete, and restore may be the best approach for the HyperKitty side because HyperKitty maintains all that state. Of course this could be done inside the database. Also, perhaps you can (ab)use the ArchivePolicy enum by adding an "inactive" element, but core has no way to enforce those on the archiver (which can be a third party host like mail-archive.com) and I'm not sure HyperKitty ever consults core about that once the archive is created. I'm not sure what you mean about IArchiver; as far as I can see that interface is sort of half-duplex: it provides the information core needs *about* the archiver to do core's side of archiving, not for core to communicate *with* the archiver. In fact all of the concrete code is callbacks provided by the archiver, and once a message is archived the core forgets about it. So this isn't "just" an extension; it's a fundamental redesign of IArchiver. I'm not sure that's not a good thing, but we do need to think about it. ISTM we're gradually converging back on the monolithic approach to MLM, with the distribution, administration, and archiving quite tightly interwoven, and I'm not sure I like that. OTOH, we do get a lot of requests for ever more bundling.

8 years, 6 months

Re: list of subscribers

by Simon Hanna

On 02/04/2018 08:37 PM, Peter Münster wrote: > On Sun, Feb 04 2018, Simon Hanna wrote: > >> You should be able to use mailmanclient to get a list of subscribers with >> names. > It seems, that mailmanclient does not know about the real name (the > first name and the last name in Django). But this seems to work: > > from django.contrib.auth.models import User > user = User.objects.get(email='address(a)of.user') > print(user.first_name) > print(user.last_name) > > So, I'll try to make some loop over a list with email addresses, that I > can get on the web interface. These are names that are saved in Postorius' (django) database and have nothing to do with mailman. Furthermore you will only find them if people have logins for the frontend. They don't have to. Also these names are optional. They aren't populated during signup and people have to provide them afterwards themselves. >> Names are optional though, if people signup without them you won't be able to >> get them. > My usage of mailman is perhaps a bit special: users can't sign up, only > the site owner signs up manually with create_user(email=, first_name=...) > Then the site owner creates the mailing lists and uses mass subscription > (for example all members of a basketball team). At one moment, the list > of subscribers should be verified by all members, just to be sure, that > nobody got forgotten. > > >> Currently there is no option to require names. I'll open an issue in >> postorius about showing the name in the member list if there is one >> associated. > Thanks. It would be nice, to see the first_name and the last_name of the > django-auth user object. > > >> IIRC one person(postorius account) can also signup at different lists using >> different names (regardless of address). > You mean the "display_name" of mailmanclient here? I won't use it. > For my usage, I prefer a clear association of email, first name and > last name in one account, no need for "display_name" here. Displaying the names stored in django probably won't happen. Matching the names in django with the members in lists would require lots of code where people can just supply their name when they signup for a list. Also you might want to be known by name on one list and not on others...

8 years, 6 months

Re: Error when sending customized welcome message template

by Markus Grandpré

Dear Mr. Sapiro, Thank you once again for your help. The templates are now being sent without any errors. However, while using the many variables that can be sent with a template, I noticed that the resolution of the variable $hyperkitty_url is not working, even though i am using a private archive in this list and a URL to this archive exists. Best regards, Markus Grandpré Am 13.03.25 um 14:12 schrieb Mark Sapiro: > On 3/13/25 2:54 PM, Markus Grandpré wrote: >> Dear List, >> >> As soon as a template "[list:user:notice:welcome]" exists, and at >> least one email address is provided during mass subscribe, while >> sending an invitation is disabled and sending a welcome message is >> enabled, the following error occurs: >> >> HTTP Error 400: ('Connection aborted.', ConnectionResetError(104, >> 'Connection reset by peer')) > > Was this template set in Postorius? If so, there is an issue with your > setting for POSTORIUS_TEMPLATE_BASE_URL. The default is > ``` > POSTORIUS_TEMPLATE_BASE_URL = http://localhost:8000/ > ``` > which should work if your wsgi server is listening on the local host, > port 8000, but setting it to the base scheme and host you use to access > Postorius is generally good. > -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: +49 7531 88 4342

1 year, 4 months

Re: Postorius not HTML-decoding < to "<" characters

by Mark Sapiro

> > Does that mean the DB has data with mismatched tags in it? The database has exactly what list members receive by email. What we are talking about is how this is rendered in HyperKitty. > Interestingly, the quoted part of my message has < where my message > has proper less-than and greater-than for the Apache tags. > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > It's inconsistent with the archive rendering mode at lists.mailman3.org. Here's what's going on. In normal text, mistune disables HTML tags by converting `<` to the html entity `<`, but your browser renders the HTML entity `<` as `<` so you see what was written. The issue here is the text you quoted was originally in a markdown code block, i.e. preceded and followed by lines of three backticks. Code blocks are intended to be seen literally as written so they are wrapped in <pre><code> ... </code></pre> tags in the HTML and also HTML escaped. The problem is the tag disabling converts `<` to `<` but then the HTML escaping converts `<` to `&lt;` which your browser then renders as `<` rather than `<`. (aside, it will be interesting to see how that is rendered in the archive) If HyperKitty is set to render as plain text rather than markdown it doesn't interpret code blocks so this doesn't happen. There are other anomalies with the markdown rendering, e.g., as pointed out by Jeremy at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Those notwithstanding, we prefer markdown rendering for this list because often people post Python snippets or `mailman shell` interactions and enclosing those in markdown code blocks renders them much better. > I haven't currently got an instance that I can test on but will keep > this in mind when the time comes to migrate. > > Should the rendering at lists.mailman3.org get modified, please share > the procedure. > > > > Testing: less-than and greater-than around a tag: > > <Location /mailman/accounts/signup> > > Testing: less-than and greater-than around a tag in a quoted block: > > > <Location /mailman/accounts/signup> Both the above tests look fine in the archive. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

Mailman-users search results for query "Postorius"