Search results for "Postorius" - Mailman-users

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, 4 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, 9 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, 9 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, 2 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, 10 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, 6 months

Re: One-click unsubscribe?

by Stephen J. Turnbull

Jered Floyd writes: > > As I discovered (to my chagrin) Mailman's current simple RFC > > 2369 List-Unsubscribe field doesn't, even for personalized lists where > > there might be a personalized link in the footer. > > My understanding from up-thread is that the RFC 2369 headers are > added pre-personalization. They are. It would also be trivial to personalize them; they just aren't. > If we add a timestamp to the encrypted token I suggest there should > be a pretty broad window allowed (i.e. several months). I guess it would be a matter of keeping 2 tokens in the database. > > Safety would suggest adding a random nonce and that would need to > > be saved in the database.) > > Do you just mean a salt? Or are you suggesting adding a > per-subscription nonce stored in the DB? (In which case, that could > simply be the URI token...) Per-subscription and it would be the URI token. > I agree with your analysis, but this would be a very specialized > attack, especially if we don't provide direct feedback on if the > request was successful (which we are not required to do). I think we do need to provide feedback, at least when the request fails due to an expired token. > I have trouble constructing a practical threat here I don't know if there's a practical threat. I don't think the known plaintext attack on the key is practical if we use a key dedicated to this purpose. You'd need at least a large university's collection of tokens, and what could you do with it that would be worth the effort? The DOS attack is practical if encryption is expensive enough. But storing the token would make that a single database lookup. > and I think the encrypted tuple, or a plaintext tuple and truncated > HMAC (like how SRS works) would be sufficient. Checking the encrypted tuple is cheaper and simpler. > The real risk without a per-subscription random unique identifier > would be a replay attack -- the user is unsubscribed multiple > times? That feels outside of the threat model. The identifier has to be unique to the subscription. If there are multiple valid unsubscriptions, the later ones won't have an existing subscription to unsubscribe. That does argue for the nonce -- that would stop the attack in the case where the user resubscribes. > > And you could combine the two strategies which would allow sites that > > don't use Postorius to configure the reverse proxy, while sites that > > do would get it for "free" since we'd configure Postorius to do it. > > I hadn't considered this -- I definitely like this approach because it > means the same function need not be implemented twice, differently. OK, that's part of the design we'll start with. > guess the big question is now just what the simplest content of the URI > should be. I think there should be just an opaque token plus an optional expiration date for sites paranoid enough to have a rotation policy for the keys. We need to do some thinking about how to implement "several months validity" in case of a sudden key change. The expiration date is irrelevant to the implementation of 8058, it's just for the benefit of the user (and data collection for how old the token is, I guess). This is shaping up pretty well, I think. > The Internet is an increasingly hostile place. True enough. > Regardless, not something we can do much about. There's hope. When Yahoo! and AOL broke the Internet in 2014 by setting p=reject DMARC policies, the Ministry of Education issued "administrative guidance" that *yahoo.* addresses should not be used for school business, and my university sent them all to spam. ;-) Including yahoo.jp which did not have a p=reject policy. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

5 months, 3 weeks

Re: mailman admin (django) interface does not work anymore after deleting website example.com

by Torge Riedel

Am 10.03.19 um 16:44 schrieb Mark Sapiro: > On 3/10/19 8:18 AM, Torge Riedel wrote: >> I deleted the existing "example.com" and added a new one >> "lists.mydomain.de". >> >> Now the admin (django) interface always gives "An error occurred while >> processing your request". After one of the first navigation clicks I saw >> a message that "site with id 1 is missing". > > In your Django settings your have > > SITE_ID = 1 > > which pointed to the example.com domain you deleted. > > You need to override this in settings_local.py. Probably > > SITE_ID = 2 > > but if that doesn't work, try '0' > Ah, thank you Mark. That makes a kind of sense. I changed the database directly to fix it. And renamed example.com to lists.mydomain.de. Now the error is gone. I'm wondering why the initial database set up of postorius (?) adds "example.com". Is there a way to directly add my domain instead? Somewhere in settings_local.py?

7 years, 2 months

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.

4 years, 10 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, 2 months

Mailman-users search results for query "Postorius"