Search results for "Postorius" - Mailman-users

New messages not being archived

by Sarah H

I have 2 active lists that are properly mailing out and working, plus an admin testing list that is as well. The list info pane correctly shows the mail volume and the imported archives from the previous 2.1 installation are present for both active lists. None of the 3 lists are generating new entries in the archive, all 3 are set up with default settings except 1 active and admin are set to private. I know that hyperkitty is showing some new content as admin was created in postorius and the list is present in hyperkitty and working in mailman. None of the logs show anything of note, mailmanweb.log has no new entries since it caused a serious issue when I changed the domain, uwsgi-error is the same and uwsgi.log has proper access logs. When trying to add a new thread via the hyperkitty interface I can see the email go through the maillog, I get the email with the entered content and everything else works, it just doesn't add a new thread to the archive. The installation is set up with the default settings from the virtualenv installation guide. Any assistance would be appreciated.

5 years, 3 months

Re: duplicate SITE_IDs and broken /postorius/lists/ display; Mailman Client

by Stanisław Findeisen

On Thu, Mar 24, 2022 at 09:27:06PM -0700, Mark Sapiro wrote: > The issue is client.create_domain doesn't support setting a Web Host. Web Hosts are the sites in the django_site table and SITE_ID is the id of > the table entry. See `sites` in the Django admin UI. > > So when you create a domain with client.create_domain it gets arbitrarily assigned to a `site` Ok thanks, this is good to know. How about mailing list creation using Mailman Client, like this? domains = client.domains domains = list(filter(lambda x: (domain_name == x.mail_host), domains)) # .. check if domains is a singleton list .. domain1 = domains[0] domain1.create_list(list_name, style_name=style_name) Do you know of any quirks/deficiencies related to this kind of code? This code is taken from mailman3-utils: https://github.com/sfindeisen/mailman3-utils , a set of scripts I stitched together to facilitate common Mailman3 operations on the command-line. Most importantly this can apply the (currently hardcoded) set of list settings uniformly across the different lists (and different domains). (I realize part of this overlaps with the mailman command, especially in the local setting.) Thanks Stanisław

4 years, 7 months

Re: Dump/restore users (with passwords) via API

by Abhilash Raj

On Mon, Sep 17, 2018, at 12:15 PM, Dmitry Makovey wrote: > We are trying to dump/restore users using API calls and it seems that > API allows us to dump password hashes (a good thing), but then API does > not allow to insert users back using saved password hashes - only > cleartext passwords. I'd say that is intentional. You don't want people to be setting up hashes as passwords. > Aside from create_user is there any other way to > create users/change their password? Not that I know of, not using the API atleast. You could potentially use the low level API that inserts records in the database or use SQL to dump and restore that data. What do you use the Core's user/password for? Currently, the user passwords are basically just a carry-over from Mailman2 and there shouldn't be any use for it. I have been considering removing that completely have Postorius do all the authentication/authorization. Email based authentication should rely on more reliable identities like email signatures, intead of having to send cleartext passwords over email. -- thanks, Abhilash Raj (maxking)

8 years, 1 month

Re: Mailman web interface / uwsgi

by Stephen J. Turnbull

Mark Sapiro writes: > On 11/27/22 00:19, Jan Eden via Mailman-users wrote: > > > > I see. But the mailman.cfg is placed in /etc/mailman3, and this file > > also belongs to the core, doesn't it? In any case, I changed the > > configuration parameter for [archiver.hyperkitty] as you suggested and > > all settings are in one place now. > > In that case, it's probably just an oversight. Yes, I think that's what's going on. There's been quite a bit of simplification and unification of the Django configuration over time, which is ongoing and not 100% reflected in all documentation. Because of the way most Linux distros work (and I think it's probably true for *BSD and other POSIX systems), it makes sense to put users' site configurations in /etc. I don't see a particular reason why with the current relatively small set of config files we'd want to put HyperKitty or Postorius files elsewhere than /etc/mailman3 (although it might make sense to have more separation given the existence of EMWD's Affinity etc). Steve

3 years, 11 months

Re: How to store additional information about lists?

by Stephen J. Turnbull

Andreas Barth writes: > public: anyone can subscribe and read the archive. This is already possible, more or less the default list configuration. "Subscribe and read archive" involves multiple separate list attributes, enforced by three separate applications. Subscription policy is controlled by whether you need approval of an admin or not, and whether you need to verify your email or not, plus the ban lists. Archive access (assuming you have one at all) is contrlled by a different list attribute, archive_policy. Core has final say on subscriptions, but Postorius could do it if email subscriptions are disabled. HyperKitty handles the archive permissions. These various aspects are currently quite loosely coupled. > restricted: for employees (or members - or whatever) only. So they > could subscribe themself. The archive and posting may be restricted > to subscribers or to anyone in that group - both would be working > for me. I think this can be implemented with the controls we already have. The basic idea is to handle the "anyone in that group" case by mass subscribing and setting the subscription to no-mail. Obviously, this is most practical with a fairly static membership (eg, students at a school). A fluid membership (for example, a volunteer organization) would be made easier to manage with a "member adapter" to an external database to handle the "do I know this person" questions. ("Member adapter" is Mailman 2 terminology, I don't know if it's exactly the same in Mailman 3; it does or *should* exist in Mailman 3, though.) It's possible that we could make this easier to configure with some changes to core. However, if this is as close to what you need as I think it is, I would advise against vendoring Mailman, and instead writing some scripts to help manage mass subscription, or create the member adapter. > (How to know who is allowed to subscribe is another question - having > an internal mailing list which contains all the members just for this > purpose would be ok for me.) That's helpful to know. This sounds very similar to the Systers approach, where the Mailman core User database is the authoritative membership database for the organization. > private: hand-selected people, think about e.g. board or steering > committees internal discussions. Of course, the archive (if there is > any) should be restricted to the actual members. Posting to these > lists is currently not restricted, so no derivation needed from the > current set in postorius. This is already possible by requiring admin approval, or by setting the ban list to something that matches everything like "^.".

5 years, 5 months

Re: proper update procedure for MM3 docker containers

by Fabian A. Santiago

On 2018-08-06 12:24 PM, Abhilash Raj wrote: > On Mon, Aug 6, 2018, at 6:28 AM, Fabian A. Santiago wrote: >> Hello, >> >> Can someone remind me of the proper / best way to update my docker >> containers for MM3 / postorius based on maxking's images? Thanks. >> >> and this for both the stable and rolling releases. > > Well, the process is fairly straightforward, when moving form an older > to a newer release, > > Stop and remove the container ($docker-compose stop, $docker-compose > rm) and then start the new ones ($ docker compose up -d). > > That should be all! > >> >> -- >> Fabian S. >> >> OpenPGP: >> >> 0x643082042DC83E6D94B86C405E3DAA18A1C22D8F (new key) >> >> *** >> >> 0x3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC (to be retired, still >> valid) >> _______________________________________________ >> 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/ thank you. -- Fabian S. OpenPGP: 0x643082042DC83E6D94B86C405E3DAA18A1C22D8F (new key) *** 0x3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC (to be retired, still valid)

8 years, 2 months

Re: General question mailman3: message sender acceptance "always"

by Mark Sapiro

On 10/23/23 09:08, Wikinaut wrote: >>> In the Postorius held messages view, click on the message's subject to >> open a dialog showing the messages content > > Dear Mark, sorry: > How should I know this? Well, the subject of the message in the held messages view looks like a link. Maybe click it once to see what it does. > I'd rather prefer to have these both changes: > > i) relabel the existing one od three buttons from "accept" to "accept once" ; and > ii) add a fourth button "accept all messages from this sender (i.e. add to white list)" That wouldn't include options like "discard further posts from this user", "reject further posts from this user" and perhaps other possibilities. If I were going to do anything, it would probably be adding a line above the list of held messages saying something like "Click the message's subject for more options." -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

Re: New Mailman Releases

by Abhilash Raj

On 10/26/22 12:32, Odhiambo Washington wrote: > > > On Wed, Oct 26, 2022 at 8:44 AM Abhilash Raj <maxking(a)asynchronous.in > <mailto:maxking@asynchronous.in>> wrote: > > Hi, > > I am pleased to announce several new releases for GNU Mailman project. > > 1. Mailman Core 3.3.6 [1] > 2. Postorius 1.3.7 [2] > 3. Hyperkitty 1.3.6 [3] > 4. Mailmanclient 3.3.4 [4] > 5. Django-mailman3 1.3.8 [5] > > All the releases are published to PyPI and you can find links to all > the > PyPI projects: > > https://docs.mailman3.org/en/latest/ > <https://docs.mailman3.org/en/latest/> > > A full list of changelogs are available below: > > [1]: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.…> > [2]: > https://docs.mailman3.org/projects/postorius/en/latest/news.html#section-2 <https://docs.mailman3.org/projects/postorius/en/latest/news.html#section-2> > -- Something weird is going on with the page missing the bullets. > [3]: > https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-6 <https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-6> > [4]: > https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… <https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien…> > [5]: > https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst > <https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst> > > > Finally, the minimum Python version required is 3.7 although, 3.9 is > recommended if you are doing a new install for longest support. 3.10 is > supported for Django apps, but Mailman Core is missing that due to one > of the core dependencies not support 3.10 yet (aiosmtpd). > > > > Hello @Abhilash Raj <mailto:maxking@asynchronous.in> > > Thank you and the whole MM3 team for all the free work you do to make us > have mailing lists :) > > I have a question regarding the Python version. > I have a very recent installation of MM3, via the Virtual Environment > method, running smoothly - so far. > The Python version that got installed is 3.10.6 > > wash@lists:~$ sudo su - mailman > (venv) mailman@lists:~$ which python > /opt/mailman/mm/venv/bin/python > (venv) mailman@lists:~$ /opt/mailman/mm/venv/bin/python -V > Python 3.10.6 > (venv) mailman@lists:~$ mailma > mailmail3 mailman > (venv) mailman@lists:~$ mailman --version > GNU Mailman 3.3.5 (Tom Sawyer) > (venv) mailman@lists:~$ > > 1. What does the incompatibility with Python-3.10 portend for my setup > and anyone else with Python-3.10? The bug in aiosmtpd is a bit weird and has to do with how the test cases in aiosmtpd and Python 3.10 changes interact with SSL. For the intents and purposes of Mailman, we don't use SSL for the communication between MTA and aiosmtpd, so there _shouldn't_ be any issuer with your setup. Ideally, `pip` shouldn't have allowed you to install aiosmtpd in a Python venv with 3.10, but that depends on which version of pip you are using since the newer versions have better support for such management. > 2. Is it possible to downgrade the Python in a Venv down to 3.9 without > breaking the installation? You can keep the current installation running and create a 2nd installation by simply creating a 2nd venv with 3.9. Something like, `/opt/mailman/mm/venv-3.9/`. You can install things into that venv and when you are done and ready to switch, you can update all the paths in various places to use update 'venv-3.9' instead of 'venv'. In case you encounter any issues, you can always revert back to older 'venv' in the paths wherever the are needed and bring back the old install. Venvs are good for multiple installs so you can switch back and forth pretty easily. > > And finally, is there documentation/procedure to upgrade a VENV install > in this case? You don't want to upgrade venv is what i've heard, you should always create a new one if you are bumping python versions. If you are just upgrading packages in the existing venv, then you can follow: https://docs.mailman3.org/en/latest/upgrade-3.2.html -- thanks, Abhilash Raj (maxking)

4 years

Re: lists.mailman3.org web site.

by Barry Warsaw

On Aug 30, 2016, at 12:01 AM, Mark Sapiro wrote: >Django Allauth is now properly configured and working on >lists.mailman3.org. You can log in by email/password as noted above or via >OAuth2 with a GitHub, GitLab, Google or Facebook identity. > >If you are an existing user, in order to use one of the OAuth2 providers, you >must first log in with email and password and go to the Account Connections >tab in your account settings and add the 3rd party account(s) you wish. This works pretty great. I tried it with my GitHub and GitLab accounts and was easily able to associate those with my Postorius and HK accounts. I didn't try FB or Google, but I guess those would work the same way. I'll miss Persona but I think this is an entirely acceptable alternative, with plenty of choice for folks wanting to control which authority they delegate to. I'd mildly like to see Launchpad support, but I understand 1) it's a minority platform; 2) it only supports OAuth 1. Thanks to the developers for adding this support and to Mark for enabling it. Cheers, -Barry

10 years, 2 months

Re: mailman-suite: Error 500 on Lists /setting/ pages

by Mark Sapiro

On 11/18/20 8:43 AM, ljsbw-it(a)riseup.net wrote: > I just installed Mailman3 (mailman-suite) on my Server following these instructions: https://lab.uberspace.de/guide_mailman-3.html Please see <https://wiki.list.org/x/12812344> > and everything works fine so far. I can create lists, subscribe people and send mails through lists but when I click the settings button and get redirected to /postorius/lists/listname/settings/ i get an Error 500 message. I couldn't find anything in the logs except the uwsgi log: > [pid: 20568|app: 0|req: 62/62] 100.64.115.1 () {48 vars in 1052 bytes} [Wed Nov 18 16:27:59 2020] GET /postorius/lists/listname/settings/ => generated 1102 bytes in 1438 msecs (HTTP/1.1 500) 6 headers in 209 bytes (1 switches on core 0) I think that uwsgi log message just refers to the delivery of the error page to your browser. What other logs are you looking at? There should be something in Mailman core's mailman.log or the Django log whose location is defined in settings(-local).py, probably mailman-suite/logs/mailmansuite.log. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

Mailman-users search results for query "Postorius"