Search results for "Postorius" - Mailman-users

mailman-web: ResponseNotReady

by Dmitry Makovey

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

7 years, 8 months

Problems with mailman core translation and other details

by celi＠dieese.org.br

Hi. We did a fresh install of the Debian Mailman 3 full package. I'd like all components to be translated into pt_BR. I downloaded the latest updated translations from weblate, which says that 100% of the project (all components) are translated. I checked and recompiled mailman.po with msgfmt without errors. I followed all instructions I saw, included the ones from the topic How to change the language in mailman3 in this list. Everything almost OK, except from the fact that none of mailman's core email messages are being translated, even though mailman.po shows the right messages. Also, strange things happen to these .po files. The web interface is almost perfect, but some messages (just some) are not correct - although the corresponding django.po appears to be OK. It´s the case below: the pair msgid/msgstr seems to be OK, but this particular sentence is not being translated. #: templates/postorius/lists/summary.html:88 #, python-format msgid "" "\n" " To subscribe you can send an email with 'subscribe' in the " "subject to\n" " <a href=\"mailto:%(address)s?subject=Subscribe\">" "%(address)s</a>\n" " or use the form below:\n" " " msgstr "" "\n" " Para se inscrever você pode enviar um e-mail com o assunto " "'subscribe' para\n" " <a href=\"mailto:%(address)s?subject=Subscribe\">" "%(address)s</a>\n" " ou use o formulário abaixo:\n" What am I doing wrong? Or what can I do to make things suitable? Additional info: GNU Mailman 3.3.3 (Tom Sawyer) Python 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] Postorius v. 1.3.4 HyperKitty v. 1.3.4 Thanx for any help

1 year, 4 months

Re: Patch/kludge suggestion and a question on adding accepted addresses

by David Krantz

On Sun, Apr 23, 2017 at 11:04 PM, Barry Warsaw <barry(a)list.org> wrote: > On Apr 23, 2017, at 10:33 PM, David Krantz wrote: > >>I'd suggest adding a catch for AttributeError similar to the one for >>KeyError in _HeldMessageBase in rest/post_moderation.py. It solved my >>immediate problem at least. I run the version from git with the tag >>263711b3b7988c7c474e3b8952dc7e0f02f04fa2 > > Can you file a bug and attach either the problematic message or the traceback? Will do. I have lost the message (I was too quick in removing it), but I of course still have the stacktrace. And I have a patch for my kludge. > Did you talk to your MTA's SMTP port, to Mailman's LMTP port, or some other > process? It matters because LMTP is the way messages get from the upstream > SMTP daemon (e.g. Postfix, Exim) into Mailman, and the LMTP server rejects any > messages that don't have a Message-ID. It was to the SMTP port of the MTA. I can try to recreate it although I have better filters now so it might be difficult to get passed to mailman. >>I have another question: In the old mailman you could add accepted >>senders without adding them to the list. Is that possible in Mailman >>3/Postorius? > > You do this by creating a "nonmember" subscription for the sender, and then > setting that member's moderation_action to Action.accept. Okay. I see no way of doing that in my instance of Postorius but in this case it is okay to do it in the command prompt. cheers, // David

8 years, 1 month

Re: Change language to welcome message in mailman3

by Mark Sapiro

On 7/24/20 2:10 PM, Massimo Zappalà wrote: > Hi everyone, > > My Version installed on Debian buster: > mailman3: 3.2.1 > postorius: 1.2.4 > hyperkitty: 1.2.2 > > All interfaces work well in Italian language, but "Welcome message" is in English. First question: Is the Subject: in English or Italian? If the Subject: is in English you need to compile the Italian message catalog as I described in my reply at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. Then, as far as the message body is concerned, it is built from a template. At present, in the Mailman source distribution, the only templates that are translated are French and German You will find the complete set of English templates at /usr/lib/python3/dist-packages/mailman/templates/en/. You have choices. 1) You can create /usr/lib/python3/dist-packages/mailman/templates/it/ and make Italian translations of all the English templates in the it/ directory in files of the same names, and submit a merge request at <https://gitlab.com/mailman/mailman/-/merge_requests> to merge them into the source distribution. If you are not familiar with software development in general and Mailman development in particular, this is probably beyond what you can do. 2) Find Mailman's var/ directory. This is the directory containing archives/, data/, etc/, lists/, locks/, logs/ and perhaps other sub-directories. You then need to create the full path to var/templates/site/it/ and place Italian translations of some or all the templates there. When doing so, you can add site customizations. 3) You can use Postorius to create templates for individual lists. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

Re: Internal Server Error, Need 2 values to unpack in for loop; got 1

by Elias Rudberg

Hello Mark, and thanks for answering! > Can you get the page at /mailman3/postorius/lists/ and /mailman3/ > postorius/lists/?all-lists Yes, those are OK. > If those are OK, look in your web server access logs for `GET /mailman3/ > postorius/lists/` messages with the same timestamp as those errors. Is > there some bogus query fragment on those? Yes, there are strange-looking long queries there at the times when these errors happen. Here is an example of what such a request URL looks like, where I have replaced some parts with [...] to avoid including anything sensitive: Request URL: https://[...ip-address...]/mailman3/postorius/lists/?widget=[...]svg[...]onload=confirm[...]xss-widget[...]&height=[...]svg[...]onload=confirm[...]xss-height[...]&screen=[...]svg[...]onload=confirm[...]xss-screen[...]&pass2=[...]svg[...]onload=confirm[...]xss-pass2[...]&redirect_to=[...]svg[...]onload=confirm[...]xss-redirect_to[...]&items=[...]svg[...]onload=confirm[...]xss-items[...]&string=[...]svg[...]onload=confirm[...]xss-string[...]&hidden=[...]svg[...]onload=confirm[...]xss-hidden[...]&f=[...]svg[...]onload=confirm[...]xss-f[...]&step=[...]svg[...]onload=confirm[...]xss-step[...]&role=[...]svg[...]onload=confirm[...]xss-role[...]&preview_nonce=[...]svg[...]onload=confirm[...]xss-preview_nonce[...]&date=[...]svg[...]onload=confirm[...]xss-date[...]&event=[...]svg[...]onload=confirm[...]xss-event[...] I looked up the IP address that those requests come from (all seem to come from the same IP address) and that corresponds to a hostname called something with "scanner" that looks like it belongs to some cybersecurity company. There are also many other requests from that same IP address, including things like "GET /file://etc/passwd" and similar, so it looks like someone is bombarding us with various weird requests as a form of "scanning" where they are trying to find vulnerabilities. That could also explain why we see those "Internal Server Error" errors recurring every day, if they run that vulnerability scan daily. So maybe those strange request URLs that lead to the error messages "[Django] ERROR (EXTERNAL IP): Internal Server Error" that we are seeing, are constructed by someone who is actively trying to trigger bugs. But anyway, no matter what strange request URL comes in, I guess the "Internal Server Error" indicates something going wrong in Mailman or in Django, a bug in how the request is processed? / Elias

10 months, 3 weeks

Re: How to store additional information about lists?

by Andreas Barth

* Stephen J. Turnbull (turnbull.stephen.fw(a)u.tsukuba.ac.jp) [210522 14:33]: > Andreas Barth writes: > > > I need to add custom attributes to the mailing lists: > > It's a rather different use case, but Systers Mailman contains > extensive modifications including Systers-specific attributes. Might > be a useful example (although I don't know how recently they've merged > from mainline. ISTR the last time this came up the Systers repo had > moved and it wasn't clear where. Try a quick Google and if no joy, I > can probably put you in touch with somebody who has a clone. Thanks, I'll give it a try. > > Enhance the boolean public to a tri-state: public, restricted audience > > and private (restricted audience means: some people could subscribe > > themself > > I'm not sure tri-state is a good idea. The boolean public controls > visibility of the list in listinfo pages. I'm not sure if combining > that with who-can-subscribe logic is safe Perhaps I expressed it badly. Currently it is "list public" vs "subscribers only". I need something inbetween, so that some (i.e. most) people have access to the restricted audience lists but not just everybody. , and there are pending RFEs > to change the visibility logic, which might cause you annoyance at > upgrade. I also am not sure it's a *bad* idea :-), although I suspect > if we were to add the feature to our distribution, we'd probably > implement as a per-list check for permission (this could be a list of > Users, a list of Addresses, or a function to be called with one or the > other). That would be working for me as well. > No, I don't think there's provision for custom attributes in core. Of > course you could change the database schema, but you'd have to provide > a migration for that. Migrations for somebody else's custom > attributes being a hard thing to automate on our side, we don't > provide for them. Just as an idea, how about always one "custom attributes" field. So that from a database pov this field is always there. In that field, the attributes could then be stored as e.g. json (which is of course a bit worse from performance than multiple entries, but well). Rest would give access to this field, but anything else is really up to the local implementation? > Does this need to be implemented in core (eg, because restricted > audience users would subscribe by mail), or could you get away with a > modification to Postorius only? It could be done in postorius - the restriction that subscribing by mail needs moderators action would be ok (or if it annoys me, this part be move to a cron job). Andi

4 years

Solved Re: after last upgrade I've got a CSRF failed verification

by Guillermo Hernandez (Oldno7)

El 27/10/22 a las 5:48, Mark Sapiro escribió: > On 10/26/22 04:33, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> I did it via pip and all seems to be working, but when I try to >> discard or accept any message via postorius it shows a Forbidden 403 >> error CSRF verification failed. >> >> In my settings.py I have commented out these variables: >> >> # Other security settings >> # SECURE_SSL_REDIRECT = True >> # If you set SECURE_SSL_REDIRECT to True, make sure the >> SECURE_REDIRECT_EXEMPT >> # contains at least this line: >> # SECURE_REDIRECT_EXEMPT = [ >> # "archives/api/mailman/.*", # Request from Mailman. >> # ] >> # SESSION_COOKIE_SECURE = True >> # SECURE_CONTENT_TYPE_NOSNIFF = True >> # SECURE_BROWSER_XSS_FILTER = True >> # CSRF_COOKIE_SECURE = True >> # CSRF_COOKIE_HTTPONLY = True >> # X_FRAME_OPTIONS = 'DENY' >> >> I've been messing with them whith no results. It's like it lacked >> some value in some template... > > > It's not an issue with the code per se or the templates. These updates > are all installed on mail.python.org and lists.mailman3.org and are > working fine. > > After upgrading did you run > > django-admin collectstatic --clear > django-admin compress > django admin migrate Since I made all the mailman3 enviroment wide server open (not using venv) I already executed the migration doing a su -m mailman3 -c "python3 manage.py collectstatic" su -m mailman3 -c "python3 manage.py migrate" Being mailman3 the user who runs all of mailman3 related stuff I had problems doing the migrate part, showing an error of lacking perms. I solved it running the migration under root (I know it could be trouble after, but...) After that the compress part showed errors... but the postorius web maintenance was working well except for the CSRF error verification. I will trace the compress errors and will try to find the problem later. With your point to the CSRF_TRUSTED_ORIGINS parameter, I can now do the accept or discard part of a receiving message to the lists (I put below the config that is working for me). All seems to be working now flawlessly. Thanks once again for your guidance. ############ SESSION_COOKIE_SECURE = True SECURE_CONTENT_TYPE_NOSNIFF = True SECURE_BROWSER_XSS_FILTER = True CSRF_COOKIE_SECURE = True CSRF_COOKIE_HTTPONLY = True X_FRAME_OPTIONS = 'DENY' # CSRF_TRUSTED_ORIGINS = [ "https://*.mydomain-example.xxx", "https://mydomain-example", "https://mydomain", ] ############ > > If you have and it doesn't help, you probably need to add > CSRF_TRUSTED_ORIGINS to your settings.py. > > See > https://docs.djangoproject.com/en/4.1/ref/settings/#csrf-trusted-origins > and note the differences between Django <4.0 and >=4.0. > -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 7 months

Re: Installing mailman 3

by Abhilash Raj

When you set DEBUG=False, Django doesn't serve static files because of which you see only text and no styles. http://docs.mailman3.org/en/latest/pre-installation-guide.html#django-stati… If you do set DEBUG=False, you need to serve the static pages somehow. Alternatively in you case, you can remove the part of the `settings.py` which changes the Emailbackend when `DEBUG=False` so that you don't have to worry about serving static files and still send out emails. On Wed, Aug 2, 2017, at 09:46 AM, Rafael Mora wrote: > For testing purpose I turned back to false the DEBUG var and everything > started working fine with HyperKitty > > I don't understand... this is the trace when I click Login from Postorius > to HyperKitty > > [02/Aug/2017 16:43:42] "GET /postorius/lists/ HTTP/1.1" 200 3645 > [02/Aug/2017 16:43:48] "GET /accounts/login/?next=/postorius/lists/ > HTTP/1.1" 200 10950 > [02/Aug/2017 16:43:49] "GET /static/CACHE/css/hyperkitty.2f591b4e31fe.css > HTTP/1.1" 200 156657 > > > What should I check? > > > > > > > > > El mié., 2 ago. 2017 a las 10:56, Mark Sapiro (<mark(a)msapiro.net>) > escribió: > > > On 08/02/2017 07:55 AM, Rafael Mora wrote: > > > HyperKitty is looking for some files in /static/CACHE/... but it doesn't > > > find them: > > > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" > > > 404 107 > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" > > > 404 107 > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css HTTP/1.1" > > > 404 107 > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > > 404 > > > 105 > > > [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > > 404 > > > 105 > > > > > > > > > Should I run any command to activate the CACHE dir? > > > > > > You need to ensure you have a working sass compiler. As I said at > > < > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > >, > > See the third bullet under > > <http://docs.list.org/en/latest/prodsetup.html#dependencies>. > > > > Then you need to run commands like > > > > django-admin collectstatic --clear > > django-admin compress > > > > > > -- > > 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 > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > -- > > Atentamente / Best Regards > > Ing. Rafael Mora > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj

7 years, 10 months

Re: Dealing with confirmation requests for unsubscribes

by Mark Sapiro

On 11/18/20 7:41 AM, Brian Carpenter wrote: > Hello List, > > I ran into the following issue for some mailman 3 lists that I am hosting: > > https://gitlab.com/mailman/mailman/-/issues/768 > > Since there is no way for a list owner to deal with a moderation request > for an unsubscription task, I assume I need to do something via the > command line. This is where I need some help with. How do I deal with > these moderation requests that are unable to be reviewed in an admin gui > (Postorius/Affinity)? mailman shell -l list(a)example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the test.msapiro.net mailing list This >>> list(getUtility(IPendings).find(mlist=m, pend_type='unsubscription', token_owner=TokenOwner.moderator)) will return something like [('a8df55f557b5718505280d2613937e25a3109252', {'type': 'unsubscription', 'list_id': 'list.example.com', 'email': 'user(a)example.com', 'display_name': 'Mark S', 'when': '2020-11-18T22:56:53', 'token_owner': 'moderator'})] What you want is the token, in this case 'a8df55f557b5718505280d2613937e25a3109252' Then do >>> ISubscriptionManager(m).confirm('a8df55f557b5718505280d2613937e25a3109252') which will return (None, <TokenOwner.no_one: 0>, None) and finally: >>> commit() > I do recommend removing such choices for Postorius for Member policy. I > will be doing this for Affinity until issue 768 is resolved. The correct thing to do is fix <https://gitlab.com/mailman/mailman/-/issues/768>. We almost certainly will do that rather than remove the moderate and confirm then moderate unsubscription policies. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

Error when click on mailing list: An error occurred while processing your request.

by adam.heathcote＠utas.edu.au

Hey there, We have a Mailman3 server with quite a few lists all running with no issues. Recently I imported a list from our old Mailman 2 server which went fine. I attempted to remove the current owner and add myself but now when clicking on the list, Postorius shows: An error occurred while processing your request. The output of /opt/mailman/web/logs/mailmanweb.log is here: ERROR 2024-07-09 17:11:33,371 2795 django.request Internal Server Error: /mailman3/lists/net-ops.list.utas.edu.au/ Traceback (most recent call last): File "/opt/mailman/venv/lib64/python3.9/site-packages/django/core/handlers/exception.py", line 56, in inner response = get_response(request) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/core/handlers/base.py", line 197, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/views/generic/base.py", line 103, in view return self.dispatch(request, *args, **kwargs) File "/opt/mailman/venv/lib64/python3.9/site-packages/postorius/views/generic.py", line 76, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/views/generic/base.py", line 142, in dispatch return handler(request, *args, **kwargs) File "/opt/mailman/venv/lib64/python3.9/site-packages/postorius/views/list.py", line 411, in get return render(request, 'postorius/lists/summary.html', data) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/shortcuts.py", line 24, in render content = loader.render_to_string(template_name, context, request, using=using) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/loader.py", line 62, in render_to_string return template.render(context, request) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/backends/django.py", line 61, in render return self.template.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 175, in render return self._render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/loader_tags.py", line 157, in render return compiled_parent._render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/loader_tags.py", line 63, in render result = block.nodelist.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/defaulttags.py", line 321, in render return nodelist.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/defaulttags.py", line 52, in render output = self.nodelist.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) TypeError: sequence item 1: expected str instance, NoneType found I've tried removing it and reimporting it to no avail. Is there anything I can besides manually creating it and adding the members and owners from the old server? Cheers

11 months, 1 week

Mailman-users search results for query "Postorius"