Search results for "Postorius" - Mailman-users

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, 4 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, 1 month

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

4 years, 10 months

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, 10 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, 4 months

Re: Hyperkitty performance problem

by monochromec

Following the root cause analysis which Tobias started all those weeks ago we (the admin team behind the installation) are still struggling with the following phenomenon: messages on average take more than 24 hours to be processed, more precisely, the average lifetime of a pickled message object in `/var/lib/mailman3/queue/pipeline` clocks in at around 26 hours). Couple of stats of the installation: standard installation from Bookworm OS repos, Hyperkitty as archiver and Postorius as web frontend as explained above, running Python 3.11.2 from the standard systemd service as packaged with the Bookworm deb file. All backends (Core + Hyperkitty) are supported by Postgres version 15+248. The MTA is a standard Postfix installation, again from OS packages. The underlying VM has 7 cores with just under 24 GB of main memory. This production instance is handling less than 130 mailing list (MLs) with an average of less than 10 postings per day per ML. CPU core utilisation hovers around 50% with the lion share allocated to the four pipeline runners as part of the MM configuration. OS resource utilisation is well below bounds (approx. 8 GB of main memory allocated to running processes), plenty of available sockets space (I noticed some transient `Connection lost during _handle_client()` warnings in the logs so I checked that the SMTP runner can connect to Postfix for delivering the messages after processing by checked the socket allocation of the running processes). Cursory review of the corresponding Core classes (runner + pipeline implementation in addition to `posting_pipeline`) didn't reveal any further pointers. What I did notice though that increasing the logging levels of the components (namely `smtp`, `pipeline` and `lmtp` to `debug`) in `/etc/mailman3/mailman.cfg` didn't add any useful information to the logs as configured after restarting the Core. As outlined above, Hyperkitty doesn't seem to do a check based on ML and message ID before archiving a message in the database. But this only add a REST roundtrip and Postgres communication through Hyperkitty's underlying Django framework to the overall system load and the driving UWSGI instance is well within CPU cycle bounds. Any pointers are appreciated - more than happy to provide more info if required.

1 year

Re: Converting discussion list to read-only list (settings)

by Mark Sapiro

On 10/14/19 5:40 PM, Paul Arenson wrote: > >> Assuming MUA means a mail application. And if that mail application has no reply list function then the setting doesn't work. MUA means Mail User Agent which is another name for mail application, YES. > Uh-oh: I AM LOST AGAIN. (will all caps give me a larger font?) > >> It is the presence of the >> List-Post: header in the message that allows the MUA to offer/process >> the "reply-list" function. > > Ok, I asked how to make it ANNOUNCE ONLY and you said to use "allow_list_posts is False" which is the same as "Include the list post header". Not exactly. You asked what settings were different between discussion style and announce only style. What I answered was that the only setting that differed as set by the style was what Postorius calls "Include the list post header". What I didn't say explicitly was that this is not sufficient to prevent posting to the list. > So does this mean that for a subset of users I cannot make it ANNOUNCE ONLY? And is it some other setting (send to moderator) that prevents it from being a DISCUSSION list? What exactly do you want? You found some info on configuring an announce only list and I referred you to a FAQ on that subject. Both of these do not directly address Mailman 3, but they do give useful information. I am going to stop guessing at what you want to accomplish, so tell me what you want to happen when someone sends a post to the list either from HyperKitty or by email. What should happen to the message? What if anything should be sent to the user? Should this behavior be the same for all users or just a subset. If a subset, how do you identify that subset and what should happen when others attempt to post? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

Re: What's the difference between (purpose of) reject and ignore

by denis.bitouze＠univ-littoral.fr

Hello, Andy Smith wrote: > On Sun, Jun 26, 2022 at 12:37:05PM -0000, denis.bitouze(a)univ-littoral.fr wrote: > >> AFAICS, it is not documented since, at Postorius → Settings → Message >> Acceptance → Default action to take when a (non-)member posts to the >> list, I only read: “Discard: this simply discards the message, with >> no notice sent to the post's author”. So no mention that this would >> set it to (silently) discard all future mails from them. > > Well that is because that isn't what that part does. As it says, > that part is the "Default action to take when a member/non-member > posts to the list". So that's where you set what you want to happen > when ANY non-member posts. This is what will happen any time any > non-member posts. > By contrast, when you set an action on a particular held message, it > is asking you want you want to do with posts from THAT INDIVIDUAL > ADDRESS for the future. > So hopefully you can see that these things are different. One is a > whole-list property that applies to posts from classes of posters > (members, non-members). The other is per-poster property as a > reaction to as held message from them. OK, I see, thanks. >> Just to be sure: for this feature, is it necessary to click on the >> subject and to choose in the drop-down list “Discard (no >> notification)”, or is it enough, on the .../held_messages page, to >> select the messages and click on “Discard”? > > Doing it from the held messages page will be a one-time thing; it is > only by clicking on the individual message that you can choose an > action for future messages from that address. OK. Too bad this cannot be done from the list of messages on the .../held_messages page: it would be very helpful when you are overwhelmed by spams...

3 years, 6 months

Re: moving lists to another server

by Mark Sapiro

On 11/20/23 00:58, Odhiambo Washington wrote: > > What is the command to export the archive as a mbox from the DB? > I can't figure out which option it is by looking at 'mailman-web -h'. Normally you do this on the old server via the HyperKitty web UI which has download buttons which do things like https://example.com/archives/list/list@example.com/export/list@example.com.… or for a partial archive https://example.com/archives/list/list@example.com/export/list@example.com-… However, in your case I don't think you have the old installation working any more so the above won't help. > BTW, how will ' mailman addmembers' treat a file containing: > ``` > Firstname Lastname <email@address> > Onlyname <email2@address> > ``` Correctly. It will import email@address with display name = 'Firstname Lastname' and email2@address with display name = 'Onlyname'. > I have opted for the simple way to do this: > 1. Create the site in Django Admin and create/configure the list in > Postorius > 2. Add the members from the file dump, with delivery set to regular. > 3. Send the members an email informing them that they need to set their > delivery preferences. > > I am stuck on the issue of exporting the archives to mbox file as already > stated above. Perhaps you can export the mbox via the web UI on the old server or maybe temporarily create a second mailman-web on your server with the old mailman-web database and use that web UI. Otherwise, if you have a working mailman-web that can access this database, you could try something like ``` $ mailman-web shell >>> from hyperkitty.lib.compat import get_list_by_name >>> mlist = get_list_by_name('list_name_only', 'list_domain') >>> with open('output.mbox', 'wb') as fp: ... for email in mlist.emails.order_by("archived_date").all(): ... fp.write(email.as_bytes() + b'\n') ... >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

Mailman-users search results for query "Postorius"