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, 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, 2 weeks

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

10 years, 1 month

Re: A poll: "Delete this thread"

by Odhiambo Washington

On Fri, Jun 21, 2024 at 5:46 PM Sam Darwin via Mailman-users < mailman-users(a)mailman3.org> wrote: > Thanks for the replies. Not yet a close match to what I have installed. > Jeremy is using Dockerfiles. Marc is running mailman3-web from 4 years ago > "20200530". I may need to dig into the code and attempt to debug, line by > line. "Oh, of course, in your settings refresh_cache needs to be set to 1, > you have it set to 0", or something obscure like that. Or who knows. > I am running the latest MM3 stable code, I believe, and I can delete a thread without any problems. Running in a virtualenv. Mailman 3.3.9, Postorius Version 1.3.10, HyperKitty version 1.3.8. ``` Mailman Core Version GNU Mailman 3.3.9 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] ``` -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 3 months

Try to Implement Template for The message sent to subscribers when a subscription confirmation is required

by msok＠lalawlibrary.org

My NGINX configure redirect for HTTP to HTTPS. For the domain below, mailman.example.com = my actual domain -NGINX config server { # EXTERNAL: Redirects all port 80 traffic to HTTPS listen 80 default_server; listen [::]:80 default_server; # server_name mailman.example.com; server_name mailman.example.com; # no issue for accessing from outside, it will redirect to https return 301 https://$host$request_uri; # Redirect http to https server_tokens off; } # INTERNAL: Listens ONLY on 127.0.0.1 to handle local HTTP requests server { listen 127.0.0.1:80; server_name localhost; location / { include uwsgi_params; uwsgi_pass unix:/run/mailman3-web/uwsgi.sock; uwsgi_param HTTP_HOST $host; } location /mailman3/static { alias /var/lib/mailman3/web/static; } location /mailman3/static/favicon.ico { alias /var/lib/mailman3/web/static/postorius/img/favicon.ico; } -The URL syntax https://mailman.example.com/mailman3/lists/list-id/confirm/?token=$token -The error message when tried to add subscriber HTTP Error 400: HTTPSConnectionPool(host='localhost', port=443): Max retries exceeded with url: /postorius/api/templates/list/list-id/list:user:action:subscribe (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1029)'))) Please help! Thanks, Marin

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

8 months, 1 week

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

9 months, 2 weeks

Mailman-users search results for query "Postorius"