Search results for "Postorius" - Mailman-users

Re: add / remove / set moderation bit of non-members via mailman shell

by Mark Sapiro

On 2/7/24 02:37, Zaheer Abbas wrote: > > I do the above via postorius because I couldn't find a way to do this via > mailman shell. Something like ``` mark@msapiro:~$ mailman shell -l list(a)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(a)example.com mailing list >>> NEW_NONMEMBERS = [('First User', 'user1(a)example.com'), ... ('Second User', 'user2(a)example.com'), ... ('Third User', 'user3(a)example.com'), ... ] >>> from mailman.app.membership import add_member >>> from mailman.interfaces.subscriptions import RequestRecord >>> for display_name, email in NEW_NONMEMBERS: ... record = RequestRecord(email, ... display_name=display_name, ... delivery_mode=None, ... ) ... member = add_member(m, record, role=MemberRole.nonmember) ... member.moderation_action = Action.accept ... >>> commit() >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

Re: Domain admin

by Johannes Winter

Am Wed, 25 Apr 2018 08:39:58 -0700 schrieb Mark Sapiro <mark(a)msapiro.net>: > On 04/24/2018 11:57 PM, Johannes Winter wrote: > > > > We would like to give our users the priviledge to create lists per > > domain. I Haven't found any options for that in the web interface. > > > > Is this possible somehow with mailman3? > > > It is not currently possible. From the point of view of Mailman Core, > anyone who can run the 'mailman' command or access the REST API can > create domains and lists. > > Postorius could support this in some way and could maintain it's own > 'authorized users' data, but it would be better to also add some > concept of domain admin to core. > > These would be significant changes. > A possible workaround could be to create several webhosts to control access rights to the mailing lists. At least I understand the option to create new "web-hosts" in "add domain" in this way. But I haven't found any further information for setting up multiple web-hosts. Is there any yet?

8 years, 3 months

Re: Mailman 3 installation from latest Debian packages

by Mark Sapiro

On 2/12/21 4:49 AM, Matthew Blissett wrote: > 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… Everything works as expected at <https://lists.mailman3.org/mailman3/> and <https://mail.python.org/mailman3> which are installed from source. > 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). I can't speak to the Debian package possibility, but it might possibly be related to the way your browser handles the javascript. I don't know anything in configuration that would cause this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

Re: Configure administrative users via command line?

by Mark Sapiro

On 7/18/23 11:38, kjohnson(a)eclypse.org wrote: > > How can I configure administrative users via command line? I need to process a moderation request. I have root access on the server. A pointer to the appropriate documentation would be more than welcome. Thank you to anyone who can provide help. I'm not sure what you want. If you are an owner or moderator of a list or a superuser, you can handle moderation requests via Postorius. If you are a list owner or a superuser, you can manage owners and moderators via Postorius. You can add superusers via the command line django admin `createsuperuser` command. It might be good if the command line `mailman addmembers` and `mailman delmembers` commands accepted a `role`, but they don't. You can manage owners and moderators via the REST API which you can access via curl. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…>. You can also do this via `mailman shell`. -- 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: List description as sender

by Mark Sapiro

On 09/14/2018 05:35 AM, Henrik Rasmussen wrote: > When receiving a mail from Mailman 3, the From: User name is the description of the list, like From: Long desription of the list for all members of certain project <project(a)lists.example.com>. > > Starting to get old, I recall something about a discussion we once had on http://mail.python.org/pipermail/mailman-users/, but I don't recall the reason for this and I can't find the discussion, so it might be something I dreamed. Specifically what messages are you talking about? The only case I see offhand where the From: is as you describe is in posts from an anonymous list. In any case, the list description is described in Postorius as "This description is used when the mailing list is listed with other mailing lists, or in headers, and so forth. It should be as succinct as you can get it, while still identifying what the list is." I.e., it shouldn't be a long description. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 10 months

Re: User cannot reset password

by Greg Newby

On Sun, Aug 11, 2024 at 11:10 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/11/24 10:56, Greg Newby wrote: > > I imported MM2.1 lists to Mailman3 (using import21 - details are in my > > previous messages to mailman-users), and have had a couple of reports of > > people for whom the password reset function via "Forgot password" on the > > list login screen doesn't work as expected. > > > Django (web) accounts (Postorius and HyperKitty) are separate from > Mailman core. Users inported from MM 2.1 do not have web accounts. They > have to sign up, not request a password reset. > 1. Will the new (Django) and imported (Postorius) usernames automatically be matched to the same email address? The goal is for someone to use the web-based front end to manage their migrated subscriptions. 2. How can I customize the email that went to users who selected "Forgot password?" ( You are receiving this email because you, or someone else, tried to access an account with email I didn't find that string in the source code. Thanks as always! ~ Greg

1 year, 11 months

Re: Error Logging - what changed with the New Year releases?

by Mark Sapiro

On 1/14/23 11:44, Odhiambo Washington wrote: > On Sat, Jan 14, 2023 at 7:13 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> Nothing in those releases per se would affect this. This is Django and >> django-allauth. Perhaps when you updated the Mailman packages, you also >> updated these dependencies. >> > > Which dependencies would those be? Django and django-allauth. > When I upgraded, the command I ran was: > > pip install --upgrade --force mailman mailmanclient postorius hyperkitty > mailman-hyperkitty django-mailman3 Do you mean --force-reinstall? pip has no --force option. I *think* --force-reinstall will upgrade dependencies. Depending on your pip version, --upgrade alone may or may not upgrade dependences. Older versions of pip will, but newer versions, at least without --force-upgrade require --upgrade-strategy eager to update dependencies. > And how do I find out what is suppressing the logging for the social > accounts? That's a django-allauth question. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

Re: MM2 -> MM3 Migration: listinfo page

by Jeremy Stanley

On 2023-03-09 13:49:09 +0300 (+0300), Odhiambo Washington wrote: [...] > I'd rather not touch the MM2.1 domain because references have been made to > it in publications. > What I am struggling with is the listinfo.html file: > ``` > https://lists.kictanet.or.ke/mailman/listinfo/kictanet > ``` > I am struggling to add reference to the MM3 subscription link user the > " Subscribe to KICTANet by filling out the following form:" > The HTML code to insert there beats me :) Redirecting the listinfo pages to your Postorius interface should be sufficient to keep those URLs which are referred to in publications working. We do basically the same thing Mark mentioned, for the reasons you say you don't want to: https://opendev.org/opendev/system-config/src/commit/ae7884a/playbooks/role… If someone follows a link to the old MM2 https://lists.opendev.org/cgi-bin/mailman/listinfo/service-discuss URL they get redirected to https://lists.opendev.org/mailman3/lists/service-discuss.lists.opendev.org/ so that there's no risk they'll try to use the old MM2 subscription form. -- Jeremy Stanley

3 years, 4 months

Re: configuring postfix local recipient table

by Alexander Inzinger-Zrock

Am 28.04.25 um 16:27 schrieb Stephen J. Turnbull: > Alexander Inzinger-Zrock via Mailman-users writes: > > > + also checked that command ''postmap'' (under /usr/sbin) is available > > for user 'mailman' (usr/sbin was not in path; it is now). > > This should not matter since the full path is in postfix.cfg, so > Mailman should find it and run it unless there is some permissions > problem or the executable itself is broken, regardless of PATH. > > You've probably run all these pretty recently, but if you've made any > changes since then: > > What is the output of the "mailman lists" command? (expect the test > list with domain) 2 matching mailing lists found: testliste01@MY_DOMAIN testliste02(a)my-example.com + MY_DOMAIN - replaced my domain by MY_DOMAIN + second was a test domain, created via postorius to check if i mesed up with the first one - no differences > What is the output of the "mailman aliases" command? (expect none) Indeed, none. > After "mailman aliases" do you get aliases in the postfix_lmtp file? > No.

1 year, 3 months

Upgrade

by Mark Sapiro

On 5/22/19 2:07 PM, David Krantz wrote: > Hi all, > > I am running a relatively old version of mailman 3, namely 3.2.0a1 > from late september 2017. This is installed using the old > mailman-bundler method. I use postfix and postgres. > > I really have two questions: > > First: What is the normal way to upgrade such a setup? I guess that I > just can get the updated versions of all packages through git, set up > new venv's to simplify a rollback, back up the database and then just > restarting with the new version hoping for the best. That's more or less correct. I did this on mailman3.org a little over a year ago. I suggest you see <https://wiki.list.org/DOC/Mailman%203%20installation%20experience> which describes much of what I did. you can also see <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=re…> for what I had with Mailman Bundler. The biggest hurdle is now Postorius and Hyperkitty are Python3 so you need Python3 versions of various dependencies. Here's roughly what I did. git clone everything from GitLab. As a developer, I've always been running off the heads. There are occasional glitches, but I can work around these. You can also install from PYPI if you want more stability. Everything is mailman, mailman-hyperkitty, mailmanclient, django-mailman3, hyperkitty and postorius. But, I'm getting ahead. Create a new python3.5+ virtualenv. Python3.5 is the minimum, but 3.6 or 3.7 would be even better. Activate that virtualenv and if you are using the branches from GitLab, in each branch directory, do python setup.py clean --all python setup.py install or just pip install everything. You also need to do the things indicated in the Preliminaries and Installation sections of <https://wiki.list.org/DOC/Mailman%203%20installation%20experience>. Also see the Migration section for scripts I use to update from GitLab and build 'everything' and the rest of the document too. Then once you have things set up, it's pretty much a matter of just updating the various scripts you use to run things to point to the new command files in, in my case, /opt/mailman/mm/bin/. One caveat to note is if you are using the Whoosh backend. The Python2 version is incompatible with Python3 so you need to remove the fulltext_index directory and run the django management rebuild_index command to recreate it. You should be able to just run rebuild_index or maybe clear_index followed by update_index without removing the old index first, but there are reports that this doesn't work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 2 months

Mailman-users search results for query "Postorius"