Search results for "Postorius" - Mailman-users

Re: Mail going to Held Messaging even the moderation is set to Accept Immediately

by Mark Sapiro

On 7/21/20 8:09 AM, Shashikanth Komandoor wrote: > > As per my understanding on Mailman 3, if the moderation attribute is > set to "Accept immediately (bypass all other rules)" then without checking > any rules, it should be delivered to the recipients of the list > irrespective of the message or body of the message but is there any such > checking if the body content or subject or any thing else is checked even > if the moderation bit is set to "Accept immediately". Member moderation Accept Immediately does not bypass ALL rules. It only bypasses those rules after member-moderation. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/chains/builtin…>. However, I don't think that's the issue here. I think the issue is the poster is both an owner and a member. There is an issue in Postorius such that in cases like this, setting the member's moderation action actually sets that of the owner which has no effect on posting. See <https://gitlab.com/mailman/mailman/-/issues/659> -- 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: spanish localization

by Mark Sapiro

On 2/13/21 4:08 PM, Victoriano Giralt wrote: > > Mark, please, how do you check when translations happened? Nov 7th is a > very significant date for me (it is my wedding anniversary) and I'm 90% > sure that I dedicated time to Weblate after that date... With respect to Mailman core, all I'm doing is downloading the .po for Spanish and comparing it to mailman/messages/es/LC_MESSAGES/mailman.po from the Mailman core 3.3.3 package on PyPI and they are identical. If there are translated strings on weblate that are different from that, they don't show up in the downloaded <https://hosted.weblate.org/download/gnu-mailman/mailman/es/>. > All strings related to Mailman (core, django_mailman3, postorius and > hyperkitty) are translated into Spanish 100%, but the interfaces, after > updating to the latest releases, are still in Englanish (more English than > Spanish). > > This is not a fight, we want to help, but do not know how. And I too want to help. It would be a help to me if you can give me examples of specific strings whose weblate translation differs from what's in the distributed .po files. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

Mass subscribe operation fails with http error

by Stephen J. Turnbull

b.watts(a)ucl.ac.uk writes: > I have reviewed similar threads, including: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… In that thread, it appears that there is some kind of deadlock going on, and increasing the number of gunicorn workers. The configuration for gunicorn is usually in /etc/mailman3/gunicorn.conf, and the line to add or update would be "workers = 3". See https://docs.mailman3.org/en/latest/install/virtualenv.html#setting-up-guni…, which recommends workers = "ncores + 1". > I have updated the config in: > /etc/mailman3/settings.py > to contain: > POSTORIUS_TEMPLATE_BASE_URL = 'https://mailinglists.ucl.ac.uk' After accessing your external webserver, this is just going to get routed to the internal WSGI server for Postorius, usually "http://127.0.0.1:8000" if you are running Postorius/mailmanweb on the same host as Mailman core. (This is defined in the "bind" parameter in gunicorn.conf if you have a different configuration.) There's no reason to route through the external webserver (I'm not sure why Mark suggested it in that thread, except maybe to test if changing the URL and recreating the template would help). -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

4 months, 2 weeks

Re: Docker Support Sucks

by Allan Hansen

Hi Brian, You have been one of the good and generous people providing support. I hope i can repay a bit with this: These are one-line bash scripts I wrote after moving to MM3, so I could do things not yet in MM3, such as letting my moderators request a list’s members from me. I need one more script that will sync a text file to an existing list, deleting and adding as necessary. The scripts are for public use, reuse, misuse and overuse. I claim no rights and no responsibilities. mm3Members.bash #!/bin/bash # mm3Members # # Obtain a list of members of a given list # # Usage: # mm3Members.bash <listName> # # # Revisions: # Date Name Reason for change # 28-Mar-2020 Allan Hansen Initial # exec /opt/mailman/mm/venv/bin/mailman -C "/opt/mailman/mm/mailman.cfg" members $1 |grep -v -e "has no members"|sed -e 's/.*/\L&/‘ mm3ASddMembers.bash #!/bin/bash # mm3AddMembers # # Add members from a given list. # # Usage: # mm3AddMembers.bash <fileName> <listName> # <fileName>: text file with addresses to add. Same legal formats as in mass subscribe # # # Revisions: # Date Name Reason for change # 28-Mar-2020 Allan Hansen Initial # exec /opt/mailman/mm/venv/bin/mailman -C "/opt/mailman/mm/mailman.cfg" members --add $1 $2 mm3DeleteMembers.bash #!/bin/bash # mm3DeleteMembers # # Deletes members from a given list # <fileName> List of members to delete. Legal format the same a formats used for mass subscribes # # Usage: # mm3DeleteMembers.bash <fileName> <listName> # # Revisions: # # Date Name Reason for change # 28-Mar-2020 Allan Hansen Initial # exec /opt/mailman/mm/venv/bin/mailman -C "/opt/mailman/mm/mailman.cfg" members --delete $1 $2 mm3MemberCount.bash #!/bin/bash # mm3MemberCount # # Obtain count of the members of a given list # # Usage: # mm3MemberCount.bash <listName> # # Revisions: # Date Name Reason for change # 28-Mar-2020 Allan Hansen Initial # /home/hansen/scripts/mm3Members.bash $1|wc Yours, Allan Hansen hansen(a)rc.org > On Jul 21, 2020, at 18:31 , Brian Carpenter <brian_carpenter(a)emwd.com> wrote: > > On 7/21/20 8:55 PM, Mark Sapiro wrote: >> On 7/21/20 5:40 PM, Brian Carpenter wrote: >> >> Abhilash (@maxking) is one person and he has a $DayJob. We're all doing >> the best we can. > > Well, I still need support. > >> This is not a Docker issue per se. It is a consequence of upgrading >> Mailman core to 3.3.1+ and processing many old, stale, previously >> unprocessed bounces. See >> <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> > > I am not worried about the bounce issues at this point. I am just trying to get a membership list exported for a client. > >> >>> So, I want to totally move away from the use of Docker (mainly because I have found it buggy and the support is simply lacking) and install Mailman 3 for this client from source. However I need to get an export of their list members. But of course, I can't. Rest API times out and I don't know how to apply the instructions I was given to fix it and I don't have days to way for one. So please help. >>> >>> I increased the gunicorn workers to 4, hoping that would allow me to do the CSV export. No. So was given these instructions: >>> >>> ### >>> The issues seems to be due to timeout not due to high load. You want to increase the timeout for gunicorn and you can do that by specifying a gunicorn.ini config file: >>> >>> [webservice] >>> configuration: /path/to/gunicorn.cfg >>> >>> and then in the gunicorn.cfg you can add >>> >>> [gunicorn] >>> timeout = 90 >>> graceful_timeout = 30 >>> ### >>> >>> I applied the above changes to /opt/mailman/core/mailman-extra.cfg and created the gunicorn.cfg file. Restarted the docker container (mailman-core) and no access to Postorius due to no REST api. >>> >>> After restarting docker-mailman, I can't access Postorius due to the following error: >>> >>> ERROR 2020-07-20 20:16:27,351 15 postorius Mailman REST API not available >> Is Mailman core running? If not, whats in core's mailman.log as to why not? > > It looks like but no error message in mailman.log. However I noted that the gunicorn process did not start. > > This is with the configuration line enabled in mailman-extra.cfg: > > # docker-compose restart mailman-core > Restarting mailman-core ... done > [root@nicu-net docker-mailman]# tail -f /opt/mailman/core/var/logs/mailman.log > Jul 22 01:25:17 2020 (22) in runner caught SIGTERM. Stopping. > Jul 22 01:25:17 2020 (25) out runner caught SIGTERM. Stopping. > Jul 22 01:25:17 2020 (25) out runner exiting. > Jul 22 01:25:17 2020 (21) command runner exiting. > Jul 22 01:25:17 2020 (22) in runner exiting. > Jul 22 01:25:17 2020 (24) nntp runner caught SIGTERM. Stopping. > Jul 22 01:25:17 2020 (24) nntp runner exiting. > [2020-07-22 01:25:19 +0000] [27] [INFO] Shutting down: Master > Jul 22 01:25:21 2020 (1) Master stopped > Jul 22 01:25:26 2020 (1) Master started > Jul 22 01:25:44 2020 (27) rest runner started. > Jul 22 01:25:44 2020 (26) pipeline runner started. > Jul 22 01:25:44 2020 (20) bounces runner started. > Jul 22 01:25:45 2020 (22) in runner started. > Jul 22 01:25:45 2020 (28) retry runner started. > Jul 22 01:25:46 2020 (29) virgin runner started. > Jul 22 01:25:46 2020 (25) out runner started. > Jul 22 01:25:46 2020 (23) lmtp runner started. > Jul 22 01:25:46 2020 (24) nntp runner started. > Jul 22 01:25:47 2020 (30) digest runner started. > Jul 22 01:25:47 2020 (19) archive runner started. > Jul 22 01:25:47 2020 (21) command runner started. > > This is with the configuration line disabled in mailman-extra.cfg: > > # docker-compose restart mailman-core > Restarting mailman-core ... done > [root@nicu-net docker-mailman]# tail -f /opt/mailman/core/var/logs/mailman.log > Jul 22 01:27:49 2020 (1) Master stopped > Jul 22 01:27:53 2020 (1) Master started > Jul 22 01:28:10 2020 (30) digest runner started. > Jul 22 01:28:10 2020 (29) virgin runner started. > Jul 22 01:28:10 2020 (24) nntp runner started. > Jul 22 01:28:10 2020 (25) out runner started. > Jul 22 01:28:10 2020 (22) in runner started. > Jul 22 01:28:11 2020 (28) retry runner started. > Jul 22 01:28:11 2020 (27) rest runner started. > [2020-07-22 01:28:11 +0000] [27] [INFO] Starting gunicorn 19.9.0 > [2020-07-22 01:28:11 +0000] [27] [INFO] Listening at: http://172.19.199.2:8001 (27) > [2020-07-22 01:28:11 +0000] [27] [INFO] Using worker: sync > [2020-07-22 01:28:11 +0000] [32] [INFO] Booting worker with pid: 32 > [2020-07-22 01:28:11 +0000] [33] [INFO] Booting worker with pid: 33 > [2020-07-22 01:28:11 +0000] [34] [INFO] Booting worker with pid: 34 > [2020-07-22 01:28:11 +0000] [35] [INFO] Booting worker with pid: 35 > Jul 22 01:28:11 2020 (19) archive runner started. > Jul 22 01:28:11 2020 (21) command runner started. > Jul 22 01:28:12 2020 (23) lmtp runner started. > Jul 22 01:28:12 2020 (20) bounces runner started. > Jul 22 01:28:12 2020 (26) pipeline runner started. > > -- > Please let me know if you need further assistance. > > Thank you for your business. We appreciate our clients. > Brian Carpenter > EMWD.com > > -- > EMWD's Knowledgebase: > https://clientarea.emwd.com/index.php/knowledgebase > > EMWD's Community Forums > http://discourse.emwd.com/ > > _______________________________________________ > 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/

6 years, 1 month

Re: Hyperkitty 403 Forbidden Error

by Phil Thompson

On 06/08/2019 09:48, Phil Thompson wrote: > On 06/08/2019 03:38, Abhilash Raj wrote: >> On Mon, Aug 5, 2019, at 10:06 AM, Phil Thompson wrote: >>> I'm in the process of setting up mailman3. The only problem I seem to >>> be >>> having is getting Hyperkitty to archive messages. Rather than the >>> authorisation problems people have previously asked about on the >>> list, I >>> am getting a 403 error... >>> >>> Aug 05 15:38:40 2019 (10229) HyperKitty failure on >>> http://localhost/mailman3/hyperkitty/api/mailman/urls: >>> <html><title>Forbidden</title><body> >>> <h1>Access is forbidden</h1></body></html> (403) >>> Aug 05 15:38:58 2019 (10222) HyperKitty failure on >>> http://localhost/mailman3/hyperkitty/api/mailman/archive: >>> <html><title>Forbidden</title><body> >>> <h1>Access is forbidden</h1></body></html> (403) >>> >>> Any suggestions would be appreciated. >> >> How did you install Hyperkitty? > > On Ubuntu... > > apt-get install mailman3-full > >> You probably need to the set the API key correctly in both Core and >> Hyperkitty. >> >> Have you looked at documentation here[1]? >> >> [1]: >> https://hyperkitty.readthedocs.io/en/latest/install.html#connecting-to-mail… >> >> Note that the MAILMAN_ARCHIVER_KEY = "value" (this value should be in >> quotes, single or double, doesn't matter) in your settings.py for Web >> (Django) should be same as the `api_key : value` (without quotes here >> in hyperkitty.cfg config file). > > That's all correct. I'm familiar with the authorisation issues that > other people have had. > > The only thing I'm doing differently (as far as I am aware) is that > I'm using a URL prefixed with /mailman3 which is stripped off in my > nginx configuration... > > # mailman3. > location /mailman3/ { > uwsgi_pass unix:/run/mailman3/web/uwsgi.sock; > include uwsgi_params; > uwsgi_param SERVER_ADDR $server_addr; > uwsgi_modifier1 30; > uwsgi_param SCRIPT_NAME /mailman3; > } > > location /mailman3/static { > alias /var/lib/mailman3/web/static; > } > > location /mailman3/static/favicon.ico { > alias /var/lib/mailman3/web/static/postorius/img/favicon.ico; > } > > ...but I don't see this affecting the mailman to Hyperkitty > communication. Posting to lists and the Postorius and Hyperkitty > frontends seem to work fine. I have now fixed the 403 error (by setting MAILMAN_ARCHIVER_FROM to my public IP address). However I now get a 400 Bad Request error. I have traced this to the archive() function in hyperkitty/views/mailman.py which is expect a POST but is actually getting a GET, specifically... GET '/mailman3/hyperkitty/api/mailman/archive?key=...' ...which seems to be a fairly fundamental problem. Again, any suggestions would be welcome. Phil

7 years, 1 month

Re: 120 gmail users removed from lists !

by Odhiambo Washington

If Yunohost installed Mailman3 for you, then it's better to ask them to update it for you. On Tue, Oct 24, 2023 at 7:51 AM Yvan ♞ <elemac(a)free.fr> wrote: > Hello, > Thanks for this answer, my problem is I'm on yunohost server and the > update 3.3.9 is not available now. > Any "handmaid" solution should be great. > Sincerely > > Le 22/10/2023 à 10:45, Stephen J. Turnbull a écrit : > > elemac(a)free.fr writes: > > > > > Hello, on 15th October, 120 users with gmail address where suddenly > > > removed from lists in mailman3, something changed in google ? > > > > Google is evil, who knew? > > > > Google decided to publish a DMARC policy of "p=none". This announces > > to the world that you have to decide for yourself whether to accept > > mail from Gmail with a broken DKIM signature from gmail.com. Gmail > > has decided that they will not accept such email from themselves, even > > though they know more about the sender than anyone else, and even have > > access to the original sender copy. > > > > Mark has a patch that applies your preferred DMARC mitigation to Gmail > > authors unconditionally. I think it's in the new version just > > released 3.3.9, so you can upgrade. The name of the variable is > > dmarc_addresses, and in Postorius it will be in the same settings > > group as other DMARC settings, with a similar tag. > > > > If for some reason you strongly prefer not to upgrade immediately but > > want this feature, it's commit #8532f751b6b8bfee3210c1327d755756f99d99ac > > (you can shorten that to 8532f). I do not recommend this. It probably > > is independent of other changes in 3.3.9 from other releases. But if > > not you could have issues. > > > > I think you also need the patches in Postorius, but I don't think > > they've been released yet. "Coming soon" as they say. The relevant > > commit is #770add1ebf27fd335c675607f26bb8f7cf313ddd, > > > > If you search back in the archives, I think Mark posted a link to his > > original patches. > > > > Steve > > > _______________________________________________ > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to odhiambo(a)gmail.com > -- 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]

2 years, 10 months

Re: Changing subscription address

by Stephen J. Turnbull

Abhilash Raj writes: > The existing subscription workflow is a multi-step process that can be > paused and resumed. We pause when we send out a confirmation > email and then resume when that confirmation token is somehow > processed via email or API. So, post receiving the confirmation and > before actually subscribing, we can se the address as primary if the > user doesn’t have one and subscribe user as inhert. We don’t do any > of that if user already has chosen a primary address and it doesn’t > match the current address. OK, it sounds like we're thinking basically the same process, just using slightly different words to describe it (and mine have definitely been inaccurate about current logic at points, adding to the confusion :-P ). > Also, mass-subscribe and import does allow you to verify an address by > clicking this “Pre-verified” checkbox, which can be useful if you are > migrating from a different service or you exported a list of users from > somewhere you know to be valid. I wasn't aware of that. I haven't yet done a mass-subscribe from Postorius (I have a bunch of scripts for generating mailing lists from student rosters and just retargeted them to the REST API :-). Steve

5 years, 5 months

Re: Filter who can send on mailman3 list?

by Marcus Granath

It seems like the version used is: Postorius Version 1.1.2 The menus I can see are the following: Info Subscription requests Held messages Members Settings Mass operations Banned addresses Header filters Delete list And from the "Members" I can select "Subscribers", "Moderators", "Owners" - so I can manage to delete "subscribers" and add somebody as Moderator or Owner for my list. But I cannot find anywhere to set or add something like "non-member". What I basically want to achieve is that my "sendmail" script (executed from linux) will send announce-mails to this mailing list - and will set an "pseudo-address" (not my own name and address) as sender of this e-mail, i.e "ABC Announcement <no-reply(a)abc.com>" - and to get this "pseudo-mail" to be one of the accepted users (together with me and some team mates with real addresses) to send on the list - one option I understood was to use the "non-member" user for this "ABC Announcement <no-reply(a)abc.com>". But in my web-interface (as described above), I cannot find where to add and manage such user (non-member). Or can I use some other API (then the web-page) to do that kind of operation? ;-)

5 years, 5 months

Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by David Partain

On Tue, 2021-03-02 at 13:43 -0800, Mark Sapiro wrote: > > This is all because you are using the Ubuntu 18.04 package which is > about 4 years out of date and is from the era where HyperKitty, > Postorius and django_mailman3 still ran under Python 2.1.7. > > Unless you want to remove the Ubuntu package and install everything > with > pip, you need to just stick with what you have that at least partly > works and we'll try to determine how to fix the utf8mb4 issue. Hi Mark, You're a very patient soul. Thank you. Yes, I'm resigned to exactly that. The archives when folks send emojis will break, but that's just life. Mail will get sent. Heck, I guess I could edit the file in /var/lib/mailman3/archives/hyperkitty/spool to get rid of the emoji in the worst case... Once I've migrated my 1500 mailing lists (this weekend) to the server, I'll think about how to get a new server set up that I can shift to and I'll install that with pip, since that'll clearly give me something more supportable. Is Ubuntu 20.04 a reasonable platform for that? Cheers, David

5 years, 6 months

Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Sun, Dec 25, 2022 at 5:13 PM Stephen J. Turnbull < stephenjturnbull(a)gmail.com> wrote: > Odhiambo Washington writes: > > > > Besides mod_wsgi as Mark suggests and the uwsgi configuration, the > > > only thing I can think of is an Apache rewrite rule. It's not in the > > > Postorius and HyperKitty templates. > > > > And I do not have any rewrite rules in my VHOST config: > > > > https://pastebin.ubuntu.com/p/9MRMJST9zZ/ > > Is there a mod_wsgi.conf file? I've never seen this "mysterious" > insertion of "/mailman3" in URLs. I'm trying to imagine where > mod_wsgi would get it from, and just can't think of why that would be > in mod_wsgi or its .load or .conf files in the Apache config. The > maintainable place for URL configuration is the main apache.conf or a > site-specific include file such as sites-available/mailman.conf. I > guess it could be in an instance-specific configuration file or stanza > of uwsgi to create a namespace. > > Steve > There is none that is in use anywhere. Only /etc/mailman3/uwsgi.ini -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 8 months

Mailman-users search results for query "Postorius"