Search results for "Postorius" - Mailman-users

Re: How to delete non-users

by Allan Hansen

Hi Mark, Thank you for looking into it. We are very strict about memberships, which we are because of spam, bots and malicious contributors and because we don't want anyone to think that our lists are used for spam: When a user applies, the server sends a message to the moderator. The moderator communicates with the potential member and accepts or does not accept the application. At this point, if the user has not been accepted, but tried to send a message to the list, a non-member membership is created. When he/she logs in to list his/her account, the list to which he/she holds non-memberships will be listed and the user will think that he/she has been properly subscribed (why else are the lists listed). Noone notices the column that shows the role as 'nonmember.' So he/she thinks that the subscription request has been accepted, but nothing is working. That's why the 'non-member' record is an issue. I also don't see why non-members are automatically added, filling up the database with junk (at least from our point of view, with all respect). But our lists don't accept messages from non-members. Such messages are quietly discarded, as most are spam, as mentioned above. So now the user is neither getting emails from the lists nor is unable to send messages to the list. The next step for the user is to complain to me. ☹ I have looked for a template that could be used to warn someone when he/she is added as a non-member, but did not find one. It's also not clear that I'd want one, as most of these non-subscriptions are by spammers and I prefer not to reply to spammers. __ I tried your suggestion below, Mark. Here's my transcript: ********** 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. >>> lm = getUtility(IListManager) >>> for l in lm: ... for nm in l.nonmembers.members: ... nm.unsubscribe() ... >>> ********** I did this twice, once with commit() and once typing ctrl/d (ctrl/D) just gave me a beep. Calling commit() did not return to the ... as in your example, but showed the >>> prompt, so I tried ctrl/D (beep) and then ctrl/d (exit). I then went to the Postorius page for one of the lists and found that all the non-members were still present. Yours, Allan On 9/16/22, 15:01 , "Mark Sapiro" <mark(a)msapiro.net> wrote: On 9/16/22 11:19, Allan Hansen wrote: > Hi all, > > This is a bit of an emergency: > > I am getting a bunch of complaints from potential list members of my lists that they can't subscribe and they don't get messages. Apparently, the issue is that they are non-members. I have never created any non-members but looking at the docs it seems that if someone sends a message to the list, they automatically become non-members. > For individuals I have been able to delete their non-membership and they then could subscribe properly. I don't understand. the fact that an address is a non-member of a list should not impact subscribing that address as a member. > I have looked at some of my most popular lists and they have hundreds of non-members! It will take me an awful amount of time to remove each one manually, and not doing it - handling each as they complain - is also a lot of waste of time and cause of frustration for all involved. What is actually happening when the non-member attempts to subscribe as a member? What do they do and what it the result? > I have tried scripting it with delmember, but it does not take the '-r nonmember' option ('findmember' does!). > > Can anyone help me find out how to > a. delete all non-members of all my lists If you have access to `mailman shell` you could do: ``` $ mailman shell 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. >>> lm = getUtility(IListManager) >>> for l in lm: ... for nm in l.nonmembers.members: ... nm.unsubscribe() ... >>> commit() ``` > b. prevent MM3 from creating new non-members in the future (so I don't have to keep removing them) nonmembers are an integral part of Mailman 3's architecture. The basic idea is a nonmember has a moderation action and setting a nonmembers moderation replaces MM 2.1's adding that address to one of *_these_nonmembers (The legacy *_these_nonmembers attributes still exist, but only to support regexps). It would require extensive modification to not create nonmembers. However, I still don't understand why the presence of a nonmember record is an issue. -- 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/

2 years, 8 months

Re: Message does not appear in archive

by Paul Arenson

> It's of course up to you, but I recommend Mailman 3. There are still > some rough edges, and there are a number of settings not yet exposed in > Postorius, but we are working on it and it is quite usable today. Thank you, Mark. My thoughts now. I have used nothing but MM for ages so will wait…. And it would require less convincing for the two groups I host > > Which is why upgrading from Mailman 2 to 2 still seems like the best idea. > Do you mean Mailman 3? OOPS!! yes. > I suspect it will be some time before Cpanel offers Mailman 3. It is > fairly straightforward to migrate an existing Mailman 2.1 list and it's > archives to Mailman 3, but it requires access to the underlying Mailman > 2 file system which you may not have in a hosted cPanel environment. > > See <http://docs.list.org/en/latest/migration.html> for more on migration. Thanks. I had a look just now. I suspect we won’t worry about broken URL links. Most people check archives to try to keep track of a conversation. With difficultly now, but much easier in MAILMAN 3. And going forward, they might just be motivated to post from the archives!!!! (As I am now doing!!!) The rest of the upgrade procedures are pretty much lost on me (not having done this kind of thing before), so either I wait or pay someone who might be willing to do it. (Assuming there is a someone and assuming it can be done in my CPanel environment) Also, this particular account is hosted by an educational NPO, so they may have restrictions. I will ask them if it is possible. Thanks! Paul

6 years, 9 months

Re: MM3 templates

by Odhiambo Washington

On Wed, Feb 15, 2023 at 6:35 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/15/23 05:22, Odhiambo Washington wrote: > > > > 1. Where is this template that the system used and can I edit it? > > > /opt/mailman/mm/venv/lib/<python_version>/site-packages/mailman/templates/en/list:user:action:subscribe.txt > > You can edit it, but your edits will be overwritten if you upgrade. > I will not touch that. > > 2. Why is it not using the template I created? > > Is the template you placed in > /opt/mailman/mm/var/templates/lists/kictanet.lists.kictanet.or.ke/en/ > named list:user:action:subscribe.txt and does Mailman have permission to > read it? > Yes. [18:47 ~ ]$ ls -al /opt/mailman/mm/var/templates/lists/ kictanet.lists.kictanet.or.ke/en/ total 48 drwxr-xr-x 2 mailman mailman 512 Feb 14 08:53 . drwxr-xr-x 3 mailman mailman 512 Feb 14 08:54 .. -rw------- 1 mailman mailman 615 Jan 17 13:57 domain:admin:notice:new-list.txt -rw------- 1 mailman mailman 341 Jan 17 13:54 list:admin:action:post.txt -rw------- 1 mailman mailman 158 Dec 17 13:32 list:member:digest:footer.txt -rw------- 1 mailman mailman 452 Jan 17 13:54 list:member:digest:masthead.txt -rw------- 1 mailman mailman 137 Jan 17 13:55 list:member:generic:footer.txt -rw------- 1 mailman mailman 1219 Dec 8 15:12 list:member:regular:footer.txt -rw------- 1 mailman mailman 944 Jan 17 15:50 list:user:action:subscribe.txt -rw------- 1 mailman mailman 247 Jan 17 13:56 list:user:notice:post.txt -rw------- 1 mailman mailman 802 Jan 17 13:56 list:user:notice:probe.txt -rw------- 1 mailman mailman 639 Jan 17 13:57 list:user:notice:welcome.txt > Did you try to create a template in Postorius? If you did, that one will > take precedence. > Not at all. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 3 months

Re: Invalid confirm text

by Mark Sapiro

On 8/14/20 3:28 AM, w.schoener(a)alp.dillingen.de wrote: > > Now, when I try to subscribe to the list, I get my first message in german language, with the confirm request: > return the message unchange. > > When I return the message, I get an answer: > Invalid confirm text. With current releases of Mailman, the confirm request you receive should be: From: <listname>-confirm+<hex-token>@<list.domain> Subject: confirm <hex-token> with actual values for <listname>, <hex-token> and <list.domain>. This will change in Mailman 3.3.2, see <https://gitlab.com/mailman/mailman/-/merge_requests/678> > My request is pending. And there is no way to solve this pending request, in the webinterface, no subscription request is shown, no member is shown and no no-member is shown. Your reply should go to <listname>-confirm+<hex-token>@<list.domain>. Some MTA/MDA in the delivery chain may drop the ++<hex-token> suffix. If this is the issue, you can send a message with the one line confirm <hex-token> as either the Subject or body of the message to <listname>-request@<list.domain>. That should work. Note in the web UI (Postorius), at least in recent versions, even though it shows "Subscription requests 0" that should be a pull-down with the two choices Pending Approval and Pending Confirmation and selecting Pending Confirmation should show yours. The count badge only counts Pending Approval. > Have you any hint, what is going wrong. What do I have to respect to create a message, where the confirmation is working. See the current English confirmation template at <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/templates/en/l…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

Re: Apache Conf

by Thomas G

I found ! Based on https://stackoverflow.com/questions/26848945/exclude-an-alias-from-virtualh… We have to exclude /static/ <VirtualHost *:80> ServerName mailing.hatlab.fr ErrorLog ${APACHE_LOG_DIR}/mailing.error.log CustomLog ${APACHE_LOG_DIR}/mailing.access.log combined Alias /static/ /opt/mailman/static/ <Directory /opt/mailman/static/> Require all granted </Directory> ProxyPassMatch ^/static ! ProxyPass / http://localhost:8000/ ProxyPassReverse / http://localhost:8000/ </VirtualHost> Le ven. 19 oct. 2018 à 21:08, Thomas G <thomas82710(a)gmail.com> a écrit : > Same result with Alias "/static/" "/opt/mailman/static/" > > I have sometimes: > [Fri Oct 19 22:05:52.583841 2018] [proxy_http:error] [pid 8328:tid > 140435053815552] (104)Connection reset by peer: [client 1xxxxxxx1794] > AH01102: error reading status line from remote server localhost:8000 > [Fri Oct 19 22:05:52.583874 2018] [proxy:error] [pid 8328:tid > 140435053815552] [client 1xxxxxxx:51794] AH00898: Error reading from remote > server returned by /static/hyperkitty/libs/jquery/jquery-1.10.1.min.js > But it's not systematic. > > Alias seem to be ignored by the proxy. > > > Le ven. 19 oct. 2018 à 20:48, Mark Sapiro <mark(a)msapiro.net> a écrit : > >> On 10/19/18 12:17 PM, Thomas G wrote: >> > Hi tried both. >> > >> > Same result. >> > >> > xxxx - - [19/Oct/2018:21:14:22 +0200] "GET >> /static/postorius/js/script.js >> > HTTP/1.1" 404 4051 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) >> > Gecko/20100101 Firefox/60.0" >> >> >> What's in the apache error log? >> >> -- >> 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/ >> >

6 years, 7 months

Re: Cannot setup announce-only mailing list

by Abhilash Raj

On Thu, Jan 30, 2020, at 9:58 AM, Mark Sapiro wrote: > On 1/30/20 5:42 AM, Alberto Granzotto wrote: > > > > Of course, I want to keep this mailing list "read only" for members, and > > I want only selected people to post to that mailing list. > > > > Any idea on how to achieve that? > > > There is only one difference between the `Discussion` and `Announce` > list styles, and that is for an `Announce` list, the `allow_list_posts` > attribute is set to `False`. In turn, all that does is cause the > List-Post: header to be set to NO rather than the list posting address. > > There is a discussion at <https://wiki.list.org/x/4030685> of how to set > up an announce list for Mailman 2.1. Most of this translates > straightforwardly to Mailman 3, although not all the relevant settings > are exposed in Postorius. > > In short, you need to set this up manually using things like moderation > settings and custom templates for the welcome message. Mark, do you think we should make the actual announce-only style reflect these settings so folks don't have to manually set these after they create a announce-only list? I am not sure the reason behind these settings lacking for the current announce-only style. Are there situations where announce-only list would have different list setting? > > -- > 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/ > -- thanks, Abhilash Raj (maxking)

5 years, 4 months

Re: Please help - Held message is crashing mailman.

by Alex King

Thanks for your help Mark, it's ideal having the pointer to the issue in gitlab. I'll raise a bug with Ubuntu because this makes mailman3 in their LTS version unusable for me. Perhaps they can backport a fix for their version in LTS, otherwise they may have a backport or PPA source where I can get a 3.2 version, or just pin some packages from cosmic or disco. I think documenting this will be useful to people who hit the issue in future (Bionic/18.04 is supported until 2023, and likely the most used until 20.04 is released). Thanks, Alex On 7/04/19 4:29 AM, Mark Sapiro wrote: > On 4/5/19 10:27 PM, Alex King via Mailman-users wrote: >> Hi, >> >> I've used mailman a lot in the past, and decided to install mailman3 in >> a recent install. I'm unimpressed so far, it seems buggy. >> >> Running on Ubuntu 18.04.2 LTS from packages, mailman3 3.1.1-9, >> mailman3-web 0+20170523-14, python-django-postorius 1.1.2-3. >> >> After a few messages, I now can't go to the "Held Messages" in >> postorius, I get a 500 error. >> >> I tried to interact on the command line, but could not work out how. >> Reading >> https://mailman.readthedocs.io/en/latest/src/mailman/docs/install.html >> and >> https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/shell.ht…, >> I tried: >> >> # mailman shell >> Welcome to the GNU Mailman shell >> >>>>> command = cli('mailman.commands.cli_withlist.shell') >> Traceback (most recent call last): >> File "/usr/lib/python3.6/code.py", line 91, in runcode >> exec(code, self.locals) >> File "<console>", line 1, in <module> >> NameError: name 'cli' is not defined >> >> I did a lot of reading of the manual and googled, but I have no idea >> where the cli object is supposed to come from.....? The documentation >> is confusing. > > The line > > command = cli('mailman.commands.cli_withlist.shell') > > in > <https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/shell.ht…> > is dependent upon some behind the scenes setup to make the doctests > work. Granted this is confusing, but basically all that does is set > things up for the doctests to run the 'mailman shell' command. It is not > intended to be run from within 'mailman shell'. > > >> Anyway, after some trial and error, i found: >> >> # mailman shell >> Welcome to the GNU Mailman shell >>>>> list_manager = getUtility(IListManager) >>>>> m=list_manager.get("committee(a)[redacted].org") >>>>> from mailman.interfaces.requests import IListRequests >>>>> requests = IListRequests(m) >>>>> [x for x in requests.held_requests][0].id >> 8 >>>>> requests.get_request(8) >> Traceback (most recent call last): >> File "/usr/lib/python3.6/code.py", line 91, in runcode >> exec(code, self.locals) >> File "<console>", line 1, in <module> >> File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", >> line 85, in wrapper >> return function(args[0], config.db.store, *args[1:], **kws) >> File "/usr/lib/python3/dist-packages/mailman/model/requests.py", line >> 120, in get_request >> result.data_hash, expunge=False) >> File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", >> line 85, in wrapper >> return function(args[0], config.db.store, *args[1:], **kws) >> File "/usr/lib/python3/dist-packages/mailman/model/pending.py", line >> 138, in confirm >> value = json.loads(keyvalue.value) >> File "/usr/lib/python3.6/json/__init__.py", line 354, in loads >> return _default_decoder.decode(s) >> File "/usr/lib/python3.6/json/decoder.py", line 339, in decode >> obj, end = self.raw_decode(s, idx=_w(s, 0).end()) >> File "/usr/lib/python3.6/json/decoder.py", line 355, in raw_decode >> obj, end = self.scan_once(s, idx) >> json.decoder.JSONDecodeError: Unterminated string starting at: line 1 >> column 1 (char 0) >> >> It seems something was written out to disk that can't be read in for >> some reason (assuming a json object on disk?) > > This is <https://gitlab.com/mailman/mailman/issues/385> which should be > fixed by <https://gitlab.com/mailman/mailman/merge_requests/333>. The > fix in in Mailman core version 3.2.0 > > >> How do I debug this further? How do I find the json being decoded? Any >> help would be appreciated. (I found mailman2 just worked, I was happy >> with that.) > > The issue is in storing a pickled representation of the json encoding of > 'rule_misses'. This gets very long if you have lots of header filters, > and with at least the mysql backend gets truncated in the database which > causes the Unterminated string error. > > I'm not sure what your options are for upgrading. The current Debian > packages are all >= 3.2.0 [1], but Ubuntu doesn't get 3.2.0 until cosmic > (18.10) [2]. > > [1] https://packages.debian.org/search?keywords=mailman3 > [2] https://packages.ubuntu.com/search?keywords=mailman3 > >> (My colleague posted a bug about this I believe but I don't have the >> link to that.) > > I haven't seen it. > >

6 years, 2 months

Hyperkitty archive: date format in thread overview of list does not honor DATETIME_FORMAT of settings.py

by Christian Schneider

Dear mailman community, with the help of you I was able to set up a new mailman3 environment (a big THANK YOU!!! :-)): OS: Ubuntu 24.04-LTS mailman: GNU Mailman 3.3.10 (Tom Sawyer) Python: 3.12.3 (main, Feb 4 2025, 14:48:35) [GCC 13.3.0] Method: Python Virtual Environment Installation My configuration files are placed in the following directory: /etc/mailman3 - gunicorn.py - mailman.cfg - settings.py The environment is up and running: A list for testing is set up and mails are transfered (and archived) using the test-list - successfully... :-) Looking at the thread overview of the list (in Hyperkitty archives) I realized that the shown date format is unusual (for Germany), like: Do Mai 22, 3:57 nachm. (meaning: Thu May 22, 3:57 p.m.) I would prefer a format like: 22-05-2025 15:57:24 So I tried to reconfigure this setting in settings.py according to this URL: https://docs.mailman3.org/en/latest/config-web.html#configure-postorius-hyp… In settings.py I set DATETIME_FORMAT to 'd-m-Y H:i:s' but the format did not change. (After changing settings.py I initiated a restart of mailman3 and mailmanweb) I also set USE_L10N to False as suggested in Django-Docs: https://docs.djangoproject.com/en/3.1/ref/settings/#std:setting-DATETIME_FO… My /etc/mailman3/settings.py is parsed - as far as I can say because changing USE_I18N to false (in /etc/mailman3/settings.py) switches date to English as this is my locales-setting on Ubuntu... Nevertheless the format stays the same (in this case: Thu May 22, 3:57 p.m.) How can I adjust the date format (in the discussion boxes) at the thread overview page (url: https://my-domain.de/archives/list/test-list@lists.my-domain.de/)? Any hint is appreciated! Thank you very much and kind regards Christian

2 weeks, 2 days

Re: Automatic migration from Mailman 2.1 (Debian buster) to Mailman 3 (Debian bookworm)

by Marc SCHAEFER

Hello, On Sat, May 25, 2024 at 11:38:40AM -0400, Mark Sapiro wrote: > The host name displayed in the web UI is based on the SITE_ID setting in > Django's settings. This is a system configuration not associated with any > lists. it references an entry in the django_sites table in the database. Thank you, will look into this. > As far as the comment/display name in From: is concerned, what specific > emails are you talking about? This. Sorry, I mixed From: with Subject: and the content: Date: Sat, 25 May 2024 13:37:29 -0000 From: postorius(a)lists2.alphanet.ch To: schaefer@XXX Subject: [example.com] Please Confirm Your E-mail Address Hello from example.com! You're receiving this e-mail because user Schaefer-XXX has given your e-mail +address to register an account on example.com. To confirm this is correct, go to [ ... ] Thank you for using example.com! example.com I guess it's the same SITE_ID setting in Django's DB: $ grep SITE_ID /usr/share/mailman3-web/settings.py SITE_ID = 1 However, I guess it's the default creation, by the Debian package, of the SQLite local database which presumably was done with example.com. I will anyway switch to a remote PostgreSQL database, and thus create a new one with the correct names. That should fix it. > for ADMINS in your Django settings. ADMINS = ( ('Mailman Suite Admin', 'schaefer(a)alphanet.ch'), ) That looks correct. > The `mailman import21` command will properly import the Mailman 2.1 > from_is_list and Sender filters -> dmarc_* DMARC mitigation settings. Thank you. Aka mailman-wrapper import21 on Debian so to switch to the correct user. > If you have some customization in this area, that probably won't be handled. Obviously.

1 year

Re: Problems with mailman core translation and other details

by Mark Sapiro

On 2/7/24 12:47, Celi via Mailman-users wrote: > yes. thank you for asking. > > > > Em 07/02/2024 16:46, Mark Sapiro escreveu: >> On 2/6/24 2:41 PM, celi--- via Mailman-users wrote: >>> It´s the case below: the pair msgid/msgstr seems to be OK, but this >>> particular sentence is not being translated. >>> >>> #: templates/postorius/lists/summary.html:88 >>> #, python-format >>> msgid "" >>> "\n" >>> " To subscribe you can send an email with 'subscribe' >>> in the" >>> "subject to\n" >>> " <a href=\"mailto:%(address)s?subject=Subscribe\">" >>> "%(address)s</a>\n" >>> " or use the form below:\n" >>> "" ... >> >> >> Is the rest of that page translated appropriately? There is a possible issue with msgid "" "\n" " To subscribe you can send an email with 'subscribe' in the" "subject to\n" " <a href=\"mailto:%(address)s?subject=Subscribe\">" "%(address)s</a>\n" " or use the form below:\n" "" it should be msgid "" "\n" " To subscribe you can send an email with 'subscribe' in the " "subject to\n" " <a href=\"mailto:%(address)s?subject=Subscribe\">" "%(address)s</a>\n" " or use the form below:\n" Ignore the folded line, but note the trailing space in " To subscribe you can send an email with 'subscribe' in the " If that's the issue it is with the Debian package. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

Mailman-users search results for query "Postorius"