Search results for "Postorius" - Mailman-users

Re: If I manually add email addresses to a list and then delete them, how do i permanent delete them from Users?

by Eggert Ehmke

Works for me too! Thank you. Only the path to python is #! /opt/mailman/venv/bin/python In my installation. Cheers, Eggert Am Dienstag, 25. April 2023, 22:51:52 CEST schrieb Mark London via Mailman-users: > Andrew - The script had: > > DELETE_MAILMAN_USER = False > > When I set it to True, it got rid of the orphaned email addresses. > Thanks! - Mark > > On 4/25/2023 6:02 AM, Andrew Hodgson wrote: > > > Mark London wrote: > > > > > > > >> I added some email addresses manually to a mailing list and then removed > >> them. But now I can't find how to totally remove them from mailman3. > >> They show up in the Users list. > > > You may find this script useful: > > https://www.msapiro.net/scripts/clean_users.py > > > > > > > > I have it running in a cronjob. Thread discussing the script can be found > > here: > > > > > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread > > /GH4K42T66FU5PBHJH6ZDQEIUTXVDSLOC/ > > > > > > > TLDR you end up with orphaned Django users both from when users > > subscribe/unsubscribe and due to spam signups using the Postorius form > > which never get confirmed. > > > > > > > Thanks. > > Andrew. > > > _______________________________________________ > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message > /K3PO2XMCDR2342GVPHEQJNZPVPEPY6R4/ > > This message sent to eggert(a)eehmke.de ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

3 years

Re: Hyperkitty import from mailman2

by Sten Aus

Hi Happy new year and thank you for your support! I have managed to get it to work. I have imported config.pck from Mailman 2.1 and list archive from mobx format and it shows just great! Now just little more testing and I can finally import all old data to new Mailman 3. I imported list called "test" and the list was already created inside Mailman3 (before import). And import was successful. I will let you know the results! All the best Sten On 25/12/2017 10:25, Marvin Gülker wrote: > Am 24. December 2017 um 22:30 Uhr +0200 schrieb Sten Aus <sten.aus(a)eenet.ee>: >> Oh my god. :) That's it! There are no latest messages and front page shows >> only last month "activity". Thank you! I did not thought that I should check >> some older posts. :D > I know that feeling. It took me a while to figure this out as > well. Error on OSI Layer 8. > >> But how did you manage to import all the lists and members from Mailman2 to >> Mailman3? As I understand Mailman3 does not "support" (by manual) import >> right now? > You'll be surprised, but those mailinglists were not managed by Mailman2 > before. They were managed by mlmmj[1]. I wrote a script that converted > mlmmj's archive into mbox format, and then used the "hyperkitty_import" > command as explained by the Hyperkitty manual[2]. This worked > surprisingly well. As for the subscribers, Mailman 3's Postorius has a > mass-subscription facility in the admin interface. I extracted the list > of all subscriber emails from the mlmmj mailinglist and used that > mass-subscription facility to subscribe people again. There's an option > to disable delivery of the welcome email that should be ticked before > this I guess, though. It can be reset afterwards again. > > Greetings > Marvin > > [1] http://mlmmj.org/ > [2] http://hyperkitty.readthedocs.io/en/latest/install.html#importing-the-curre… >

8 years, 3 months

Re: Issue with Held Messages

by Jean-Luc Wasmer

On 2016-08-19 17:58, Mark Sapiro wrote: > On 08/17/2016 09:17 PM, Jean-Luc Wasmer wrote: >> >> No matter what action I set for member posts (Hold for moderator, >> Reject) they are always delivered. > > > I don't know why this would be. Perhaps the member's moderation is set > to Accept immediately - you can see this on ther member's options page > in Postorius when logged in as a list owner. Apart from "Mode of Delivery" that is set to "Regular" for the user, none of the following attributes are set: Mail Delivery Receive own posts to the list Receive acknowledgement mails Conceal address from the subscriber list Avoid duplicate copies of messages > When the message is delivered, what are the X-Mailman-Rule-Hits: and > X-Mailman-Rule-Misses: headers? > There is no X-Mailman-Rule-Hits header. X-Mailman-Rule-Misses: approved; emergency; loop; member-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header; nonmember-moderation By the way, I didn't mention before but in Settings | Message Acceptance, the "Acceptable aliases:" box contains "[]". When I try to Save changes after modifying something, I gut "An error occured: []" in the yellow banner (instead of "The settings have been updated."). >> When I tried from a non-member email address, the message got held but >> when I try to see it I get a Server Error (500) page. The log files >> shows: >> >> ERROR 2016-08-18 01:04:30,231 base 21026 34722993152 Internal Server >> Error: /mailman3/lists/test.mydomain.com/held_messages >> Traceback (most recent call last): > ... >> File >> "/usr/local/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanclient/_client.py", >> line 443, in held >> moderation_reasons=entry['moderation_reasons'], >> KeyError: u'moderation_reasons' > > > This is apparently <https://gitlab.com/mailman/mailmanclient/issues/10> > fixed by <https://gitlab.com/mailman/mailmanclient/merge_requests/16> Any ETA when this will be pushed to "mailman-bundler"? Cheers, Jena-Luc

9 years, 8 months

Re: Messages not going to held queue

by Stephen J. Turnbull

Mail Person writes: > I have it set I guess by "it" you mean the user's moderation status, but there are *many* variables that affect whether mail is delivered or not. These include emergency moderation, spam filtering, and HTML handling (and there are probably others I don't remember off the top of my head), as well as individual variables such as not_metoo and the moderation status. All I can rule out is emergency_moderation, because that would prevent your test mail from being delivered when the test user is set to allow. > the user did not get a moderation email, myself as the moderator did > not get a notification, and Postorius did not show them in the held > messages queue. When you set the test user to accept, did you set it to "accept" or to "default processing"? Setting it to "accept" bypasses almost all of the acceptance checks. Usually "default processing" is what you want. > As far as logs, in var/log/mailman3 I do not see any logs other > than mailman.log, plugins.log and smtp.log. In the SMTP log I can > see that the message is getting to mailman: Does mailman.log show any errors? > This leads me to believe the message is being discarded or for some > reason not getting to the moderation queue. Sure, but Mailman doesn't do that for no reason. The only thing I can think of offhand that might happen in a mostly default configuration is that you're using an MUA that creates a multipart message where the plain part is empty and the actual message is HTML (yes, I've seen that in the wild). In some configurations that would cause the HTML part to be deleted, then the message could be recognized as empty and discarded. I haven't analyzed the code thoroughly but I don't recall a log message on that execution path so it might fit your case.

3 years, 7 months

Re: Heads up: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated

by Thomas Krichel

This issue is still there for me. I am starting a new installation from scratch, with the venv method in 3.13. (venv) root@darni ~ # mailman-web migrate System check identified some issues: WARNINGS: ?: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated, use: settings.ACCOUNT_LOGIN_METHODS = {'email', 'username'} ?: settings.ACCOUNT_EMAIL_REQUIRED is deprecated, use: settings.ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: No migrations to apply. I have root@darni /etc/mailman3 # head -15 /etc/mailman3/settings.py # Mailman Web configuration file. # /etc/mailman3/settings.py # Get the default settings. from mailman_web.settings.base import * from mailman_web.settings.mailman import * # Settings below supplement or override the defaults. # see https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/U... del ACCOUNT_AUTHENTICATION_METHOD ACCOUNT_LOGIN_METHODS = {'email', 'username'} del ACCOUNT_EMAIL_REQUIRED ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] Which is what I believe Wikinaut suggested works for her/him. But the warning is still there. I added Marks suggestions to add verbiage in the actual codebase root@darni /etc/mailman3 # tail -17 /usr/local/mailman/venv/lib/python3.13/site-packages/mailman_web/settings/mailman.py ### added by ToK #: Django Allauth #ACCOUNT_AUTHENTICATION_METHOD = "username_email" #ACCOUNT_EMAIL_REQUIRED = True #ACCOUNT_EMAIL_VERIFICATION = "mandatory" #ACCOUNT_UNIQUE_EMAIL = True ACCOUNT_LOGIN_METHODS = {'email', 'username'} ACCOUNT_SIGNUP_FIELDS = ['username*', 'email*', 'password1*', 'password2*'] ACCOUNT_EMAIL_VERIFICATION = "mandatory" ACCOUNT_UNIQUE_EMAIL = True ACCOUNT_EMAIL_UNKNOWN_ACCOUNTS = False del ACCOUNT_EMAIL_REQUIRED ACCOUNT_SIGNUP_FIELDS = ['username*', 'email*', 'password1*', 'password2*'] Restarted root@darni /etc/mailman3 # systemctl restart mailman3 ; systemctl restart mailmanweb Same old. (venv) root@darni ~ # mailman-web migrate System check identified some issues: WARNINGS: ?: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated, use: settings.ACCOUNT_LOGIN_METHODS = {'email', 'username'} ?: settings.ACCOUNT_EMAIL_REQUIRED is deprecated, use: settings.ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: No migrations to apply. Maybe I missunderstood something. -- Written by Thomas Krichel http://openlib.org/home/krichel on his 22190th day.

1 month, 3 weeks

Re: disabling social login

by Dmitry Makovey

On 11/06/2017 10:59 AM, Abhilash Raj wrote: > On Mon, Nov 6, 2017, at 10:26 AM, Simon Hanna wrote: >> On 11/06/2017 07:22 PM, Dmitry Makovey wrote: >>> Hi, I'm trying to disable social login and running into troubles >>> stepping on it's remnants all over the place. What's the proper sequence >>> for disabling social login in MM3 install? >> comment out 'allauth.socialaccount' and all social providers in the >> INSTALLED_APPS in your settings.py > > This apparently doesn't work, Hyperkitty apparently depends on this to > do some stuff. I haven't dug up in there, but the migrations would break > if we remove this from INSTALLED_APPS. > > Instead, please let the 'allauth.socialaccount' be there, along with > 'allauth.account' and 'allauth' and everything else related to allauth > should be removed. > > It looks something like this: > > ```` > INSTALLED_APPS = ( > 'hyperkitty', > 'postorius', > 'django_mailman3', > # Uncomment the next line to enable the admin: > 'django.contrib.admin', > # Uncomment the next line to enable admin documentation: > # 'django.contrib.admindocs', > 'django.contrib.auth', > 'django.contrib.contenttypes', > 'django.contrib.sessions', > 'django.contrib.sites', > 'django.contrib.messages', > 'django.contrib.staticfiles', > 'rest_framework', > 'django_gravatar', > 'paintstore', > 'compressor', > 'haystack', > 'django_extensions', > 'django_q', > 'allauth', > 'allauth.account', > 'allauth.socialaccount', > ) > > ``` > > I tested this works, see [1]. thanks! that worked indeed. > > > [1]: https://lists.araj.me/postorius/lists/ >> They shouldn't be enabled by default in the first place I guess, since >> pretty much all of them require further setup in order to work >> properly... >> >> How are you running MM3? >> _______________________________________________ >> Mailman-users mailing list >> mailman-users(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > -- Sr System and DevOps Engineer SoM IRT

8 years, 5 months

Re: Help with mailman user and mailman Web users

by Mark Sapiro

On 2/15/22 05:57, Sherin wrote: > > I have installed mailman3 server and configured MailmanWeb ( > hyperkity + Postorious ) . The service and everything works fine, but I > am little bit confuses with the user management in mailman3, > > 1) I created an owner user for a mailing list using the mailmanclient > api tools, # from mailmanclient.client import Client > 2) I can't login to the Mailmanweb with this user There are Mailman users and Django users. These are distinct. Creating a Mailman user does not automatically create a Django user and vice versa. In order to log in to the web UI, one must be a Django user, so this user has to go to the web UI and Sign Up. > For further investigation shows the mailman have its own database and > the web frontend have its own database too. > So my question is how to configure the webfrontend ( hyperkit+ > postorious ) to use the accounts logins created from the mailmanclient > api from the mailman core database. You can't. Well, I suppose you could modify the HyperKitty sync_mailman job or create another Django job to create Django users for Mailman users who aren't currently Django users, but short of that, there's no config for it. > Or is there a way to use only one user management system ? No. Mailman core and the web UI are separate applications by design in order to enable Mailman core to operate with any appropriate web UI. We provide Postorius and HyperKitty as web UIs for management and archiving and they are based on Django which has its own user management. It was our hope that other, perhaps more light weight, web UIs would be developed and available, but aside from EMWD's proprietary Harmony/Empathy PHP applications, we are not aware of any. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

Re: Mailman3 without Hyperkitty in docker

by Abhilash Raj

On Sat, Mar 2, 2019, at 1:09 AM, Danil Smirnov wrote: > Thank you very much Abhilash! > > Could you set up 'latest' tag in postotius repo <https://hub.docker.com/r/maxking/postorius/tags> please - as it exists for core/web? > I'd like to have consistent approach across the images... Done, triggered a build on Dockerhub. docker.io/maxking/postorius:latest This should be available when the build is done. > > Also it would be really great to extend image labelling used for *quay.io/maxking/mailman-*:rolling* images to Docker Hub ones... Version identification is quite hard for Docker... rolling tags should be available on DockerHub too. They are replicated on both registries. > > With my best regards, > Danil > > сб, 2 мар. 2019 г. в 03:19, Abhilash Raj <maxking(a)asynchronous.in>: >> __ >> >> >> On Thu, Feb 28, 2019, at 10:18 PM, Danil Smirnov wrote: >>> Hi Abhilash, >>> >>> Thank you very much - the previous error is fixed now. >>> >>> But I have another one now, which causes the same 500 Server Error: >>> >>> bash-4.3# cat /opt/mailman-web-data/logs/uwsgi-error.log >>> *** Starting uWSGI 2.0.18 (64bit) on [Fri Mar 1 05:42:09 2019] *** >>> compiled with version: 6.3.0 on 01 March 2019 01:52:42 >>> os: Linux-3.10.0-693.11.1.el7.x86_64 #1 SMP Mon Dec 4 23:52:40 UTC 2017 >>> nodename: mailman-web >>> machine: x86_64 >>> clock source: unix >>> detected number of CPU cores: 2 >>> current working directory: /opt/mailman-web >>> detected binary path: /usr/local/bin/uwsgi >>> !!! no internal routing support, rebuild with pcre support !!! >>> setgid() to 101 >>> setuid() to 100 >>> chdir() to /opt/mailman-web >>> your memory page size is 4096 bytes >>> detected max file descriptor number: 1048576 >>> building mime-types dictionary from file /etc/mime.types...1168 entry found >>> lock engine: pthread robust mutexes >>> thunder lock: disabled (you can enable it with --thunder-lock) >>> uwsgi socket 0 bound to TCP address 0.0.0.0:8080 fd 8 >>> uwsgi socket 1 bound to TCP address 0.0.0.0:8000 fd 9 >>> Python version: 3.6.8 (default, Jan 30 2019, 23:58:16) [GCC 6.3.0] >>> Python main interpreter initialized at 0x55a2df7f57e0 >>> python threads support enabled >>> your server socket listen backlog is limited to 100 connections >>> your mercy for graceful operations on workers is 60 seconds >>> mapped 166752 bytes (162 KB) for 2 cores >>> *** Operational MODE: threaded *** >>> Traceback (most recent call last): >>> File "/usr/local/lib/python3.6/site-packages/django/utils/module_loading.py", line 20, in import_string >>> return getattr(module, class_name) >>> AttributeError: module 'django.contrib.auth.middleware' has no attribute 'SessionAuthenticationMiddleware' >>> >>> The above exception was the direct cause of the following exception: >>> >>> Traceback (most recent call last): >>> File "wsgi.py", line 38, in <module> >>> application = get_wsgi_application() >>> File "/usr/local/lib/python3.6/site-packages/django/core/wsgi.py", line 13, in get_wsgi_application >>> return WSGIHandler() >>> File "/usr/local/lib/python3.6/site-packages/django/core/handlers/wsgi.py", line 136, in __init__ >>> self.load_middleware() >>> File "/usr/local/lib/python3.6/site-packages/django/core/handlers/base.py", line 34, in load_middleware >>> middleware = import_string(middleware_path) >>> File "/usr/local/lib/python3.6/site-packages/django/utils/module_loading.py", line 24, in import_string >>> ) from err >>> ImportError: Module "django.contrib.auth.middleware" does not define a "SessionAuthenticationMiddleware" attribute/class >>> unable to load app 0 (mountpoint='') (callable not found or import error) >>> *** no app loaded. going in full dynamic mode *** >>> *** uWSGI is running in multiple interpreter mode *** >>> spawned uWSGI master process (pid: 1) >>> spawned uWSGI worker 1 (pid: 37, cores: 2) >>> --- no python application found, check your startup logs for errors --- >>> --- no python application found, check your startup logs for errors --- >>> --- no python application found, check your startup logs for errors --- >>> --- no python application found, check your startup logs for errors --- >>> --- no python application found, check your startup logs for errors --- >>> --- no python application found, check your startup logs for errors --- >>> --- no python application found, check your startup logs for errors --- >>> --- no python application found, check your startup logs for errors --- >>> --- no python application found, check your startup logs for errors --- >>> --- no python application found, check your startup logs for errors --- >>> --- no python application found, check your startup logs for errors --- >>> --- no python application found, check your startup logs for errors --- >>> >>> As per my investigation, this error possibly caused by Django upgrade: >>> >>> *The SessionAuthenticationMiddleware class is removed. It provided no functionality since session authentication is unconditionally enabled in Django 1.10.* >>> >>> See https://docs.djangoproject.com/en/2.0/releases/2.0/ >>> >>> After I've removed the line >>> https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web… >>> from settings.py, the container is finally working. >>> >>> I've placed PR in github: >>> https://github.com/maxking/docker-mailman/pull/314 >> >> Thank you for your contributions! >> >> I have merged your pull request and it should now be out (hopefully!). >> >>> >>> Thank you for your help. >>> >>> Danil >>> >>> >>> пт, 1 мар. 2019 г. в 04:33, Abhilash Raj <maxking(a)asynchronous.in>: >>>> >>>> >>>> On Thu, Feb 28, 2019, at 5:19 PM, Abhilash Raj wrote: >>>> > On February 27, 2019 11:53:34 PM PST, Danil Smirnov <danil(a)smirnov.la> wrote: >>>> > >Hi Mark, >>>> > > >>>> > >Actually all this stuff happens inside the container after it's started >>>> > >and >>>> > >initialized without errors. I didn't amend the image anyhow. >>>> > > >>>> > >Also I have the configuration based on docker-compose.yaml provided in >>>> > >the >>>> > >repository which works just fine for mailman-web image. >>>> > > >>>> > >The very same config with postorius image (+ UWSGI_STATIC_MAP param) >>>> > >fails >>>> > >with 500 error... >>>> > > >>>> > >Now answering your questions: >>>> > > >>>> > >ср, 27 февр. 2019 г., 22:56 Mark Sapiro <mark(a)msapiro.net>: >>>> > > >>>> > >> do you have django-q in INSTALLED_APPS in your Django settings and >>>> > >what >>>> > >> is set for Q_CLUSTER? >>>> > >> >>>> > > >>>> > >I've checked settings.py inside the container and I haven't found any >>>> > >of >>>> > >the mentioned configurations there. >>>> > > >>>> > >Does the manage.py that's being run here point to the right >>>> > >settings.py? >>>> > >> >>>> > > >>>> > >No clue. >>>> > > >>>> > >Also I wonder why we have some Hyperkitty-related cronjobs in non-HK >>>> > >configured image? >>>> > > >>>> > >https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web… >>>> > >>>> > Because I am a dum dum ;-) >>>> > >>>> > Will work on removing those crons and stuff. Would be nice if you >>>> > opened an issue on Github so that I don't forget. >>>> >>>> Should now be fixed in the latest image. >>>> >>>> > >>>> > >Danil >>>> > > >>>> > > >>>> > > >>>> > >> -- >>>> > >> 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/ >>>> > >> >>>> > >_______________________________________________ >>>> > >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/ >>>> > >>>> > >>>> > -- >>>> > Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>> >>>> -- >>>> thanks, >>>> Abhilash Raj (maxking) >> >> -- >> thanks, >> Abhilash Raj (maxking) >> >> -- thanks, Abhilash Raj (maxking)

7 years, 2 months

Re: [Mailman-Users] MM3 startup issues

by hansen＠rc.org

Mark Sapiro wrote: > Restoring original Subject:, and doesn't this thread belong on > mailman-users(a)msailman3.org - CCing there. Sorry about both, Mark. I'm now here. Didn't know this one existed and was told to use the other list server. > > On 1/4/20 5:47 PM, Allan Hansen wrote: > > > > > a. The server was set up with the wrong domain > > name (our fault), so I had to add the ‘correct’ one. I had seen the command ‘Add Domain’ > > in > > the UI and thought that would do it, but Brian kindly sent me a list of additional > > instructions, which we then implemented. That made it possible to create a list in the new > > domain, subscribe people and post messages. However, messages are not archived. What extra > > step is needed to enable archiving? > > What are the setytings in Postorius -> Settings -> Archiving? > > Archive policy: Private archives > > Archive archivers: hyperkitty, prototype > Are the messages in Mailman's var/archives/prototype/LIST@DOMAIN/new > directory? Yes! I found them. But the message files end with the name of the old host, not the new host name under the new domain. > Are there messages in Mailman's var/archives/hyperkitty/spool/ directory? There are 5 .pck files there dated 1/5/2002. > What's the setting for base_url in mailman-hyperkitty.cfg? It's base_url: https://<OLDHOSTNAME>/archives I suppose it should be changed to base_url: https://<NEWHOSTNAME>/archives But: What if we decided to have more than one domain, as the UI indicates is kosher? > Are there any errors in var/logs/mailman.log? Yep. Lots. They all are of this nature: Exception in "hyperkitty" archiver Traceback: ... File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connection.py", line 430, in _match_hostname match_hostname(cert, asserted_hostname) File "/usr/lib/python3.7/ssl.py", line 327, in match_hostname % (hostname, dnsnames[0])) ssl.SSLCertVerificationError: ("hostname 'OLDHOSTNAME' doesn't match 'NEWHOSTNAME'",) > > b. When I go to the server using the new domain (both > > before and after logging in), I see not just the lists I created in the new domain, but > > the lists created in the old domain. These lists of lists are domain specific and should > > not be listed together. That’s just IMHO, but not serious, as I will soon get rid of > > anything in the old domain. So feel free to ignore this one if this is intended, which I > > could see might be the case. > Set > FILTER_VHOST = True > in settings_local.py > > Yes, Brian told me to do the same (well, settings.py). > > This is the what I wrote back: > > hansen@rccrmail:/opt/mailman/mm$ sudo vi settings.py > > Edited the setting to: > > # Only display mailing-lists from the same virtual host as the webserver > > FILTER_VHOST = True > You shouldn't edit settings.py. You should override the setting by > putting it in settings_local.py. Silly. I should have remembered that from back in the days. But if the local file is overriding, it should have worked, I'd think. > > Then Brian told me to restart qcluster: > > hansen@rccrmail:/opt/mailman/mm$ sudo systemctl restart qcluster > qcluster is not what you need to restart. You need to restart whatever > is supporting the wsgi interface to Django. This may be uwsgi or > gunicorn or ??. Whatever it is, that's what needs to be restarted. Beats me, Mark. Brian, do you know? > > I then logged in, but the same lists are showing. It > > either takes the system a long time to reset or it has ignored the > > setting. > > Just tried it again, and the lists are all showing. Do I need to manually recompile the > > file? > > > > c. I then > > moved on to the templates and added a template for the message text to send to new > > subscribers. That resulted in the following error message when I went in as moderator to > > approve of a new subscription: > > Something went wrong > > Mailman REST API not available. Please start Mailman core. > > Postorius is unable to access core's REST API. Is Mailman running? > > Well, I was able to post to the lists, so I assume it is. Listing at processes, I > > see a bunch of postgres, python3, nginx, django-adminp but > > nothing explicitly with a ‘mailman’ string. > If you do ps ax|grep runner=, what do you see? If you don't see at > least three processes with --runner=rest:0:1, stop Mailman and start > Mailman. Yep. I did not get the whole string before. With your options I see three of these rest:0:1 processes. So I guess the REST stuff is running anyway. > If so, what's > in /opt/mailman/mm/var/logs/mailmansuite.log or whatever it's > called - defined as filename in the file handler in the LOGGING > definition in settings(_local).py. > hansen@rccrmail:/opt/mailman/mm/logs$ tail -f mailmansuite.log > return Site.objects.get_current(request) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py", > line 60, in get_current > return self._get_site_by_request(request) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py", > line 45, in _get_site_by_request > SITE_CACHE[domain] = self.get(domain__iexact=domain) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/manager.py", > line 82, in manager_method > return getattr(self.get_queryset(), name)(*args, **kwargs) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/query.py", line > 408, in get > self.model._meta.object_name > django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist. > This is because of the domain change. In settings(_local).py you have a > setting for SITE_ID. Possibly, setting that in settings_local.py to a > value one greater that the current setting will do. Trying setting it to 1 (it was 0 before). > To be certain of the > correct value, you need to look at the django_site table in mailman's > database. That table has 3 columns, id, domain and name. The id for the > row of your domain is what needs to be set as SITE_ID. You lost me here. No idea how to access the Mailman database. Brian, do you know? > > [ABH] At this point I click to accept a subsription > > request: > > ERROR 2020-01-06 07:32:41,439 699 postorius.middleware Mailman REST API not available > > Traceback (most recent call last): > > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line > > 672, in urlopen > > chunked=chunked, > > File "/opt/mailman/mm/venv/lib/python3.7/site packages/urllib3/connectionpool.py", line > > 421, in _make_request > > six.raise_from(e, None) > > File "<string>", line 3, in raise_from > > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line > > 416, in _make_request > > httplib_response = conn.getresponse() > > File "/usr/lib/python3.7/http/client.py", line 1321, in getresponse > > response.begin() > > File "/usr/lib/python3.7/http/client.py", line 296, in begin > > version, status, reason = self._read_status() > > File "/usr/lib/python3.7/http/client.py", line 265, in _read_status > > raise RemoteDisconnected("Remote end closed connection without" > > http.client.RemoteDisconnected: Remote end closed connection without response > > So yes, the REST API is not there. How can I get it going? > Stop Mailman and then start it. No idea here, either. I looked online and found this: $ from mailman.commands.cli_control import Stop But it complained: from: too many arguments Must have found an out-of-date page. :-) Yours, Allan

6 years, 3 months

Re: Can't add emails to accept_these_nonmembers

by Mark Sapiro

On 2/27/26 07:17, Ibiam Chihurumnaya via Mailman-users wrote: > > Currently running Mailman 3.3.10 and I followed the instructions from https://docs.mailman3.org/en/latest/install/virtualenv.html# to install. OK. > I get something else when I do it differently - how I've been doing it so far -. > > mailman shell > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > >>>> from mailmanclient import Client >>>> from mailmanclient import Client >>>> client = Client('http://localhost:8001/3.1', '**', '**') >>>> sg = client.domains[0] >>>> sy = sg.get_lists()[-1] >>>> sy > <List 'systems-logs(a)lists.sugarlabs.org'> >>>> sy.settings > {'acceptable_aliases': [], ... OK. You are using Mailman Client which is a bunch of Python bindings for Mailman core's REST API and which is intended for use by HyperKitty, Postorius and Django-Mailman3 to communicate with Mailman core via its REST API. If you are using `mailman shell` you already have direct access to all of Mailman core. Using Mailman Client is just adding overhead to things you could do directly. If you really want to use Mailman Client, rather than invoking `mailman shell` and all it brings that you don't use, you could just invoke your venv's python, e.g., $ /opt/mailman/venv/bin/python or if your venv is active, just (venv) $ python and then import Client and continue as above. > Yes, but like I've mentioned in another thread, I don't have access to the web UI because > I can't get a confirmation link. You can always confirm your address manually UPDATE account_emailaddress SET verified = 't' where email = 'your_address'; -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months

Mailman-users search results for query "Postorius"