Search results for "Postorius" - Mailman-users

Re: Internal Server Error: /mailman3/postorius/lists/.../held_messages - humanize: where to put?

by Flo

On 8/25/25 23:36, Mark Sapiro wrote: > On 8/25/25 12:42, Flo via Mailman-users wrote: >> Hi, >> >> I have setup in Debian Trixie mailman3-full and came that far, that I >> have created a mailing list. I can sent emails to the members. > > Your primary support resource for the Debian package is Debian. See > https://wiki.list.org/x/12812344 > That's right. > > You need to add 'django.contrib.humanize' to the INSTALLED_APPS list in > settings.py. If you Debian packages don't do this, it should definitely > be reported to Debian. > In /usr/share/mailman3-web/settings.py there is: INSTALLED_APPS = ( ... 'django.contrib.humanize', ... ) And POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8001' I think this has also something to do with it. But looks correct for me. Flo But maybe the path

3 months, 2 weeks

Re: How to change the language in mailman3

by Massimo Zappalà

Hi everyone, Debian buster run on my server. I installed the apt install mailman3-full package and configured it. Everything works fine. I'm trying to change the language (mailman3, postorius and hyperkitty) from English to Italian, but it's not clear what I'm missing. These are the files that I modified to try to set the Italian language: /etc/mailman3/mailman.cfg default_language: it --------------------------------------------------------------- /etc/mailman3/mailman-web.py LANGUAGE_CODE = 'it-IT' TIME_ZONE = 'Europe/Rome' USE_I18N = True USE_L10N = True USE_TZ = True --------------------------------------------------------------- /usr/lib/python3/dist-packages/django/conf/global_settings.py TIME_ZONE = 'Europe/Rome' USE_TZ = True LANGUAGE_CODE = 'it-IT' --------------------------------------------------------------- With this command, I set the Italian language to the list. It takes the setting, but it doesn't work sudo mailman shell -l test(a)pratico.work >>>m.preferred_language='it' >>>commit() >>>CTRL-D Can anyone tell me what I'm missing? Thank you in advance Max

5 years, 4 months

Re: django fake users

by Andrew Hodgson

Brian Carpenter wrote: >On 1/17/21 6:24 AM, Andrew Hodgson wrote: >> I don't think this would help the issue. What I am seeing here is users signing up through Postorius using the sign up option which then creates an account in Django (but not Mailman). Yesterday alone I had over 700 of these accounts created. I don't know whether they pass email confirmation or not (I don't see this in Django admin), however they don't get added as users in Mailman and they don't attempt to subscribe to any list. >You can select "Email Addresses" in Django. On the "Email Addresses" >page, select No under the By verified heading in the FILTER box. There you should see a list of unverified email/users. Thanks for that, was looking in the wrong place. The fake accounts currently in my system aren't actually being verified as I kind of expected. Andrew.

4 years, 10 months

Re: Can't Start Mailman3 Core on Fresh Install

by Jonathan Green

I've triple checked the password in mailman.cfg and used the same username/password directly in MySQL and was able to get to the mailman3 database. I did run a test script in python3 using the PyMySQL connector and got the same error. Is there some permissions issue I need to look for? I ran the install as user root - perhaps the user running the python script doesn't have access somehow? On Thu, Jul 21, 2022 at 7:48 AM Stephen J. Turnbull < stephenjturnbull(a)gmail.com> wrote: > Mail Person writes: > > > Hi Everyone. I'm installing Mailman3 on a Ubunu 18.03 server using > > MySQL as the backend. After installing using the mailman3-full > > package and configuring it, I'm getting the following error when > > trying to start the mailman3 service: > > > Jul 21 04:28:44 eps mailman3[81963]: > > sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) > > (1045, "Access denied for user 'mailman3'@'127.0.0.1' (using > > password: YES)") > > I would guess that the password doesn't match. This can happen > because some configuration is done with Python modules (.py files, the > configuration is Python code) where strings are *delimited* by quote > marks (which are not part of the value) and some (.cfg files) are > .ini-style, where all values are read as strings, and so quote marks > become part of the value. > > The web database (mostly user information) and the mailing list > database are separate (because not all Mailman installations use > Postorius and HyperKitty). Are you sure you have the right user and > password for the mailing list database configured in mailman.cfg? > > Other reasons would be in this reference: > > > Jul 21 04:28:44 eps mailman3[81963]: (Background on this error at: > > http://sqlalche.me/e/e3q8) > > > I'm not sure why the access issue is happening. Mailman3-web is > > running fine and I can see the site at mailman3/postorius/lists > > (but it says Page Not Found). > > "Page not found" is probably a consequence of the same access error. > You can probably see it in the database logs. > >

3 years, 4 months

About the path forward [was: ... regarding message acceptance]

by Stephen J. Turnbull

I'm not Mark, but .... :-) "Plans", you ask? Hmm.... Pawel Grzywaczewski writes: > Any plans to implement message acceptance based on another list? I think that most Mailman 2.1 features are plausible proposals for Mailman 3. While we don't make decisions based on user voting, we do care about user requests. If you want to make a formal request, post a request for enhancement (ie, issue) on our GitLab issue tracker, and post a link here so other interested people can follow it. > What about adding list1 as member to list2? In Mailman 2.1 there > was an 'umbrella' feature I think it doesn't exist in Mailman3. > Any plans to add it? Same as above. I don't know Mark's plans, but he's been active on these lists. I myself hope to have some time for development later in the summer, but I've been away from the code for quite a while, and have at least two prior projects I've expressed interest in. I have no idea about Abhilash or Terri's time, except that they're always busy, and there are a couple of other developers who might drift back in at some point if something exciting starts happening. However, these kinds of additions described above are somewhat more complicated in Mailman 3 than they were in Mailman 2. We have added the ability to identify groups of lists as domains (and therefore have multiple lists by the same name if they are each in a different domain), and the ability to identify groups of email addresses as users. This means that there are more opportunities for unfortunate things to happen. For example, a user might have a particular address for posting to a particular list, and be unhappy if they were accidentally "unmasked" when they posted by a different address, and that post was accepted because those addresses are both owned by the same user. Whether you think this one is a "real problem" or not, we need to do more than a little thinking about such things as we improve Mailman. We missed the window for GSoC this year. We've had excellent success in getting students (I don't think we were ever denied a slot we asked for), so prospects for next year are good. I myself am looking at mandatory retirement in a couple of years, and am planning to ramp up development/consulting activity over this period. So I know a year is a long time, but we are actively supporting existing features, and intend to continue development for the foreseeable future. Finally, Brian Carpenter and EMWD are actively developing alternatives to Postorius and HyperKitty. (Affinity and Empathy, respectively; I believe Affinity is already in beta, Empathy I don't know about status). You can find out more about them in the Mailman Developers <mailman-developers(a)python.org> archives and in the archives of this list. These are independent friendly projects, not hostile forks. You may find them to provide more straightforward access to configurations you want, although they do depend on Mailman core for much "back office" functionality, and obviously they're less mature than Postorius and HyperKitty. But they have the advantage of targeting a much more mature Mailman core, so they'll catch up fast. EMWD hosts a lot of Mailman lists and hosts, so I for one would consider a request for features from Affinity developers to be representative of many list owners.[1] Footnotes: [1] Not to deprecate Empathy, but the relationship between core and any archiver is pretty much "arm's length". Archiver features are mostly independent of the core.

5 years, 4 months

Mailman 3 installation from latest Debian packages

by Matthew Blissett

Hi, I've installed mailman3-full 3.3.3-1 from Debian bullseye (Debian testing). The dropdown controls on the UI for Postorius (e.g. "Subscription requests", "Mass operations" and the username button to log out) and the similar controls on Hyperkitty (e.g. "Threads by month") do not work. You can see the latter at http://newlistszm.gbif.org/mailman3/hyperkitty/list/test@newlistszm.gbif.or… I found https://lists.gem5.org/archives/list/gem5-announce@gem5.org/ which is running the same version, but presumably not using these Debian packages as the Javascript is slightly different. Could this be a problem with the Debian packaging, or perhaps my configuration -- which is very close to the defaults (i.e. Mailman and Apache configuration generated by dpkg). Has anyone set up a working installation using these packages? Thanks, Matt Blissett PS, I wrote a similar message earlier in the week to a Debian list: https://alioth-lists.debian.net/pipermail/pkg-mailman-hackers/2021-February…

4 years, 10 months

attachment.html

by Sam Darwin

Hi, Using a typical modern email client such as Gmail, the messages are usually html formatted. Then, Hyperkitty displays attachment.html on every message. Can that be removed? I was searching for the topic "attachment.html" in the archives and there wasn't much information. What finally cracked the code was Mark's comment: If in Postorius on the list's Settings -> Alter Messages page, Filter Content and Convert html to plaintext are both Yes, the HTML should be converted to plain text and that should appear in HyperKitty. It turns out "Filter content" affects many settings. It's easy to skip over that. I wonder if the UI might call attention somehow, with a graphic element, or with text: "Settings on this page will not take effect. Because 'Filter content' has not been enabled". It is right that "Filter content" must be set in order to remove attachment.html ? And now, a search will have more results. :-)

2 years, 5 months

Re: Handling of SPAM mails in mailman3 - Check for X-Spam Header

by Mark Sapiro

On 1/16/20 10:51 AM, Torge Riedel wrote: > > Such SPAM mails are currently hold for moderation with reason "not from > a list member". Is there no check for the "X-Spam: Yes" header or is > this check done later? If you set a Header Filter (in Postorius the Header filters tab) those checks are done before non-member moderation. This won't work for posts from members because the header checks are done between member moderation checks and non-member moderation checks, but if you create a Header Filter for header 'x-spam' and pattern 'yes' with action hold, a message from a non-member which has an X-Spam: Yes header should be held for that reason. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[Mailman-Users] mailman 3 and freeipa

by Stephen J. Turnbull

Crossposting and redirecting replies to mailman-users(a)mailman3.org. Steven Jones writes: > I cant find anything on this so far but can Mailman3's webui use > freeipa as the authentication mechanism? Hi Steve, I don't have a complete answer offhand (and right now I'm just reducing my inbox so a single google search is as much as I can do), but searching for "freeipa django" indicates that there are "connectors" for Django and FreeIPA. The nicest option would be a plugin for Django's socialauth application. If that doesn't seem to exist, perhaps you can just add a FreeIPA application to the Django configuration. You would need to add it to both Postorius and HyperKitty configurations. Steve -- Associate Professor Division of Policy and Planning Science http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN

6 years, 8 months

Re: Deleting messages from HyperKitty archive

by Mark

On 2024-03-26 08:45, Mark Sapiro wrote: > On 3/25/24 13:00, Mark wrote: >> >> Regarding updating, the Hyperkitty docs say to (a) update the code >> base; and (b) update the database schemas. >> >> Although updating the database is mentioned, there isn't anything >> about updating the code base. > > Updating the code base just means installing an updated version. E.g. > upgrading from 1.3.8 to 1.3.9. > Thanks Mark. Was another case of "If all else fails, read the instructions..." $ sudo systemctl stop mailman3 $ sudo systemctl stop mailmanweb (venv) $ pip install -U mailman postorius django-mailman3 hyperkitty mailman-web (venv) $ mailman-web migrate (venv) $ mailman-web compress (venv) $ mailman-web collectstatic (venv) $ mailman-web compilemessages $ sudo systemctl start mailman3 $ sudo systemctl start mailmanweb https://www.mailman3.org/en/latest/upgrade-guide.html Successfully upgraded to Hyperkitty 1.3.9 and the delete message link now shows for the list owners. Best, Mark

1 year, 8 months

Mailman-users search results for query "Postorius"