Search results for "Postorius" - Mailman-users

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

Re: Sanity check of upgrade procedure

by David Newman

On 10/26/22 3:10 PM, Mark Sapiro wrote: > On 10/26/22 11:08, David Newman wrote: >> >> For these new releases, is that mistune step still needed? > > > No. That is one of the issues fixed in HyperKitty 1.3.6 which now > requires mistune>=2.0.0,<3.0 and will work with those versions. OK, thanks. Before getting to mistune, this command, run as mailman in a venv: pip install -U mailman postorius django-mailman3 hyperkitty mailman-web uwsgi Mailmanclient produced this error: .. Attempting uninstall: mailman-web Found existing installation: mailman-web 0.0.6.dev9+gc606169 Uninstalling mailman-web-0.0.6.dev9+gc606169: Successfully uninstalled mailman-web-0.0.6.dev9+gc606169 ERROR: Could not install packages due to an OSError: [Errno 13] Permission denied: 'WHEEL' Check the permissions. The command also said I needed to upgrade pip. Doing that produced a similar error. How to resolve this error? Thanks again. dn

3 years, 9 months

Re: Unknown attribute: max_message_size

by Alexander Klotz

Hi, unfortunately we still have problems configuring a list so that it allows a message size larger than 40 KB. Neither the workaround described here: https://gitlab.com/mailman/postorius/commit/f86ab7fb5cc6edeb23c43336b677c24… (required was already set to false) nor this docker setup by yova https://gitlab.com/mailman/postorius/issues/246 worked. Are there any other options we could try? Thanks! Regards, Alex Klotz (CultureBase editorial staff) Am 28.05.18 um 17:16 schrieb Mark Sapiro: > On 05/28/2018 08:05 AM, Alexander Klotz wrote: >> Hi, >> >> just encountering the same problem in postorious, how are the chances of >> a fix being released soon? > > > It is fixed in the current branch heads. We plan a new release very > soon. There are still a few things we want to get in the release, so > it's not quite ready yet, but we're working on it. >

8 years, 1 month

Re: Don't start nntp runner by default - was: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Danil Smirnov

Hi Mark, On Fri, May 24, 2024 at 11:24 PM Mark Sapiro <mark(a)msapiro.net> wrote: > We could default mailman.cfg to contain `start: no` in the runner.nntp > section so people would need to enable it if they wanted it. What do > others think? > I'd vote for disabling it by default and also for moving the Postorius NNTP-related settings from the "Settings - List Identity" page (the last five settings) to a separate page. Users who are born later than my generation are sometimes confused and misinterpret those settings. Once a user set "Newsgroup moderation" to "Moderated" by mistake which implicitly made the mailing list moderated too. Sincerely, Danil Smirnov

2 years, 2 months

Re: Mailman, etc. upgrade woes and persistent bugs

by Allan Hansen

Mark, Thank you for this reminder, but it’s not really sufficient for most. The ‘Mailman Settings’ dialog does, indeed show the other preferences tags, and yes, as you say, the dialog for ‘List-based preferences’ only shows values that are not inherited and when you set a value there, it shows. There a two problems with this: a. Once a value is overridden on the ‘List-based preferences’ dialog, you cannot go back to it being inherited by removing the override. b. You cannot see, on this dialog, what the inherited value is. This is not user-friendly. May I suggest the following: That each option shows the following: o Value 1 o Value 2 (or the equivalent for pull-down menus) A box showing inheritance status: [ ] Use inherited value from address-based preference: Value2 If the ‘Use inherited value’ is chosen, then the inherited value shows. but the value radio buttons become non-selectable. If not, then whatever value the value radio box has become the value for the list, From what I see, the ‘Use inherited value’ is the default for new lists/addresses. To change a value, the user would uncheck this box, making the radio buttons selectable, and then set the desired value. Yours, Allan > On Feb 12, 2021, at 11:52 , Mark Sapiro <mark(a)msapiro.net> wrote: > >> I then looked at several of the disabled accounts, but the subscription info page in Postorius had no information about whether an account was enabled or disabled. Why is this not displayed???. The members can't see if their account is enabled. Is this another example of the disconnect between Mailman and Postorius? > > > If the user has a Django account, she can see all that info at (e.g. for > this list) <https://lists.mailman3.org/mailman3/accounts/subscriptions/ <https://lists.mailman3.org/mailman3/accounts/subscriptions/>> > She gets there from `Mailman settings` in the dropdown under her user > name. She can also get there via the `Manage Subscription` button on the > list's Info page. That takes her to `List-based preferences` for the > list. Any setting not selected there is inherited from the Address-based > preferences or Global Mailman preferences

5 years, 5 months

Github auth deprecated API

by Quanah Gibson-Mount

The version of mailman3 I'm running apparently uses a deprecated API for GitHub authentication. Does anyone know if this has been fixed? I couldn't find an issue for it on the postorius issue tracker. Sample email: ==================================================== Hello there! On May 14th, 2020 at 00:38 (UTC) your application used an access token (with the User-Agent python-requests/2.21.0) as part of a query parameter to access an endpoint through the GitHub API. https://api.github.com/user Please use the Authorization HTTP header instead as using the `access_token` query parameter is deprecated. Depending on your API usage, we'll be sending you this email reminder on a monthly basis. Visit https://developer.github.com/changes/2020-02-10-deprecating-auth-through-qu… for more information about suggested workarounds and removal dates. ==================================================== Thanks, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

6 years, 2 months

[Django] ERROR (EXTERNAL IP): Internal Server Error: /hyperkitty/list/direttivo@catania.linux.it/top-threads

by blackout69

Il 28/02/21 19:31, Abhilash Raj ha scritto: > On Sun, Feb 28, 2021, at 10:17 AM, blackout69 wrote: >> Hello everybody,I received this error message and from that moment the >> maiilan3 has stopped working.I restarted the following services mailman3 >> and mailman3-web and everything started working fine.Can you tell me >> what is the problem my django server has encountered? > What version of Hyperkitty are you running? It might be useful to include the versions of all the related Mailman packages, including: hyperkitty, django-mailman3, mailmanclient. Thanks Abhilash Raj for the reply Mailman Core Version GNU Mailman 3.2.1 (La Villa Strangiato) Mailman Core API Version 3.0 Mailman Core Python Version 3.7.3 (default, Jul 25 2020, 13:03:44) [GCC 8.3.0] Postorius 1.2.4 HyperKitty 1.2.2 mailmanclient 3.2.2 django-mailman3 1.2.0-3 mailmanclient 3.2.2-1 -- blackout69

5 years, 5 months

Re: MM3 not starting afte an upgrade -addendum

by Gelpi Andrea

To solve the problem I had to remove VHOST parameter from config file. I remember that Vhost was mandatory for my configuration when I set it up two month ago. So I don't understand why now I had to remove it to have MM3 working. Il 24/07/20 18:59, Mark Sapiro ha scritto: > On 7/24/20 1:33 AM, Gelpi Andrea wrote: >> >> Is anything changed since two month aggo when I applied some pathces? > > > What exactly are you asking? There have been multiple commits to the > master branches of the Mailman components in the last two months and new > releases of django-mailman3, hyperkitty and postorius in early June. > -- Gelpi ing. Andrea ************************************************** I documenti vitali dimostreranno la loro vitalitˆ spostandosi spontaneamente da dove li avevate lasciati a dove non riuscirete a trovarli. **************************************************

6 years

Re: Extracting mailing list users

by Odhiambo Washington

On Fri, Dec 30, 2022 at 1:57 PM Jan Eden via Mailman-users < mailman-users(a)mailman3.org> wrote: > Hi, > > I would like to export users of my mailing lists including their full > name (if present). The export button in Postorius creates a CSV with > addresses only, and the tool bin/list_members mentioned in the > [Mailman 2 FAQ] does not seem to be available in Mailman 3. > > I have full access to the server/database, so scraping the web interface > with [Mark's script] seems unneccessary. Is there an SQL statement (or > an equivalent of bin/list_members) to extract the data? > > Thanks, > Jan > > For MM3: (venv) [mailman@gw ~/mm]$ mailman members listname@domain --output some_file.txt -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 7 months

Re: Unable to remove non-member

by Mark Sapiro

On 7/22/24 13:31, kapoortoman--- via Mailman-users wrote: > Hi Everyone, > > I ran across a strange issue today. A client reported the inability to > remove a non-member in the following format: > > z_email/domain.org.za(a)domain.org.za An unquoted local part cannot contain a slash. > The reported error from Postorius was: > > "The user could not be removed" > > I used https://mailtester.ninja/ to validate the email > address and it is syntactically correct. If I ask https://mailtester.ninja/ to validate `z_email/domain.org.za(a)domain.org.za` it tells me that `domain.org.za(a)domain.org.za` is valid, not that `z_email/domain.org.za(a)domain.org.za` is valid. What's in Mailman core's mailman.log for this? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

Mailman-users search results for query "Postorius"