Search results for "Postorius" - Mailman-users

Re: List Migration from MM2.1 -> MM3

by Odhiambo Washington

On Mon, Aug 15, 2022 at 7:57 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/15/22 7:28 AM, Odhiambo Washington wrote: > > On Mon, Aug 15, 2022 at 4:59 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> Your /opt/mailman/mm/venv/bin/mailman is talking to a different Mailman > >> core than the one reading that mailman.cfg and the one Postorius is > >> talking to. > >> > > > > How can I track the one it's talking to? > > > Try `/opt/mailman/mm/venv/bin/mailman info` > So this command's output pointed to /opt/mailman/var/etc/mailman.cfg instead of my file that is in /opt/mailman/mm/mailman.cfg According to the HOWTO <https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10> I am following, mailman.cfg should be in /opt/mailman/mm/. Now I am wondering what I am missing again. Did something change? Should I place all my config files in /opt/mailman/var/etc/ instead of /opt/mailman/mm/ ? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

4 years, 1 month

Re: MIMEDefang to fix footers

by Mark Sapiro

On 11/13/20 9:51 AM, Ryan Morash wrote: > Does anyone know how to use MIMEDefang to fix the footer as attachment issue when using Mailman3? I've seen several guides/scripts referring to its use with Mailman2, but I'm unsure of how they would match with Mailman 3. I don't use MIMEDefang and don't specifically recommend it, but I have looked at <https://stuff.mit.edu/~jik/software/mailman_mimedefang/>, and it seems that the only Mailman specific things involved in the installation and configuration of this script are the addition of the "MAILMAN_MIMEDEFANG" lines as the first and last lines of the footer template. The only thing Mailman 3 specific in that is how to edit the footer template. This can be done on a per-list basis via Postorius since 1.2.0 or more directly in Mailman core by setting URIs, see <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> or by creating templates in Mailman's var/templates directory, see <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

Re: Mailman 3 installation documentation

by Terri Oda

Hurrah! I'm very excited about these updates. :) On October 6, 2019 8:17:15 p.m. PDT, Abhilash Raj <maxking(a)asynchronous.in> wrote: >Hi All, > >I have been trying to work on revamping the documentation site we have >at https://docs.mailman3.org. It is on https:// but I am not sure why >the http->https redirect doesn't work in Readthedocs. I have set it to >"serve always from https". > >Anyway, it might not look too different right now, but there are some >small re-organizations. I have been learning some new ReST and Sphinx >tricks and been trying to cross-reference and link various sections and >settings. The docs site shows up Mailman's logo now (I didn't even know >we could do that ;-). > >There is a place[1] for all supported Django settings that Postorius >and Hyperkitty have. I am also planning to add some common Django >settings that often people have to lookup and is not fun for people >from non-python backgrounds. Hopefully, it will make lives easier for >administrators. > >I have reverted my own stupid decision to use "sudo pip3 install" in >the docs to instead use virtualenv. The installation docs are going to >grow to be more comprehensive. > >I am also working on mailman-web project[3], which should simply >installation process for all the web components using a single project >and provide better guidance on Django's settings file management and >howto run manage.py commands. > >I have added a `mailman-web` command, which, for those of you familiar >with internal details of Django, is going to be our custom manage.py >script. It sets up settings correctly and would hopefully reduce the >pain of using `django-admin` and/or finding out the right path for >`manage.py` script. It is still not ready for prime time, but it is >usable. Early adopters can play with it if they like! > > >I would really appreciate if people who have tried to manually install >Mailman 3 in the past would share their experiences about what they >think could be documented better. You can reply here or open an >issue[2]. > >The user documentation are going to follow, hopefully soon :) > > >[1]: >https://docs.mailman3.org/en/latest/config-web.html#configure-postorius-hyp… >[2]: https://gitlab.com/mailman/mailman-suite-doc/issues >[3]: https://gitlab.com/mailman/mailman-web > >-- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

6 years, 11 months

Re: very few moderation capabilities for moderators

by Guillermo Hernandez (Oldno7)

On 16/9/21 16:40, Mark Sapiro wrote: > On 9/16/21 2:39 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> Hi all: >> >> I need to provide the list moderators a way to change the moderation >> flag for users from whichever it is (normally "list default >> processing") to "hold for moderation" and viceversa (to "list >> default" or to "accept") >> >> I understand that it could be done via console script (That's the way >> I did on mailman2: I made two commands using "withlist", one to hold, >> moderar.py, and other one to accept, desmoderar.py. I show you below) > > > Are you asking what the equivalent MM 3 scripts would be? > More or less: I'm asking for a general direction here. I think I cannot use tthe "withlist" method as before, inside a python script, and I'm not sure how to do it. I've been reviewing all the command docs that I've found, but I have no clear way. I need a shell or a python script that I can pass the list and the mail address to put on hold/hold (that way the moderators can log in a special account thhat asks for the address to hold/unhold). I did it in mailman2 whith the bin/withlist command, but now whithlist seems to be an alias for shell and is interactive.Thats not my goal) > >> But I think I'm not the only one that could use as an improvement a >> way to do this on postorius/web. > > > Postorius allows a list owner or site admin to set Moderation for list > members and non members at e.g. > https://www.example.com/mailman3/lists/list.example.com/members/(non)member/. Yes, I know that. But the owner cannot be 24/7 attending the lists (as we all know), and could need a help hand from moderators. Not just from accepting mails on hold, but to put on hold a member (and be capable of reversing it) when the netiquete dissapears completely and some thread becomes a flame and all goes south. I'ts the admin capability I miss the most for moderators in mailman. > Currently, a list moderator who is not an owner cannot do this, but a > moderator can set Moderation for the sender of a held post when > handling the post. But I'm talking about a moderator can put a member mails in hold when it is marked to accept. To prevent putting more gas in the fire. > >

5 years

Re: mailman admin (django) interface does not work anymore after deleting website example.com

by Torge Riedel

Am 10.03.19 um 16:44 schrieb Mark Sapiro: > On 3/10/19 8:18 AM, Torge Riedel wrote: >> I deleted the existing "example.com" and added a new one >> "lists.mydomain.de". >> >> Now the admin (django) interface always gives "An error occurred while >> processing your request". After one of the first navigation clicks I saw >> a message that "site with id 1 is missing". > > In your Django settings your have > > SITE_ID = 1 > > which pointed to the example.com domain you deleted. > > You need to override this in settings_local.py. Probably > > SITE_ID = 2 > > but if that doesn't work, try '0' > Ah, thank you Mark. That makes a kind of sense. I changed the database directly to fix it. And renamed example.com to lists.mydomain.de. Now the error is gone. I'm wondering why the initial database set up of postorius (?) adds "example.com". Is there a way to directly add my domain instead? Somewhere in settings_local.py?

7 years, 6 months

New messages not being archived

by Sarah H

I have 2 active lists that are properly mailing out and working, plus an admin testing list that is as well. The list info pane correctly shows the mail volume and the imported archives from the previous 2.1 installation are present for both active lists. None of the 3 lists are generating new entries in the archive, all 3 are set up with default settings except 1 active and admin are set to private. I know that hyperkitty is showing some new content as admin was created in postorius and the list is present in hyperkitty and working in mailman. None of the logs show anything of note, mailmanweb.log has no new entries since it caused a serious issue when I changed the domain, uwsgi-error is the same and uwsgi.log has proper access logs. When trying to add a new thread via the hyperkitty interface I can see the email go through the maillog, I get the email with the entered content and everything else works, it just doesn't add a new thread to the archive. The installation is set up with the default settings from the virtualenv installation guide. Any assistance would be appreciated.

5 years, 2 months

Re: duplicate SITE_IDs and broken /postorius/lists/ display; Mailman Client

by Stanisław Findeisen

On Thu, Mar 24, 2022 at 09:27:06PM -0700, Mark Sapiro wrote: > The issue is client.create_domain doesn't support setting a Web Host. Web Hosts are the sites in the django_site table and SITE_ID is the id of > the table entry. See `sites` in the Django admin UI. > > So when you create a domain with client.create_domain it gets arbitrarily assigned to a `site` Ok thanks, this is good to know. How about mailing list creation using Mailman Client, like this? domains = client.domains domains = list(filter(lambda x: (domain_name == x.mail_host), domains)) # .. check if domains is a singleton list .. domain1 = domains[0] domain1.create_list(list_name, style_name=style_name) Do you know of any quirks/deficiencies related to this kind of code? This code is taken from mailman3-utils: https://github.com/sfindeisen/mailman3-utils , a set of scripts I stitched together to facilitate common Mailman3 operations on the command-line. Most importantly this can apply the (currently hardcoded) set of list settings uniformly across the different lists (and different domains). (I realize part of this overlaps with the mailman command, especially in the local setting.) Thanks Stanisław

4 years, 5 months

Re: Dump/restore users (with passwords) via API

by Abhilash Raj

On Mon, Sep 17, 2018, at 12:15 PM, Dmitry Makovey wrote: > We are trying to dump/restore users using API calls and it seems that > API allows us to dump password hashes (a good thing), but then API does > not allow to insert users back using saved password hashes - only > cleartext passwords. I'd say that is intentional. You don't want people to be setting up hashes as passwords. > Aside from create_user is there any other way to > create users/change their password? Not that I know of, not using the API atleast. You could potentially use the low level API that inserts records in the database or use SQL to dump and restore that data. What do you use the Core's user/password for? Currently, the user passwords are basically just a carry-over from Mailman2 and there shouldn't be any use for it. I have been considering removing that completely have Postorius do all the authentication/authorization. Email based authentication should rely on more reliable identities like email signatures, intead of having to send cleartext passwords over email. -- thanks, Abhilash Raj (maxking)

8 years

Re: Mailman web interface / uwsgi

by Stephen J. Turnbull

Mark Sapiro writes: > On 11/27/22 00:19, Jan Eden via Mailman-users wrote: > > > > I see. But the mailman.cfg is placed in /etc/mailman3, and this file > > also belongs to the core, doesn't it? In any case, I changed the > > configuration parameter for [archiver.hyperkitty] as you suggested and > > all settings are in one place now. > > In that case, it's probably just an oversight. Yes, I think that's what's going on. There's been quite a bit of simplification and unification of the Django configuration over time, which is ongoing and not 100% reflected in all documentation. Because of the way most Linux distros work (and I think it's probably true for *BSD and other POSIX systems), it makes sense to put users' site configurations in /etc. I don't see a particular reason why with the current relatively small set of config files we'd want to put HyperKitty or Postorius files elsewhere than /etc/mailman3 (although it might make sense to have more separation given the existence of EMWD's Affinity etc). Steve

3 years, 9 months

Re: proper update procedure for MM3 docker containers

by Fabian A. Santiago

On 2018-08-06 12:24 PM, Abhilash Raj wrote: > On Mon, Aug 6, 2018, at 6:28 AM, Fabian A. Santiago wrote: >> Hello, >> >> Can someone remind me of the proper / best way to update my docker >> containers for MM3 / postorius based on maxking's images? Thanks. >> >> and this for both the stable and rolling releases. > > Well, the process is fairly straightforward, when moving form an older > to a newer release, > > Stop and remove the container ($docker-compose stop, $docker-compose > rm) and then start the new ones ($ docker compose up -d). > > That should be all! > >> >> -- >> Fabian S. >> >> OpenPGP: >> >> 0x643082042DC83E6D94B86C405E3DAA18A1C22D8F (new key) >> >> *** >> >> 0x3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC (to be retired, still >> valid) >> _______________________________________________ >> 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/ thank you. -- Fabian S. OpenPGP: 0x643082042DC83E6D94B86C405E3DAA18A1C22D8F (new key) *** 0x3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC (to be retired, still valid)

8 years, 1 month

Mailman-users search results for query "Postorius"