Search results for "Postorius" - Mailman-users

urllib.error --was: Re: No module named 'mailman3hyperkitty'

by Axel Rau

> Am 17.01.2022 um 00:19 schrieb Mark Sapiro <mark(a)msapiro.net>: > > On 1/16/22 10:24 AM, Axel Rau wrote: >> ModuleNotFoundError: No module named 'mailman3hyperkitty' > > This comes from mailman.cfg from the class: definition in the [archiver.hyperkitty] section you probable have something like > > class: mailman3hyperkitty.Archiver > > instead of > > class: mailman_hyperkitty.Archiver Correcting this, does not stop server errors. While selecting a list in the browser, I’m getting: - - - Traceback (most recent call last): File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/django/views/generic/base.py", line 70, in view return self.dispatch(request, *args, **kwargs) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/postorius/views/generic.py", line 74, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/django/views/generic/base.py", line 98, in dispatch return handler(request, *args, **kwargs) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/postorius/views/list.py", line 290, in get 'hyperkitty' in archivers and # noqa: W504 File "/usr/local/py_venv/mailman_33/lib/python3.9/_collections_abc.py", line 769, in __contains__ self[key] File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/base.py", line 146, in __getitem__ return self._get(key) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/base.py", line 88, in _get return self.rest_data[key] File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/base.py", line 74, in rest_data response, content = self._connection.call(self._url) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/connection.py", line 160, in call raise HTTPError(params.get('url'), response.status_code, urllib.error.HTTPError: HTTP Error 500: {"title": "500 Internal Server Error"} ERROR Un-handled exception: HTTP Error 500: {"title": "500 Internal Server Error"} - - - Question: Am I missing aliases in my nginx.conf? I just have: - - - location / { uwsgi_pass unix:///tmp/uwsgi.sock; include /usr/local/etc/nginx/uwsgi_params; } location /static { alias /usr/local/mailman3/static; } location /static/favicon.ico { alias /usr/local/mailman3/static/postorius/img/favicon.ico; } - - - Any help appreciated, Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

4 years, 9 months

Re: Member Issue Discovered

by Victoriano Giralt

El vie, 23-10-2020 a las 08:19 -0700, Mark Sapiro escribió: > > This would be more difficult for Postorius/Hyperkitty because those > users are Django users, but that isn't an issue for Affinity. > All of a sudden, an idea has dawned on me ... Wouldn't it be possible for Postorius/Hyperkitty, both Django applications, to use Mailman core user model as their User model? It is just a setting for Django (AUTH_USER_MODEL). I've used it for some of my applications and works nicely. This would certainly improve users' experience. -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

6 years

Delete user

by Rainer Herbst

Hi *! Recently, I have updated my docker images to 0.4.2 and it worked great. In the Postorius GUI, I see a new topic "Users" and found it quite comfortable. But one problem remais open - how can I delete a user alltogether, i.e. including his subscription and account data from the database? The reason for this question are the GDPR regulations - we do subscribe new staff members to some lists automatically, and should unsubscribe them and delete the entries after they left our organization. Viele Grüße Rainer Herbst Leiter IT-Service Phone: +49 331 7499-257 e-mail: rainer.herbst(a)aip.de https://www.aip.de ----------------------------------------------------------------------------------------------- Leibniz-Institut für Astrophysik Potsdam (AIP) An der Sternwarte 16, 14482 Potsdam Vorstand: Prof. Dr. Matthias Steinmetz, Wolfram Rosenbach Stiftung bürgerlichen Rechts Stiftungsverzeichnis Brandenburg: 26 742-00/7026 ----------------------------------------------------------------------------------------------- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: application/x-pkcs7-signature Name: smime.p7s

4 years, 7 months

The future is here?

by Stephen J. Turnbull

ieso(a)johnwillson.com writes: > For our purposes, it replaces "how to install mailman3" guides with > a single script that aims to actually do the entire thing for > you. If a single script would work, we'd have one already, I'm pretty sure. The problem is that a large proportion (I'm tempted to say "almost all" ;-) Mailman 3 installations need to fit in to an existing system configuration or pre-conceived design. I'd say that that the "standard" Mailman stack is: 0. Intel server box (not a VM) 1. Linux kernel 2. any distro 3. Postfix MTA 4. Apache webserver with wsgi module enabled 5. PostgreSQL database manager 6. Python 3 >= 3.6 7. Mailman core 8. Postorius 9. HyperKitty 10. All the above on a single host with a single public IP address and canonical domain. So 2 and 7 brook no controversy (2 because you can't argue with "anything goes", and 7 because, well, if you're arguing about 7, you're not ready to install Mailman nohow!) But every single one of the rest of those is *very* debatable -- there are already people using all of the options mentioned below (and more) in production. VMs and containers are frequently used for 0, BSDs (including MacOS) are fine for 1, Exim4 and Sendmail have varying degrees of support already for 3 (and I'll bet there are people running qmail), people do use other webservers such as nginx for 4, aside from PostgreSQL there are the MyQSL databases that are supported and some crazy folks will try to use SQLite or Oracle in production for 5, Postorius is optional and there is a commercial alternative that is used in production in a hosting service and may eventually be available for installation on your own host for 8, ditto 8 for 9 and there are yet other options such as mailarchive.com, and for 10, some people for either security or performance reasons or both want a multihomed system. So there are a minimum of 3 MTAs * 3 production-ready RDBMSes (my understanding is that there are Mailman config tweaks for standard MySQL that MariaDB doesn't need or vice-versa) to deal with, and possibly some optional options we'd like to deal with. The alternative is to say: here's the deal, spin up a Linux VM and run this script ... but that's basically what Abhilash's Docker install is (except the obvious that container != VM) -- and even that requires tweaks that are less than obvious to a lot of people to get the necessary network connectivity. So I don't see Ansible (or any such system) as a panacea. Rather, I see it as a standard language that might help us in systematically tracking variables in provisioning Mailman systems. One Ansible role would be a useful reference, and if that grows into a family of roles that are easy to compare and implement "turn-key" Mailman 3 installations for a ton of users, that would be great. That's my motivation for encouraging research into it. Now, I could be wrong -- Ansible could be more powerful than I'm giving it credit for, or that "standard" configuration might not be merely what several Mailman core devs run, it might actually be the majority of systems new to Mailman. In that case just one script would be a major contribution. So don't let me discourage anybody. But do be aware that you probably do have to make a choice between a quagmire of options and mandating a particular stack (or small set of them) for simplicity.

5 years, 10 months

Re: Do not show archives to public

by Andrew Bernard

Hi Abhilash, This resulted in dozens of messages about Django errors, when I turned on Private Archives, and then accessed the page. Is that to be expected? [Hard to imagine.] Perhaps you have to wait? But how long typically? Andrew On Tue, 18 Jun 2019 at 22:37, Abhilash Raj <maxking(a)asynchronous.in> wrote: > On Tue, Jun 18, 2019, at 4:32 AM, andrew.bernard(a)gmail.com wrote: > > Is there a way to have list archives only visible to list subscribers? > > Presently, they are world visible - unless I have configured my site > > incorrectly. > > You can set archives to be private in Postorius under > > Settings -> Archiving -> Private Archives > > It might take some time for the changes to sync back to Archiver > after you have updated the settings. > >

7 years, 4 months

Re: Is it possible yet to install Mailman 3 for Ubuntu 22.04?

by Eggert Ehmke

I can confirm the virtualenv method. It works well on all Debian derived systems like Ubuntu, and you are independent of the package release cycle of the distribution. My system works on Debian 11, Mailman3, MariaDb, uwsgi, Apache, Postfix. No problems so far. Regards, Eggert Am Freitag, 14. April 2023, 22:30:14 CEST schrieb Mark Sapiro: > On 4/14/23 12:44, Mark London wrote: > > Is it possible yet to install Mailman 3 for Ubuntu 22.04? > > Yes. We recommend following the instructions at > <https://docs.mailman3.org/en/latest/install/virtualenv.html> but there > are also Debian/Ubuntu packages. You can install the mailman3-full > package with apt. This will install Mailman core as well as the > Postorius and HyperKitty web packages, but the versions are several > releases old.

3 years, 6 months

Re: Mailman do not honor non-members moderation setting sometimes

by Mark Sapiro

On 6/16/20 1:28 AM, Alan So wrote: > Some of our users reported that their list do not honor the nonmembers moderation setting sometimes. We were not able to repeat the issue consistently earlier. Luckily, we found the following way to repeat the issue: > > 1) Create a new list with user(a)example.com as owner. (Ordinary disussion mailing list style) > 2) Change the list Settings -> Message Acceptance -> Default action to take when a non-member posts to the list: Discard > 3) Add a non-member user(a)example.com and change the moderation setting to Hold for Moderation > 4) Send an email to the list using user(a)example.com. > > The message is discarded instead of being held. The above can also be repeated with the list setting Default action to take when a non-member posts to the list: Accept immediately. The message sent from user(a)example.com is accepted instead of being held. So, it looks like that the non-members moderation setting is ignored for this case. > > Further study indicate that the issue did not happen if the owner is set to user(a)example.com *after* adding the non-member. It looks like that we can avoid the issue during list creation. However, the issue can also be triggered through other ways such as adding the non-member as member and remove. There are also ways to resolve the issue by removing all corresponding member, non-member, owner setting and add them back in the following order: non-member, owner. However, it does not always work and so I do not go into the detail at this moment to complicate the issue. This is a known issue. See <https://gitlab.com/mailman/mailman/-/issues/659#note_270261964>. When the same user/address has both non-member and owner roles, setting moderation for the non-member in Postorius actually sets moderation for the owner which is meaningless because the owner role is never checked for moderation. Since the reference above is obscure, I have created https://gitlab.com/mailman/postorius/-/issues/436 for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

Dealing with email bounces from web signups

by Andrew Hodgson

Hi. Back on the topic of bogus web signups again. I am dealing with several hundreds of these per month and we're talking a very low traffic system here. I have a cronjob to remove the users from the database. Right now a concern for me is handling the bounces for the confirmation emails that don't get delivered. These are coming from postorius(a)lists.hodgsonfamily.org<mailto:postorius@lists.hodgsonfamily.org> which I have redirected to a mailbox so as not to clutter up the mail queue. What I would ideally like is if we get a bounce from one of these confirmation mails we delete the user from the database but that is probably a future request. We don't get too many of these, around 20-30 a week. What are other people doing with these messages? Thanks. Andrew.

4 years, 7 months

Re: moderator cannot login to the list

by Brian Carpenter

On 12/16/20 7:36 AM, Gregory Edigarov via Mailman-users wrote: > GNU Mailman 3.2.1 (La Villa Strangiato) > Python 3.7.3 (default, Jul 25 2020, 13:03:44) > > I've imported some lists from mailman-2.1 > using 'mailman import21' command. > > the import went fine, I am able to login into postorius as admin, and > see all imported mail list data. > but login as a moderator member of a list. I tried to reset moderator > password via rest api. > That doesn't help. > > how is that supposed to be done? > > thank you. Hi Gregory, Are we talking about the same user as the one that is logging in as admin? Or do you have additional moderators that need to be able to login and moderate your lists? -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 10 months

Re: message size

by Mark Sapiro

On 7/12/22 10:18 AM, ronald.clarke--- via Mailman-users wrote: > Dear Mailman users, > I recently had a message from a user of my Mailman account blocked because there were attachments that exceeded 2 MB. This is the message I got: > "Message body is too big: 5312119 bytes with a limit of 2000 KB". > Is there any way to increase the maximum allowable size of attachments? In Mailman 3, there is a list setting for maximum list size. See Postorius -> Settings -> Message Acceptance -> Maximum message size, but the message you got is from Mailman 2.1. The appropriate list for that is https://mail.python.org/mailman3/lists/mailman-users.python.org/ In MM 2.1 this is controlled by the list admin UI General Options -> max_message_size. -- 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

Mailman-users search results for query "Postorius"