Search results for "Postorius" - Mailman-users

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, 8 months

Re: Change Member's Address

by Mark Sapiro

On 1/13/26 11:30 AM, alain williams wrote: > > Like it or not it is sometimes easier for me to do that sort of thing than try > to explain it to them. I understand. > So: it would be really useful if the list manager were able to do this via the > web interface. As you indicate, a list admin can use the mass subscribe/removal UI to remove the old address subscription and add a new address subscription, but as you probably know, this doesn't preserve the user's other settings, and for a user with multiple subscriptions, it needs to be done list by list, so this really isn't a satisfactory way for an admin to change a user's address. There is a current issue at https://gitlab.com/mailman/postorius/-/issues/399 to simplify the process for a user to change their address and one at https://gitlab.com/mailman/postorius/-/issues/194 to allow an admin to change a user's address. Merge requests are welcome. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 3 weeks

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, 9 months

Re: Disable archives per list

by Bernd Wurst

Hello. Thank you for your answers. Am 25.02.21 um 22:01 schrieb Mark Sapiro: > Normally a list admin can select which of the enabled archivers is > active for that list via Postorius. To prevent this, you would have to > modify Postorius. It would be easy enough to just remove settings from > the relevant templates. This will take effect for all lists at once, I suppose. :( > I'm not sure what you mean by "custom archiver settings", but other than > enable/disable and public/private, probably not. Hyperkitty has a rather cool frontend but stores all messages from all lists together in one database table. Additionally, neither Mailman nor Hyperkitty seems to know or tell anything about archive sizes of a list. This is horribly for accounting. So I thought if I can have a separate hyperkitty installation per user without having to duplicate the whole mailman. Alternatively, I'd like to enable archiving only for some customers that buy a suitable plan. I did not really get into mailman plugins. Is is possible for plugins to hook into such settings? I could not really find examples for plugins. regards, Bernd

5 years, 4 months

Re: Question about lists and domains on Mailman 3

by Philip Colmer

On Wed, 29 Dec 2021 at 11:48, Jeff <mm3(a)steele.com> wrote: > I believe that you need to add "FILTER_VHOST = True” to your “settings.py" > Brilliant! Thank you, Jeff. > > > On Dec 29, 2021, at 5:11 AM, Philip Colmer <philip.colmer(a)linaro.org> > wrote: > > > > I've got a single server hosting multiple domains. I've got Apache > working > > as the proxy in front of MM3. > > > > Regardless of whether I go to https://lists.domainA.org/mailman3/lists/ > or > > https://lists.domainB.org/mailman3/lists/, Postorius lists ALL of the > lists > > across both domains. > > > > Is there a way of configuring the system so that, if a user goes to > "domain > > A", only the lists for that domain are listed? > > > > Thanks. > > > > Philip > > _______________________________________________ > > 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/ > >

4 years, 6 months

Re: List Migration from MM2.1 -> MM3

by Odhiambo Washington

On Mon, Aug 15, 2022 at 7:57 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/15/22 7:28 AM, Odhiambo Washington wrote: > > On Mon, Aug 15, 2022 at 4:59 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> Your /opt/mailman/mm/venv/bin/mailman is talking to a different Mailman > >> core than the one reading that mailman.cfg and the one Postorius is > >> talking to. > >> > > > > How can I track the one it's talking to? > > > Try `/opt/mailman/mm/venv/bin/mailman info` > So this command's output pointed to /opt/mailman/var/etc/mailman.cfg instead of my file that is in /opt/mailman/mm/mailman.cfg According to the HOWTO <https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10> I am following, mailman.cfg should be in /opt/mailman/mm/. Now I am wondering what I am missing again. Did something change? Should I place all my config files in /opt/mailman/var/etc/ instead of /opt/mailman/mm/ ? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 10 months

Re: Issue with Held Messages

by Mark Sapiro

On 08/20/2016 07:15 AM, Jean-Luc Wasmer wrote: > On 2016-08-20 02:08, Mark Sapiro wrote: >> >> If you look at the user's options when logged in as a list owner, you >> should see an additional "Administration options" section below those >> with a "Moderation" setting. What is that set to? > > I log in as the admin user created with "mailman-web-django-admin > createsuperuser", I created the list logged in as this admin user and > its email address is displayed in the "Owners" sections of the "Members" > tab. > I only have that 1 other member and when I check it settings, the last > section is "Avoid duplicate copies of messages?" and then there's the > "Save" button. You probably have an older version of Postorius than I have. I am a few weeks behind at the moment, but I basically am running the heads of the master branches as described at <https://wiki.list.org/x/17891998>, so I am unable to see what you see. Here's an example mailman shell session to see what various member moderation actions are. > mailman@mail:/opt/mailman/mailman-bundler$ bin/mailman shell mm3_test(a)python.org > Welcome to the GNU Mailman shell > The variable 'm' is the mm3_test(a)python.org mailing list > >>> list(m.members.members) > [<Member: None <barry(a)python.org> on mm3_test(a)python.org as MemberRole.member>, <Member: Mark Sapiro <mark(a)python.org> on mm3_test(a)python.org as MemberRole.member>, <Member: mark(a)msapiro.net on mm3_test(a)python.org as MemberRole.member>, <Member: gvanrossum(a)gmail.com on mm3_test(a)python.org as MemberRole.member>] > >>> m1 = list(m.members.members)[1] > >>> m2 = list(m.members.members)[2] > >>> m1.moderation_action > <Action.defer: 4> > >>> m2.moderation_action > <Action.accept: 3> >>> By the way, I didn't mention before but in Settings | Message >>> Acceptance, the "Acceptable aliases:" box contains "[]". When I try to >>> Save changes after modifying something, I gut "An error occured: []" in >>> the yellow banner (instead of "The settings have been updated."). >> >> >> What happens if you clear the Acceptable aliases box before saving? > > Then I get "The settings have been updated." after pressing "Save changes". > But if I navigate elsewhere and come back, the brackets are back in the form. This is <https://gitlab.com/mailman/postorius/issues/51>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 10 months

Changing subscription address

by Stephen J. Turnbull

Allan Hansen writes: > Will I now have to tell her to do this for each list she is subscribed to: > > > Select ‘Mailman Settings’ in dialog pulldown. > Select one of the lists listed. > Click on ‘Manage Subscription.’ > In ‘Select Emai’, select the ‘Primary Address’ pulldown option > Click on ‘Change email used for subscription.’ Yes, that appears to be the case currently. > Someone on list some time ago advised me that it was possible to do > this easily globally. I think that what they are referring to is that if you 1. Create a user account. 2. Set and authenticate a primary email address. 3. Allow all subscriptions to inherit from 'primary email address' (rather than setting any address explicitly) *then* 4. Changing the primary email address will change the subscribed address to all the lists. Or they might have meant doing it with a script. But I didn't find a way in Postorius. > Please make this easy, as I get these requests all the time and > some, like this one, are on many lists. I don't have the Postorius knowledge to do this in a reasonable amount of time to help your user immediately, but how about this design: In the 'Mailman Settings' screen, List-based Preferences' tab, currently each list has an active link at the list's posting address (which links to a page with the same options carefully documented), a plain text display of the subscribed address, and a row of options. Suppose we 1. Add a popup menu of addresses and attach it to the displayed address for each subscription, 2. Add a 'select subscription' checkbox to each subscription. 3. Add an 'act on all selected subscriptions' fake subscription, whose checkbox has the effect of select or deselect all. I guess this should be at the top.[1] Does that seem like what you have in mind? Any other needs you want to mention? (Suggestions for feature design are welcome, but "I do this often and there's got to be a better way" is good too.) Regards, Steve Footnotes: [1] Notes to implementers: The 'act on all' row needs tristate options. It should be at the top. The "fake list" itself can be a link to a heavily documented page like the regular per subscription page but with a couple of notes on the special behavior of the selection checkbox and the tristate options. When we "subscribe by address" (mass subscribe, email subscribe) rather than via a logged-in user, we should create a user, give it that primary address, and subscribe by primary address rather by that address literally.

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

3 years, 11 months

Re: MIMEDefang to fix footers

by Mark Sapiro

On 11/13/20 9:51 AM, Ryan Morash wrote: > Does anyone know how to use MIMEDefang to fix the footer as attachment issue when using Mailman3? I've seen several guides/scripts referring to its use with Mailman2, but I'm unsure of how they would match with Mailman 3. I don't use MIMEDefang and don't specifically recommend it, but I have looked at <https://stuff.mit.edu/~jik/software/mailman_mimedefang/>, and it seems that the only Mailman specific things involved in the installation and configuration of this script are the addition of the "MAILMAN_MIMEDEFANG" lines as the first and last lines of the footer template. The only thing Mailman 3 specific in that is how to edit the footer template. This can be done on a per-list basis via Postorius since 1.2.0 or more directly in Mailman core by setting URIs, see <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> or by creating templates in Mailman's var/templates directory, see <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

Mailman-users search results for query "Postorius"