Search results for "Postorius" - Mailman-users

Re: mailman-web: ResponseNotReady

by Erin Justice

This looks similar to what I got when I installed mailman using sudo but then tried to start it using my standard user. I don't have a working install of mailman 3 at the moment to try it again for sure. -Erin > On Oct 18, 2017, at 9:00 AM, Dmitry Makovey <dmakovey(a)stanford.edu> wrote: > > > We've had an odd experience with mailman3 containers: > > ERROR 2017-10-18 15:47:09,448 60 django.request Internal Server Error: > /postorius/lists/ > Traceback (most recent call last): > File > "/usr/local/lib/python2.7/site-packages/django/core/handlers/exception.py", > line 39, in inner > response = get_response(request) > File > "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py", > line 249, in _legacy_get_response > response = self._get_response(request) > File > "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py", > line 187, in _get_response > response = self.process_exception_by_middleware(e, request) > File > "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py", > line 185, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/usr/local/lib/python2.7/site-packages/postorius/views/list.py", > line 590, in list_index > choosable_domains = _get_choosable_domains(request) > File "/usr/local/lib/python2.7/site-packages/postorius/views/list.py", > line 524, in _get_choosable_domains > return [(d.mail_host, d.mail_host) for d in domains] > File > "/usr/local/lib/python2.7/site-packages/mailmanclient/_client.py", line > 217, in __getattr__ > return self._get(name) > File > "/usr/local/lib/python2.7/site-packages/mailmanclient/_client.py", line > 183, in _get > return self.rest_data.get(key) > File > "/usr/local/lib/python2.7/site-packages/mailmanclient/_client.py", line > 172, in rest_data > response, content = self._connection.call(self._url) > File > "/usr/local/lib/python2.7/site-packages/mailmanclient/_client.py", line > 109, in call > response, content = Http().request(url, method, data_str, headers) > File "/usr/local/lib/python2.7/site-packages/httplib2/__init__.py", > line 1659, in request > (response, content) = self._request(conn, authority, uri, > request_uri, method, body, headers, redirections, cachekey) > File "/usr/local/lib/python2.7/site-packages/httplib2/__init__.py", > line 1399, in _request > (response, content) = self._conn_request(conn, request_uri, method, > body, headers) > File "/usr/local/lib/python2.7/site-packages/httplib2/__init__.py", > line 1355, in _conn_request > response = conn.getresponse() > File "/usr/local/lib/python2.7/httplib.py", line 1108, in getresponse > raise ResponseNotReady() > ResponseNotReady > > It seems like mailman-core is still operating properly, but for some > reason mailman-web is not. Can I reset mailman-web somehow to re-initiate? > > -- > Sr System and DevOps Engineer SoM IRT > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

8 years

Re: Mails are not archived at all -- how to check if Hyperkitty is running or not?

by Franklin Weng

Hi Stephen, Thanks for your explanation. Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> 於 2019年10月29日週二下午1:35寫道： > Franklin Weng writes: > > > However in the Archive section I couldn't see anything and all the > > lists were "inactive" and hence were hidden by default. > > If you can see that much, HyperKitty is running. > > Have you sent mail to the lists? Has it been delivered to subscribers? > Yes, mails to subscribers were delivered successfully. > > I confirmed that api_key set in the /etc/mailman3/mailman-hyperkitty.cfg > > and /etc/mailman3/mailman-web.py is the same. I also confirmed that the > > apache2 wsgi module has been loaded. > > > > In the mailman.cfg database is set to mysql and in the mailman-web.py > > database is set to sqlite3. Does it matter? > > I don't think they need to be the same. The HyperKitty and Postorius > databases are a Django database backed by an RDBMS (typically sqlite3, > PostgreSQL, or MySQL). The databases used by the Mailman core and the > Django webservices HyperKitty and Postorius are conceptually separate, > although they can be backed by the same RDBMS server. > As Tamas has said in the previous reply, my mailman is a fresh new install on Debian buster. I followed Debian.README and didn't change much. In Debian's setting, under /usr/share/mailman3-web/ are these files: manage.py settings_local.py -> /etc/mailman3/mailman-web.py settings_local.py.sample settings.py urls.py wsgi.py In the top of settings_locas.py there are comments saying that this file is to override default settings in /usr/share/mailman3-web/settings.py, so I suppose hyperkitty database should define here, though it is different from /usr/share/mailman3-web/settings.py. > > However, sqlite3 is likely to result in poor performance compared to > PostgreSQL or MySQL. > > You have to configure HyperKitty's database. In my sqlite3 test > installation it looks like this: > > # Top of settings.py. BASE_DIR is the directory containing settings.py. > BASE_DIR = os.path.dirname(os.path.dirname(os.path.abspath(__file__))) > > # 30-50 lines later: > DATABASES = { > 'default': { > 'ENGINE': 'django.db.backends.sqlite3', > # This database file is in the same directory as settings.py. > 'NAME': os.path.join(BASE_DIR, 'hyperkitty.db'), > # Not used with sqlite3: > 'USER': '', > 'PASSWORD': '', > 'HOST': '', > 'PORT': '', > } > } > > Does the database file named by 'NAME' exist? > In the settings_local.py, it defines sqliet3 and the file of 'NAME' /var/lib/mailman3/web/mailman3web.db exists and is a sqlite3 format file. But in settings.py (which is supposed to be overridden by setting_local.py) it defines using postgresql, which doesn't exist in my Debian system. > There is no systemd service for Hyperkitty. > systemd runs Apache, which loads mod_wsgi, which runs Python, which > imports the HyperKitty package, which responds to web requests by > building pages dynamically using Django from information from Django's > database, which may be backed by MySQL, PostgreSQL, or sqlite3. > Sounds complicated, but it performs well once you get it properly > configured. Is there any log I can trace the executing path? It looks not complicated but I didn't know and couldn't find out how to check if it works correctly. For Apache2 mod_wsgi, the wsgi.conf in mods-enabled does not enable any configuration (all commented out) and when I use ps to check, uwsgi runs as: 14233 ? Ss 0:01 /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini 14236 ? Sl 0:00 /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini The /var/log/mailman3/web/mailman-web.log is at https://pastebin.com/U3jHR6JS There seems to be something running but in the interface I still didn't see any results. Franklin

5 years, 11 months

Re: Custom templates (was: Re: Re: nginx configuration on a multitasking server)

by Mark Sapiro

On 1/14/22 6:58 PM, David Newman wrote: > > On 1/14/22 6:35 PM, Mark Sapiro wrote: >> >> The place for feature requests for Mailman core (which this is) is >> https://gitlab.com/mailman/mailman/-/issues, however, this is not >> straightforward as Mailman core doesn't know if you even have >> Postorius or some other web management UI installed or what the URL to >> access it might be. Thus it's not just a simple matter of editing >> templates. It would also require a configuration setting for the base >> URL for the web admin UI and changes in logic to provide an >> appropriate replacement depending on whether or not the base URL was >> configured. > > Understood, thanks. Although this distinction is very important for > server admins, it's likely not meaningful for many list owners and > moderators. For them, MM2.1 sent an email saying "go here" and > MM3/Django/Postorius/Hyperkitty doesn't, at least not out of the box. > > There is some pending template in use by default, just not one with a > URL included. All the templates have defaults and the defaults don't have URLs because these are unknown to core. > Is this something better handled in the venv and/or Web installation > docs? Or should I file a feature request for core, or Postorious or > someplace else? I think a feature request for core is appropriate. I'm only saying implementing this is a non-trivial change. What I do on sites I admin is put custom versions of all these domain:admin:notice:new-list.txt list:admin:action:post.txt list:admin:action:subscribe.txt list:admin:action:unsubscribe.txt list:admin:notice:pending.txt list:member:digest:footer.txt list:member:digest:masthead.txt list:member:regular:footer.txt list:user:action:invite.txt list:user:action:subscribe.txt list:user:action:unsubscribe.txt list:user:notice:post.txt list:user:notice:probe.txt list:user:notice:welcome.txt in /opt/mailman/mm/var/templates/site/en and at mail.python.org which also has German language lists, in /opt/mailman/mm/var/templates/site/de. That could be documented, but it would be preferable to be able to document just a base web management URL and then put a replacement such as $web_ui in the default templates and replace that with a URL if configured or some generic text otherwise. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

Converting non-members to members

by Alan So

Postorius is not currently exposing non-members management. Our Mailman 2 users are currently using accept_these_nonmembers, hold_these_nonmembers and reject_these_nonmembers. We know that mailman import21 will change these to nonmembers entries in Mailman 3. Since list owners will still want to manage them, we tend to move all of them to members and turn off delivery status for them. However, we met some difficulties when we try to develop using mailman client. 1) If those non-members addresses already exist as members, we will encounter error when we subscribe for them: urllib.error.HTTPError: HTTP Error 409: b'Member already subscribed' 2) We cannot change the moderation_action: urllib.error.HTTPError: HTTP Error 400: b'Cannot convert parameters: moderation_action' 3) We cannot change the preference: urllib.error.HTTPError: HTTP Error 400: b'Cannot convert parameters: delivery_status' Are there any better ways to enable the list owners to manage those previously configured nonmembers' addresses through the web? Otherwise, we probably need to have some manual effort to overcome the above three issues. We know that we can always do the above manually but we got a lot of lists to migrate to Mailman 3.

6 years, 10 months

Re: howto reallow a banned email ?

by Nicolas Pettiaux

much thanks. I use mailman 2 interface (and will switch soon to 3) i'll look asap. --- Nicolas Pettiaux - PhD - nicolas(a){educode,pettiaux}.be - Président de Educode asbl Informer, former et susciter la réflexion des acteurs du monde de l'enseignement face aux évolutions d'un monde numérique - http://2019.educode.be & http://2018.educode.be Le 2019-06-19 6:33, Mark Sapiro a écrit : > 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.

6 years, 4 months

Avoiding non-members to be saved.

by Guillermo Hernandez (Oldno7)

Hi all: Yesterday I had a problem with a private list. A spammer sent a mail forging one address that was a non-member (in fact was an "accept this no subscriber mails" from mailman 2.1 import) with very bad intentions and it was distributed. There were no list of "accept this non members" in the Postorius config (but I'm sure that that address was "accepted" in 2.1). To avoid this from any other non member address I deleted ALL non-members. I think it is solved now (deleting all and putting to hold just the non-members addresses that I would want to pass messages on) The fact is that any sender address of mails sent to the list is saved as a "non member", and it make me nervous as it will grow despite it is a legitimate message or not. Anybody knows if there is a per list config to avoid saving all that addresses as non members? o a overall config? I couldn't find anything about this in the config pages (or googling it) Thanks in advance. --

4 years, 2 months

Re: Postorius Suggestion: Give owner a view of all users of all owned lists

by Andreas Vetter

[Forgot reply to list] ---------- Forwarded Message ---------- Thank you Stephen for your questions. I have to admit that I thought about a quick and dirty solution, but you are right, it would not be optimal. Lets see: Stephen J. Turnbull wrote: > Andreas Vetter writes: > > it would be real great if owners that own several lists, but are > > not superusers, can see all users of all *their* lists and manage > > them. A down-"selected" version of the superusers view. > > > > Would that be possible? > > Possible, yes. I don't know how to do it well enough to add to our > distribution. > > Note that owners can't actually manage users -- that really does need > to be a superuser. Owners can manage subscriptions to the lists they > own. Agreed, "manage subscriptions" is what owners would need. A list of all addresses subscribed to all lists owned by the logged in person. > So first we'd want to create a new "Subscriptions" item for the > top menu; the "Users" item isn't appropriate. I'm not sure who that > item should be visible to. Most likely only owners, because > individuals already have ways to see all their subscriptions, and it's > not obvious they would want the same presentation as your superowners. Owner is the primary target group for that. But since it should be a tool for managing subscriptions in a simple way, it might also be of interest for superusers. For me as a superuser it would make life easier. > Then you'd iterate over the logged-in owner's lists and collect all of > the subscriptions. I guess you'd want them to be organized by address > rather than by list. By User is out, I think -- owners can't normally > see Users, and I'm unhappy abou the privacy implications of being able > to correlate nole(a)alset.com with head(a)dodgy.gov in general, although I > realize it's not a problem in your setting. Ah, I see the problem and agree: So, the presentation should have a sorted and searchable list of addresses and a Button next to each address, maybe labeled "Subscriptions". > Without a more complete specification of what your users need, and the > presentation they'd want to see, I personally am unwilling to go > farther than those comments. Maybe one of the other devs feels > differently. The presentation given when above "Subscriptions" Button is clicked should contain the address as kind of Headline. Then a table of all lists of the logged in owner and next to each mailing list an indication, if the address is subscribed or not and a Button to toggle subscription/unsubscription. May be a single Toggle Button or (maybe better) two buttons, a suscribe and a unsubscribe button, where one is greyed out.b In our case Delivery Status and Delivery Mode are not interesting, but others might appreciate it. In addition my owners would like to have a "unsubscribe from all my lists" button. And a "subscribe to all my lists" button. This might be visually nicer, when having the two-button approach above. In our case we would want to (un-)subscribe the address in a "do it, don't ask anyone" fashion, but maybe this is not a good idea in general. What do you think? > Also, "domain owner" is way under-implemented currently. For the > hierarchical situation you outline, all the problems go away for > domain owners. Of course then you'd need to split out lists by > domain, but to me that's a small cost to preserve sanity in the > structure. Yes, I agree, but policy here is to get rid of subdomains, and that falls on our feet now. -- Mit freundlichen Gruessen, Andreas Vetter

7 months, 2 weeks

Cache mailman3

by pau.baiges＠csuc.cat

Is there a way to delete the mailman3 cache? It's because it gives us this error and we think it's because of the cache. Internal Server Error: /mailman3/accounts/login/ TemplateDoesNotExist at /accounts/login/ django_saml2_auth/error.html Request Method: GET Request URL: http://llistes.csuc.cat/mailman3/accounts/login/?next=/mailman3/postorius/l… Django Version: 2.2.12 Python Executable: /usr/bin/uwsgi-core Python Version: 3.8.10 Python Path: ['.', '', '/usr/lib/python38.zip', '/usr/lib/python3.8', '/usr/lib/python3.8/lib-dynload', '/usr/local/lib/python3.8/dist-packages', '/usr/lib/python3/dist-packages'] Server time: dv., 15 Març 2024 10:33:00 +0100 Installed Applications: ('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Template loader postmortem Django tried loading these templates, in this order: Using engine django: This engine did not provide a list of tried templates. Traceback: File "/usr/local/lib/python3.8/dist-packages/django_saml2_auth/utils.py" in wrapper 179. result = function(request) File "/usr/local/lib/python3.8/dist-packages/django_saml2_auth/views.py" in signin 271. saml_client = get_saml_client(get_assertion_url(request), acs) File "/usr/local/lib/python3.8/dist-packages/django_saml2_auth/saml.py" in get_saml_client 169. metadata = get_metadata(user_id) File "/usr/local/lib/python3.8/dist-packages/django_saml2_auth/saml.py" in get_metadata 131. raise SAMLAuthError("Invalid metadata URL.", extra={ During handling of the above exception (Invalid metadata URL.), another exception occurred: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 34. response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 115. response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 113. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python3.8/dist-packages/django_saml2_auth/utils.py" in wrapper 181. result = handle_exception(exc, request) File "/usr/local/lib/python3.8/dist-packages/django_saml2_auth/utils.py" in handle_exception 162. return render(request, File "/usr/lib/python3/dist-packages/django/shortcuts.py" in render 36. content = loader.render_to_string(template_name, context, request, using=using) File "/usr/lib/python3/dist-packages/django/template/loader.py" in render_to_string 61. template = get_template(template_name, using=using) File "/usr/lib/python3/dist-packages/django/template/loader.py" in get_template 19. raise TemplateDoesNotExist(template_name, chain=chain) Exception Type: TemplateDoesNotExist at /accounts/login/ Exception Value: django_saml2_auth/error.html Request information: USER: AnonymousUser

1 year, 7 months

Re: New Mailman 3 installation issues

by Mark Sapiro

On 5/18/21 12:30 PM, sarah.hartt(a)ionica.ca wrote: > I have been trying to get a mailman 3 installation working for longer than I'd like to admit. Core appears to be installed and working as desired but Postorius (and hyperkitty, but I haven't even started troubleshooting it while trying to get the web interface working) is only loading the main page with no lists shown and all remaining links return a server error (specific text is: "Server error > An error occurred while processing your request." with the error text highlighted). I think I followed all of the installation instructions, including the updated pythonpath line in the systemd module, but it's entirely possible that there is an error somewhere along the way. Is there more information in logs? (nginx and django) > I have had to make two minor tweaks, the /static/ location was moved from /opt/mailman/web/static to /var/www/mailman/ (owner mailman:nginx) as nginx was giving permissions errors (even if it owned the files or with the mod set to 777) with the default location and wouldn't load the css, and installed postgres directly from their repo as the method in the guide doesn't create the user. Aside from that everything should be exactly as laid out in the installation guide. The permissions is probably a SELinux or apparmor issue. Which installation guide are you following? I'm guessing https://docs.mailman3.org/en/latest/install/virtualenv.html. Are you saying that ``` sudo apt install postgresql ``` doesn't create a `postgres` user? It should. > The logs are showing everything running and the DB logs show all the queries going through successfully, there are no errors in the web logs corresponding with the errors being served on the site aside an entry for a 500 in the access logs > > [18/May/2021:12:13:01] "GET /archives/ HTTP/1.1" 500 1102 "http://mailman3/mailman3/lists/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.91 Safari/537.36" "-" This is a GET of /archives/ which is HyperKitty. Django should log something for this with more detail. > when I took a look in the DB tables many of them appear to be empty, I have a few lists in core that were imported from 2.1 but no new lists created. Empty tables per se is not necessarily a problem depending on which ones. > Mailman: 3.3.4 > Postorius: 1.3.4 > OS: Oracle Linux 8.3 > Python: 3.6 > postgres: 13.2 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

Re: Please help: Mailaman3 -

by Abhilash Raj

On Fri, Sep 4, 2020, at 8:34 AM, Jane Anara via Mailman-users wrote: > Thank you Abhilash for your reply. I installed Mailman Core version 3.3.1. > > After your message, I ran `mailman start` and then ran the development > server. It complained of the port already in used and exited. That is > what I got in the past as well. This time, I changed the CORE REST API > port on django settings.py from port 8000 to 8001 and ran the > development server (which I often ran on 8001) on port 8006. The error > has gone away. By default, Core's REST API runs on Port 8001 and Django uses 8000. If you were using 8000 for the Core's Port in settings.py, that would mean Postorius was trying to talk to itself and hence the 404 errors with the URLs. > > Thank you for your help. > > Regards, > Jane > _______________________________________________ > 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, 1 month

Mailman-users search results for query "Postorius"