Search results for "Postorius" - Mailman-users

Re: howto reallow a banned email ?

by Mark Sapiro

On 6/18/19 9:12 PM, Nicolas Pettiaux wrote: > > By mistake a user has been banned to post to mailman list. How can I > allow him not only to post but also to become a member of a list ? > > I have not found any info on the web, or I have been unable to search > correctly. Do you have the Postorius web UI in your installation? If so go to the list's Ban List and remove the unwanted entry. Or is this perhaps a Mailman 2 question? If so you'll find the ban_list in the web admin UI at Privacy options... -> Subscription rules. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

Re: Another set of new releases

by Abhilash Raj

On Sat, Jan 18, 2020, at 6:18 AM, Torge Riedel wrote: > Am 13.01.20 um 03:42 schrieb Abhilash Raj: > > - Django-mailman3 1.3.2 > > Hi, > > are there somewhere release notes for Django-mailman3? Unfortunately, no. I've been meaning to create one, but mostly it is an internal library and any user facing changes are documented in the changelog for Postorius and Hyperkitty. If you look at the commits[1] since last release, there wasn't much changed except for new translations. https://gitlab.com/mailman/django-mailman3/compare/1.3.1...1.3.2 > > Thanks for your work and regards > Torge > _______________________________________________ > 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)

5 years, 5 months

Re: If I manually add email addresses to a list and then delete them, how do i permanent delete them from Users?

by Andrew Hodgson

Mark London wrote: >I added some email addresses manually to a mailing list and then removed them. But now I can't find how to totally remove them from mailman3. They show up in the Users list. You may find this script useful: https://www.msapiro.net/scripts/clean_users.py I have it running in a cronjob. Thread discussing the script can be found here: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… TLDR you end up with orphaned Django users both from when users subscribe/unsubscribe and due to spam signups using the Postorius form which never get confirmed. Thanks. Andrew.

2 years, 1 month

Re: How to authorise members visibility?

by Mark Sapiro

On 5/25/22 02:50, Pierre Malard via Mailman-users wrote: > Hello, > > My setup: > - Debian 11 > - Mailman3-full v 3.3.3-1 > > My Question: > How to configure the visibility of a list of subscribers to a list? > > I created a list and set "subscriber visibility" to subscribers only. When I log in as such and try to view the list information, I can't see anywhere how to display that list. > It's the same regardless of the setting used for this "subscriber visibility" field (only moderators, only subscribers or anyone). This is a bug in Postorius. See https://gitlab.com/mailman/postorius/-/issues/369 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

Re: Unable to remove non-member

by Mark Sapiro

On 9/28/20 6:43 AM, Brian Carpenter wrote: > Hi Everyone, > > I ran across a strange issue today. A client reported the inability to > remove a non-member in the following format: > > z_email/domain.org.za(a)domain.org.za > > The reported error from Postorius was: > > "The user could not be removed" Is that all it said? The code says it is The user could not be removed: <error message> Where <error message> is the relevant HTTP error. > I used https://verifalia.com/validate-email to validate the email > address and it is syntactically correct. Mailman core thinks it's OK too as does RFC5322. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

Re: Help needed to create filters that were working in Mailman 2.

by Mark Sapiro

On 6/21/23 11:36 AM, mrl(a)psfc.mit.edu wrote: > I'm using version 1.3.8 Which I installed on Ubuntu 22 on April 18. I'm guessing this feature was installed in 1.3.9? The attached screenshot (which may not make it to the list but should be in your direct copy) is from Postorius 1.3.8 installed via pip. If you don't see this, possibly you have installed the Debian/Ubuntu package and this is a Debian issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: Screen Shot 2023-06-21 at 1.07.49 PM.png

2 years

There are currently no mailing lists!?

by Christian

I recently upgraded Debian 10 'buster' and when I logged in to Postorius in the browser I got the ' Mailman REST API not available. Please start Mailman core' message. So I started it up from the command line doing 'sudo -u mailman /opt/mailman/mm/venv/bin/mailman start -f' which yielded Starting Mailman's master runner Generating MTA alias maps mailman@lists: Now when I do ' https://lists.ccalternatives.org/mailman3/lists/?all-lists' in my browser I get the message ' There are currently no mailing lists.' Meanwhile their archives exist. Are the lists actually gone or ? What am I doing wrong/what's going on here please? Thank you in advance. One more thing...I am running mailman core version GNU Mailman 3.3.5, Core API Version 3.1, and Core Python Version 3.7.3.

11 months

Re: missing links in admin request mail Fwd: New subscription request to Mm3-test-mem from hstahl@uw.edu

by Brian Carpenter

On 2/25/21 5:26 PM, Stephen Willey Mats Mats wrote: > Mailman2 and other mailman3 installs I’ve seen included links in the moderation ‘requires approval’ or list subscription request approvals. But the messages from my mailman3 server does not have the links. What configuration am I missing? > > I’m running off the stable 0.3 docker images as updated this morning to the current releases (3.3.3, 1.3.4, 1.3.4) > > thanks, > steve Hi Steve, You will need to edit the templates for those notifications via Postorius and add the URL to your Mailman 3 admin UI. I believe the templates are: list:admin:action:post list:admin:action:subscribe -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 3 months

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

4 years, 4 months

Mailman-users search results for query "Postorius"