Search results for "Postorius" - Mailman-users

Mailman 3 installation documentation

by Abhilash Raj

Hi All, I have been trying to work on revamping the documentation site we have at https://docs.mailman3.org. It is on https:// but I am not sure why the http->https redirect doesn't work in Readthedocs. I have set it to "serve always from https". Anyway, it might not look too different right now, but there are some small re-organizations. I have been learning some new ReST and Sphinx tricks and been trying to cross-reference and link various sections and settings. The docs site shows up Mailman's logo now (I didn't even know we could do that ;-). There is a place[1] for all supported Django settings that Postorius and Hyperkitty have. I am also planning to add some common Django settings that often people have to lookup and is not fun for people from non-python backgrounds. Hopefully, it will make lives easier for administrators. I have reverted my own stupid decision to use "sudo pip3 install" in the docs to instead use virtualenv. The installation docs are going to grow to be more comprehensive. I am also working on mailman-web project[3], which should simply installation process for all the web components using a single project and provide better guidance on Django's settings file management and howto run manage.py commands. I have added a `mailman-web` command, which, for those of you familiar with internal details of Django, is going to be our custom manage.py script. It sets up settings correctly and would hopefully reduce the pain of using `django-admin` and/or finding out the right path for `manage.py` script. It is still not ready for prime time, but it is usable. Early adopters can play with it if they like! I would really appreciate if people who have tried to manually install Mailman 3 in the past would share their experiences about what they think could be documented better. You can reply here or open an issue[2]. The user documentation are going to follow, hopefully soon :) [1]: https://docs.mailman3.org/en/latest/config-web.html#configure-postorius-hyp… [2]: https://gitlab.com/mailman/mailman-suite-doc/issues [3]: https://gitlab.com/mailman/mailman-web -- thanks, Abhilash Raj (maxking)

5 years, 1 month

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/ >

3 years, 9 months

Re: Mailman, etc. upgrade woes and persistent bugs

by Stephen J. Turnbull

Brian Carpenter writes: > I was going to respond in detail but it will be an effort in futility. > My opinions are DEFINITELY not valued by you But they are. I 100% buy the part about providing full option data and controls in the list format (as in Mailman 2). Isn't that the most important aspect of your proposal for Postorius? In the rest of the discussion, all I did was ask what are the use cases for distinguishing admin-disabled from user-disabled. I don't know anybody better to ask than you! IMO, these use cases matter, because as I explained in another post, it seems it would be useful to provide the admin with *more* information than just the disabling agent in cases where an admin is considering reenabling a disabled subscription. I could be wrong, that's why I ask. I apologize for not ending with a question mark, I should have done so. I ask again, please, if you know, explain when admins are reenabling disabled subscriptions (other than the OP's mass disable case, which I think we understand pretty well). I personally have never reenabled a subscription except at user request. I understand my experience is extremely limited AND biased, but it is what it is, and it's all I have right now. I wouldn't be surprised if Mark's and Abhilash's are similar (although Mark does have his bicycle club list, and they're mostly not power users). So, please share yours. As for the abandoning Postorius part, do you think that hurts my feelings? On the contrary, if you can do that, I feel pride. Affinity being proprietary hurts my feelings (even though I understand perfectly well why it's necessary), but list admins and subscribers benefitting from Affinity is vindication of Barry's decision to split out the UIs from the core, despite the pain that causes some site admins. I had nothing to do with that decision, but I'm happy to be associated with a project that cares enough for users to enable such progress. Sincere regards, Steve

3 years, 9 months

Re: 3rd Party Account is not working

by kwp.klein＠gmail.com

Here is my /mailamn/config/mailman-web/settings_local.py. I get an error message curl http://172.19.199.3:8000/postorius/lists/ curl: (7) Failed connect to 172.19.199.3:8000; No route to host Please comment out all the lines that are not necessary. MAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = '172.19.199.1' EMAIL_PORT = 25 USE_SSL = False INSTALLED_APPS = ( 'hyperkitty', 'postorius', 'django_mailman3', # Uncomment the next line to enable the admin: 'django.contrib.admin', # Uncomment the next line to enable admin documentation: # 'django.contrib.admindocs', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'paintstore', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', #'django_mailman3.lib.auth.fedora', #'allauth.socialaccount.providers.openid', #'allauth.socialaccount.providers.github', #'allauth.socialaccount.providers.gitlab', #'allauth.socialaccount.providers.google', )

3 years, 9 months

Re: Mailman 3 installation, no mails in hyperkitty, unable to add footer.

by Mark Sapiro

On 8/23/19 8:11 AM, ugniusviln(a)gmail.com wrote: > I have read documentation, but still have stupid questions, could You please help, because I can't make it working. I do not understand something important. I have no experience with python at all. I have mailman 3, python 3.5 in my debian OS system, and additional packages like uwsgi and ect. using https://buildmedia.readthedocs.org/media/pdf/gnu-mailman/latest/gnu-mailman… about till chapter 6. I understand mailman suite has hyperkitty already. But I am not sure about: > > 1. Does mailman-suite have hyper-kitty inside? Because if I run $python manage.py runserver - it runs. In installed it under dedicated OS user home and fonfigured to run. > I can create lists, event add lists to hyperkitty page using: $django-admin runjob new_lists_from_mailman list server sends messages to list members as well. But nothing happens more. No emails come to hyperkitty, arciver log 0 size. > $ python manage.py runjobs -l shows the lists of the jobs, so seems nothing to add. How exactly did you install Mailman? The document you reference gives alternatives. You don't say exactly what you did. > 2. If I (using Postorius web interface) add footer template to my list under regular message, something strange happens. Mailman stops to send messages for list members. No any entries in the logs. Just Mailman log writes: "unable to connect localhost port 25" and no more explanation. If I delete list's footer template (web interface), mailman starts working again. What is bad here? How to add custom footer? In mailman 2 if was working so good and was easy to setup. It appears that no MTA is listening on localhost port 25. Is your MTA even running? It is extremely unlikely that this has anything to do with adding a termplate in Postorius. You might be better off installing Debian's 'mailman3-full' package <https://packages.debian.org/search?keywords=mailman3-full&searchon=names&su…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

Still unable to get mailman3 working on Ubuntu 20.04 LTS

by Stephen J. Turnbull

Michael Heseltine writes: > and type in the password listed in settings_local.py, All of the settings*.py files are for Django, that is, for Postorius and HyperKitty. Configuration of Mailman 3 core is mostly done in .cfg files, typically in /etc/mailman but I don't know about the instructions you're following. From docs/database.rst: You would then need to set both the `class` and `url` variables in `mailman.cfg` like so:: [database] class: mailman.database.postgresql.PostgreSQLDatabase url: postgres://myuser:mypassword@mypghost/mailman The "class" line is verbatim. In the "url" line the words beginning with "my" are dummies that you need to replace with the appropriate values. Howto_Install_Mailman3_On_Debian10 provides a template for mailman.cfg which you may want to copy and customize at least the passwords) Steve

2 years, 10 months

Mailman 3 Internationalization setup

by Abhilash Raj

Hi All, Mailman 3 is now setup for continuous internationalization. We are using Hosted Weblate[1], which is the hosted service for the Weblate project[2]. It is actually quite nice and I've been learning how to properly document a Django project from it's documentation. Which brings me to it's documentation. Weblate has great documentation for translators[2]. The UI pretty simple and should be easy to navigate around. We have setup the workflow in a way that each commit in Gitlab generates a webhook and updates Weblate. Weblate is then able to pull all the changes in real time. To pull translations back into Gitlab, I have a custom script running every night that pulls translations (as commits) and generates pull requests against the upstream repos. Weblate has the ability to automatically push the translations back, but for security reasons, I didn't want to give a 3rd party service direct push access to our repos. I've been working on a Patch to Weblate[3], which would allow it to send translations as Merge Requests (as compared to direct-push). After it is merged and deployed at hosted.weblate.org, I hope I can retire my custom script. We have setup the following projects: - Mailman Core (https://hosted.weblate.org/projects/gnu-mailman/mailman/) - Postorius* (https://hosted.weblate.org/projects/gnu-mailman/translations/) - Hyperkitty (https://hosted.weblate.org/projects/gnu-mailman/hyperkitty/) - Django-mailman3 (https://hosted.weblate.org/projects/gnu-mailman/django-mailman3/) There should be empty .po files generated for most languages supported by Django and Mailman Core. If there are any questions or bugs related to source strings, please send out an email to mailman-developers(a)python.org. The current translation %age is pretty low, hopefully we'll be ale to get it close to Mailman 2 sometime soon :) [1]: https://hosted.weblate.org/projects/gnu-mailman/ [2]: https://docs.weblate.org/en/latest/user/translating.html [3]: https://github.com/WeblateOrg/weblate/pull/3024 [*] Yeah, the URL for Postorius is a bit weird, because it was called "translations" before. At the time, I didn't know the difference between a project and a translation component in Weblate terminologies. And they don't give out permissions to change the URL, so we're maybe stuck with it. -- thanks, Abhilash Raj (maxking)

5 years, 1 month

Re: at the finish line of mailman3 docker, but can't sign in.

by Abhilash Raj

On Fri, Jul 30, 2021, at 12:23 PM, bob B wrote: > ok > > ./manage was the piece I was missing so getting closer :). > > I set the MAILMAN_ADMIN_EMAIL in the .yaml, but what url do I use to login ? > > > http://mailman.domain.com/postorius/lists/. **This url does not like > the email address I used for forget password. Your email has to be confirmed by Postorius for you to login at /accounts/login. MAILMAN_ADMIN_EMAIL requires you to go through the forgot password process to set an actual password, it doesn't set a default password. If you email setup is broken for some reason and you can't get it working, one thing you could do is ask Django to simply print the outgoing emails to stdout by adding the following to the settigns_local.py (and restarting mailman-web container): EMAIL_BACKEND = 'django.core.mail.backends.console.EmailBackend' You can find the emails in `docker logs mailman-web` output (or whatever the command for container's stdout is) and click on the link to verify and login into your account. > or > http://mailman.domain.com/admin **** this url has no > password reset option To reset, you want to go to /accounts/password/reset/. URL should be findable from the Sign In page. > > I added that environment variable "MAILMAN_ADMIN_EMAIL" after i already > upped my containers, > > But I then ran "docker-compose down" then "docker-compse up -d". Does > that reload and setup everything again? or could that be the issue? It reloads the configuration, but the admin is created in database, so that isn't re-created. > > > When I tried to send the test email it said "socket.gaierror: [Errno > -2] Name does not resolve" sp maybe my mailman-web container can get > dns??? Yeah, seems like something is wrong with the DNS setup there. What version of container images are you using? Also, what is the value of SMTP_HOST? Do you have that setup to point to the MTA? -- thanks, Abhilash Raj (maxking)

3 years, 3 months

Re: Held messages page not rendering the message

by mike-mailman＠earth.li

Thanks Peter My javascript console does not have the errors listed in that bug - instead I have: This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. held_messages Source map error: Error: request failed with status 404 Resource URL: https://downtonband.org.uk/mailman3/static/postorius/libs/popperjs/popper-v… Source Map URL: popper.min.js.map Source map error: Error: request failed with status 404 Resource URL: https://downtonband.org.uk/mailman3/static/postorius/libs/bootstrap/js/boot… Source Map URL: bootstrap.min.js.map I'm also on an older version of the debian packages than listed in that bug... still I tried the suggested fix just in case but it did not help. Thanks for the suggestion though - it certainly looks similar.

1 year, 8 months

Re: Update a member's display_name

by Mark Sapiro

On 1/16/19 7:24 AM, Nick Wynja wrote: > I believe I figured it out. > > I was updating `user.display_name` when the name I was seeing in Postorius was `user.addresses[0].display_name`. > > Here are all of the steps for anyone looking to solve the same thing: If you are using mailman shell, the next 2 are not necessary > from mailman.interfaces.usermanager import IUserManager > from zope.component import getUtility IUserManager and getUtility are already in the namespace created when mailman shell starts. And this one > from mailman.testing.documentation import dump_list isn't needed here. > user_manager = getUtility(IUserManager) > > u = user_manager.get_user('aperson(a)example.com') > u.addresses[0].display_name = "Anne" > commit() -- 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

Mailman-users search results for query "Postorius"