Search results for "Postorius" - Mailman-users

Auto discard after max_days_to_hold not working.

by Stephen J. Turnbull

Hitashi mancho via Mailman-users writes: > I have migrated around 300 mailing lists from Mailman 2 to Mailman > 3. In most of the mailing lists we have configured > "max_days_to_hold" to 2. It was working fine in Mailman 2. However, > it is not working in Mailman 3. This doesn't seem to be exposed in Postorius. It's not all that old in Mailman 3 (April 2020) so it's possible that it is not moved from Mailman 2 to Mailman 3 by the migration scripts. You can use "mailman withlist" to access that variable: Use "mailman withlist -l LIST(a)DOMAIN.TLD", then at the prompt: >>> m.max_days_to_hold to examine the value for LIST(a)DOMAIN.TLD. To do a mass change, something like for ml in `mailman lists`; do mailman withlist -l $ml -r fix_mdth done where you put in Mailman's bin directory the file 'fix_mdth.py' containing def fix_mdth(ml): ml.max_days_to_hold = 2 commit() Of course if there are list where you want a longer or indefinite hold you'll need to change those back, since this approach changes all of them. You can get more information with "mailman withlist --detail". -- GNU Mailman consultant (installation, migration, customization) Sirus Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

11 months, 1 week

Re: Post installation issues (recipients refused) with Exim4 in a virtual host environment

by Kyriakos Terzopoulos

Hi, I have the following in my mailman log [11/Oct/2023:12:31:39 +0300] "GET /3.1/lists/ testlist(a)myproject.eu/held/count HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.5" [11/Oct/2023:12:31:43 +0300] "GET /3.1/lists/testlist.myproject.eu HTTP/1.1" 200 425 "-" "GNU Mailman REST client v3.3.5" [11/Oct/2023:12:31:43 +0300] "GET /3.1/lists/testlist(a)myproject.eu/config HTTP/1.1" 200 3111 "-" "GNU Mailman REST client v3.3.5" [11/Oct/2023:12:31:43 +0300] "GET /3.1/lists/testlist.myproject.eu/archivers HTTP/1.1" 200 100 "-" "GNU Mailman REST client v3.3.5" [11/Oct/2023:12:31:51 +0300] "GET /3.1/lists/testlist.myproject.eu HTTP/1.1" 200 425 "-" "GNU Mailman REST client v3.3.5" Oct 11 12:31:51 2023 (1534165) deque: do_confirm_verify Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/app/workflow.py", line 69, in __next__ return step() File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/app/subscriptions.py", line 382, in _step_send_confirmation raise StopIteration StopIteration [11/Oct/2023:12:31:51 +0300] "POST /3.1/members HTTP/1.1" 202 143 "-" "GNU Mailman REST client v3.3.5" [11/Oct/2023:12:31:51 +0300] "GET /3.1/lists/testlist.myproject.eu HTTP/1.1" 200 425 "-" "GNU Mailman REST client v3.3.5" [11/Oct/2023:12:31:51 +0300] "GET /3.1/lists/testlist(a)myproject.eu/config HTTP/1.1" 200 3111 "-" "GNU Mailman REST client v3.3.5" [11/Oct/2023:12:31:51 +0300] "GET /3.1/lists/testlist.myproject.eu/archivers HTTP/1.1" 200 100 "-" "GNU Mailman REST client v3.3.5" *Kyriakos Terzopoulos *Web developer / e-learning expert *Tel:*+30 211 213 9858 *Mobile:* +30 694 526 4512 * E-mail: *kyriakos.terzopoulos(a)gmail.com * Skype:* kyriakos.terzopoulos Find me on Facebook <http://www.facebook.com/cirrus3d> Follow me on Twitter <http://twitter.com/#%21/cirrus3d> On Wed, 11 Oct 2023 at 11:54, Odhiambo Washington <odhiambo(a)gmail.com> wrote: > On Wed, Oct 11, 2023 at 11:15 AM Kyriakos Terzopoulos < > kyriakos.terzopoulos(a)gmail.com> wrote: > > > Hi, > > > > I have set up (I believe successfully) and configured the following in a > > Virtualhost environment (with HestiaCP): > > > > - A record for lists.mydomain.com > > - Venv > > - Mailman core > > - Mailman web (run migrate, collectstatic, compress, compilemessages) > > Postorius > > - gunicorn, hyperkitty > > - Nginx > > - SMTP exim4 conf > > > > I can see Posrorius and I have logged in and created my first mailing > list: > > > > [image: Screenshot 2023-10-11 at 10.57.31 AM.png] > > > > My issue is that even though I have subscribed to my list as you can see > > above, I am not receiving the confirmation email. I get a "recipients > > refused" error. The smtp log for mailman is as follows: > > > > Oct 11 10:41:20 2023 (1533666) > > <169701007904.1534165.14569329382406660776@localhost> recipients > refused: > > {' > > kyriakos.terzopoulos(a)gmail.com': (550, b'Verification failed for > > <testlist-bounces+kyriakos.terzopoulos=gmail.com(a)myproject.eu > > >\nUnrouteable > > address\nSender verify failed')} > > > > Oct 11 10:41:20 2023 (1533666) > > <169701007904.1534165.14569329382406660776@localhost> smtp to > > testlist(a)myproject.eu for 1 recips, completed in 0.26796579360961914 > > seconds > > > > Oct 11 10:41:20 2023 (1533666) > > <169701007904.1534165.14569329382406660776@localhost> post to > > testlist(a)myproject.eu from > > testlist-confirm+c9b20c5290bec43147a7e96a6b8cd825daf913d7(a)myproject.eu, > > 1667 bytes, 1 failures > > > > Oct 11 10:41:20 2023 (1533666) > > <169701007904.1534165.14569329382406660776@localhost> delivery to > > kyriakos.terzopoulos(a)gmail.com failed with code 550, b'Verification > failed > > for <testlist-bounces+kyriakos.terzopoulos=gmail.com(a)myproject.eu > > >\nUnrouteable > > address\nSender verify failed' > > > > I have used the configuration for exim that is here > > < > > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > > > > > and > > I have also tested with the alternative approach that is documented in > > > > What do you have in the Exim's mainlog? > > > -- > 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] > _______________________________________________ > 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 kyriakos.terzopoulos(a)gmail.com >

2 years, 5 months

Re: Easiest way to install a new mailman3 deployment?

by Stephen J. Turnbull

ieso(a)johnwillson.com writes: > Here's an interesting suggestion I received that I'm going to kick > around a bit.. has anyone tried using Ansible to assist the > installation process? > > https://github.com/rivimey/ansible-mailman3 rivimey is very competent. That would undoubtedly be a good place to start. However, her setup may be more complicated than most folks need (IIRC, she has a multi-homed setup with Mailman core, Postorius, and HyperKitty on three separate IPs on a separate subnet in the DMZ, while Mailman was really designed for three Mailman applications running on the same host, along with the database server and MTA). > I hadn't heard of Ansible before, but it looks perfect for this > kind of situation. By the way: Ansible is not the only such application, but a Friend of Mailman used to work there (I think he's since been transferred elsewhere after they got acquired by RedHat), so if people want to work on this kind of thing, we may have more resources vs. Ansible than say Chef or Puppet. I'm not sure we want to maintain an Ansible configuration, but I imagine we could stick it in contrib as "an example that works for somebody YMMV unsupported NO WARRANTY". :-) Steve

5 years, 3 months

Re: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Mark Sapiro

On 5/24/24 2:18 AM, marcus--- via Mailman-users wrote: > > The problem, however, is that it does not send out any mails, nor do they appear in the archive. > > When I look in the Mailman-Log I find: > > May 16 01:44:55 2024 (6833) Cannot connect to SMTP server localhost on port 25 This is a misleading error message. It can occur when Mailman's out runner can't read a template. You need to check ownership and permissions on mailman/templates in the code tree and Mailman's var/templates directory which probably has permissions errors from running inport21 as root. Also, if you've set any templates in Postorius, they may not be accessable if your setting for POSTORIUS_TEMPLATE_BASE_URL is not good. > May 16 01:48:15 2024 (61252) error opening connection to nntp_host: localhost > [Errno 111] Connection refused > May 16 01:48:15 2024 (61252) NNTP error for list vereinsmitglieder(a)ludothek.de: > [Errno 111] Connection refused Are you gating messages to/from usenet for this list? If so, you have to set host: and port: and maybe user: and password in the nntp section of mailman.cfg -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

Unable to update templates

by Mark

Hi, I'm unable to update the custom welcome template (list:user:notice:welcome) after it's initial creation. When the custom welcome template is created (in Postorius), and a user then subscribed by the list-owner (using mass subscribe), the welcome message is received as expected. However when I update the template, the databases are updated correctly but the Welcome message is still sent with the old template content. mailman.templates mailmanweb.postorius_emailtemplate Additionally, if I delete the template and create a new one the old content still gets sent. I cannot find where this content is written or is being cached. Any clues on tracking this bugbear down gratefully received. Regards, Mark $ mailman info GNU Mailman 3.3.9 (Tom Sawyer) Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] config file: /etc/mailman3/mailman.cfg db url: postgresql://******:******@localhost/mailman devmode: DISABLED REST root url: http://localhost:8001/3.1/ -- Installed with venv. ===================== Query to DB - mailman ===================== SELECT URI FROM TEMPLATE WHERE NAME = 'list:user:notice:welcome' AND context = 'testlist.example.com'; ====================== Result (all directories and file owned by 'mailman' with '765' permissions) ====================== file:///templates/list/testlist.example.com/list:user:notice:welcome ====================== Content of above Welcome file ====================== This is the second test Welcome message. ====================== Text of the welcome message actually received. (It's the content of the first custom template.) ====================== This is the first test message to Welcome new members.

10 months, 1 week

Re: default language ignored

by Mark Sapiro

On 10/02/2017 05:46 AM, Marc Sluiter wrote: > Hi, > > one last question for now: how do switch the language of the mails sent by mailman? > I have this in my configuration, but without effect: > > [language.de] charset: iso-8859-1 > [language.de] description: German > [language.de] enabled: yes > > [mailman] default_language: de It has no effect because there are as yet no translations in Mailman 3. You need to create templates in the desired language. See <http://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/templates.html> That refers to setting URLs for templates which does work, but the easiest way is to put them in the default search path in Mailman's file hierarchy at $var-dir/templates/. Sitewide ones in $var-dir/templates/site/, Domain specific in $var-dir/templates/domains/ and list specific ones in $var-dir/templates/lists/. For example, a list specific, English language regular (non-digest) message footer might go in $var-dir/templates/lists/mymaillist.example.com/en/list:member:regular:footer > Is it also possible to change the language for a single list? Yes, although that is not yet exposed in Postorius. The list has a preferred_language attribute which you can set via REST or 'mailman withlist' aka 'mailman shell'. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 6 months

Re: list of subscribers

by Mark Sapiro

On 02/04/2018 11:37 AM (UTC -0800), Peter Münster wrote: > On Sun, Feb 04 2018, Simon Hanna wrote: > >> 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. This would seem to be specific to your use case. I think in general what we would want to display is the display_name from the list's member record. > Off topic: I have "Receive own postings = Yes", but I don't receive > copies of my postings to this list... We tried to send your copy of your post to you, but your MTA called it spam. Feb 4 19:38:09 mailman postfix/smtp[29085]: 89D4C8031E: to=<pmlists(a)free.fr>, relay=mx1.free.fr[212.27.48.7]:25, delay=1.3, delays=0.04/0/0.81/0.41, dsn=5.0.0, status=bounced (host mx1.free.fr[212.27.48.7] said: 550 spam detected (in reply to end of DATA command)) (time stamp is UTC -0000) I suspect it doesn't like the fact that it's From: you but not sent by your server. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 2 months

Re: nginx configuration on a multitasking server

by Mark Sapiro

On 12/22/21 7:54 PM, David Newman wrote: > On 12/22/21 7:29 PM, Mark Sapiro wrote: > >> This looks like a uwsgi issue as discussed at >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… >> although that's with apache and not nginx so it may not be. > > If I'm reading the thread correctly, it's Apache workarounds to an > underlying Debian issue, so I agree it may not apply with nginx. I think you're correct that it doesn't apply to nginx, but the symptom is not the same. It is not a Debian issue per se. It is an Apache change that got installed with a Debian update, but the underlying issue is with Apache. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > There are 260 files named 'urls.py' under /opt/mailman, mostly for > socialaccount stuff. > > Where does that change go? All files? Or just this one: > > /opt/mailman/venv/lib/python3.9/site-packages/postorius/urls.py Not that one. The one whose content looks like https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/urls.py. It is probably in the same directory as your Django settings. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

Mailman 3 MFA with django-allauth[mfa]

by Liam Reilly

Has anyone successfully got MFA working in Mailman 3 with django-allauth[mfa]? I'm struggling to get it working with the limited documentation I could find. (https://docs.allauth.org/en/dev/mfa/index.html) If signed in as a user, I can browse to /accounts/2fa/ to activate MFA, but I was hoping to make it a mandatory part of the Sign Up process. Is there something that needs to be done with the URLs somewhere? This list site is an example of how I'd like it to work: https://mailing-lists.imperial.ac.uk/ Here is what I added to settings.py: #---------------------------------------- INSTALLED_APPS= ['hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'django.contrib.humanize', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.mfa', 'allauth.socialaccount'] # Specifies the adapter class to use, allowing you to alter certain default behaviour. MFA_ADAPTER = "allauth.mfa.adapter.DefaultMFAAdapter" # Used to override forms. Defaults to: MFA_FORMS = { 'authenticate': 'allauth.mfa.forms.AuthenticateForm', 'reauthenticate': 'allauth.mfa.forms.AuthenticateForm', 'activate_totp': 'allauth.mfa.forms.ActivateTOTPForm', 'deactivate_totp': 'allauth.mfa.forms.DeactivateTOTPForm', } MFA_RECOVERY_CODE_COUNT = 10 MFA_TOTP_PERIOD = 30 MFA_TOTP_DIGITS = 6 #---------------------------------------- Thanks.

5 months, 1 week

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

by Mark Sapiro

On 11/11/22 16:36, Caballero, Danny (Dan) wrote: > 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? That's 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 assuming the docker container installation also had all the lists/users? It seems this must be related to a large number of lists/users and we must be doing a number of queries that doesn't scale well. This seems excessive. We'll have to look at the processing to see what we're doing. There have been some recent improvements in scaling. What Mailman core version is this? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

Mailman-users search results for query "Postorius"