Search results for "2021" - Mailman-users

Re: aborted connection

by Sandor Dibuz

On 2/20/22 01:56, Mark Sapiro wrote: > > First, If your Mailman core version is >= 3.3.5, you shouldn't be > running gatenews via cron. Mailman's nntp runner runs it. See > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… > > But, that probably isn't it because in Mailman >= 3.3.5, running > gatenews via cron should produce this error > > The gatenews command is run periodically by the nntp runner. > If you are running it via cron, you should remove it from the crontab. > If you want to run it manually, set _MAILMAN_GATENEWS_NNTP in the > environment. > > > However, since you have no lists using a news->mail gateway, you don't > need to run gatenews at all so just remove it from the crontab. I installed Mm3 from Debian stable distro packages as one of the suggested installations methods in Mm3 docs. It's a bit of dated though I know but it was the easiest and fastest. Mailman Core Version GNU Mailman 3.3.3 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] So I disabled gatenews cron job. Maybe later I bite the bullet and upgrade to a recent version (either venv or docker haven't decided yet) but will have to learn how to avoid conflicts with already installed deb packages first. So far so good and everything works, have to check changelogs if an upgrade is worth it. Thank you all your help, Mark. Sanyi

3 years, 4 months

Re: Mailman 3 database restore unexpected behavior

by Odhiambo Washington

Have you looked at the tables and actually seen the duplicates? SELECT COUNT... Again, restoring a database usually should drop the table before restoring. On Tue, Mar 28, 2023, 14:00 Tibor Molnar <tibor.molnar(a)waltoninstitute.ie> wrote: > Mailman3 built from source using virtual environment. > Version: > GNU Mailman 3.3.8 (Tom Sawyer) > Python 3.9.2 (default, Feb 28 2021, 17:03:44) > [GCC 10.2.1 20210110] > config file: /etc/mailman3/mailman.cfg > > Issue: > I have restored the database number of times recently and experienced that > every time after restoration (an hour after) all members getting an email > that they are unsubscribed due to bounces, however non of the users are > actually unsubscribed from any lists. It looks like there are duplicates in > database and all the duplicates are getting unsubscribed? > > Bounces message: > name(a)email.com unsubscribed from [listname] mailing list due to bounces > > Only restoring two files: mailman3 and mailman3web > > Did anyone come acroos this behavior ? > It is not right that after restoring a database all 1000 user get an email > that they are unsubscribed, but they are actually not. > I may do something wrong during the restoring process. > Please advise me. > _______________________________________________ > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to odhiambo(a)gmail.com >

2 years, 3 months

Re: Mailman notify generating emails for request that aren't visible.

by Simon Coggins

Thats part of the issue. It looks like these are in the PendingsDB but not showing up in the UI. Even if I go into Subscription Requests -> Pending Approvals or Pending Confirmations no pending items are shown at all. But in the pendingDB via mailman shell I can see 3 pending unsubscriptions. -Simon --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 On 1 Nov 2021, at 12:26 pm, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: On 10/31/21 7:15 PM, Simon Coggins wrote: The version of postorius is 1.3.4 Then you should be able to click Subscription requests even though the badge shows 0 and click Unsubscription Requests in the dropdown. I know it's an issue, but the badge only counts subscription requests pending approval and not unsubscription requests. -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

Re: Problems with New MM3 Installation

by Jeff

> On May 11, 2021, at 1:18 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > > Set base_url: in /usr/local/mailman3/mailman-hyperkitty.cfg to a url > that will reliably access HyperKitty, probably the same base URL that a > user with a web browser would use. > Thanks Mark, I really appreciate your assistance. New messages are now being archived as expected, but I still have a few small remaining issues to work out with my MM3 installation: 1) some emails that arrived before I got the archive working are still sitting in: /usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain]/new Strangely this includes at least one email that was archived. Should this directly be cleared as messages are archived? Is there a way to force it to be cleared? 2) Some messages that arrived while I was having other problems with the setup have been stored in: /usr/local/mailman3/mm/var/queue/shunt What should I do to get these messages processed? 3) Similar to above, some messages are in: /usr/local/mailman3/mm/var/queue/bad How can I get these messages processed? 4 Modified the template for “list:admin:action:post” through Postorious and emails that arrived after that were put in the “shunt” queue. I traced this problem to POSTORIUS_TEMPLATE_BASE_URL. By default, it is set to "http://localhost:8000 <http://localhost:8000/>” which is where uwsgi is listening. However, uwsigi is listening for uwsgi:/ not http://. Should I change POSTORIUS_TEMPLATE_BASE_URL to “uwsgi://localhost:8000 <uwsgi://localhost:8000>” or keep http but make it something else? Thanks again for any help anyone can provide. Jeff

4 years, 1 month

Re: Installation - creating the mailman.cfg permissions

by Abhilash Raj

On 9/13/21 1:23 AM, Koen Martens wrote: > > On 13-09-2021 08:40, Stephen J. Turnbull wrote: >> Mark Dale via Mailman-users writes: >> >> > Although the instructions say to create the file as user "mailman", >> > should it be created by root (with/without virtualenv?) and then >> > chown to "mailman"? >> >> Yes. Since the file is created with a text editor, whether you're in >> a virtual environment or not is irrelevant (unless your preferred text >> editor is installed only in the virtual environment). >> >> I guess that's an oversight in the documentation. Thanks for the >> report. +1 > > I think the relevant point is that the documentation instructs you to > execute the command to invoke the text editor as user 'mailman3', which > will not work since user mailman3 won't have access to create files in > /etc. Yeah, I opened a ticket[1] to fix that aspect, I think there should be a note that any changes in `/etc` should be made using `sudo` or `root` user. The files inside /etc/mailman3 should be readable by `mailman` user, but it doesn't have to writable by it. [1]: https://gitlab.com/mailman/mailman-suite-doc/-/issues/37 > > Cheers, > > Koen > > _______________________________________________ > 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)

3 years, 9 months

Re: Hyperkitty "All Threads" results in error

by Mark Dadgar

Aaaand I spoke too soon. I am now seeing the same error when I click the All Threads button in hyperkitty. Not every time, because that would be too easy, but often. I really only have one high-volume list with archives, so I can’t tell if it’s list-specific. I ran the mailman-post-update script after the last update, which I believe executes all the commands suggested below. Here’s the crash trace. Any thoughts? - Mark Internal Server Error: /archives/list/trackjunkies(a)pdc-racing.net <mailto:archives/list/trackjunkies@pdc-racing.net>/latest VariableDoesNotExist at /archives/list/trackjunkies(a)pdc-racing.net <mailto:archives/list/trackjunkies@pdc-racing.net>/latest Failed lookup for key [sender] in None Request Method: GET Request URL: https://mail.pdc-racing.net/archives/list/trackjunkies@pdc-racing.net/latest <https://mail.pdc-racing.net/archives/list/trackjunkies@pdc-racing.net/latest> Django Version: 3.0.12 Python Executable: /opt/mailman/mm/venv/bin/python Python Version: 3.8.5 Python Path: ['/opt/mailman/mm', '/opt/mailman/mm/', '/opt/mailman/mm/bin', '/usr/lib/python38.zip', '/usr/lib/python3.8', '/usr/lib/python3.8/lib-dynload', '/opt/mailman/mm/venv/lib/python3.8/site-packages'] Server time: Mon, 1 Mar 2021 23:25:02 -0800 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') 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') Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py", line 828, in _resolve_lookup current = current[bit] During handling of the above exception ('NoneType' object is not subscriptable), another exception occurred: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py", line 836, in _resolve_lookup current = getattr(current, bit) During handling of the above exception ('NoneType' object has no attribute 'sender'), another exception occurred: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py", line 842, in _resolve_lookup current = current[int(bit)] During handling of the above exception (invalid literal for int() with base 10: 'sender'), another exception occurred: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/hyperkitty/lib/view_helpers.py", line 134, in inner return func(request, *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/hyperkitty/views/mlist.py", line 115, in archives return _thread_list(request, mlist, threads, extra_context=extra_context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/hyperkitty/views/mlist.py", line 144, in _thread_list return render(request, template_name, context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/shortcuts.py", line 19, in render content = loader.render_to_string(template_name, context, request, using=using) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/loader.py", line 62, in render_to_string return template.render(context, request) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/backends/django.py", line 61, in render return self.template.render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py", line 171, in render return self._render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py", line 163, in _render return self.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py", line 936, in render bit = node.render_annotated(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py", line 903, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/loader_tags.py", line 150, in render return compiled_parent._render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py", line 163, in _render return self.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py", line 936, in render bit = node.render_annotated(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py", line 903, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/loader_tags.py", line 62, in render result = block.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py", line 936, in render bit = node.render_annotated(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py", line 903, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/defaulttags.py", line 209, in render nodelist.append(node.render_annotated(context)) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py", line 903, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/loader_tags.py", line 188, in render return template.render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py", line 173, in render return self._render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py", line 163, in _render return self.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py", line 936, in render bit = node.render_annotated(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py", line 903, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/defaulttags.py", line 513, in render return self.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py", line 936, in render bit = node.render_annotated(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py", line 903, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/templatetags/i18n.py", line 132, in render context.update({var: val.resolve(context) for var, val in self.extra_context.items()}) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/templatetags/i18n.py", line 132, in <dictcomp> context.update({var: val.resolve(context) for var, val in self.extra_context.items()}) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py", line 691, in resolve arg_vals.append(arg.resolve(context)) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py", line 795, in resolve value = self._resolve_lookup(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py", line 847, in _resolve_lookup raise VariableDoesNotExist("Failed lookup for key " Exception Type: VariableDoesNotExist at /archives/list/trackjunkies(a)pdc-racing.net <mailto:archives/list/trackjunkies@pdc-racing.net>/latest Exception Value: Failed lookup for key [sender] in None Request information: USER: mark GET: No GET data POST: No POST data FILES: No FILES data On Feb 17, 2021, at 5:34 PM, Mark Dadgar <mark(a)pdc-racing.net> wrote: > > On Oct 14, 2020, at 4:37 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >> On 10/14/20 11:12 AM, Mark Dadgar wrote: >>>> On Oct 4, 2020, at 10:34 AM, Mark Dadgar <mark(a)pdc-racing.net> wrote: >>>> >>>> So I have been wrestling with this problem for a while now. Most times, but not every time, when someone clicks on the All Threads link in hyperkitty, a 500 error is generated. >> >> >> Does this happen on all lists, only some lists or only one list? >> >> >>>> I googled it, obviously, and at first I thought it was related to this issue, but that has not proven to be the case: >>>> >>>> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… >> >> What did you google? This query gets a lot of stuff with some hints, but >> nothing definitive. >> >> django render raises VariableDoesNotExist("Failed lookup for key " >> >> One thing I noted at >> <https://askbot.org/en/question/3095/django-error-variabledoesnotexist-faile…> >> was >> >> models out of date - run python manage.py syncdb and python manage.py >> migrate >> >> You could try that. Note that your django admin command might be >> something other than `python manage.py`. Also note syncdb has been >> removed from Django >=1.9. Currently, the above becomes `makemigrations` >> followed by `migrate`. >> >> I also suggest running the django admin commands >> >> `collectstatic --clear --noinput` >> and >> `compress` > > > My re-install seems to have fixed this issue as well. BONUS! > > - Mark > ----- > mark(a)pdc-racing.net | 408-348-2878 > > > _______________________________________________ > 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/ - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 4 months

Re: spanish localization

by Abhilash Raj

On Sat, Feb 13, 2021, at 9:21 PM, Stephen J. Turnbull wrote: > Victoriano Giralt writes: > > > I've visited Weblate, all Spanish strings are translated. Spanish > > is 100% translated, but, none of them have been "approved", > > whatever that is. It seems that a reviewer needs to approve the > > translation in order for them to be incorporated or released or > > whatever. I was sure I had reviewed everything between November 7th > > and the day Abhilash announced the release candidate and asked for > > translation review, but nothing has made it to the released > > version. > > > > Maybe there's something in the translation flow that we are doing wrong. > > I'm starting to miss the good old days when Mailman 2 translators just > > downloaded the .po files and returned them :-) > > Probably all it needs is for someone other than the submitter to check > a box. I doubt there is an assigned reviewer/owner, just any > translator registered for that language. That's the way Debian used > to work, anyway, and it seems like a good way for open source to work. > > @Abhilash, you set up Weblate, right? Do you know anything about this? https://docs.weblate.org/en/latest/workflows.html This is the documentation from Weblate about the whole workflow. There is a Project level setting which mandates that a Reviewer review and approve all the translated strings, but that is turned off for GNU Mailman project. -- thanks, Abhilash Raj (maxking)

4 years, 4 months

Re: EMWD/Affinity/Empathy in 2023

by Mark Sapiro

On 1/16/23 07:58, jaboyib556--- via Mailman-users wrote: > > However, I saw reports of EMWD being a one-man show and the owner sadly passing away in 2021; but I've also seen threads here referring to the Affinity and Empathy projects in 2022. It wasn't clear to me if EMWD is still an active business and Affinity and Empathy are still active offerings. Does anyone here have any direct contact/relationship/experience with EMWD/Affinity/Empathy following the owner's passing? Or knowledge of any other offerings publicly available today that are similar to Affinity/Empathy? I have had some contact, but not much. As far as I know, they are still in business and offering list hosting including Mailman 3 lists with Affinity and Empathy. They no longer offer support for installation and maintenance of Mailman on other people's servers. When we first were developing Mailman 3, we designed it in a modular fashion with a REST API for the core engine so that users who were so inclined could develop their own web UIs for archiving and list management. We also recognized that we needed to develop our own to make a complete package. Thus, we developed HyperKitty and Postorius for that, but we have always hoped that the community would develop others (hopefully open source and Python based). As far as I know, it was only EMWD that did this and for business reasons, kept it proprietary. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

Re: The future is here?

by Jonathan M

On 8 Jan 2021, at 04:18, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > Discourse is a different kettle of fish. They concentrate on the much > more straightforward (from a network and interapp communication > configuration standpoint) web service because that's what their users > expect. Mail is a lot more baroque from that standpoint. > > We shouldn't hope to successfully "encourage" hosts to do things our > way. Maybe Mail-in-a-Box is a useful comparator in terms of complexity (though it appears to be less configurable than Discourse, and the software itself is not comparable). Maybe my experience hasn’t been typical. I’ve mainly used a shared server which didn’t have Mailman installed, but of course had email set up. It was relatively easy to install Mailman 2 but impossible to install Mailman 3. I could probably install Mailman 3 on Digital Ocean or similar, but get the feeling that the mail server is the hardest part. If I ever can set aside enough time to get it working I should write the idiot’s guide that I needed. It would be great if there were a “Mailman-in-a-Box” including everything necessary to get Mailman working from scratch on a VPS (in addition to the primary, flexible way that allows experts to use Mailman 3 according to their personal preference). I will look into Abhilash’s Docker container setup. I think the first time I saw that I didn’t know he was “maxking” and assumed it was a third-party thing that would likely be abandoned. Best wishes Jonathan

4 years, 5 months

Re: Ann: Mailman Core 3.3.5 is out

by Mark Sapiro

On 9/29/21 9:59 AM, Brett Delmage via Mailman-users wrote: > On Wed, 29 Sep 2021, Eggert Ehmke via Mailman-users wrote: > >> Should I upgrade my Mailman 3.3.3 installed from Debian Bullseye? I >> would have >> to bypass the Debian installer. Or will there be Debian packages >> available? >> Same question for Postorius 1.3.6 Since Mailman 3.3.4 has been out for over six months and the latest Mailman 3 in even Debian sid is still 3.3.3, I would expect a long wait before these latest releases are available in Debian/Ubuntu. > I am excited to see 3.3.5 with its many updates available. Thanks to all > the contributors. > > I would like to know this too, as I was just about to install parallel > to the Debian package(s). I expect there are many of us. > > Going forward, what is the best way to maintain a stable version of > 3.3.5 with security and defect fixes only, exluding new features? Is > picking and applying individual checkins on gitlab the only way? I would suggest abandoning the Debian packages and installing as documented at <https://docs.mailman3.org/en/latest/install/virtualenv.html>. You should be able to keep all your existing configuration files and the database. You could even keep `list` as the Mailman user if desired. Once you have done this, upgrading via pip from PyPI or even from GitLab is very simple. -- 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

Mailman-users search results for query "2021"