Search results for "Postorius" - Mailman-users

Re: My list has been switched from public to private archives, but they are still visible

by Enrique Terrazas

I am having a very similar issue. Here is what I have found: There are basically three archive settings we can select via the postorious web front end for archives. These can be found in: Settings > Archiving and they are: Public archives Private archives Do not archive this list In the Django administrative interface we can find those same(?/similar?) settings here: Main Page > Hyperkitty > Mailing lists > Mailing List object(x) > Archive policy: never private public I’m not sure which of the two takes precedence. My guess is postorius since that is a list owner accessible setting and the Django administrative interface would typically not be accessible to list owners. We have noticed the following odd behavior, not sure if it is a bug. For existing lists with private archives, when switching to “Do not archive this list” in postorious, the desired effect of no longer archiving the list is instantaneous. However, after the daily cron job that syncs with Mailman Core happens, the existing archives now become publicly accessible. Is this behavior based on the assumption that the list will no longer be archived and will therefore be purged? Enrique > On Sep 19, 2019, at 1:08 PM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > On Thu, Sep 19, 2019, at 3:31 AM, Paul Arenson wrote: >> Can anyone help with this? >> >> I set my list to private archives today. Up until then, it was pubic. >> And yet, if you go to the list page, you will see that if you click >> archives (top left), you can see them. (Filled with a bunch of tests >> posts for now) > > This change takes a bit of time to sync up Hyperkitty. THere is a daily > cron job which syncs this information from Mailman Core. > > I have made a change which should fix this problem and the process would > become synchronous. > > You can run `python manage.py runjobs --daily` command to force sync > that information. > >> >> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist.toky… >> >> Am I misunderstanding what a private archive is? > > Not really, your expectation is right. > >> >> Is something wrong with my setup (which is hosted)? >> >> Thank you. >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… >> > > -- > 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://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

5 years, 2 months

Re: Changing subscription address

by Allan Hansen

Hi Steve, My comments below: On 3/15/21, 21:28 , "Stephen J. Turnbull" <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: >I don't have the Postorius knowledge to do this in a reasonable amount >of time to help your user immediately, but how about this design: < >In the 'Mailman Settings' screen, List-based Preferences' tab, You may mean the 'Subscriptions' tab. >currently each list has an active link at the list's posting address >(which links to a page with the same options carefully documented), a >plain text display of the subscribed address, and a row of options. >Suppose we > >1. Add a popup menu of addresses and attach it to the > displayed address for each subscription, >2. Add a 'select subscription' checkbox to each subscription. >3. Add an 'act on all selected subscriptions' fake subscription, > whose checkbox has the effect of select or deselect all. I guess > this should be at the top.[1] > >Does that seem like what you have in mind? Any other needs you want >to mention? (Suggestions for feature design are welcome, but "I do >this often and there's got to be a better way" is good too.) The above will work fine, Steve, as it will cover the special needs of people who have several addresses that they use for different lists. It's very flexible. For the other 99% of my users, something much simpler is needed: Under 'User profile for <name>', under the 'E-mail Addresses', add button to ensure that 'Primary E-mail' is used for all lists. Then they can 'Create account' if needed. 'Add E-mail'. 'Make Primary' the new e-mail. 'Use Primary For All Lists'. 'Remove' the old e-mail. This requires them to set up an account, but I'm OK with asking them to do that. And, indeed, new subscriptions should default to 'Use Primary.' That would be fine, but it can be even simpler, which I would much prefer: Instead of the 'Use Primary For All Lists', may I suggest a tool that lets me set all subscriptions to 'Use Primarry' where there either is no account or where the primary e-mail is already chosen as the subscription address (which together form the 99% I mentioned). In that case, the procedure becomes much easier for me to explain to them, and no new functionality needs to be added (although what you suggested is fine). 'Create account' If needed. 'Add E-mail'. 'Make Primary'. "Remove' old email. Is that possible now? Does a member have to have an account for me to set it up thus for them? Thank you for considering this, Steven. Yours, Allan

3 years, 8 months

Re: Issue with Held Messages

by Jean-Luc Wasmer

On 2016-08-20 02:08, Mark Sapiro wrote: > On 08/19/2016 10:39 PM, Jean-Luc Wasmer wrote: >> 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 > > > If you look at the user's options when logged in as a list owner, you > should see an additional "Administration options" section below those > with a "Moderation" setting. What is that set to? I log in as the admin user created with "mailman-web-django-admin createsuperuser", I created the list logged in as this admin user and its email address is displayed in the "Owners" sections of the "Members" tab. I only have that 1 other member and when I check it settings, the last section is "Avoid duplicate copies of messages?" and then there's the "Save" button. >> 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."). > > > What happens if you clear the Acceptable aliases box before saving? Then I get "The settings have been updated." after pressing "Save changes". But if I navigate elsewhere and come back, the brackets are back in the form. > You may find <https://wiki.list.org/x/17891998> of interest. Indeed, I actually stumbled upon it yesterday. It would have helped me, specially setting up Apache's vhost (the example provided in the bundler only helped getting half of it working). One of the issues was the permissions to the run/wsgi path. Also, as I run on FreeBSD I had to create an rc script... I don't mind sharing it, it's not super advanced but it does the job.

8 years, 3 months

Re: why owner mails rerouted to list

by Mark Sapiro

On 10/22/19 2:20 AM, Tamas HOLCZER via Mailman-users wrote: > Hi All, > > we have moved to Mailman3 from Mailman2 recently, and have a quite > strange problem: > > Every message sent to owners is forwarded to the lists instead of the > owner's mail address. ... > We are using GNU Mailman 3.2.1 (La Villa Strangiato) from the Debian > Buster repo. As MTA we use exim4 (running on the same machine as > Mailman), and have Amavisd on a separate machine for spam filtering. This may be an exim configuration issue. You can stop the mail from being delivered to the list by ensuring the Postorius Settings - Message Acceptance -> Acceptable aliases is empty and Settings - Message Acceptance -> Require Explicit Destination is Yes. This will cause the messages to -owner, etc to be held. First ensure exim, particularly the router for list messages is configured as in <https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#exim4-co…>. > From MYLIST-bounces(a)MYDOMAIN.COM Mon Oct 21 21:13:59 2019 > Return-path: <MYLIST-bounces(a)MYDOMAIN.COM> > Envelope-to: MYADDRESS(a)MYDOMAIN.COM > Delivery-date: Mon, 21 Oct 2019 21:13:59 +0200 > Received: from [SPAMFILTER] (helo=localhost) > by MAILSERVER.MYDOMAIN.COM with esmtp (Exim 4.92) > (envelope-from <MYLIST-bounces(a)MYDOMAIN.COM>) > id 1iMd7u-0007pv-VR; Mon, 21 Oct 2019 21:13:59 +0200 > X-Virus-Scanned: by amavis-dc > Received: from MAILSERVER.MYDOMAIN.COM ([MAILSERVER-LOCAL-IP]) > by localhost (spamfilter.MYDOMAIN.COM [SPAMFILTER]) (amavisd-new, port 10023) > with ESMTP id Pe6CPG7d_0VR; Mon, 21 Oct 2019 21:13:57 +0200 (CEST) > Received: from MAILSERVER2.MYDOMAIN.COM ([MAILSERVER-PUBLIC-IP] helo=MAILSERVER.MYDOMAIN.COM) > by MAILSERVER.MYDOMAIN.COM with esmtp (Exim 4.92) > (envelope-from <MYLIST-bounces(a)MYDOMAIN.COM>) > id 1iMd7t-0007pn-Mu; Mon, 21 Oct 2019 21:13:57 +0200 It seems the issue occurs here. The Received: header below is the receipt of the message from Mailman to MYLIST-owner. That header clearly says the envelope recipient is MYLIST-owner(a)MYDOMAIN.COM. Then the header above looks like the delivery of the message from the Mailman list to one or more list members. What we don't see is the intermediate step of LMTP delivery of the message to Mailman's LMTP server. That delivery must have had envelope recipient MYLIST(a)MYDOMAIN.COM rather than MYLIST-owner(a)MYDOMAIN.COM I think what's missing is `rcpt_include_affixes = true` in the exim transport for Mailman. > Received: from MAILSERVER2.MYDOMAIN.COM ([MAILSERVER-PUBLIC-IP] helo=MAILSERVER.MYDOMAIN.COM) > by MAILSERVER.MYDOMAIN.COM with esmtp (Exim 4.92) > (envelope-from <MYLIST-bounces(a)MYDOMAIN.COM>) > id 1iMd7r-0007pR-JZ > for MYLIST-owner(a)MYDOMAIN.COM; Mon, 21 Oct 2019 21:13:55 +0200 > From: MYLIST-owner(a)MYDOMAIN.COM > To: MYLIST-owner(a)MYDOMAIN.COM -- 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: username

by Stephen J. Turnbull

bryan.kartzman(a)yu.edu writes: > will do this. The university does use SSO for many applications and > I was asked by upper management of the IT department to try and > implement it here. I'm still trying to understand your reply to my > SSO question from last week (my SSO knowledge is limited and I'll > have to read up on Shibboleth, SAML, as well as Django) so for now > I'm thinking to not use SSO If they want to use it, pass the buck to them. I'm happy to help with the Mailman side (on a time-available basis or as a paid consultant -- time available is probably a much better deal, though!) But I can't know what the system in use is, so maybe you should get them to write an outline of the system (what software, what requirements, what ID-related attributes are available). > then transition to SSO later. I don't think that will be a problem technically, as long as the user ids are the same for the same people. There will be UX issues though in the configuration I use. I think people will accept them quickly, but the UX will be different, which makes folks nervous if you don't warn them and explain why it's OK. > If you have any pointers as to > where to read up on SSO, SAML, Shibboleth and also on Django please > point me in the right direction. For django, search "site:djangoproject.com REMOTE_USER". For shibboleth, the relevant documentation is on the atlassian site. Here's the main documentation for the "service provider" component (this is the part that Postorius would be using indirectly): https://shibboleth.atlassian.net/wiki/spaces/SP3/overview search there for "REMOTE_USER" for the most relevant documentation. The SAML protocol is above our pay grade. :-) There's an introduction to the SAML architecture linked from the service provider documentation. That's way more than you need for this task, I think, so just skim it. Another guy did the Shibboleth config, so I'm a little fuzzy on this, but again I think that's mostly IT/NOC responsibility. (IIRC the main thing was getting the ID provider credentials and our host certs from the NOC, you can't generate those yourself!) The parts that hook into mailman are a list of translations of ID attributes to Apache variables, some email addresses for error reporting, and in Apache some translations of Apache variables to HTTP headers. But you need to make sure it's SAML. I'm no expert on this stuff, but it seems like there are a bunch of these protocols, like OpenID and OAuth2 out there. Django knows how to do those, too, but we need to know which one! Steve

1 year, 5 months

Re: Installing Mailman3 under a Python Virtual environment running on RHEL9

by Odhiambo Washington

On Tue, May 21, 2024 at 2:44 PM Andy Macheta <andy.macheta(a)gmail.com> wrote: > Hi, > So tried, without much success, to get Postorius working on my Mailman3 > server and every internet trick& tip I tried did not work so decided to > take a new approach as recommended at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > Used this reference: > https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-depe… > which I know is more for Debian/Ubuntu systems but I was hoping that 90%+ > would also work with Red Hat. > Fell at the first hurdle with no packages available called "python3-dev" > or "python3-venv" > The virtualenv method should work for all OSes, not just Debian/Ubuntu. I use it on FreeBSD too. I have never touched RHEL, but Google-foo tells me that you need to do: yum install -y python3-devel Alternatively, search for the package in yum , use the following command: yum search python3 | grep devel You could also search for the venv one by: yum search python3 | grep env Whatever else you'd need to install on the base OS, just use the above search method and install it. Feel free to post questions here if you aren't sure on what to install. The documentation - https://docs.mailman3.org/en/latest/install/virtualenv.html - requires you to install the following in the base OS: 1. python3-dev python3-venv sassc lynx 2. A database server - could be PostgreSQL or MySQL. You can search for them too :) 3. An MTA - could be Postfix or Exim. Your choice. 4. A webserver - could be Apache or Nginx The challenge you're likely to face is probably to do with how to start the MM3 core and MM3 web services, but you can figure that out, no? Alternatively, just dump RHEL and use any Debian-based OS :) Is there anyone that has managed to install a running version of Mailman3 > that has a working GUI whether it is on bare metal or Python virtual > environment and if so, could they kindly let me know how they did it?? > The closest I've come is a running command line version of Mailman3 which > is fine for me of course but not for anyone else as they like access via > web browser. > Let's see if you can get this running in the next 3hrs. Do you use WhatsApp? Let's chat on +254732000004 -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

6 months

Re: UnpicklingError on mailman lists command

by Mark Sapiro

On 8/3/21 7:35 AM, Bryan Loniewski wrote: > Okay, that helped identify possible culprits. Three of our lists are hitting/over the max BLOB length (65,535 bytes) for accept_these_nonmembers. I executed this SQL command for each of the BLOB cols you referenced and only accept_these_nonmembers is borked: > > MySQL [mailman]> SELECT list_name, OCTET_LENGTH(accept_these_nonmembers) as howManyBytes from mailinglist where OCTET_LENGTH(accept_these_nonmembers) > 64000; > +---------------+--------------+ > | list_name | howManyBytes | > +---------------+--------------+ > | <snip> | 65535 | > | <snip> | 65535 | > | <snip> | 65535 | > +---------------+--------------+ > 3 rows in set (0.01 sec) > > So, putting aside *why* these lists are so large wrt that column, can or should I alter the col type(s) to MEDIUMBLOB? If yes, would that remain on suite upgrades? If no, is there a better alternative? Or some recommendation in between? Modifying the column type at this point will not help because the data has already been truncated and the missing piece is gone. It may help avoid future issues, but I suspect it's not necessary. It would probably 'stick' on an upgrade as long as there were no new migration affecting those columns, but if there were such a migration, it could fail due to the existing type not being as expected. I suspect these lists were imported from Mailman 2.1 with the `mailman import21` command. The goal of that is to import the addresses as non-members with the appropriate action and put only the regexps in the MM 3 *_these_nonmembers. Prior to Mailman 3.3.2, import21 would add the entire 2.1 *_these_nonmembers and then delete the non-regexps. Possibly something went wrong in that process because of the truncation and left the new *_these_nonmembers in a broken state. Or possibly you just have a huge number of regexps in these list's accept_these_nonmembers. I suggest you use mysql to update this column's data for these three lists. to a value which unpickles as an empty list. This value is the python bytes b'\x80\x04\x5d\x94\x2e' (i.e. 5 bytes with hex values 80, 04, 5d, 94 and 2e). I'm not sure how that is stored in a MySQL BLOB, but I'm sure you can determine that. This will allow you to actually access those lists in Mailman. Also note that beginning with Postorius 1.3.3, the *_these_nonmembers settings are exposed on the List Settings -> Message Acceptance form. If you still have the original MM 2.1 config.pck files, you can examine them with Mailman 2.1's bin/dumpdb command to see what was in accept_these_nonmembers, and then see if the appropriate MM 3 nonmembers were created and if the remaining regexps are not too long, add them. If you need help with this, I will help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

Re: Installing mailman 3

by Abhilash Raj

Hi, On Tue, Aug 1, 2017, at 02:11 PM, Rafael Mora wrote: > It's ok now, but still I can't make it send the confirmation email > > This is from mailman.log: > > > [mailman@localhost logs]$ tail -f mailman.log > Aug 01 15:59:18 2017 (2327) lmtp runner started. > Aug 01 15:59:18 2017 (2333) virgin runner started. > Aug 01 15:59:18 2017 (2332) retry runner started. > Aug 01 15:59:18 2017 (2330) pipeline runner started. > Aug 01 15:59:18 2017 (2325) command runner started. > Aug 01 15:59:19 2017 (2328) nntp runner started. > Aug 01 15:59:19 2017 (2326) in runner started. > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET > /3.0/lists?count=0&page=1&advertised=true HTTP/1.1" 200 90 > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET > /3.0/lists?count=10&page=1&advertised=true HTTP/1.1" 200 90 > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/domains HTTP/1.1" 200 > 90 > > > > > What should I do? If you are talking about Account confirmation emails, they usually are sent out from Django and not Mailman Core itself. To configure Django you need to edit the `settings.py` file, wherever that is one your installation. If you are following the guide mentioned at http://docs.mailman3.org/en/latest/prodsetup.html, it should be at `mailman-suite/mailman-suite_project/settings.py`. To configure your Django to send emails, have a look at http://docs.mailman3.org/en/latest/config-web.html#setting-up-email-required. That documentation page has pretty much everything you need in order to have a running Web Frontend, please go through it and make sure you have everything configured. Finally, the actual emails from Mailing lists are supposed to be handled by Core. You need to configure Postorius & Mailman both to communicate. The settings are mentioned http://docs.mailman3.org/en/latest/config-core.html#configuring-mta here. Hope that helps! > > > > > > > El mar., 1 ago. 2017 a las 15:36, Mark Sapiro (<mark(a)msapiro.net>) > escribió: > > > On 8/1/17 1:14 PM, Rafael Mora wrote: > > > > > > Why does it say Address already in use? > > > > > > Because you are starting lm tp runner and it's already running. > > > > Do 'mailman stop'. Then ensure no Mailman processes are running. kill > > any if necessary. Then do 'mailman start'. > > > > -- > > 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 > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > -- > > Atentamente / Best Regards > > Ing. Rafael Mora > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj

7 years, 3 months

Re: Mailman3 without Hyperkitty in docker

by Abhilash Raj

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)

5 years, 8 months

Re: Hyperkitty on Debian 12

by Markus Grandpre

Dear Michael, thank you very much for your clarification. Best regards, Markus Am 3/26/24 um 17:38 schrieb Michael Oberrauch: > On Tue, 2024-03-26 at 08:06 +0100, Markus Grandpré wrote: >> Dear Mr Sapiro, >> >> thank you very much for your help. The required command is: >> >> # mailman-web hyperkitty_import \ >> -l mailman21-migration-test-04(a)mailman.uni-konstanz.de \ >> /var/mailman21/testlist.mbox >> >> Due to the following warnings, I still have to customize Hyperkitty: >> >> django_mailman3.MailDomain: (models.W042) Auto-created primary key >> used >> when not defining a primary key type, by default >> 'django.db.models.AutoField'. >> HINT: Configure the DEFAULT_AUTO_FIELD setting or the >> DjangoMailman3Config.default_auto_field attribute to point to a >> subclass >> of AutoField, e.g. 'django.db.models.BigAutoField'. >> ... >> >> Can you give me another hint? As Linux admin I installed the packages >> mailman and mailman-web that were offered to me under Debian 12. >> Although during the installation of the packages user "list" was >> created, I cannot use it: >> >> # su - list >> This account is currently not available >> >> As with Mailman 2.1, I will probably have to continue working with >> Mailman3 as root. Too bad that there is no documentation for Debian >> admins like me, who don't want to dive too deep into the python >> framework. Or have I overlooked something? >> >> Best regards, >> Markus >> >> > > Hi Markus, > > we are also running MM3 on Debian 12 from Package Repositories. > > First of all, you should not try to directly switch user (su) to the > lists user, it's generally intended to executes commands as that user, > if necessary; either using `runuser`, `sudo`, or `su -c`. > > However, the prepackaged scripts `mailman-wrapper` and `mailman-web` > already do this and therefore you ca run those as root without > permission problems. > > On Debian there are two relevant users for MM3: the list user runs > mailman core, whereas the www-data user runs Postorius and Hyperkitty. > So you have to make shure, that the www-data user can access the .mbox > files while importing. > > Hope that helps. > > Cheers, > Michael > > > > _______________________________________________ > 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… > > This message sent to markus.grandpre(a)uni-konstanz.de -- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342

8 months

Mailman-users search results for query "Postorius"