Search results for "2021" - Mailman-users

Re: Message-Footer after migrating to Mailman3

by Stephen J. Turnbull

Peter Münster writes: > On Mon, May 24 2021, Mark Sapiro wrote: > > var/templates/site/de/list:member:generic:footer.txt Note "de" in the above. > I have created an empty file > /var/lib/mailman/templates/site/en/list:member:generic:footer.txt Do you really mean "en"? If the user's primary language setting is de, I presume /var/lib/mailman/templates/site/de/list:member:generic:footer.txt will override /var/lib/mailman/templates/site/en/list:member:generic:footer.txt Steve

2 years, 10 months

EMWD/Affinity/Empathy in 2023

by jaboyib556＠v3dev.com

Hi all, We're exploring Mailman 3 and the custom interfaces provided by EMWD's Affinity and Empathy look very interesting: https://www.mailmanhost.com/affinity-mailman/ However, I saw reports of EMWD being a one-man show and the owner sadly passing away in 2021; but I've also seen threads here referring to the Affinity and Empathy projects in 2022. It wasn't clear to me if EMWD is still an active business and Affinity and Empathy are still active offerings. Does anyone here have any direct contact/relationship/experience with EMWD/Affinity/Empathy following the owner's passing? Or knowledge of any other offerings publicly available today that are similar to Affinity/Empathy? Thanks!

2 years, 5 months

Re: Sad news - Brian Carpenter

by Mark Dadgar

On May 12, 2021, at 12:45 PM, smorytko(a)gmail.com wrote: > https://www.tributearchive.com/obituaries/21066847/Brian-Keith-Carpenter/wa… > > I mentioned some "unfortunate circumstances" in a recent post. An inquiry from Mark Sapiro prompted me to do a search and I sadly found this. > > Brian's company managed our list and on 4/22 we became aware that he was hospitalized with Covid. > > Rest in peace Brian. That’s awful. Brian was a great help to me in setting up a solid MM3 installation after my mess of a self-install and he’s been a constant source of assistance on this list. RIP Brian. 😞 - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 1 month

Re: statistics monitoring for Mailman3

by Seth Seeger

> On Mar 12, 2021, at 12:10 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 3/11/21 8:05 PM, Mark Sapiro wrote: >> >> The data are in Mailman's smtp.log, but I'm not aware of anyone who's >> written anything to analyze it. It would be fairly easy to do depending >> on exactly what you want. > > > You inspired me. See <https://www.msapiro.net/scripts/smtp_report>. I get the following error: File "./smtp_report", line 44 print(f' {lname}: {tot}') ^ SyntaxError: invalid syntax I'm running python3 (3.5.3), and I'm afraid I don't know enough python to know what's wrong. Thanks, Seth

4 years, 3 months

Re: Upgrade commands under Docker

by Abhilash Raj

> On Oct 26, 2021, at 10:36 AM, Seth Seeger <seth(a)tofutavern.com> wrote: > > Another docker upgrade question... according to the upgrade docs > > https://docs.mailman3.org/en/latest/upgrade-3.2.html#post-upgrade > > you are supposed to stop the web service and run a series of commands (compress/collectstatic/etc). How do you stop the service under Docker? If I stop the container, then I cannot access the manage.py command. Docker will run all the commands you find in the documentation when the container starts up. The process needs to be documented there, but it is essentially as describe in this issue’s description: https://github.com/maxking/docker-mailman/issues/293 -- thanks, Abhilash Raj (maxking)

3 years, 8 months

Re: Subscription request cannot be moderated: 404 Not Found

by Eric Broens

Hi Mark, Unfortunately the provided options didn't work out either: 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 ************* mailing list >>> ISubscriptionManager(m).confirm('4d6b4b11266c7332684c5a492eb3f92c531f761b') Traceback (most recent call last): File "<console>", line 1, in <module> File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/subscriptions.py", line 578, in confirm workflow.restore() File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/workflow.py", line 142, in restore raise LookupError(self.token) LookupError: 4d6b4b11266c7332684c5a492eb3f92c531f761b I noticed that the mail address was also listed as a non-member. After deleting it there, I could not accept the subscription either. Next, I have rejected the subscription and added it using the mass subscription option in the WebUI. I'll monitor if such cases will happen again. Thanks,Eric On Saturday, January 16, 2021, 06:05:19 PM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 1/16/21 7:49 AM, Eric Broens via Mailman-users wrote: > Hi Mark, > I can't find any log entry which indicate a problem with this subscription request. > The _request table does not contain a request for the specific mailinglist, but I am not sure if subscription requests are included in this table. It is unclear and confusing, but the requests are not in the _request table. See <https://gitlab.com/mailman/mailman/-/issues/768#note_415536043>. So this is normal. > The token is found in the pended table: > > +-----+------------------------------------------+---------------------+ > | id | token | expiration_date | > +-----+------------------------------------------+---------------------+ > | 115 | 4d6b4b11266c7332684c5a492eb3f92c531f761b | 2031-01-04 16:17:38 | > +-----+------------------------------------------+---------------------+ > > These are the relevant entries in the pendedkeyvalue table: > +------+--------------+-------------------------------------+-----------+ > | id | key | value | pended_id | > +------+--------------+-------------------------------------+-----------+ > | 1130 | type | subscription | 115 | > | 1131 | list_id | "********************" | 115 | > | 1132 | email | "***********************@*********" | 115 | > | 1133 | display_name | "" | 115 | > | 1134 | when | "2021-01-06T16:17:38" | 115 | > | 1135 | token_owner | "moderator" | 115 | > +------+--------------+-------------------------------------+-----------+ > > Can I workaround this problem for this specific subscriber by adding entries in the _request table, and if so what do I need to add? Adding to the _request table won't help. Try confirming by emailing listname-confirm+4d6b4b11266c7332684c5a492eb3f92c531f761b(a)list.domain You could also try confirming via mailman shell mailman shell -l list.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 list.example.com mailing list >>> ISubscriptionManager(m).confirm('4d6b4b11266c7332684c5a492eb3f92c531f761b') Traceback (most recent call last): File "<console>", line 1, in <module> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.3b1-py3.7.egg/mailman/app/subscriptions.py", line 570, in confirm raise LookupError LookupError In my case, I get the LookupError because the token doesn't exist, but I think it should work for you. -- 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/

4 years, 5 months

Re: at the finish line of mailman3 docker, but can't sign in.

by John Covici

I have a couple of questions about the container, if its OK. First, it says to run you create the directory /opt/mailman/mailman-core and /opt/mailman/mailman-web and then do the git clone. What directory should the git clone be in? A couple of more questions -- is there a way to install the web server and the mta in the container, this way I could make the whole thing be independent of my host configs? On Fri, 30 Jul 2021 16:04:48 -0400, bob B wrote: > > is this the info you need for the container version > > [root@..... docker-mailman]# docker ps > CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES > 30af82ac9315 maxking/mailman-web:0.3 "docker-entrypoint.s…" 2 hours ago Up 2 hours 127.0.0.1:8000->8000/tcp, 127.0.0.1:8080->8080/tcp mailman-web > cd01a99cf908 maxking/mailman-core:0.3 "docker-entrypoint.s…" 2 hours ago Up 2 hours 127.0.0.1:8001->8001/tcp, 127.0.0.1:8024->8024/tcp mailman-core > 77fe89ced9e8 postgres:9.6-alpine "docker-entrypoint.s…" 2 hours ago Up 2 hours 5432/tcp dockermailman_database_1 > > > for smtp host > ------------ > cat /opt/mailman/web/settings_local.py > #allowed_hosts = ['127.0.0.1', 'localhost','HOST.DOMAIN.org'] > #ALLOWED_HOSTS = ['127.0.0.1', 'localhost','HOST.DOMAIN.org'] > ALLOWED_HOSTS = ['*'] > DEBUG = True > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'smtp.example.com' > EMAIL_PORT = 25 > --------------------------- > cat /opt/mailman/core/mailman-extra.cfg > # mailman-extra.cfg > > [mta] > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > # mailman-core hostname or IP from the Postfix server > lmtp_host: localhost > lmtp_port: 8024 > # Postfix server's hostname or IP from mailman-core > smtp_host: smtp.example.com > smtp_port: 25 > configuration: /etc/postfix-mailman.cfg > [mailman] > # This address is the "site owner" address. Certain messages which must be > # delivered to a human, but which can't be delivered to a list owner (e.g. a > # bounce from a list owner), will be sent to this address. It should point to > # a human. > site_owner: my_real_email_is_in_the_file.com > __________________________________ > > My docker most machine /etc/postfix/main.cf has > > transport_maps = > regexp:/opt/mailman/core/var/data/postfix_lmtp > local_recipient_maps = > regexp:/opt/mailman/core/var/data/postfix_lmtp > relay_domains = > regexp:/opt/mailman/core/var/data/postfix_domains > > > # Support the default VERP delimiter. > recipient_delimiter = + > unknown_local_recipient_reject_code = 550 > owner_request_special = no > > ------------------------------ > > > > is that correct? I leave them set to smtp.example.com because the will send out via the docker host machine, and so i ONLY have my actual outbound server listed in /etc/postfix/main.cf on the docker host machine, or do i need to replace smtp.example.com with our outbound server? > > > Also, If I want to blow away everything away (databse etcc) and rebuild it... what are those steps? > _______________________________________________ > 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/ > -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

3 years, 11 months

Global ban using regex

by Henrik Rasmussen

Using some regex testers and generators like https://regex101.com and https://www.site24x7.com/tools/regex-parser.html, the regex (.*)(a)inker\.azerbaijan\.su seems to match EVERYTHING(a)inker.azerbaijan.su (EVERYTHING is constantly changing in current spam mails). However, entering the regex to the Global Ban Add ban /postorius/bans/ result in: `An error occurred: Invalid Parameter "email": Expected a valid email address or regular expression, got (.*)(a)inker\.azerbaijan\.su.'` Same result when using [Ban list] in postorius/lists/[LISTNAME]/bans/. Entering a none regex addresses like eknejfj(a)inker.azerbaijan.su works fine. Does Mailman use a different regex syntax I am using GNU Mailman 3.3.4 (Tom Sawyer) and Mailman Core Python Version 3.8.10 (default, May 6 2021, 06:30:44) [GCC 9.3.0] (maxking/mailman-core:0.3 and maxking/mailman-web:0.3)

2 years

Re: Error on timeout vs retry values

by Andrew Hodgson

Abhilash Raj wrote: > On Aug 24, 2021, at 1:00 PM, Andrew Hodgson <andrew(a)hodgson.io> wrote: >> >> I just received the same error this evening when rebuilding Mailman3 on a new Debian 11 instal. There is a later version of Django on the new install. >> >> I got the original settings from the Mailman-Suite Gitlab project. I have made the modification but does this need to be made in that Gitlab project as well as that is where a lot of folks are getting their base Settings.py from? >I have just updated the mailman-suite gitlab project with this change. Thanks for doing this all working this end. Andrew.

3 years, 10 months

Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Mark Sapiro

Simon Coggins wrote: > On 7 Nov 2021, at 10:54 am, Mark Sapiro <mark@msapiro.netmailto:mark@msapiro.net> wrote: > I wound up taking a different approach. I check for other references to > the message in the message store and only delete the message if there > are none. The fix is at > https://gitlab.com/mailman/mailman/-/merge_requests/932/diffshttps://gitlab… > Oh nice. That seems like a sensible solution. Thanks for tackling so quickly. I’ll do some testing today and roll it out once testing is complete. I made a small change to defend against 'impossible' situations. See https://gitlab.com/mailman/mailman/-/merge_requests/933/diffs

3 years, 7 months

Mailman-users search results for query "2021"