Search results for "Postorius" - Mailman-users

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, 3 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

2 years, 1 month

Re: My list has been switched from public to private archives, but they are still visible

by Abhilash Raj

On Thu, Sep 19, 2019, at 11:15 AM, Enrique Terrazas wrote: > I am having a very similar issue. Here is what I have found: > > There are basically three archive settings we can select via the > postorious web front end for archives. These can be found in: Settings > > Archiving and they are: > Public archives > Private archives > Do not archive this list This is interface of Mailman to set the archives. > > In the Django administrative interface we can find those > same(?/similar?) settings here: Main Page > Hyperkitty > Mailing lists > > Mailing List object(x) > Archive policy: > never > private > public This is basically a hotline to the database. You can change these values, but they would be overriden with the values that are in Mailman Core on the daily cron job run. I would suggest not to tinker with values there since you could leave database in a corrupted state. Since there is an ORM layer there, chances are less but still a possibility :) > > I’m not sure which of the two takes precedence. My guess is postorius > since that is a list owner accessible setting and the Django > administrative interface would typically not be accessible to list > owners. We have noticed the following odd behavior, not sure if it is a > bug. For existing lists with private archives, when switching to “Do > not archive this list” in postorious, the desired effect of no longer > archiving the list is instantaneous. However, after the daily cron job > that syncs with Mailman Core happens, the existing archives now become > publicly accessible. Is this behavior based on the assumption that the > list will no longer be archived and will therefore be purged? Source of truth is Mailman Core's database. Postorius is a front-end to change that and owners have permissions to do that. Hyperkitty only syncs back that information daily. I have a fix in the master which makes such that this information is synced synchronously and is available immediately to Hyperkitty. For now, you could either run the "python manage.py runjobs --daily" or wait for a day if that is possible. > Enrique > > > On Sep 19, 2019, at 1:08 PM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > > > On Thu, Sep 19, 2019, at 3:31 AM, Paul Arenson wrote: > >> Can anyone help with this? > >> > >> I set my list to private archives today. Up until then, it was pubic. > >> And yet, if you go to the list page, you will see that if you click > >> archives (top left), you can see them. (Filled with a bunch of tests > >> posts for now) > > > > This change takes a bit of time to sync up Hyperkitty. THere is a daily > > cron job which syncs this information from Mailman Core. > > > > I have made a change which should fix this problem and the process would > > become synchronous. > > > > You can run `python manage.py runjobs --daily` command to force sync > > that information. > > > >> > >> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist.toky… > >> > >> Am I misunderstanding what a private archive is? > > > > Not really, your expectation is right. > > > >> > >> Is something wrong with my setup (which is hosted)? > >> > >> Thank you. > >> _______________________________________________ > >> Mailman-users mailing list -- mailman-users(a)mailman3.org > >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org > >> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… > >> > > > > -- > > thanks, > > Abhilash Raj (maxking) > > _______________________________________________ > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… > > -- thanks, Abhilash Raj (maxking)

6 years, 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, 8 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, 6 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, 4 months

Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Mark Sapiro

On 10/26/20 6:10 PM, Shashikanth Komandoor wrote: > > How to find out the versions of the each and every component > of the mailman 3 like mailman core, mailmancilent, postorius, > hyperikitty, mailman-hyperkitty, django-mailman3, mailman-suite and so, > after installation? cd to the directory in which you cloned the gitlab project for the component and do `git log` > If I am running an old mailmanclient or older version of any > other mailman component, please suggest how to upgrade either one or > multiple components based on the requirement. Is there any link that > would help me to upgrade ? > > I have used the > link https://docs.mailman3.org/en/latest/devsetup.html to install the > mailman 3 components. I expected that the procedure followed in this > link would install the latest versions of the mailman 3 components. > Please correct me if I am wrong. Is there any latest version > compatibility table ? If you installed each of mailman, mailmanclient, django-mailman3, postorius and hyperkitty according to instructions like $ cd ~/mailman $ git clone https://gitlab.com/mailman/mailmanclient.git Then set up mailmanclient: $ cd mailmanclient $ python setup.py develop $ cd .. from that document, you should have the latest version. If that is the case, `git log` in the mailmanclient directory should begin like commit aaa529808e2d61899f90509da4ea802a70d2c8ff (HEAD -> master, origin/master, origin/HEAD) Merge: ff39dd8 8670751 Author: Abhilash Raj <maxking(a)asynchronous.in> Date: Thu Oct 15 01:09:32 2020 +0000 Merge branch 'fix-ci' into 'master' Use GHCR for the CI image See merge request mailman/mailmanclient!130 commit 8670751caff689733751ef323ef521c4a3fa1237 Author: Abhilash Raj <raj.abhilash1(a)gmail.com> Date: Wed Oct 14 17:36:58 2020 -0700 Use GHCR for the CI image commit ff39dd8f03a820f442f2251553c444370df3b914 Merge: 80ebed4 76d44e1 Author: Abhilash Raj <maxking(a)asynchronous.in> Date: Fri Aug 7 19:35:05 2020 +0000 Merge branch 'invite' into 'master' Add support for inviting an email address to join a list. See merge request mailman/mailmanclient!129 or if you did this before Oct 15, maybe it starts with commit ff39dd8f03a820f442f2251553c444370df3b914 The particular commit you need for your issue is commit 86eb0da3cdb48e253b0d36138ab7cf91259a7583 Merge: c8dcb1e 28d1c3a Author: Abhilash Raj <maxking(a)asynchronous.in> Date: Sat May 16 08:02:21 2020 +0000 Merge branch 'held-count' into 'master' Add a new get_held_count() API to get a count of held messages. See merge request mailman/mailmanclient!122 Note that unless you intend to do actual development of Mailman 3, you should be following <https://docs.mailman3.org/en/latest/install/virtualenv.html> rather than <https://docs.mailman3.org/en/latest/devsetup.html>. -- 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

Re: mailman 3.x upgrade and downgrade

by C. Souza

On Tue, Jul 12, 2022 at 12:21 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/12/22 6:12 AM, skooperit(a)gmail.com wrote: > > Hi all, > > > > I have a few contradictory questions. > > > > 1. How to upgrade the 3.x version? > > > > 2. Is it possible to migrate (downgrade) the lists from mailman 3.x to > 2.1? > > > > 3. If so, what would be the best way to do that? > > > > > > My mailing list server is running on a CenOS-7x with postgreSQL and the > following mailman packages: > > > > django-mailman3 1.3.5 > > mailman 3.3.2 > > mailman-hyperkitty 1.1.0 > > mailman-web 0.0.3 > > mailmanclient 3.3.2 > > postorius 1.3.3 > > > > We have ~200 lists with more than a decade of history. > > > So you have installed Mailman 3, apparently following > https://docs.mailman3.org/en/latest/install/virtualenv.html. There is a > caveat. Current released versions of HyperKitty (I don't see your > version above) don't work with mistune >= 2.0.0. > > This is https://gitlab.com/mailman/hyperkitty/-/issues/431, fixed by > https://gitlab.com/mailman/hyperkitty/-/merge_requests/379 but not yet > released. > > If your installed mistune is not 2.0.0rc1, you can work around this with > this patch > ``` > --- a/hyperkitty/lib/renderer.py > +++ b/hyperkitty/lib/renderer.py > @@ -4,7 +4,7 @@ from django.conf import settings > > import mistune > from mistune.plugins.extra import plugin_url > -from mistune.scanner import escape_html, escape_url > +from mistune.util import escape_html, escape_url > > > class MyRenderer(mistune.HTMLRenderer): > ``` > Or you can downgrade mistune with > ``` > pip install mistune==2.0.0rc1 > ``` > in your virtualenv. > > To answer your questions, to migrate your lists, you use `mailman > import21` and to migrate archives, `mailman-web hyperkitty_import`. Give > these commands with the `--help` option for more info. > > Downgrading lists from Mailman 3 to Mailman 2.1 is not currently > possible. There is no inverse to `mailman import21`. You can export a > HyperKitty archive as a mbox to use as input to Mailman 2.1s bin/arch. > > -- > 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 Mark. You're right it was installed in a virtualenv using pip. I can't see the mistune package, maybe it wasn't a requirement for that version of mm3. 1 Package Version 2 ------------------- ---------- 3 aiosmtpd 1.2.4 4 alembic 1.5.3 5 arrow 0.17.0 6 asgiref 3.3.1 7 atpublic 2.1.2 8 authheaders 0.13.0 9 authres 1.2.0 10 bleach 3.3.0 11 blessed 1.17.12 12 certifi 2020.12.5 13 cffi 1.14.4 14 chardet 4.0.0 15 click 7.1.2 16 cmarkgfm 0.5.2 17 cryptography 3.3.1 18 decorator 4.4.2 19 defusedxml 0.6.0 20 Django 3.0.12 21 django-allauth 0.44.0 22 django-appconf 1.0.4 23 django-compressor 2.4 24 django-extensions 3.1.0 25 django-gravatar2 1.4.4 26 django-haystack 3.0 27 django-mailman3 1.3.5 28 django-picklefield 3.0.1 29 django-q 1.3.4 30 djangorestframework 3.12.2 31 dkimpy 1.0.5 32 dnspython 2.1.0 33 docutils 0.16 34 falcon 2.0.0 35 flufl.bounce 3.0.1 36 flufl.i18n 2.0.2 37 flufl.lock 3.2 38 gunicorn 20.0.4 39 HyperKitty 1.3.3 40 idna 2.10 41 importlib-resources 5.1.0 42 lazr.config 2.2.3 43 lazr.delegates 2.0.4 44 mailman 3.3.2 45 mailman-hyperkitty 1.1.0 46 mailman-web 0.0.3 47 mailmanclient 3.3.2 48 Mako 1.1.4 49 MarkupSafe 1.1.1 50 networkx 2.5 51 nose 1.3.7 52 oauthlib 3.1.0 53 packaging 20.9 54 passlib 1.7.4 55 pip 21.0.1 56 postorius 1.3.3 57 psycopg2-binary 2.8.6 58 publicsuffix2 2.20191221 59 pycparser 2.20 60 Pygments 2.7.4 61 PyJWT 2.0.1 62 pyparsing 2.4.7 63 python-dateutil 2.8.1 64 python-editor 1.0.4 65 python3-openid 3.2.0 66 pytz 2021.1 67 rcssmin 1.0.6 68 readme-renderer 28.0 69 requests 2.25.1 70 requests-oauthlib 1.3.0 71 rjsmin 1.1.0 72 robot-detection 0.4 73 setuptools 39.2.0 74 six 1.15.0 75 SQLAlchemy 1.3.23 76 sqlparse 0.4.1 77 typing-extensions 3.7.4.3 78 urllib3 1.26.3 79 uWSGI 2.0.19.1 80 wcwidth 0.2.5 81 webencodings 0.5.1 82 wheel 0.36.2 83 Whoosh 2.7.4 84 zipp 3.4.0 85 zope.component 4.6.2 86 zope.configuration 4.4.0 87 zope.deferredimport 4.3.1 88 zope.deprecation 4.4.0 89 zope.event 4.5.0 90 zope.hookable 5.0.1 91 zope.i18nmessageid 5.0.1 92 zope.interface 5.2.0 93 zope.proxy 4.3.5 94 zope.schema 6.0.1

4 years, 2 months

Message of the day

by Stephen J. Turnbull

Henrik Rasmussen writes: > Are there any way of displaying a "Mesage of the day" to the users > of Postorius and Hyperkitty? Not built in to those applications. However, you could easily alter a template, possibly the base template, to include a file would contain your message with appropriate formatting. Django has a conditional include feature so you wouldn't get an error and no glitch in the display if the file weren't present. Extensions to the idea would include putting the formatting in CSS (sort of pointless by itself) and adding Django code to check whether the user's previous login was before the MOTD was changed (and then the CSS could be used to hide the message in case they had logged in recently, and presumably already saw it). It wouldn't be hard to add a MOTD table to Django, and then you could display all messages more recent than previous login. I'm not interested in doing this myself but would be willing to help a volunteer write the code and get it committed (subject to Steering Committee consensus, but I don't see why not). Steve

4 years, 10 months

Integration with spamassassin?

by Stephen J. Turnbull

Peter Chubb via Mailman-users writes: > Has anyone integrated Mailman3 with Spamassassin? > > What I'd like is a way for emails that I click 'discard' on in > Postorius, to be submitted to the spamassassin Bayes classifier to > make it more likely similar ones will be rejected in future at SMTP > conversation time. I've not heard that anyone has done this. If there's a way to direct email into the classifier, then you can tell Mailman to send discarded emails to some email address, I believe. But I don't know anything about how that classifier is trained. You're likely to get better answers on Spamassassin channels. To make it one-click would require code changes in both Mailman and Postorius. Not terribly hard as such, but would require some thought as we probably wouldn't want it to be Spamassassin-specific (I think Mark uses SpamBayes on some of his lists, for example, and I suppose rspamd also knows about classifier training). Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

5 months

Mailman-users search results for query "Postorius"