Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: Missing bits of French translation

by iMark

>> On 5/12/26 17:30, iMark wrote: >> >> 3. Page text fails. eg. >> ENGLISH: You have to sign in to visit the archives of this list. >> FRENCH: Is in English. >> >> Looking at the .po file ... >> >> /opt/mailman/venv/lib/python3.11/site-packages/mailman/messages/fr/LC_MESSAGES/mailman.po >> >> "PO-Revision-Date: 2024-06-25 17:09+0000\n" ====================================== > On 2026-05-13 02:19, Mark Sapiro wrote: > That file is out of date. It may or may not be from the latest > Postorius released version but it has been subsequently updated for > the next release. > > That particular string is marked fuzzy in the current .po - see > <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/locale/fr/…> > > It is marked fuzzy because the msgid was changed at some point from > ``` > msgid "You have to login to visit the archives of this list." > ``` > to > ``` > msgid "You have to sign in to visit the archives of this list." > ``` > > The translations are managed at Weblate. The particular French > translation for Postorius is at > <https://hosted.weblate.org/projects/gnu-mailman/postorius/fr/>. > > The above string is one of 19 that are marked for edit. > > You are more than welcome to create an account at Weblate and fix > whatever needs fixing in the French translation and Weblate will > submit a merge request to update the .po on GitLab. We would be > grateful for your help. ======================================= Thanks Mark. I edited the .po file (on my installation) for Postorius ... /opt/mailman/venv/lib/python3.11/site-packages/postorius/locale/fr/LC_MESSAGES/django.po ... for example ... msgid "You have to sign in to visit the archives of this list." msgstr "Vous devez vous identifier pour consulter les archives de cette liste." ... and recompiled the .mo file ... msgfmt -o /opt/mailman/venv/lib/python3.11/site-packages/postorius/locale/fr/LC_MESSAGES/django.mo /opt/mailman/venv/lib/python3.11/site-packages/postorius/locale/fr/LC_MESSAGES/django.po ... and the text on the webpage is now displayed in French. Happy days! I've created an account at Weblate and will get onto the .po file there. Thank you again for your help.

2 weeks, 1 day

[MM3-users] Re: Unable to get Postfix to bounce messages to non-existent lists

by skenny＠scss.tcd.ie

Thanks Mark Sapiro and Stephen J. Turnbull for your responses. Re the output of mailq - this was initially confusing (to me anyway). The diagnostic for the message stuck in the queue was "connection timed out", but the IP listed was the Postfix mail server's not Mailman's. At a guess, Postfix was trying to send the message to Postfix's local domain after it failed to LMTP it over to the Mailman server, and was unable to do that too. Since I posted yesterday, I hit upon a solution that seems to work ... I set relay_recipient_maps to the same value as transport_maps, so that the relevant config lines now look like this: transport_maps = regexp:/var/mailman-data/postfix_lmtp local_recipient_maps = $alias_maps relay_domains = regexp:/var/mailman-data/postfix_domains relay_recipient_maps = regexp:/var/mailman-data/postfix_lmtp This seems to have the desired effect (and, I hope, no unintended consequences). If I fire a message at a non-existent list now, I get an immediate bounce message in my mail client - "Recipient address rejected: User [nonexistent-list(a)lists.scss.tcd.ie] unknown in relay recipient table". No longer is the message loitering in the Postfix queue. The Postfix documentation for relay_recipient_maps says "Optional lookup tables with all valid addresses in the domains that match $relay_domains. [...] Technically, tables listed with $relay_recipient_maps are used as lists: Postfix needs to know only if a lookup string is found or not, but it does not use the result from the table lookup." For transport_maps, it says "Optional lookup tables with mappings from recipient address to (message delivery transport, next-hop destination). " Postfix does what we want now: bounce the message is the list name isn't found in relay_recipient_maps, forward it on to the Mailman server via LMTP (transport_maps setting) if it is. Re Stephen J. Turnbull's comment about the patch allowing Postfix to query Mailman's database and more, I think I'll hold off for the moment, but good to know. We will reconfigure when it makes it into an official release (we're using Maxking's Docker images). As ever I'm really grateful for your taking the time to respond, many thanks. Kind regards.

2 years, 3 months

[MM3-users] Re: Unable to update templates

by Mark

On 5/28/25 01:14, Mark wrote: >> >> Then I created a template using Postorius and updated the uri in >> mailman.templates to: >> >> file:///opt/mailman/mm/var/templates/lists/testlist.example.com/en/list:use… >> - and that works. >> >> It's looking promising. Now I just need to modify my script that >> periodically copies the data from the >> "mailmanweb.postorius_emailtemplate" table to a file and updates the >> uri. On 2025-05-28 19:17, Mark Sapiro wrote: > Which says get the template from the file system at that location and > don't ask for it from Postorius at all. This would be the default > action if there were no entry for this template in the > mailman.template table at all. I.e. you now have a template in > Postorius, but it is not used. I have jumped the gun on thinking that the template as a file was working. It's not. It's the same story: the initial file template is good, but it's for sure getting cached somewhere, and an updated file is ignored. The same as when the template was being drawn from the database. Restarting mailman3 and mailmanweb didn't help, neither did rebooting the server. Looking at Gunicorn status, I see a failing connection to 127.0.0.1 which is the error message I was getting when adding a new subscriber - with the custom Welcome template in the database (which is why I moved it to file). 127.0.0.1 and locahost are in the ALLOWED_HOSTS and CSRF_TRUSTED_ORIGINS of the settings.py file I'm at a loss with this caching problem. Any other clues happily received. $ gunicorn --version gunicorn (version 21.2.0) $ gunicorn status [2025-05-29 02:29:41 +0000] [17838] [INFO] Starting gunicorn 21.2.0 [2025-05-29 02:29:41 +0000] [17838] [ERROR] Connection in use: ('127.0.0.1', 8000) [2025-05-29 02:29:41 +0000] [17838] [ERROR] Retrying in 1 second. [2025-05-29 02:29:42 +0000] [17838] [ERROR] Connection in use: ('127.0.0.1', 8000) # ps -ef | grep gunicorn root 1522331 1521736 0 22:57 pts/1 00:00:00 grep gunicorn mailman 1608073 1 0 May20 ? 00:01:24 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/gunicorn -c /etc/mailman3/gunicorn.conf mailman_web.wsgi:application mailman 1608075 1608073 1 May20 ? 02:24:20 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/gunicorn -c /etc/mailman3/gunicorn.conf mailman_web.wsgi:application

11 months, 4 weeks

[MM3-users] Re: Problem with digests not being sent daily

by Mark

On 2024-06-22 00:04, Mark Sapiro wrote: >>>> ...The mmdf files don't exist in the list's directory although there >>>> have been many posts to the list throughout the day. > If you look at some point prior to 22:30, are there > /opt/mailman/mm/var/lists/<list_id>/digests.mmdf files at that time? > and if so, what happins if you run `mailman digests --periodic` > manually at that point? I changed the digest and notify crons to 05:00. 0 5 * * * @daily /opt/mailman/venv/bin/mailman digests --periodic 0 5 * * * @daily /opt/mailman/venv/bin/mailman notify At ~04:50 I posted an email to the list. The message was delivered to members and archived. Nothing showed up in /opt/mailman/mm/var/lists/<LISTID> # cd /opt/mailman/mm/var/lists/<LISTID> # ls -la total 8 drwxr-xr-x 2 mailman mailman 4096 Jun 22 04:52 . drwxr-xr-x 6 mailman mailman 4096 Mar 25 21:32 .. Then, as "mailman", I ran "mailman digests --periodic" manually and got the same error (as expected since there is nothing there) ... $ /opt/mailman/venv/bin/mailman digests --periodic Traceback (most recent call last): File "/opt/mailman/venv/bin/mailman", line 8, in <module> sys.exit(main()) ^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 1157, in __call__ return self.main(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 1078, in main rv = self.invoke(ctx) ^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/mailman/bin/mailman.py", line 69, in invoke return super().invoke(ctx) ^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 1688, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 1434, in invoke return ctx.invoke(self.callback, **ctx.params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 783, in invoke return __callback(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/decorators.py", line 33, in new_func return f(get_current_context(), *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/mailman/commands/cli_digests.py", line 126, in digests maybe_send_digest_now(mlist, force=True) File "/opt/mailman/venv/lib/python3.11/site-packages/mailman/app/digests.py", line 106, in maybe_send_digest_now os.rename(mailbox_path, mailbox_dest) FileNotFoundError: [Errno 2] No such file or directory: '/opt/mailman/mm/var/lists/<LISTID>/digest.mmdf' -> '/opt/mailman/mm/var/lists/<LISTID>/digest.6.3.mmdf'

1 year, 11 months

[MM3-users] Re: Disabling Mass operations

by iMark

> On 1/23/26 17:39, iMark wrote: >> Hi All, >> >> Can anyone give me a pointer on disabling "Mass operations" >> (subscribe/removal) in Postorius. >> >> Just removing the menu link from the list-owners administration pages >> would be a good start. On 2026-01-24 02:01, Mark Sapiro wrote: > > This patch will do that > ``` > --- a/src/postorius/templates/postorius/menu/list_nav.html > +++ b/src/postorius/templates/postorius/menu/list_nav.html > @@ -84,6 +84,7 @@ > {% if user.is_superuser or user.is_list_owner %} > <li class="nav-item"><a href="{% url 'list_template_list' > list.list_id %}" class="nav-link {% nav_active_class current > 'templates' %}">{% trans 'Templates' %}</a></li> > <li class="nav-item"><a href="{% url 'list_settings' > list.list_id %}" class="nav-link {% nav_active_class current > 'list_settings' %} ">{% trans 'Settings' %}</a></li> > + {% if user.is_superuser %} > <li class="dropdown nav-item"> > <a href="#" class="{% nav_active_class current > 'list_mass_ops' %} dropdown-toggle nav-link" data-bs-toggle="dropdown" > role="button" aria-haspopup="true" > aria-expanded="false"> > @@ -98,6 +99,7 @@ > <li><a href="{% url 'mass_removal' list.list_id %}" > class="dropdown-item">{% trans 'Mass removal' %}</a></li> > </noscript> > </li> > + {% endif %} > <li class="nav-item"><a href="{% url 'list_bans' > list.list_id %}" class="{% nav_active_class current 'list_bans' %} > nav-link">{% trans 'Ban List' %}</a></li> > <li class="nav-item"><a href="{% url 'list_header_matches' > list.list_id %}" class="nav-link {% nav_active_class current > 'list_header_matches' %}">{% trans 'Header filters' %}</a></li> > <li class="nav-item"><a href="{% url 'list_delete' > list.list_id %}" class="{% nav_active_class current 'list_delete' %} > nav-link">{% trans 'Delete' %}</a></li> > ``` > Some lines in the above may be wrapped but basically it just adds > > {% if user.is_superuser %} > > and > > {% endif %} > > around the Mass operations code. > Thank you very much Mark. That is perfect. /opt/mailman/venv/lib/python3.11/site-packages/postorius/templates/postorius/menu/list_nav.html Cheers.

4 months

[MM3-users] Re: moving list from mm3 -> mm3

by Jens Günther

Thanks Mark for our answers, I already got a bit further. Am 09.12.23 um 00:27 schrieb Mark Sapiro: >> But it returns {"title": "405 Method Not Allowed"} and I don't know >> where to look in the docs, since it shows almost always a way through >> mailman shell. > You need a PUT command, not POST. Try the above with `-X PUT`. With the `-X PUT`-command, there is the following error: {"title": "400 Bad Request", "description": "Unexpected parameters: bounces_address, created_at, digest_last_sent_at, fqdn_listname, http_etag, join_address, last_post_at, leave_address, list_name, mail_host, next_digest_number, no_reply_address, owner_address, post_id, posting_address, request_address, usenet_watermark, volume"} -> I don't know why, since I tried it with the exact same example-list from where I got all these parameters (ex- and then import) ... do I still miss something? Or does it only work on "fresh" lists? > You can use Postorius -> Mass operations -> Mass subscribe to add the > members, but you can't do that for owners and moderators. Also you lose > information about the members such as Delivery status, Delivery mode and > other user settings. Is there another way to preserve these information about the members? (in general I don't think a lot of people put in effort to customize there memeberships ... and furthermore they would need to register, right?) >> ## registered users > > That is not the answer. Those are Mailman core users, not Django (web > login) users. You need to get the relevant entries from the auth_users > and account_emailaddress tables and add them to the new DB. Ok, that would be fine. Are there any more relations to other tables/columns that need to be set? (I just realised, that there are 2 different id in each table ... the one in auth_users is the user_id in account_emailaddress :-) scary). Do you have any suggestions on how to add them correctly? Thank you in advance for now and another big one in general to all of you on this list that try to help continouisly with all these problems. It's a great pleasure to be able to ask for help on a list like that. Thank you! Have a good rest of the year. Regards, Jens.

2 years, 4 months

[MM3-users] Re: config incoming email in my domain cpanel

by Rafael Mora

El jue., 3 ago. 2017 a las 14:09, Simon HANNA (<simon.hanna(a)serve-me.info>) escribió: > > > On August 3, 2017 8:50:41 PM GMT+02:00, Rafael Mora < > rafael.mora.guti(a)gmail.com> wrote: > >El jue., 3 ago. 2017 a las 13:21, Mark Sapiro (<mark(a)msapiro.net>) > >escribió: > > > >> On 08/03/2017 10:42 AM, Rafael Mora wrote: > >> > > >> > I've found the MX records on my cpanel but how do I redirect the > >emails > >> > going to my list to my private server? > >> > >> > >> You have to configure the MTA that is the MX for the domain to relay > >the > >> mail to the Mailman server. > >> > > > >Our domain is: LABBRANDS.COM We have that domain config in a Hosgator > >hosting. The emails sent to labbrands.com go to our hosting, so how do > >I > >tell cpanel in hostgator hosting that the mails sent to the list ( > >mailing(a)labbrands.com) are redirect to the MTA (postfix) in my private > >server (we have static public IP address) ?? > > > You can't redirect one email address using DNS! > If you don't want to host an entire domain on your own server, I suggest > using a subdomain (lists.example.con) instead. > Should I configure my private Centos7 server with subdomain lists.labbrands.com? Doing so how do I redirect the email to the private Centos where postfix and MM3 are installed? > You could probably also redirect one email in cpanel to the subdomain, but > I'm not sure how mailman and clients like emails with different domains... > In theory postfix can send emails using any domain. You just have to make > sure spf, dkim and PTR records are properly set. Otherwise you'll most > likely get issues with rejected mail... > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 9 months

[MM3-users] Re: Splitting hosts: mta&core vs postorius

by Stephen J. Turnbull

Ruth Ivimey-Cook writes: > On 21/06/2020 04:52, Mark Sapiro wrote: > > Change that to greyarea-post > Problem is, if I do that (which I did in the beginning), the core rest > service listens on localhost / 127.0.0.1 I don't understand. I'm not in a position to test with Mailman itself right now, but the standalone gunicorn[1] does the right thing (takes an IP address and binds to the corresponding interface, or takes a domain name, resolves it to the IP address, and binds that to the corresponding interface). It does not substitute localhost. It could be a Mailman bug (Mailman 3 is usually configured with all components running on the same host, and that's how it's tested), but first, does greyarea-post resolve to a routable address on the relevant network when queried from that host? > IMO, the hostname parameter needs to be split up into a "what address > should the rest of the world use to address me" and separately "what > address(es) should I listen on". Multiple listen addresses enable > multihomed hosts to get the right connectivity, too. I'm not clear on what you're saying. An address is a rendezvous point; if you're not listening on the address that others are using, you won't meet. What good does it do to split them up? It's not clear to me why you think Mailman might want to be multihomed (which is different from the host wanting to be multihomed). I don't object to the work to make it so. But my paranoia says it's best if Mailman is cordoned off into the DMZ with webservers and other hazmat. By design, Mailman core doesn't need to talk to the Internet or to the secure internal network -- Internet functions are delegated to the MTA and the webapps, and local configuration is via shell access which in principle could be console. I'd rather not enable the complexity of a multihomed application unless there's an important use case. (I don't make the final decision, but I am listened to by Those Who Do.) Footnotes: [1] gunicorn is the Python module that manages web services for the REST interface.

5 years, 11 months

[MM3-users] Re: MM3 Docker

by Odhiambo Washington

On Sun, 6 Jan 2019 at 23:39, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/6/19 8:47 AM, Odhiambo Washington wrote: > > > > If you could include the missing steps that you left out then I could > > possibly be able to follow the steps :-) > > > Please help me understand what steps are missing and I will try to > provide the information. Okay. At the installation stage, you say the following: "I already had some things set up in /opt/mailman including a git subdirectory containing clones of the GitLab mailman, mailmanclient, mailman-hyperkitty, hyperkitty, django-mailman3 and postorius projects. On the third server I have added mailman-suite because I use the settings.py from that project as the basis for mine." Please assume that the reader is a newbie to python3 virtualenv and give the details of the commands they need to execute to (a) clone all the projects needed and (b) create the virtualenv. The next steps are: mkdir /opt/mailman/mm Then you say "I then created a /opt/mailman/mm directory and within that a Python 3.6 virtualenv" What happens here is something that needs clarification, because you are specific about "python3.6". I have googled and realized that one has to be specific about the python version they want to use in their virtualenv as shown here -> https://stackoverflow.com/questions/45293436/how-to-specify-python-version-… exact command to execute to create the /opt/mailman/mm/venv exact command to execute to activate virtualenv From there, I think the newbie can follow and fumble till they come up with a working MM3 site. Come to think of it, your steps kind of look clearer than most that I have encountered. I do understand that there are only a few people working on the MM3 development, which I think is the reason there still isn't a document similar to the ones included with MM2.1x source under doc/ However, if your steps here are polished a little, they can possibly become one such doc. I think MM3 docs would come with three options - virtualenv option, docker option and package option. Installing from source seems like something not easily doable. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

7 years, 4 months

[MM3-users] Re: Dealing with confirmation requests for unsubscribes

by Brian Carpenter

On 11/18/20 6:17 PM, Mark Sapiro wrote: > On 11/18/20 7:41 AM, Brian Carpenter wrote: >> Hello List, >> >> I ran into the following issue for some mailman 3 lists that I am hosting: >> >> https://gitlab.com/mailman/mailman/-/issues/768 >> >> Since there is no way for a list owner to deal with a moderation request >> for an unsubscription task, I assume I need to do something via the >> command line. This is where I need some help with. How do I deal with >> these moderation requests that are unable to be reviewed in an admin gui >> (Postorius/Affinity)? > > mailman shell -l list(a)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 test.msapiro.net mailing list > > This > >>>> list(getUtility(IPendings).find(mlist=m, pend_type='unsubscription', > token_owner=TokenOwner.moderator)) > > will return something like > > [('a8df55f557b5718505280d2613937e25a3109252', {'type': 'unsubscription', > 'list_id': 'list.example.com', 'email': 'user(a)example.com', > 'display_name': 'Mark S', 'when': '2020-11-18T22:56:53', 'token_owner': > 'moderator'})] > > What you want is the token, in this case > 'a8df55f557b5718505280d2613937e25a3109252' > > Then do > > ISubscriptionManager(m).confirm('a8df55f557b5718505280d2613937e25a3109252') > > which will return > > (None, <TokenOwner.no_one: 0>, None) > > and finally: > >>>> commit() > > >> I do recommend removing such choices for Postorius for Member policy. I >> will be doing this for Affinity until issue 768 is resolved. > The correct thing to do is fix > <https://gitlab.com/mailman/mailman/-/issues/768>. We almost certainly > will do that rather than remove the moderate and confirm then moderate > unsubscription policies. > > Worked like a charm Mark. Thank you! I forget you guys have a slower process than I when it comes to implementing gui changes. For me, once you have fixed that issue (768), it will be easy for me to reintroduce those two policies for unsubscribing. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 6 months

Search results for query "sapiro"