Search results for "Postorius" - Mailman-users

Re: Mailman, etc. upgrade woes and persistent bugs

by Andreas Barth

* Stephen J. Turnbull (turnbull.stephen.fw(a)u.tsukuba.ac.jp) [210212 12:04]: > hansen(a)rc.org writes: > > b. The ability of members to change their addresses for all lists > > they are subscribed to. > > What exactly do you want here? I can think of a number of ways to > implement that, depending on whether the old address is to be > deactivated from the lists, unsubscribed from the lists, or deleted > from the Mailman and/or Postorius Users. There may be other > variables to consider, as well; I haven't thought about this. AFAICS > this is not a trivial feature, and I'd really like to hear from people > who want "something like" this about exactly what they want and their > use cases. Or we'll release an insufficiently designed feature that > causes somebody hundreds of problems.... I thought user could do that if they have an web account, and multiple mail addresses are associated with the account? Or does my memory serve me wrong there? Andi

5 years, 7 months

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, 11 months

Re: Apache Configuration for Subdomain

by Mark Sapiro

On 7/26/22 14:20, Mail Person wrote: > Ok, progress with tinkering some. Using the below configuration I can manually navigate to lists.example.com/mailman3/postorius/lists/ and all is working fine. If I go to lists.example.com/mailman3 it for some reason redirects to lists.example.com/mailman/postorius/lists/ which generates a 404. This is a uWSGI issue. > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost Others have found that changing this to ``` ProxyPass /mailman3/ unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ``` fixes it. Note the added slashes after `mailman3` and `localhost`. See this thread https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > Going to lists.example.com also hits a 404. Here > RewriteEngine on > RewriteCond %{SERVER_NAME} =lists.example.com [OR] > RewriteCond %{SERVER_NAME} =www.lists.example.com > RewriteRule ^ https://%%7BSERVER_NAME%7D%%7BREQUEST_URI%7D [END,NE,R=permanent] You're redirecting http to https, but have you defined a VirtualHost for port 443? Just copy your <VirtualHost *:80> block to a <VirtualHost *:443> block. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

Re: Handling of Mail from non-subscribers

by Mark Sapiro

On 5/8/20 4:42 PM, Peter Adebahr via Mailman-users wrote: > > I have a fresh setup of MM3 on Ubuntu 20, installed by apt-get. It seems > to be running fine so far, except for some (to me) strange behaviour: > > When posting to the list as a non-subscriber, I see the mail coming in > on mailman's smtp.log, then it vanishes. No notice of this mail being > hold is sent to the sender, no notice to the moderator, and logging into > Postorius as owner of the list, it is not showing up in "Held messages" > > "Hold for moderation" has been set. Set in "Default action to take when a non-member posts to the list"? If that is the case, find the non-member in Users -> Non-Members and look at the Non-member Options link. What is the "Administration options Moderation" setting? for that non-member? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

Re: Configuring the List-Archive and Archived-At headers

by Mark Sapiro

On 3/20/19 6:50 PM, Mark Sapiro wrote: > On 3/20/19 5:43 PM, Ralph Seichter wrote: >> With archiving enabled, mail is sent with headers like the following: >> >> Archived-At: <https://example.com/hyperkitty/list/foo-users@lists.example.com/message/ABC/> >> List-Archive: <https://example.com/hyperkitty/list/foo-users@lists.example.com/> >> List-Post: <mailto:foo-users@lists.example.com> >> List-Subscribe: <mailto:foo-users-join@lists.example.com> ... > What that means is the lists.example.com domain must first be known to > Django at <https://lists.example.com/admin/sites/site/ > > Then at https://lists.example.com/postorius/domains/, the Web Host for > the example.com domain needs to be lists.example.com I didn't look carefully enough at your example. If the mailto: links are @lists.example.com, then that is the Mail Host at https://lists.example.com/postorius/domains/ for which the Web Host needs to be lists.example.com. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

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

4 years, 8 months

Re: Where do I find the bounced messages?

by Mark Sapiro

On 12/20/22 02:29, Sörös Zoltán wrote: > Greetings, > I am running several lists under mailman3. I am getting notifications > about users being put on nomail because of their bounces - but I can > find no way to actually see the bounced messages. > > Do mailman3 store the received bounces? Where? They are stored in the message store in the database but only temporarily. > Is there any setting to forward these bounces to the list owner? There are two relevant settings. These are exposed in Postorius -> Settings -> Bounce Processing. They are: Notify owner on bounce increment - sends a notice to the owner including the DSN when a user's bounce score is incremented, but to a value less than the bounce threshold. Notify owner on disable - sends a notice to the owner including the DSN when a member's subscription is automatically disabled due to the bounce threshold being reached. -- 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

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

1 year, 6 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.

7 years, 9 months

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

2 years, 6 months

Mailman-users search results for query "Postorius"