Search results for "Postorius" - Mailman-users

Re: Heads up: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated

by Andreas Vetter

I created a new issue: https://gitlab.com/mailman/mailman-web/-/issues/35 On Freitag, 7. Februar 2025 12:19:22 CET Andreas Vetter wrote: > Hello, > I have a venv installation of: > mailman postorius django-mailman3 hyperkitty mailman-web > I just did a > pip install -U --upgrade-strategy eager > > When running > mailman-web runjobs -l > I get the following Warning: > System check identified some issues: > > WARNINGS: > ?: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated, use: > settings.ACCOUNT_LOGIN_METHODS = {'email', 'username'} > > I guess this is from allauth (version django-allauth-65.4.1). > > Changing ACCOUNT_AUTHENTICATION_METHOD to ACCOUNT_LOGIN_METHODS in > /etc/mailman3/settings.py is not enough. One has to edit > venv/lib/python3.11/site-packages/mailman_web/settings/mailman.py -- Mit freundlichen Gruessen, Andreas Vetter

1 year, 7 months

Re: Message Personalization: embed User name in header/footer

by Mark Sapiro

On 05/06/2018 11:30 PM, Johannes Winter wrote: > Am Sun, 6 May 2018 07:26:45 -0700 > schrieb Mark Sapiro <mark(a)msapiro.net>: >> >> We're working on getting template editing in Postorius for release >> later this month. >> > > Cool! I hope you also fix this issue > https://gitlab.com/mailman/mailman/issues/409 while doing do? The two things are related only in that they both involve templates which is not to say that we won't come up with something for https://gitlab.com/mailman/mailman/issues/409 but only that they aren't a "package". -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 4 months

Re: Python 3.9 support

by dancab＠caltech.edu

Thanks for your help Mark. We use AWS RDS for MySQL. I found there was an automated update applied by AWS around the time show in the logs for the error. Feb 23 23:27:10 2022 (300) Uncaught runner exception: (pymysql.err.OperationalError) (1053, 'Server shutdown in progress') The outage lasted for about 1 minute. We have Mulit-AZ failover configured for RDS and a new DB instance started within that minute. What is interesting is that Hyperkitty archiving continued to work and Postorius was still responsive. Only mail delivery was hung overnight. I had to restart the Gunicorn process followed by a Mailman core restart for mail to flow again. Any insight into how we could monitor this in the future? For example which specific "runner" reported the error above? Thanks again. -- Dan

4 years, 6 months

Update a member's display_name

by Nick Wynja

Hi all, I want to update some list member's display_name either with mailman shell or mailmanclient. These mostly aren't users in Postorius so I only want to operate on the subscribed list member. I've tried everything I can find in the docs and am stuck. I've tried using `user_manager.get_user()` and then updating `user.display_name` followed by a `commit()` but it doesn't seem to persist the change. The `absorb_existing` flag for mailmanclient's `User.add_address()` looks promising but the docs read "It will import the existing user into the current one, not overwriting any previously set value." which in some cases, the member already has a display_name set. I haven't tried this yet. I'd appreciate any help pointing in the right direction. Thanks, Nick

7 years, 8 months

Re: Cannot request password reset: "The e-mail address is not assigned to any user account"

by dave＠aasv.org

The concept of a Django user sounds like the big thing I was missing. Thank you; I believe I have resolved the immediate need. I'm thinking, then, that if I want to be able to programmatically create the Django users in parallel with our Mailman users (I don't want to have registration open to the world), I'm going to have to do some coding... either create some sort of Postorius API or perhaps better would be to make a social / OAuth plug-in that will use our existing membership site. (Once I get stuck on that, I'll switch to the developer list.) Thanks again.

4 years, 7 months

Re: Emergency Moderation

by Abhilash Raj

On Sun, May 24, 2020, at 11:34 AM, Mark Sapiro wrote: > On 5/24/20 10:59 AM, Allan Hansen wrote: > > In the MM3 settings there is an option to ‘Hold for moderation’ when members or non-members post to the list. > > I use that for the same cases where in MM2 I switched a list to ‘Emergency Moderation.’ > > > If you imported your MM 2.1 lists with `mailman import21`, `emergency` > was set appropriately for the imported list and should be working to > hold posts regardless of other settings. > > > > My own current top-of-the-list issues: > > > > A bug: Moderators can’t see/edit the list of members even when allowed to by list setting. > > The visibility issue is <https://gitlab.com/mailman/postorius/-/issues/369>. > > Editing membership beyond what could be done via the admindb interface > (i.e. clearing a moderated poster's mod flag) was never allowed for a > moderator in MM 2.1. > > In MM 3, a moderator can set a member's moderation when handling a held > post. Do you think a non-owner moderator should be able to make other > changes to a member? > > > > A feature request: Member changing email address on all lists he/she belongs to, without involving moderators. > > > This is <https://gitlab.com/mailman/postorius/-/issues/399> and we're > working on it. Another way to achieve this request, without needing the Preferred Address route is to simply Patch the Member resource with the new address, which wouldn't trigger the full subscription workflow and would have the extra advantage of having the same delivery_mode and preferences. I created: https://gitlab.com/mailman/postorius/-/issues/425 to track this issue. > > -- > 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, Abhilash Raj (maxking)

6 years, 3 months

Re: Help request, almost got it going, but ....

by Abhilash Raj

Hi Claus, On Fri, 1 Sep 2017 23:33:56 +0200 Claus-Justus Heine via Mailman-users <mailman-users(a)mailman3.org> wrote: > First: thanks for all those development work, I am aware of the fact > that this is free software and most of the development probably happened > in someones spare-time. > > I have some problems: > > - I tried to install mailman v3. "Read the (non) docs" was of little > help, but I got to some partly success following the commands in the > scripts in the docker image at > > https://github.com/maxking/docker-mailman If you can point out what were the few things that you think were missing in the docs but you were able to figure out using the scripts in container image, it would help us improve the documentation. You can send them here or open an issue on Gitlab project[1]. [1]: https://gitlab.com/mailman/mailman-suite-doc/issues > > Things seemed to work out, I generated a test-list "Playground" and now > I am just in the progress to click through all the configuration options > in the the postorius Web-GUI. So far so good > > Now I read the "Message Acceptance" tab AND here is the problem: > > Seemingly, at some point in the deep dungeons of the source code the > "Acceptable aliases" Text-Box is not interpreted correctly. > > Specifically, at the start it contains the string > > [] > > When then changing something int the "Message Acceptance" tab, an error > shows up in the web-page (but no-where in the logs) > > "An error occured: []" > > and the bogus [] is restored. I tried to dig into the source code, and > well, the data source of the text-field is an array or list of > acceptable email-adresses. But seemingly finally at some point in the > source code an empty list is not converted to the empty string, but to > the string []. > > I can get rid of the error message "An error occured: []" by inserting > an email-at '@' at just some place in the input box, this yields > (clicking "Save changes" again and againg ...): > > [u"[u'@']"] > [u'[u\'[u"[u\\\'@\\\']"]\']'] > [u'[u\'[u\\\'[u\\\\\\\'[u"[u\\\\\\\\\\\\\\\'@\\\\\\\\\\\\\\\']"]\\\\\\\']\\\']\']'] > > and so on. > > Unfortunately, I did not find the location of this bug, although I was > finally able to add some "foobar" string to the already bogus web-output. > > Any help would be appreciated. > > BTW: > * where is the bug-tracker for mailman3? > * The documentation is really, well, close to non existent. Personally, > I think the name of the URL "read-the-docs" is almost cynical. > > Guess I give up on it, it just does not seem to be ready for production. > > > This was (following the docker stuff at githb) with > > Pythong3: > mailman==3.1.0 > mailman-hyperkitty==1.1.0 > > Python2: > mailmanclient==3.1.0 > postorius==1.1.0 > hyperkitty==1.1.1 > django-mailman3==1.1.0 > > Here I realize a slight version difference between the hyperkitty stuff. > But this is a bug in postorius. So what. > > Thanks for any help, cheers > > Claus > -- thanks, Abhilash Raj

9 years

Re: Cron Error: <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs monthly

by Mark Sapiro

On 2/2/23 21:25, Odhiambo Washington wrote: > On Fri, Feb 3, 2023 at 3:23 AM Mark Sapiro <mark(a)msapiro.net> wrote: >> See >> >> https://gitlab.com/mailman/hyperkitty/-/blob/master/example_project/setting… >> for mitigation. > > > What is the danger of replacing my settings.py with this one, seeing as it > differs in a number of ways with mine? If your's works, don't do it. The danger is the differences might be significant and break things. Also, that one is for HyperKitty only and doesn't include Postorius settings. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

seems solved (was: Re: error changed after restart)

by Guillermo Hernandez (Oldno7)

On 7/2/21 19:33, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 7/2/21 19:04, Abhilash Raj wrote: Well... I did reinstall all mailman relationed apps with a pip install --upgrade --force-reinstall --no-deps --no-cache-dir django-mailman3 mailman mailman-hyperkitty mailmanclient Restarted thee apache24 server... Aaaaaand closed de admin session and reopened it... (just for a "what if" sensation). I can not tell what have been the solution here, but now I can access the administrative pages and attend de pending subscriptions and discard retained messages. Thanks Abhilash and Mark for your support. >> >> On Sun, Feb 7, 2021, at 1:07 AM, Guillermo Hernandez (Oldno7) via >> Mailman-users wrote: >>> On 6/2/21 21:19, Abhilash Raj wrote: >>>> >>>> On Sat, Feb 6, 2021 at 19:44, Guillermo Hernandez (Oldno7) via >>>> Mailman-users <mailman-users(a)mailman3.org> wrote: >>>>> On 6/2/21 18:08, Abhilash Raj wrote: >>>>> >>>>> On Sat, Feb 6, 2021, at 3:04 AM, Guillermo Hernandez (Oldno7) >>>>> via >>>>> Mailman-users wrote: >>>>> >>>>> I restarted de server and the error changed. Now the log >>>>> shows "KeyError: 'subscription_mode'": >>>>> >>>>> Did you also restart Mailman Core after the upgrade? >>>>> >>>>> Yes, indeed: I stopped mailman core and all the processes related. >>>>> Did the upgrades. Started all again. Find the errors in the web user >>>>> interface. Stopped all again. Looked for errors in the log. Restarted >>>>> the complete server. Found the second error that this second mail is >>>>> about to. It happens when, in the main page that shows all the lists >>>>> you click to see one of them. It seems to me that it has been >>>>> database structure changes in django that the upgrade is not aware... >>>>> but it's a very long shot from my side. >>>> `subscription_mode` was added in Mailman Core 3.3.2 and it is actually >>>> a derived atrribute and not stored in Database. Mailman's API >>>> should be >>>> returning this attribute for each Member, but for some reason it seems >>>> to me like it isn't doing that even though do have Mailman 3.3.3 >>>> running >>>> like you said. >>>> If you have Curl installed, can you send me the output of: >>>> $ curl -u <user>:<pass> >>>> http://localhost:8001/3.1/members?count=5&page=1 >>> This is the output you asked for (it's the same you can see when you >>> try >>> to interact with one list): >>> >>> /usr/local/mailman3 # curl -u XXXXXX:XXXXXX >>> http://localhost:8001/3.1/members?count=5&page=1 >>> /usr/local/mailman3 # <html> >>> <head> >>> <title>Internal Server Error</title> >>> </head> >>> <body> >>> <h1><p>Internal Server Error</p></h1> >>> >>> </body> >>> </html> >>> >>> No log entry has been produced... >> This is weird, if you have working Core, then there should be *some* >> json returned >> from the above command. Do you have the Gunicorn running? > I have the uwsgi approach running... >> What is the >> output of `ps -ef | grep mailman`? > > none > > but if I do an ps ax | grep mailman it shows > > /usr/local/mailman3 # ps ax | grep mailman > 26803 - IsJ 0:00.87 /usr/local/bin/python3.7 /usr/local/bin/master > --force -C /usr/local/mailman3/var/et > 26834 - SJ 0:07.57 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26835 - IJ 0:05.84 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26836 - SJ 0:07.16 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26837 - SJ 0:08.74 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26838 - SJ 0:03.16 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26839 - SJ 0:07.07 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26840 - SJ 0:08.12 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26841 - SJ 0:09.07 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26842 - SJ 0:07.45 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26843 - IJ 0:00.95 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26844 - SJ 0:07.27 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26845 - SJ 0:07.69 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26859 - IJ 0:01.01 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26860 - IJ 0:05.75 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 50153 - IsJ 0:00.16 /usr/local/bin/uwsgi --ini > /usr/local/mailman3/uwsgi.ini > 50481 2 S+J 0:00.00 grep mailman > 26808 1 SJ 0:02.09 /usr/local/bin/uwsgi --ini > /usr/local/mailman3/uwsgi.ini > 26832 1 IJ 0:00.00 /usr/local/bin/uwsgi --ini > /usr/local/mailman3/uwsgi.ini > >> Are you able to run `mailman members` command to list the members of >> a list? > > Yes. All the commands are working as expected. > >> Also, how did you actually install Mailman? > > Using pip. Here is a detailled post of how I did put all together: > > https://forums.FreeBSD.org/threads/mailman-3.61050/post-488128 > > Thanks for your support > >> >> Abhilash. >> >>> TIA. >>> >>> >>> >>> >>>> It should ideally return an output that looks something like shown >>>> here[1]. You >>>> can put the username/password of Core's API server in the above >>>> command. >>>> [1]: >>>> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… >>>> >>>> >>>> Abhilash >>>>> I'm using sqlite as django database and mysql for mailman. >>>>> >>>>> ERROR 2021-02-06 11:47:49,015 26798 django.request Internal >>>>> Server Error: >>>>> /mailman3/mailman3/lists/name_and_domain.of.the.list >>>>> Traceback (most recent call last): File >>>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>>>> >>>>> line 119, in __getattr__ return self._get(name) File >>>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>>>> >>>>> line 86, in _get raise KeyError(key) KeyError: >>>>> 'subscription_mode' During handling of the above exception, >>>>> another exception occurred: Traceback (most recent call >>>>> last): File >>>>> "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py", >>>>> line 34, in inner response = get_response(request) >>>>> File >>>>> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", >>>>> >>>>> line 115, in _get_response response = >>>>> self.process_exception_by_middleware(e, request) File >>>>> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", >>>>> >>>>> line 113, in _get_response response = >>>>> wrapped_callback(request, *callback_args, **callback_kwargs) >>>>> File >>>>> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", >>>>> >>>>> line 71, in view return self.dispatch(request, *args, >>>>> **kwargs) File >>>>> "/usr/local/lib/python3.7/site-packages/postorius/views/generic.py", >>>>> line 74, in dispatch return super(MailingListView, >>>>> self).dispatch(request, *args, **kwargs) File >>>>> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", >>>>> >>>>> line 97, in dispatch return handler(request, *args, >>>>> **kwargs) File >>>>> "/usr/local/lib/python3.7/site-packages/postorius/views/list.py", >>>>> line 295, in get member.subscription_mode == File >>>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>>>> >>>>> line 124, in __getattr__ self.__class__.__name__, name)) >>>>> AttributeError: 'Member' object has no attribute >>>>> 'subscription_mode' *********************** some info about >>>>> the installed versions via pip list: pip list | grep django >>>>> django-allauth 0.44.0 >>>>> django-appconf 1.0.4 >>>>> django-compressor 2.4 >>>>> django-extensions 3.1.0 >>>>> django-gravatar2 1.4.4 >>>>> django-haystack 3.0 >>>>> django-mailman3 1.3.5 >>>>> django-picklefield 3.0.1 >>>>> django-q 1.3.4 >>>>> djangorestframework 3.12.2 pip list | grep mailman >>>>> django-mailman3 1.3.5 >>>>> mailman 3.3.3 >>>>> mailman-hyperkitty 1.1.0 >>>>> mailmanclient 3.3.2 pip list | grep >>>>> postorius >>>>> postorius 1.3.4 On 6/2/21 11:12, >>>>> Guillermo Hernandez (Oldno7) via Mailman-users wrote: >>>>> >>>>> I've just upgrade mailman 3 installation following Mr. >>>>> Sapiro advice: did a pip install --upgrade >>>>> django-mailman3 hyperkitty mailman mailmanclient >>>>> mailman-hyperkitty postorius I did a "python3 manage.py >>>>> migrate" after, too. And all seemed to run well. All the >>>>> lists showed in postorius via web, but when I try to >>>>> accesss into one of them the browser shows an error. In >>>>> the log you can see: *-*-*-*-*-*-* Traceback (most >>>>> recent >>>>> call last): File >>>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>>>> >>>>> line 119, in __getattr__ return self._get(name) >>>>> File >>>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>>>> >>>>> line 86, in _get raise KeyError(key) KeyError: >>>>> 'get_requests_count' .. (And after all the traceback >>>>> lines) AttributeError: 'MailingList' object has no >>>>> attribute 'get_requests_count' *-*-*-*-*-*-*-* The lists >>>>> seem to be distributing messeages well.. but I cannot >>>>> acces via web administration (django/postorius) Can >>>>> anyone point me in the right direction to solve this, >>>>> please? _______________________________________________ >>>>> Mailman-users mailing list -- mailman-users(a)mailman3.org >>>>> <mailto:mailman-users@mailman3.org> To unsubscribe send >>>>> an email to mailman-users-leave(a)mailman3.org >>>>> <mailto:mailman-users-leave@mailman3.org> >>>>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >>>>> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Mailman-users >>>>> mailing list -- mailman-users(a)mailman3.org >>>>> <mailto:mailman-users@mailman3.org> To unsubscribe send an >>>>> email to mailman-users-leave(a)mailman3.org >>>>> <mailto:mailman-users-leave@mailman3.org> >>>>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >>>>> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/> >>>>> >>>>> >>>>> _______________________________________________ Mailman-users mailing >>>>> list -- mailman-users(a)mailman3.org >>>>> <mailto:mailman-users@mailman3.org> To unsubscribe send an email to >>>>> mailman-users-leave(a)mailman3.org >>>>> <mailto:mailman-users-leave@mailman3.org> >>>>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >>>>> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/> >>>>> >>> >>> _______________________________________________ >>> 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/ >>> > _______________________________________________ > 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/ >

5 years, 7 months

Re: Python 3.13 compatibility

by Thomas Krichel

5 months, 3 weeks

Mailman-users search results for query "Postorius"