Search results for "Postorius" - Mailman-users

Re: Welcome message template errors

by Mark

> Did you delete and recreate the template after changing > POSTORIUS_TEMPLATE_BASE_URL? If not, the template table still has the > old URI. Yes. Every test is: delete template and users (via Postorius), make any config changes, restart everything, then new template and new user (via Postorius). > What does `ps -fwwu mailman|grep runner` show? # ps -fwwu mailman|grep runner mailman 375726 375716 0 02:00 ? 00:00:01 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=archive:0:1 mailman 375727 375716 0 02:00 ? 00:00:01 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=bounces:0:1 mailman 375728 375716 0 02:00 ? 00:00:01 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=command:0:1 mailman 375729 375716 0 02:00 ? 00:00:01 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=in:0:1 mailman 375730 375716 0 02:00 ? 00:00:01 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=lmtp:0:1 mailman 375731 375716 0 02:00 ? 00:00:01 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=nntp:0:1 mailman 375732 375716 0 02:00 ? 00:00:01 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=out:0:1 mailman 375733 375716 0 02:00 ? 00:00:01 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=pipeline:0:1 mailman 375734 375716 0 02:00 ? 00:00:01 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 mailman 375735 375716 0 02:00 ? 00:00:00 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=retry:0:1 mailman 375736 375716 0 02:00 ? 00:00:00 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=task:0:1 mailman 375737 375716 0 02:00 ? 00:00:01 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=virgin:0:1 mailman 375738 375716 0 02:00 ? 00:00:01 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=digest:0:1 mailman 375790 375734 0 02:00 ? 00:00:00 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 mailman 375791 375734 0 02:00 ? 00:00:00 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1

1 year, 10 months

Re: Bulk delivery status change?

by Stephen Daniel

OK. Ran the script. No errors while running it, but when I look at the users through Postorius GUI, they still show as 'Disabled by Bounces' ?? On Sun, Nov 10, 2024 at 11:42 AM Stephen Daniel <swd(a)pobox.com> wrote: > Thanks all! I will use these pronto. > > On Sun, Nov 10, 2024 at 11:42 AM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 11/10/24 08:34, Odhiambo Washington via Mailman-users wrote: >> > On Sun, Nov 10, 2024 at 7:16 PM Stephen Daniel <swd(a)pobox.com> wrote: >> > >> >> Mistakes were made, and for while every single outbound email bounced. >> >> I've fixed the mistakes, but now in my largest and most active email >> list, >> >> every single user's delivery status is "Disabled by Bounces". >> >> >> >> Is there a way to bulk fix this? Or do I have to go into each user, >> one at >> >> a time, and fix them? >> > >> > Please see this thread: >> > >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> >> The script in that post does all lists. For a single list see >> >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> but note that the command line >> ``` >> $ shell -l list(a)example.com >> ``` >> should be >> ``` >> $ mailman shell -l list(a)example.com >> ``` >> >> -- >> 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 >> 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 swd(a)pobox.com >> >

1 year, 4 months

Re: My list has been switched from public to private archives, but they are still visible

by Abhilash Raj

On Thu, Sep 19, 2019, at 11:42 AM, Enrique Terrazas wrote: > Thank you Abhilash, > I appreciate your prompt response. What about the once private archives becoming public after setting a list to “Do not archive this list”? Is this something you are observing? It is most definitely a bug, Hyperkitty should leave the archive in whatever previous state they were in before the "Do not archive this list" setting was added. My suspicion is that when Do Not archive list setting is enforced, Hyperkitty sets the default visibility, which I think is Public. Can you file a but at gitlab.com/mailman/hyperkitty/issues ? > Regards, > Enrique > > >> On Sep 19, 2019, at 1:38 PM, Abhilash Raj <maxking(a)asynchronous.in> wrote: >> >> On Thu, Sep 19, 2019, at 11:15 AM, Enrique Terrazas wrote: >> >>> I am having a very similar issue. Here is what I have found: >>> >>> There are basically three archive settings we can select via the >>> postorious web front end for archives. These can be found in: Settings >>> >>>> Archiving and they are: >>> Public archives >>> Private archives >>> Do not archive this list >>> >> >> This is interface of Mailman to set the archives. >> >> >>> >>> In the Django administrative interface we can find those >>> same(?/similar?) settings here: Main Page > Hyperkitty > Mailing lists >>> >>>> Mailing List object(x) > Archive policy: >>> never >>> private >>> public >>> >> >> This is basically a hotline to the database. You can change these values, >> but they would be overriden with the values that are in Mailman Core on >> the daily cron job run. >> >> I would suggest not to tinker with values there since you could leave >> database in a corrupted state. Since there is an ORM layer there, chances >> are less but still a possibility :) >> >> >>> >>> I’m not sure which of the two takes precedence. My guess is postorius >>> since that is a list owner accessible setting and the Django >>> administrative interface would typically not be accessible to list >>> owners. We have noticed the following odd behavior, not sure if it is a >>> bug. For existing lists with private archives, when switching to “Do >>> not archive this list” in postorious, the desired effect of no longer >>> archiving the list is instantaneous. However, after the daily cron job >>> that syncs with Mailman Core happens, the existing archives now become >>> publicly accessible. Is this behavior based on the assumption that the >>> list will no longer be archived and will therefore be purged? >> >> >> Source of truth is Mailman Core's database. Postorius is a front-end to >> change that and owners have permissions to do that. >> >> Hyperkitty only syncs back that information daily. I have a fix in the >> master which makes such that this information is synced synchronously >> and is available immediately to Hyperkitty. >> >> For now, you could either run the "python manage.py runjobs --daily" or >> wait for a day if that is possible. >> >> >>> Enrique >>> >>> >>>> On Sep 19, 2019, at 1:08 PM, Abhilash Raj <maxking(a)asynchronous.in> wrote: >>>> >>>> On Thu, Sep 19, 2019, at 3:31 AM, Paul Arenson wrote: >>>> >>>>> Can anyone help with this? >>>>> >>>>> I set my list to private archives today. Up until then, it was pubic. >>>>> And yet, if you go to the list page, you will see that if you click >>>>> archives (top left), you can see them. (Filled with a bunch of tests >>>>> posts for now) >>>> >>>> This change takes a bit of time to sync up Hyperkitty. THere is a daily >>>> cron job which syncs this information from Mailman Core. >>>> >>>> I have made a change which should fix this problem and the process would >>>> become synchronous. >>>> >>>> You can run `python manage.py runjobs --daily` command to force sync >>>> that information. >>>> >>>> >>>>> >>>>> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist.toky… >>>>> >>>>> Am I misunderstanding what a private archive is? >>>> >>>> Not really, your expectation is right. >>>> >>>> >>>>> >>>>> Is something wrong with my setup (which is hosted)? >>>>> >>>>> Thank you. >>>>> _______________________________________________ >>>>> Mailman-users mailing list -- mailman-users(a)mailman3.org >>>>> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >>>>> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… >>>>> >>>> >>>> -- >>>> thanks, >>>> Abhilash Raj (maxking) >>>> _______________________________________________ >>>> Mailman-users mailing list -- mailman-users(a)mailman3.org >>>> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >>>> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… >>> >>> >> >> -- >> thanks, >> Abhilash Raj (maxking) >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… -- thanks, Abhilash Raj (maxking)

6 years, 5 months

Re: Confusing mailman user model

by Gilles Filippini

Mark Sapiro a écrit le 19/07/2020 à 17:30 : > On 7/19/20 8:10 AM, Gilles Filippini wrote: >> Hi, >> >> I'm trying to understand the Mailman user model, and I'm confused about >> the respective roles of tables 'auth_user' and 'user'. > > > auth_user is a Django auth table. These are the users listed in the > Django admin web UI. > > user is Mailman core's users. > > >> Both have an 'id' column referred to as 'user_id' when used as a foreign >> key. But there seems to be no relation at all between them as they use >> different ids for the same user. > > > Right, they are unrelated. > > >> Our mailman server was migrated from mailman2 to mailman3 about 1.5 year >> ago, and there is an inconsistency I'd like to fix: >> 2 of our users have a registered Mailman account with their respective >> email addresses in table 'auth_user', but these very same addresses in >> the 'address' table are linked to another old admin account in the >> 'user' table. > > Their Mailman account is the 'old' one. the auth_user account is a > Django account >> >> Then if add one of these addresses as a domain owner, it it the old >> admin address which is selected instead. How could I fix that? > > > That's because domain owner in a Mailman thing and involvs the Mailman > user. You could delete the Django users via the Django admin UI and then > re-register them via Postorius. That *might* work. When login into postorius, it is the Django account that is used, right? Then how is the mailman account retrieved from there? It seems UUIDs are used in the process, but I fail understanding how, so far. Wouldn't it be safe to retrieve the new Mailman account associated to these Django users, and link there emails from 'address' table' to them? _g.

5 years, 7 months

Re: Counter-intuitive header filter processing

by Jonas Meurer

Hi Mark, Am 18.09.2018 um 20:48 schrieb Mark Sapiro: > On 09/18/2018 10:26 AM, Jonas Meurer wrote: >> >> Apparently, that's not the case. If the default message acceptance >> setting for members is set to "reject", then mails from >> *(a)freesources.org get rejected even though the header filter says >> "accept". In other words, the default message acceptance action seems to >> overrule any header filters. >> >> Is this expected behaviour? > > > Yes. Rules are normally checked in a sequence defined in > mailman/chains/builtin.py and that sequence checks several things > including member moderation before checking header matches, so if > "Default action to take when a member posts to the list" is anything > other than "Default processing", that action will take precedence over > header matches. Thanks for the clarification. Maybe then the description for chain "accept" in postorius needs to be adjusted. Currently it says "Accept immediately (bypass other rules)". This gives the impression, that it will overrule the default action. A related followup question: what configuration is recommended for an announcement list where only specific senders (e.g. sender(a)example.org) should be allowed to post and mail from all (other) subscribers should be rejected? The only way I see to achieve this currently is: * Set default action for member posts to "Default processing" * Add a header filter to accept "sender(a)example.org" * Add a header filter to reject ".*" In my eyes, that's very counter-intuitive and cumbersome to configure. But maybe I just missed a more obvious and elegant solution to achieve the same? And one more comment: if I make the list an "anonymous list" (i.e. "hide the sender of a message, replacing it with the list address"), then header filters for the "from" header don't work any longer. That's kind of unexpected as well. I would have expected mailman to process the header filters at reading the incoming mail, not after rewriting headers of the outgoing mail? Cheers jonas

7 years, 5 months

Re: Post-installation documentation?

by Mark Sapiro

On 11/24/21 9:40 AM, David Newman wrote: > > IMO post-installation docs for list admins would be a big help in > Mailman3 adoption. I'm willing to help with this. Thank you for being willing to contribute. I think the place for list admin docs would be in the https://gitlab.com/mailman/mailman-suite-doc project which is the source for https://docs.mailman3.org/en/latest/. There is currently a userguide there at source/userguide.rst and referenced from source/index.rst. the addition of an adminguide.rst would be welcom if you want to work on that. > When I say "working": I'm looking to migrate Mailman2 mailing lists to > Mailman3, but am struggling with even basic setup tasks before we > attempt list migtration. > > For example, on admin page I've set up two lists, one public and one > private (each with unique list IDs), but neither appear in the site's > list index. Here are the steps to migrate a 2.1 list named `alist(a)example.com` and its archives. run Mailman's `bin/mailman create alist(a)example.com` follow that with ``` bin/mailman import21 alist(a)example.com /path/to/mailman2.1/lists/alist/config.pck ``` That will create the list and import its members and settings. To import archives run the Django admin command with arguments ``` hyperkitty_import -l alist(a)example.com /path/to/mailman2.1/archives/private/alist.mbox/alist.mbox ``` > And I don't know where to add list members. For imported lists, they are already added, but for new lists, you can add them in Postorius under Mass operations -> Mass subscribe or via the bin/mailman commands `addmembers` or `syncmembers`. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… > And clicking the site archives link throws this error: > > django.urls.exceptions.NoReverseMatch: Reverse for 'hk_list_overview' > with keyword arguments '{'mlist_fqdn': 'wheee'}' not found. 1 pattern(s) > tried: ['archives/list/(?P<mlist_fqdn>[^/@]+@[^/@]+)/$'] Did you specify the list's fqdn as in https://www.example.com/archives/list/list@example.com/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

Re: Removing a mail addresses and users

by Mark Sapiro

On 6/10/20 10:23 AM, Abhijith PA via Mailman-users wrote: > Hello. > > I tried to remove random email address signing ups (which I signed up > while testing) via admin panel. After removing I tried to sign up again, > but I am getting, > > 'A user is already registered with this e-mail address' You removed the user's subscription from the list, but you didn't remove the user from the system. Mailman3 has a concept of `user` which didn't exist in Mailman 2.1. User's have addresses and a user or one of the user's addresses can belong to a list with one or more roles (non-member, member, moderator or owner) > Combing through the database, I found auth_user table in mailman3web db > still contain those mail address. How to wipe email address entirely > from the db so I can signup again without the 'forget password' method There are a couple of things. If you log in to the web UI as a django superuser, you can go to the django admin UI -> Users section and delete the User, but I think that will only delete the web user and not delete the user from Mailman core. You can also log in to the web UI as the user and go to <https://lists.mailman3.org/user-profile/delete>, but that again only deletes the web user, and if you could do that, you could just subscribe once you're logged in, so I assume that's what you want to avoid. I don't think there is a way for a user as opposed to a site admin to delete her user record from Mailman core and even for a site admin, there's no way in Postorius to delete a user from core. It has to be done via REST <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> or `mailman shell`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by Mark Sapiro

On 3/2/21 12:33 PM, David Partain via Mailman-users wrote: > On Tue, 2021-03-02 at 20:07 +0000, David Partain via Mailman-users > wrote: >> On Tue, 2021-03-02 at 19:56 +0000, David Partain via Mailman-users >> wrote: >> >> I assume this is because /usr/share/mailman3-web/manage.py, which >> has: >> >> '#!/usr/bin/env python' >> >> resolves to Python 2.7.17. >> >> Should I could try changing that to '#!/usr/bin/env python3' and see >> what happens? :) I could also uninstall python2 but that becomes >> more of a nail-biter... NO! Do not do that. >> I can report that the above doesn't help. Neither does just making >> /usr/bin/python link to /usr/bin/python3.6 >> >> I still get errors in mailman-web.log pointing to 2.7 as shown in my >> previous mail. > > If I force the issue by linking /usr/bin/python to /usr/bin/python3.6, > I start seeing: > > ModuleNotFoundError: No module named 'hyperkitty > > in mailman-web.log. > > I know next to nothing about python. Is > > pip install hyperkitty > > the right answer? No. > I have the following installed now: > > # dpkg -l | grep hyperkitty > python-django-hyperkitty 1.1.4-4 > python3-mailman-hyperkitty 1.1.0-4 > > but this version of Ubuntu has no python3-django-hyperkitty or I'd just > try installing that... This is all because you are using the Ubuntu 18.04 package which is about 4 years out of date and is from the era where HyperKitty, Postorius and django_mailman3 still ran under Python 2.1.7. Unless you want to remove the Ubuntu package and install everything with pip, you need to just stick with what you have that at least partly works and we'll try to determine how to fix the utf8mb4 issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

Re: problems installing mailman3 under gentoo and upgrading mailman2 to mailman3

by Mark Sapiro

On 3/12/21 7:36 PM, John Covici wrote: > Hi. I am having a great deal of difficulty installing mailman3 using > gentoo and sendmail. Also, I want to upgrade my old mailman2 data to > mailman3. > > What I have done so far is to install the mailman3 packages from my > repository and got this: > django-mailman3 version 1.3.4, mailmanclient version 3.3.1, mailman > version 3.3.2 (apparently the core), postorius version 1.3.3 and > hyperkitty version 1.3.3. I also have mariadb and postgresql already installed. Are these gentoo packages? If so, I have no idea how they are configured. > Now trying to read your documentation, it seems it wants me to > reinstall some packages using pip in the home directory of the mailman > user in a python virtual environment, that was the first thing. But I > would like to avoid multiple package managers wherever possible -- > gentoo is already a lot of maintainance without dealing with pip's > maintainance. The binaries also seem to be different from my gentoo packages. Our documantation generally covers installing from source. If you are installing gentoo packages, you should be looking at gentoo docs and going to gentoo for help. We recommend installing Mailman and the web components in a virtualenv, but it is not a requirement. We also suggest that postgresql is a better choice than MariaDB. > So, how do I proceed with getting mailman3 up and working, configuring > the database, configs, etc and I guess after doing that upgrading > mailman2 and getting sendmail to interface properly with mailman3? Importing lists from Mailman 2 is done with the `mailman import21` command. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…>. Importing archives is done with the Django management `hyperkitty_import` command. See <https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html#import…> For sendmail, see <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

Re: Please help: Mailaman3 -

by Jane Anara

Hello Abhilash, Thank you for your reply. I did use the mailman-suit url.py before and got similar errors. At your suggestion, I again included the following in the import session: from django.urls import reverse_lazy from django.views.generic import RedirectView and the following line in the urlpatterns: url(r'^$', RedirectView.as_view(url=reverse_lazy ('list_index'), permanent=True)), The 'list_index' undefined error does not come up, however the HTTP Error 404 I posted in my last message still shows up. I abstracted the following from the error log as a potential cause: Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.6/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/venv/lib/python3.6/site-packages/postorius/views/list.py", line 779, in list_index paginator_class=MailmanPaginator) File "/opt/mailman/venv/lib/python3.6/site-packages/django_mailman3/lib/paginator.py", line 71, in paginate objects = paginator.page(page_num) File "/opt/mailman/venv/lib/python3.6/site-packages/django_mailman3/lib/paginator.py", line 46, in page number = self.validate_number(number) File "/opt/mailman/venv/lib/python3.6/site-packages/django/core/paginator.py", line 48, in validate_number if number > self.num_pages: File "/opt/mailman/venv/lib/python3.6/site-packages/django/utils/functional.py", line 48, in __get__ res = instance.__dict__[self.name] = self.func(instance) File "/opt/mailman/venv/lib/python3.6/site-packages/django/core/paginator.py", line 97, in num_pages if self.count == 0 and not self.allow_empty_first_page: File "/opt/mailman/venv/lib/python3.6/site-packages/django/utils/functional.py", line 48, in __get__ res = instance.__dict__[self.name] = self.func(instance) File "/opt/mailman/venv/lib/python3.6/site-packages/django_mailman3/lib/paginator.py", line 56, in count return self.function(count=0, page=1).total_size File "/opt/mailman/venv/lib/python3.6/site-packages/postorius/views/list.py", line 775, in _get_list_page advertised=advertised, mail_host=mail_host, count=count, page=page) File "/opt/mailman/venv/lib/python3.6/site-packages/mailmanclient/client.py", line 181, in get_list_page return Page(self._connection, url, MailingList, count, page) File "/opt/mailman/venv/lib/python3.6/site-packages/mailmanclient/restbase/page.py", line 37, in __init__ self._create_page() File "/opt/mailman/venv/lib/python3.6/site-packages/mailmanclient/restbase/page.py", line 62, in _create_page response, content = self._connection.call(self._build_url()) File "/opt/mailman/venv/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 112, in call error_msg, response, None) urllib.error.HTTPError: HTTP Error 404: I would appreciate any insight. Thank you. Regards, Jane

5 years, 6 months

Mailman-users search results for query "Postorius"