Search results for "Postorius" - Mailman-users

Re: Mailman archive issues (Hyperkitty)

by Mark Sapiro

On 6/7/21 11:54 PM, Kimmo L wrote: > Hi! > > Thanks for the support and help! > But so far i havent been successful with upgrading my postorius, hyperkitty and django pip packages from python2.7 to python3.5 or higher. As i understand, it was installed 2018 and has not been updated (because it has been working without any problem). Perhaps we can help with that. How are these installed now? What issues are you having when trying to upgrade. > Maybe the easiest way is to create a new deployment and somehow transfer data from old server to new one ? It's up to you which way to go. If you create a new deployment, I recommend following https://docs.mailman3.org/en/latest/install/virtualenv.html. You might also consider Xapian as the search engine - see https://docs.mailman3.org/en/latest/config-web.html#enable-full-text-search… and https://github.com/notanumber/xapian-haystack/tree/master Transferring the data is easy as long as the database is compatible - just dump and load, plus copy some files from Mailman's var/ directory. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

Re: HyperKitty failure

by horvath.arpad.szfvar＠gmail.com

> Can you go to https://lists.xxx.hu/hyperkitty/api/lists and get a > response from Django REST framework which is a json representation of > your mailing lists info? In this list I have just one list that I created for testing. And I can't see there the two lists I've imported from mailman2, e.g. korus. I guess because of admin is not a list list member there. I can see the korus at https://lists.xxx.hu/hyperkitty/ , but not at https://lists.xxx.hu/postorius/lists/ . I guess the setting below is not good. MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1') Should I set it to ('https://lists.xxx.hu/hyperkitty', '::1') ? Doesn't seem to work, like that. And what about MAILMAN_REST_API_URL? How can I found its proper value? It's currently the default value but if I try to reach it with wget http://localhost:8001 I get a 404. not found. How can I find the right value? 8001 is listening, so the latter value might be good. horvatha@pyEdu /etc/mailman3 (main) 12:34:13$ sudo lsof -i -P -n | grep LISTEN (...) python3 216185 list 25u IPv4 1079013 0t0 TCP 127.0.0.1:8001 (LISTEN) python3 216186 list 25u IPv4 1079013 0t0 TCP 127.0.0.1:8001 (LISTEN)

4 years, 6 months

Re: anyway to change/set options for a bunch of users?

by Mark Sapiro

On 3/22/22 06:19, bob B via Mailman-users wrote: > We just migrated to mailman 3 and one of my admins asked is there a way to change their digest options, when adding a bunch of users via mas subscription? Not yet at least. You could submit a feature request at https://gitlab.com/mailman/postorius/-/issues/new to be able to set Delivery mode when mass subscribing. > I was looking for an option to say all new users are set to digest, but I can't find it. Also, is there a way to select multiple users in list and change their digest options? I believe could do this in mailman2 but I am trying to figure out if this is possible for the GUI in mailman3? No, it's not, and in MM 2.1 you could check the digest option for multiple users in the Membership Management... -> Membership List, but if the list was paginated, you'd still need to go page by page. -- 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

Healthchecks and Django

by Stephen J. Turnbull

Philip Colmer writes: > For the MM3 servers, we're probing "/mailman3/lists/". You could create a path in urls.py called "250" that does nothing but respond with a 250 status (and maybe a hello-world page). The issue with /mailman3/lists/ is that it queries core for the lists (which, if successful, proves that core is up as a side effect). > Is there another URL we could use to check the health of a MM3 server What does this mean to you? Our Mailman 3 suite consists of three applications, core, Postorius, and HyperKitty, which might or might not be installed, and if installed might or might not be running on the same host. Core in turn depends on the MTA and starts a bunch of qrunners. Any of the above might fall over on its own. (I don't think there's any way to check on the health of a particular qrunner from the net, though.) > Or, if not, is there a way of stopping Django from sending out the > emails? There probably is, but I don't know it. Mark might, but if not asking on a Django list would be a better place.

4 years, 6 months

Re: Apache+mod_wsgi issue

by Stephen J. Turnbull

Odhiambo Washington writes: > > 2. apache.conf > > > <CUT> > > > ... > > > Alias /static "/opt/mailman/mm/static" > > > <Directory "/opt/mailman/mm/static"> > > > Require all granted > > > </Directory> > > > # WSGIScriptAlias /mailman3 /opt/mailman/mm/wsgi.py > > > # WSGIScriptAlias /accounts /opt/mailman/mm/wsgi.py > > > # WSGIScriptAlias /admin /opt/mailman/mm/wsgi.py > > > # WSGIScriptAlias /archives /opt/mailman/mm/wsgi.py > > > # WSGIScriptAlias /user-profile /opt/mailman/mm/wsgi.py > > > # WSGIScriptAlias /hyperkitty /opt/mailman/mm/wsgi.py > > > # WSGIScriptAlias /postorius /opt/mailman/mm/wsgi.py > > > WSGIScriptAlias / /opt/mailman/mm/wsgi.py > > > > This will send every http request to mod_wsgi except for requests to > > /static. This is OK if there are no other web sites on this server and > > the only http requests are for Django related things. > > This is just a virtual host. There are other websites on the server. If the above lines are in the virtual host element, they won't interfere with the other websites. If they are at top level, they will.

3 years, 6 months

Re: Apache Conf

by Thomas G

Same result with Alias "/static/" "/opt/mailman/static/" I have sometimes: [Fri Oct 19 22:05:52.583841 2018] [proxy_http:error] [pid 8328:tid 140435053815552] (104)Connection reset by peer: [client 1xxxxxxx1794] AH01102: error reading status line from remote server localhost:8000 [Fri Oct 19 22:05:52.583874 2018] [proxy:error] [pid 8328:tid 140435053815552] [client 1xxxxxxx:51794] AH00898: Error reading from remote server returned by /static/hyperkitty/libs/jquery/jquery-1.10.1.min.js But it's not systematic. Alias seem to be ignored by the proxy. Le ven. 19 oct. 2018 à 20:48, Mark Sapiro <mark(a)msapiro.net> a écrit : > On 10/19/18 12:17 PM, Thomas G wrote: > > Hi tried both. > > > > Same result. > > > > xxxx - - [19/Oct/2018:21:14:22 +0200] "GET /static/postorius/js/script.js > > HTTP/1.1" 404 4051 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) > > Gecko/20100101 Firefox/60.0" > > > What's in the apache error log? > > -- > 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/ >

7 years, 8 months

Re: Member Issue Discovered

by Stephen J. Turnbull

Brian Carpenter writes: > This is in regard to our Affinity/Empathy UIs. I believe the issue > [about data retention] that was raised originally in this > thread/post still exists with Postorius/Hyperkitty. I don't speak *for* the Mailman team on this, but my *impression* from these conversations is that we have a consensus on the team: deleting the User data (authentication and profile) is a very big deal that should be done only on explicit request, not as an automatic side effect of other changes. We understand that others have a different opinion, but we think that this is a difference of opinion, not a mistake on either side. My own suggestion is that we *should* provide the *option* to delete the User data, and prompt for it, when that User's last subscription on the server is deleted. Note that there is a race condition where the user deletes the second-to-last subscription and an admin then deletes the last one. The user won't see the option, but the admin will. I can see this as a bad outcome, depending on user's intent, whether the admin deletes the User object or leaves it in place.

5 years, 8 months

LMTP not listening

by Bartosz Sawicki

Hi everyone :), This is my first post in this group, so let me thank all of the developers for incredible work with Mailman3. Special congratulations goes to new project leader, Abhilash :) I've been using Mailman2 from over 15 years, and recently decided that it is time to upgrade. For several days I'm playing with all of the components of the system. Currently everything looks to be working nicely :) Mailman-core, Mailman-suite (Postorius, Hyperkitty) installed directly, not using docker containers. The last step was integration with MTA. I've configured Postfix and Mailman-core according to: https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#mailman-… But messages send to the list address are not delivered to the list :( I've started to investigate whats happening and realize that Postfix can not connect to mailman using LMTP. It seems that mailman is not listening on port 8024. Nov 24 13:12:31 lists postfix/lmtp[2737]: connect to 127.0.0.1[127.0.0.1]:8024: Connection refused I've checked log files, but haven't realize anything unusual . Any ideas where I could try to find cause of the problem ? My mailman.cfg file MTA section: [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: localhost lmtp_port: 8024 smtp_host: localhost smtp_port: 25 regrds.

8 years, 7 months

Re: [Mailman-Developers] Mailman 3.1 beta coming soon

by Barry Warsaw

On Dec 09, 2016, at 09:37 AM, Mark Sapiro wrote: >I understand you need to feel comfortable about everything going into >the core and this takes time and energy to review all the MRs, but I >think it is pretty important to get the DMARC mitigations into the core. >If there's anything I can do to help with this, let me know. > >I will rebase my branch again and possibly make one minor tweak, but I >think it should be OK. Thanks for pushing back on this Mark. Obviously, I have a high degree of trust in your work, but yeah, my compulsive behavior is showing through. ;) Please do rebase and if you can, remilestone the MR to 3.1. We'll get it in. >I can also work on Postorius. Also in this vein I have a question. >Should the DMARC settings be added to the Alter Messages tab in the List >Settings view or would it be better to have a separate DMARC Mitigations >tab. My gut reaction is to add a separate DMARC Mitigations tab, but Florian and Terri have final say I think. Cheers, -Barry

9 years, 7 months

Re: Strange problem in user lists

by Mark Sapiro

On 12/16/21 2:25 AM, Gelpi Andrea wrote: > > I cant' understand why, but I have two members with the wrong name. > > "A B" <C(a)dom.tld> > "D E" <F(a)dom.tld> > > My problem is that A and B must be associated with F(a)dom.tld and vice-versa. > > I tried to delete the user member and recreate it, but it has always the > wrong name. Because the display name is associated with the Mailman user and unsubscribing the user from the list doesn't change the user. > Is it possible to correct those errors? How? The user can log in to the web UI and go to the Account link in the dropdown at the username at the upper right and change the first and last name there. If you have a recent enough Postorius, a site admin can go to the Users link at the top of a page find the user, click Manage and change the Display Name. Otherwise, you can do this in `mailman shell` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

Mailman-users search results for query "Postorius"