Search results for "2021" - Mailman-users

Re: Archive search failing on one list

by Mark

On Sat, 2023-09-23 at 20:28 -0700, Mark Sapiro wrote: > > What if you do something like the following where django-admin is > whatever command you use for the Django admin command. > ``` > $ django-admin shell > Python 3.9.16 (main, Dec 11 2022, 12:49:23) > [GCC 9.4.0] on linux > Type "help", "copyright", "credits" or "license" for more > information. > (InteractiveConsole) > >>> from hyperkitty.models.mailinglist import MailingList > >>> mlist_name = 'listname(a)domain.com' > >>> mlist = MailingList.objects.get(name=mlist_name) > >>> mlist > <MailingList listname(a)domain.com (listname.domain.com)> > >>> > ``` Hi Mark, I'm still on this problem of one list's archive-search not returning any results. I created a new list today and it also has the same problem. In short, the older lists all seem fine -- their search results are up- to-date so that tells me the cron is okay. It's just these 2 newer lists that have the problem. It's taken me while to get my head around the Django admin command you have suggested, as I kept getting an error when starting: #django-admin shell >>> from hyperkitty.models.mailinglist import MailingList ... django.core.exceptions.ImproperlyConfigured ... That sent me down a rabbit hole which I haven't emerged from yet. But instead, starting with # python3 manage.py shell ... # python3 manage.py shell Python 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] on linux Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> from hyperkitty.models.mailinglist import MailingList >>> mlist_name = 'thepost(a)example.com' >>> mlist = MailingList.objects.get(name=mlist_name) >>> mlist <MailingList: <MailingList thepost(a)example.com>> >>> The format of my final line is different to yours ... Mine: <MailingList: <MailingList thepost(a)example.com>> Yours: <MailingList listname(a)domain.com (listname.domain.com)> Does this (missing list_id) give any clue as to why the archive-search isn't working, or is just that starting with "# python3 manage.py shell" is the wrong thing to do? By the way, the list_id shows correctly in the SQL query result. select * from hyperkitty_mailinglist where name like 'thepost(a)example.com'; ... name | thepost(a)example.com | list_id | thepost.example.com ... Any ideas appreciated. Mark

1 year, 8 months

Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by David Partain

On Thu, 2021-02-25 at 13:24 -0800, Mark Sapiro wrote: On 2/25/21 6:32 AM, David Partain via Mailman-users wrote: In /etc/mailman3/mailman.cfg I see: class: mailman.database.mysql.MySQLDatabase url: mysql+pymysql://mailman3:NopeNotPastingThat@localhost/mailman3?charset=utf8&use_unicode=1 Should I change the latter to be something like: url: mysql+pymysql://mailman3:NopeNotPastingThat@localhost/mailman3?charset=utf8mb4&use_unicode=1 Yes, either make it charset=utf8mb4 or I think dropping the charset= option altogether will use the database default, however I'm not clear why this would be the issue as this only controls how Mailman core accesses the database, and your issue is with HyperKitty/Django and its access is controlled by the DATABASES setting in Django's settings which you say do specify 'charset': 'utf8mb4' in OPTIONS. Also, it seems Mailman core is not even using the same database - i.e. `mailman3` whereas Django's is `mailman3web`. Hi Mark, Thanks for being patient with me. I'm still baffled but might have found the problem. I've done the above, to no avail. If I look at the queries being sent to mysql, I see stuff like this: 174 Connect mailman3web@localhost<mailto:mailman3web@localhost> on mailman3web using TCP/IP 174 Query SET sql_mode='STRICT_TRANS_TABLES' 174 Query COMMIT 174 Query SET AUTOCOMMIT = 0 174 Query SET AUTOCOMMIT = 1 174 Query SET AUTOCOMMIT = 0 I note that there is nothing about the charset, so something's clearly wonky. As previously stated, /etc/mailman3/mailman-web.py has the right thing: 'OPTIONS': { 'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", 'charset': 'utf8mb4', }, but that latter is having no effect. I then found /var/lib/ucf/cache/:etc:mailman3:mailman-web.py which doesn't have charset (but does have init_command), but I _think_ that's only about the package management system. So... I found that /usr/share/mailman3-web/settings_local.py is just a link to /etc/mailman3/mailman-web.py (which obviously has the right thing), but what about the .pyc file? # grep -i STRICT_TRANS_TABLES /usr/share/mailman3-web/settings_local.pyc Binary file /usr/share/mailman3-web/settings_local.pyc matches # grep -i charset /usr/share/mailman3-web/settings_local.pyc # It ain't in the .pyc file. Am I overly optimistic that that might the be problem? If so, I'd be grateful if someone'd tell the newbie how to recreate that file without trashing something. Cheers, David

4 years, 4 months

Re: Error on timeout vs retry values

by Robert Moody

Thank you, that's fixed it. On 19/07/21 7:28 am, Abhilash Raj wrote: > > On Sat, Jul 17, 2021, at 11:23 PM, Robert Moody wrote: >> Hi everyone, >> >> I have recently setup a new mailman3 service using the venv method. >> Everything is functionally working however I keep getting an error sent >> to the mailman email every min which I can not seem to figure out why. >> >> /opt/mailman/venv/lib/python3.7/site-packages/django_q/conf.py:142: >> UserWarning: Retry and timeout are misconfigured. Set retry larger than >> timeout, >> failure to do so will cause the tasks to be retriggered before >> completion. >> See >> https://django-q.readthedocs.io/en/latest/configure.html#retry for details. >> See https://django-q.readthedocs.io/en/latest/configure.html#retry >> for details.""" >> >> I have edited the timeout and retry values in the >> /opt/mailman/venv/lib/python3.7/site-packages/django_q/conf.py file and >> restarted both mailman and mailman-web however this still keeps repeating. > You shouldn't edit files in `site-packages` directory as they are part > of the package itself and could cause issues. > > What you want to do is override it in your settings.py (or settings_local.py) file > for Django. I am not sure which guide you followed to install Mailman, but it > should be somewhere in /opt/mailman/ I suppose (not in venv/ for sure). > > It should look something like this > > https://mailman-web.readthedocs.io/en/latest/settings.html#mailman_web.sett… > > Just the value of retry should be just > than timeout as the error says, so > not necessarily same values, but so far 300 and 360 has been working > good for us and I haven't seen any report to increase them. > > >> Any ideas? >> >> Regards, >> >> Robert >> >> >> -- >> This message has been scanned for viruses and >> dangerous content by MailScanner, and is >> believed to be clean. >> >> _______________________________________________ >> 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/ >> >

3 years, 11 months

Re: Disable user registration

by Abhilash Raj

> On Mar 20, 2021, at 6:22 AM, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > jens.guenther(a)posteo.de writes: > >> Same question here :-) > > This is not a simple question. Mailman is built from the ground up on > the assumption that users sign up. Making sign-up easy and powerful > is the raison d'etre of Mailman. > > One obvious approach is to add "^.$" to each list's ban list > (eventually that should be configurable as a list style, so "easy" to > make domainwide or sitewide), but that doesn't stop people from > creating users via Postorius. One way to address that would be to > clean out users with no subscriptions once a week or so. > > I guess you could go into the templates and remove the > accounts/signup/ links everywhere if "denial by obscurity" is enough, > or into urls.py and send that URL to a "Get out of here you hacker!" > view. Since these interventions are global, though, so the > desideratum of "no site admin intervention" is right out. Users are > site-global. Modifying urls.py to match `/accounts/signup` and redirect to a static page that says “Signups are disabled” or just event a 404 page is probably easiest to do. diff --git a/example_project/urls.py b/example_project/urls.py index 9c854989..3187756e 100644 --- a/example_project/urls.py +++ b/example_project/urls.py @@ -23,16 +23,22 @@ This file is the main URL config for a Django website including HyperKitty. from django.conf import settings from django.conf.urls import include, url from django.contrib import admin +from django.http import Http404 from django.urls import path, reverse_lazy from django.views.generic import RedirectView +def not_found(request): + raise Http404("Signups are disabled on this site.") + + urlpatterns = [ url(r'^$', RedirectView.as_view( url=reverse_lazy('hk_root'))), url(r'^hyperkitty/', include('hyperkitty.urls')), # url(r'^postorius/', include('postorius.urls')), url(r'', include('django_mailman3.urls')), + url(r'^accounts/signup', not_found), url(r'^accounts/', include('allauth.urls')), # Django admin url(r'^admin/', admin.site.urls), This did the job for me locally and will present the user with a 404 page saying the “Signups are disabled on this site”. Note it is important to put the new pattern before the “^accounts/“ pattern since the URLs are matched in the order they are defined. -- thanks, Abhilash Raj (maxking)

4 years, 3 months

Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Simon Coggins

Sorry that should be we went from 3.3.4 -> 3.3.5. I’m just reading the code now but my quick reading of it seems to say that if someone sees to 2 lists and they are both moderated, if one list moderator releases it, the email is deleted from the store and then when the second person releases it it’s now a dummy message that has no contents? That doesn’t sounds right. -Simon --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 On 4 Nov 2021, at 12:50 pm, Simon Coggins <s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au>> wrote: Since upgrading from 3.3.4 to 3.3.6 we are seeing a high instance of emails that are sent to 2 lists (EG 2 campuses). One campus will get the email and the other campus will get an email that just contains "The content of this message was lost. It was probably cross-posted to multiple lists and previously handled on another list.” Is this something new in 3.3.6? I’m trying to work out what’s going on and why it would be lost. Both lists need the email as the membership list is different so the people on the second list get a useless email. -Simon --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939

3 years, 8 months

Re: slow restart time for mailmanweb

by William Oliver

On Tue, 2021-12-28 at 13:07 -0800, David Newman wrote: > Debian 11.2, Mailman 3.3.5, Python 3.9.2, MariaDB 10.5.12-0+deb11u1 > > On a Debian system running MariaDB, mailman3 restarts quickly but > mailmanweb takes about 90 seconds: I get the same thing. Here's my log snippet: Dec 28 16:18:41 emergenus systemd[1]: mailmanweb.service: State 'stop- sigterm' timed out. Killing. Dec 28 16:18:41 emergenus systemd[1]: mailmanweb.service: Killing process 3046 (uwsgi) with signal SIGKILL. Dec 28 16:18:41 emergenus systemd[1]: mailmanweb.service: Killing process 20439 (uwsgi) with signal SIGKILL. Dec 28 16:18:41 emergenus systemd[1]: mailmanweb.service: Killing process 20440 (uwsgi) with signal SIGKILL. Dec 28 16:18:41 emergenus systemd[1]: mailmanweb.service: Killing process 20442 (sh) with signal SIGKILL. Dec 28 16:18:41 emergenus systemd[1]: mailmanweb.service: Killing process 20444 (mailman-web) with signal SIGKILL. Dec 28 16:18:41 emergenus systemd[1]: mailmanweb.service: Killing process 20446 (mailman-web) with signal SIGKILL. Dec 28 16:18:41 emergenus systemd[1]: mailmanweb.service: Killing process 20447 (mailman-web) with signal SIGKILL. Dec 28 16:18:41 emergenus systemd[1]: mailmanweb.service: Killing process 20448 (mailman-web) with signal SIGKILL. Dec 28 16:18:41 emergenus systemd[1]: mailmanweb.service: Killing process 20449 (mailman-web) with signal SIGKILL. Dec 28 16:18:41 emergenus systemd[1]: mailmanweb.service: Killing process 20450 (mailman-web) with signal SIGKILL. Dec 28 16:18:41 emergenus systemd[1]: mailmanweb.service: Main process exited, code=killed, status=9/KILL Dec 28 16:18:41 emergenus systemd[1]: mailmanweb.service: Failed with result 'timeout'. After it times out, it starts fine. If I just stop the thing and then start it, it goes fast. Here's that log: Dec 28 16:27:22 emergenus systemd[1]: Stopping GNU Mailing List Manager... Dec 28 16:27:24 emergenus mailman[23408]: Shutting down Mailman's master runner Dec 28 16:27:27 emergenus systemd[1]: mailman3.service: Succeeded. Dec 28 16:27:27 emergenus systemd[1]: Stopped GNU Mailing List Manager. Dec 28 16:27:27 emergenus systemd[1]: mailman3.service: Consumed 42.834s CPU time. Dec 28 16:27:27 emergenus systemd[1]: Starting GNU Mailing List Manager... Dec 28 16:27:29 emergenus kernel: [ 8076.868797] [UFW BLOCK] IN=eth0 OUT= MAC=00:16:3e:ef:72:96:00:23:9c:9e:9f:c0:08:00 SRC=92.63.197.108 DST=203.159.80.234 LEN=40 TOS=0x00 PREC=0x00 TTL=253 ID=58971 PROTO=TCP SPT=44610 DPT=21987 WINDOW=1024 RES=0x00 SYN URGP=0 Dec 28 16:27:29 emergenus mailman[23433]: Starting Mailman's master runner Dec 28 16:27:29 emergenus mailman[23433]: Generating MTA alias maps Dec 28 16:27:30 emergenus systemd[1]: mailman3.service: Can't open PID file /opt/mailman/mm/var/master.pid (yet?) after start: Operation not permitted I don't know what's up with the pid thing -- it moves right on in about 1 second. billo

3 years, 6 months

Re: User settings triggers error

by Mark Dadgar

On Jun 18, 2020, at 4:25 PM, Mark Dadgar <mark(a)pdc-racing.net> wrote: >>> Any thoughts on how to salvage ~20 years of list archives? >> >> >> The archives shouldn't be an issue. I don't think they are involved in >> the corruption, but anyway, hopefully you still have the archive mbox >> you imported. Then for the messages since then, you should be able to >> get a mbox from hyperkitty with something like >> >> https://example.com/hyperkitty/list/listname@example.com/export/arbitrary-n… >> >> with the obvious substitutions and appropriate start and end dates. >> >> The list is trickier. If you are going to start over with a clean >> install, and if you have a config.pck that you imported from MM 2.1, I >> suggest the following: >> >> Use the `mailman members` command to get a list of all members. Then >> depending on how much work you want to do, also get separate lists of >> plaintext and mime digest members and members with delivery disabled. >> >> Then on the new install, import the config.pck with `mailman import21` >> and import the archive mboxes with hyperkitty_import. >> >> Run `mailman members --sync` with the full current membership list, and >> record the [ADD]s. Then you can match the [ADD]s against the plain and >> mime digest members and those with delivery disabled and set their options. >> >> That's a lot to do, but it should get you close. > > I would probably be satisfied with just exporting the current list of member email addresses + names and letting people go back and change their list settings to switch to digest, etc. if necessary. > >> On the other hand, if you can wait, we might be able to figure out how >> to fix this, and it's even possible the underlying issue isn't database >> corruption. > > > Sure - I can wait. Thank you. I am probably going to go ahead with the list wipe and recreate in the next couple of days. Lack of access to the administration stuff is starting to become a problem. Sigh. So far, migrating from sqlite3 to postgres is looking like a bit of a bust. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years

Re: Question about message bounce stats

by Abhilash Raj

> On Aug 30, 2021, at 11:27 AM, Stephen J. Turnbull <stephenjturnbull(a)gmail.com> wrote: > > Ruth Ivimey-Cook writes: > >> If Abhilash has a starting point, > > IIRC it was quite primitive, and probably not at the the individual > message level, more like list level. We do keep a bounce score for Member (email, mailinglist pair) that is right now only available in Mailman’s database and is used for the purposes of un-subscriptions or disabling delivery. We haven’t had a chance to expose these values through REST API, but it is something I’d be happy to accept a patch for and isn’t too difficult if someone wants to pick up the task. It might be helpful at some point to expose some of those stats to the list owner or site admin as well in Postorius. > >> and there is acceptance from others to integrate something of this >> sort, then I could possibly help make it happen. > > If you're that interested, I'd say get started, at least on sketching > out requirements. There will probably be some nitpicking about code > style and the like, and there may be delays in integrating stuff due > to the peanut gallery contributing requirements that we decide we want > in the feature, but I don't think there's a problem with the basic > idea. Yep, +1. It would be good to first figure out what more stats do we need/want and if they just need to be exposed through the API or we need to setup some offline setup for calculating those metrics with some mechanism and then expose. > > We won't be putting tracking pixels and the like in outgoing posts, > but as long as it's internal data already generated by normal Mailman > operation, I would be somewhere between very surprised and shocked > (SHOCKED, I tell you!) if it weren't accepted. Yeah, anything that is possible to generate with regular Mailman operation is already possible for a site admin to get from logs with some scripting. So, the idea to expose them in a better UX I guess should be okay. Only thing we might want to consider is how much of that data is exposed to non-server-admins (list owners, mods etc) and the policy enforcement for that if users don’t like the default. -- thanks, Abhilash Raj (maxking)

3 years, 10 months

Re: Mailman3 service on mailman-3.3.4 is not getting started

by Mark Sapiro

On 6/23/21 12:24 AM, Shashikanth Komandoor wrote: > Hi team, > > I am trying to install mailman 3.3.4, the currently available > latest version at > https://docs.mailman3.org/en/latest/install/virtualenv.html on RHEL 7.5. > > As part of the installation, I am not creating any user with the > name *mailman* and instead going with the *root* user only. Along with that > I am using the directory */var/lib/mailman* as the root directory. It is a very bad idea to run Mailman as root. If there were some vulnerability that would enable an exploit to run arbitrary code, you wouldn't want that code to run as root. ... > Now, the issue is while I am trying to start the service, it > is showing the below error and the status looks like as following: > > # systemctl start mailman3 > Job for mailman3.service failed because a configured resource limit was > exceeded. See "systemctl status mailman3.service" and "journalctl -xe" for > details. > > # systemctl status mailman3 > ● mailman3.service - GNU Mailing List Manager > Loaded: loaded (/etc/systemd/system/mailman3.service; disabled; vendor > preset: disabled) > Active: failed (Result: resources) since Wed 2021-06-23 12:51:27 IST; > 1min 7s ago > Process: 16277 ExecStart=/var/lib/mailman/venv/bin/mailman start > (code=exited, status=0/SUCCESS) > > Jun 23 12:51:27 psumm3.nic.in mailman[16277]: os.execl(*execl_args) > Jun 23 12:51:27 psumm3.nic.in mailman[16277]: File > "/usr/lib64/python3.6/os.py", line 527, in execl > Jun 23 12:51:27 psumm3.nic.in mailman[16277]: execv(file, args) > Jun 23 12:51:27 psumm3.nic.in mailman[16277]: TypeError: expected str, > bytes or os.PathLike object, not NoneType > Jun 23 12:51:27 psumm3.nic.in mailman[16277]: Starting Mailman's master > runner > Jun 23 12:51:27 psumm3.nic.in mailman[16277]: Generating MTA alias maps > Jun 23 12:51:27 psumm3.nic.in systemd[1]: PID file > /var/lib/mailman/var/master.pid not readable (yet?) after start. > Jun 23 12:51:27 psumm3.nic.in systemd[1]: Failed to start GNU Mailing List > Manager. > Jun 23 12:51:27 psumm3.nic.in systemd[1]: Unit mailman3.service entered > failed state. > Jun 23 12:51:27 psumm3.nic.in systemd[1]: mailman3.service failed. > > I can't understand where the issue might be. What's in Mailman's mailman.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

Re: spanish localization

by Victoriano Giralt

On Fri, 2021-02-12 at 09:04 +0100, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 11/2/21 20:15, Mark Sapiro wrote: > > On 2/11/21 3:47 AM, Guillermo Hernandez (Oldno7) via Mailman-users > > wrote: > > > I contributed in january to translate to spanish all the items > > > left in > > > Mailman Core, Django-mailman, HyperKitty and Postorius via > > > Weblate. I > > > thought they will be used in the next upgrade, but I cannot see > > > any > > > improvement and there are many words untranslated. > > > > The Spanish translations for Mailman core and HyperKitty are > > currently > > completely up to date with weblate. django-mailman3 differs in one > > string that was translated on Feb 10 and hasn't yet been merged. > > Postorius also differs in a few places from the Feb 10 version that > > hasn't yet been merged. > > Ok. Thanks for checking it. I put my little contribution in Weblate > and I like that it could be used by anyone. Actually, I was going to ask these same questions, because I dedicated some hours to get the Spanish translation nearly finished, it was kind of a "spiritual" need for me, being the person that seeded the efforts for Mailman i18n support back in the late '90s :-) :-) > I tried to run this using the same command as I did for the > "collectstatic" (that solved all my previous problems for the > upgrade) > and "migrate" runs but it shows me an error: > > su -m mailman3 -c "python3 manage.py compilemessages" > CommandError: This script should be run from the Django Git checkout > or your project or app tree, or with the settings module specified. I got this very same error, and was also confused, as manage.py runs at the project level, not application level. > I'm lost. Do not feel bad, Guillermo, an old time pythonist with message translations experience, that uses i18n for some of his applications, is also dazzled and confused :-) Confused-with-translations-ly, Victoriano. -- 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 ?

4 years, 4 months

Mailman-users search results for query "2021"