Search results for "2021" - Mailman-users

Re: Mailman, etc. upgrade woes and persistent bugs

by Abhilash Raj

On Wed, Feb 17, 2021, at 10:24 PM, Stephen J. Turnbull wrote: > Abhilash Raj writes: > > > So it seems like we have some sort of agreement that we need all the > > roles to be able to see all the 4 states. > > I think it's more like there's disagreement about which roles need to > see which states, but for each role and each state, somebody thinks > that role needs to see that state. I think there's agreement that > it's harmless to allow everybody to see all states. > > > Roles here are basically Admin( i.e. list owner/moderator/site > > admin) and Subscriber. > > In this discussion, yes. However, if we're going to take the > discussion seriously, we should be more general than just this case. > I think we need to consider five roles. Starting with Brian's list of > List Owner, Moderator, List Member, and adding Anonymous (so that a > pre-login connection has a named role) and Site Owner for completeness. Yep, those are all the roles that even we recognize in Postorius. We also have the concept of Domain Owner, though that isn't really implemented yet. So, from this list, List Owner and above all will use the "by_admin" state to disable if they need to and they are the only ones who can set that state. > > > There is no access control to transition "from" any state but each > > value of non-enabled states is sort of a role's way to disable the > > delivery. Not all states are settable by all roles. > > Off-list, Ruth Ivey-Cook informs me that in "who sets what" both "who" > and "what" need to be considered is what she had in mind. So I think > that's exactly right and there's agreement. Nice. > > > 1. A subscriber can only transition from any to "enabled" or "by_user" > > state but can see if delivery was disabled "by_admin" or "by_bounces" > > as separate state in the Options page. > > 2. An admin can transition to "enabled", "by_user" and "by_moderator". > > I assume you mean "by_admin" instead of "by_moderator"? Ok, I've made a mess of it in my responses, the Core actually calls this value "by_moderator" but I have used them interchangeably in my emails. Sorry about that. https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/interfaces/mem… > > > They should use "by_user" when acting on behalf of the user and other > > when there are any administrative reason to disable delivery, whatever > > that may be. I expect "by_admin" to be used sparingly, and I don't see > > any use cases for it. > > 3. Mailman itself will use the "by_bounces" to disable delivery due to > > bounces. > > > > Is that an accurate description? > > +1 for 1 -- 3 as written. Others' mileage may vary. Cool, thanks! > > Steve > > -- thanks, Abhilash Raj (maxking)

4 years, 4 months

Re: spanish localization

by Victoriano Giralt

On Thu, 2021-02-11 at 11:15 -0800, Mark Sapiro wrote: > For Mailman core you need to run > > ``` > cd mailman/messages/es/LC_MESSAGES > msgfmt -o mailman.mo mailman.po > > ``` > to compile the mailman.po file for gettext. Mark, I'd say the Mailman core message files taht get installed by pip are "a bit outdated" (source files dates point to a nightly build) ... proof here: [root@isoc-es messages]# pwd /usr/local/lib/python3.6/site-packages/mailman/messages [root@isoc-es messages]# ll */LC*/ ca/LC_MESSAGES/: total 164 -rw-r--r-- 1 root root 66479 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 95099 Oct 30 17:30 mailman.po de/LC_MESSAGES/: total 184 -rw-r--r-- 1 root root 81693 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 104049 Jan 17 20:41 mailman.po en/LC_MESSAGES/: total 172 -rw-r--r-- 1 root root 74350 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 97233 Oct 30 17:30 mailman.po eo/LC_MESSAGES/: total 60 -rw-r--r-- 1 root root 321 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 55254 Oct 30 17:30 mailman.po es/LC_MESSAGES/: total 184 -rw-r--r-- 1 root root 80741 Feb 12 09:18 mailman.mo -rw-r--r-- 1 root root 102963 Nov 7 01:50 mailman.po fr/LC_MESSAGES/: total 124 -rw-r--r-- 1 root root 42261 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 81452 Jan 17 20:41 mailman.po he/LC_MESSAGES/: total 180 -rw-r--r-- 1 root root 79940 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 101264 Jan 17 19:20 mailman.po hu/LC_MESSAGES/: total 72 -rw-r--r-- 1 root root 9500 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 59290 Feb 3 02:44 mailman.po it/LC_MESSAGES/: total 180 -rw-r--r-- 1 root root 78543 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 100864 Jan 17 20:41 mailman.po ja/LC_MESSAGES/: total 60 -rw-r--r-- 1 root root 1296 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 55755 Oct 30 17:30 mailman.po ko/LC_MESSAGES/: total 164 -rw-r--r-- 1 root root 66668 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 94598 Oct 30 17:30 mailman.po nb_NO/LC_MESSAGES/: total 68 -rw-r--r-- 1 root root 6263 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 57744 Jan 17 19:20 mailman.po pl/LC_MESSAGES/: total 60 -rw-r--r-- 1 root root 1933 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 56068 Oct 30 17:30 mailman.po pt/LC_MESSAGES/: total 60 -rw-r--r-- 1 root root 1734 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 55963 Oct 30 17:30 mailman.po ru/LC_MESSAGES/: total 80 -rw-r--r-- 1 root root 12651 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 62127 Oct 30 17:30 mailman.po sq/LC_MESSAGES/: total 60 -rw-r--r-- 1 root root 321 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 55227 Oct 30 17:30 mailman.po tr/LC_MESSAGES/: total 168 -rw-r--r-- 1 root root 73537 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 96452 Jan 17 20:41 mailman.po zh_Hans/LC_MESSAGES/: total 64 -rw-r--r-- 1 root root 4945 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 57269 Jan 17 19:20 mailman.po -- 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

Re: OS upgrade - anything to take care of?

by Ruth Ivimey-Cook

On 13/05/2021 20:06, Mark Sapiro wrote: > On 5/13/21 11:28 AM, Ruth Ivimey-Cook wrote: > Yes, I overlooked some aspects of virtualenv. Actually, the Python in > the virtualenv is mostly symlinks to the Python it was built with, so > whether it continues to work after a Python upgrade depends on what the > symlinks are and how the Python upgrade installs. Correct. > >> I would therefore appreciate some guidance on performing the upgrade >> from 3.6 to 3.8 with the minimum of fuss. >> >> [I am not sure, but it could be possible to install python3.8 while >> using Ubuntu 18, so that the dist upgrade never breaks anything. Worth >> exploring.] > I haven't tested any of this, but I suspect if Python is for example, > /usr/bin/python3.6 and /usr/lib/python3.6 the upgrade removes those and > installs /usr/bin/python3.8 and /usr/lib/python3.8, that you could just > create symlinks from /usr/bin/python3.6 and /usr/lib/python3.6 to > /usr/bin/python3.8 and /usr/lib/python3.8 respectively and it would work. It would be nice if that worked, and I tried it, but it doesn't work because the python system and site directories under ./lib are also versioned (eg ./lib/python3.6/site-packages), so you would have to additionally create symlinks for those and/or rebuild those. > On the other hand, if the symlinks in the venv are to things like > /usr/bin/python3 and /usr/lib/python3 which used to point to 3.6 > versions and after upgrade point to 3.8 versions, it should just work. Sadly they aren't - they link to python3.6 or whatever... and even if not, the /lib/ naming gets you as well. And even if that can be worked around (eg by renaming the mailman /lib/python3.6 folder to /lib/python3.8), the python .pyc files are /also/ versioned, so you then have to find & delete them all to force the new interpreter to rebuild them or python falls down in a heap. > As far as installing Python3.8 on Ubuntu 18.04 goes, the machine I'm > typing this on is Ubuntu 18.04 and has 6 different Python3 versions > > mark@msapiro:~$ /usr/bin/python3.5 --version > Python 3.5.2 > mark@msapiro:~$ /usr/bin/python3.6 --version > Python 3.6.9 > mark@msapiro:~$ /usr/local/bin/python3.6 --version > Python 3.6.12 > mark@msapiro:~$ /usr/local/bin/python3.7 --version > Python 3.7.9 > mark@msapiro:~$ /usr/local/bin/python3.8 --version > Python 3.8.7 > mark@msapiro:~$ /usr/local/bin/python3.9 --version > Python 3.9.1 > > and /usr/bin/python3 is a symlink to /usr/bin/python3.6 and > /usr/local/bin/python3 is a symlink to /usr/local/bin/python3.9, so take > your pick... Indeed... and it would be lovely if it was that simple, but my experience was that even if you got a good python executable running, the other versioned elements of a python install caused it to mess up. What worked for me in the end was a combination of forcing a complete rebuild/reinstall with the mailman3 python3.8 install, followed by a bit of rejigging of file permissions and settings (probably because I'd messed something up, but maybe not). Regards Ruth -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

4 years, 1 month

Re: Mailman3 Issue with Sending Mail to Yahoo/AOL

by Jeff

I also run a neighborhood email list and ran into the same problem in the past. AOL and Yahoo are owned by Verizon and you are probably having the same issue with Verizon (though Verizon might not be popular in your neighborhood and therefore you don’t see it). At any rate, in my experience Verizon was the root of the problem. I solved this problem by diligently making sure SPF and DKIM were correctly set up. Once I had those set up correctly, the problems disappeared. > On May 12, 2021, at 10:47 AM, chris--- via Mailman-users <mailman-users(a)mailman3.org> wrote: > > Hi everyone. I have a dedicated Ubuntu box that is running mailman3. I have a single email list on it. The subscriber base is about 350 users. There is a good chunk of these users that are aol.com or yahoo.com users. I've been getting complaints from the Yahoo people that mail is delayed at times, or messages that come out of order. > > Looking at the mailq on the box, I can see there are plenty of emails stuck in the queue. I have all sorts of messages like this ... > > > -Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient------- > 3576C540CB4 9917 Tue May 11 11:27:13 pcho-bounces(a)pchochat.com > (host mta6.am0.yahoodns.net[67.195.204.74] said: 452 Too many recipients tnmpmscs (in reply to RCPT TO command)) > <removed list of email addresses> > > (host mta6.am0.yahoodns.net[67.195.204.74] said: 421 [IPTS04] Messages from 74.112.73.65 temporarily deferred due to unexpected volume or user complaints - 4.16.55.1; see https://postmaster.verizonmedia.com/error-codes (in reply to end of DATA command)) > <removed list of email addresses> > > > 10932540D16 32765 Tue May 11 18:34:13 pcho-bounces(a)pchochat.com > (host mta6.am0.yahoodns.net[67.195.228.111] said: 421 4.7.0 [TSS04] Messages from 74.112.73.65 temporarily deferred due to unexpected volume or user complaints - 4.16.55.1; see https://postmaster.verizonmedia.com/error-codes (in reply to MAIL FROM command)) > <removed list of email addresses> > > (host mx-biz.mail.am0.yahoodns.net[67.195.204.83] said: 421 4.7.0 [TSS04] Messages from 74.112.73.65 temporarily deferred due to unexpected volume or user complaints - 4.16.55.1; see https://postmaster.verizonmedia.com/error-codes (in reply to MAIL FROM command)) > <removed list of email addresses> > > (host mx-aol.mail.gm0.yahoodns.net[67.195.228.84] said: 421 4.7.0 [TSS04] Messages from 74.112.73.65 temporarily deferred due to unexpected volume or user complaints - 4.16.55.1; see https://postmaster.verizonmedia.com/error-codes (in reply to MAIL FROM command)) > > (host mta6.am0.yahoodns.net[67.195.228.111] said: 421 4.7.0 [TSS04] Messages from 74.112.73.65 temporarily deferred due to unexpected volume or user complaints - 4.16.55.1; see https://postmaster.verizonmedia.com/error-codes (in reply to MAIL FROM command)) > <removed list of email addresses> > > > So it seems that Yahoo/AOL keeps detecting my mailman3 server as either spam, sending too much email, or too many recipients. > > > This email server is for our neighborhood community. Its moderated to join, and we know every single user on this list. We know it's not being reported as spam by our users. > > Anyone anyone shed some light on how to appropriately solve this issue? > _______________________________________________ > 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/

4 years, 1 month

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

by Simon Coggins

On 4 Nov 2021, at 11:57 pm, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: On 11/4/21 1:02 AM, Simon Coggins wrote: > > All I’m doing is literally appending a subset of a hash of the mailing list rcpt address to the front of the message-id, so that if it gets moderated, each instance of the email has a different message-id and each moderation action has it’s own copy of the email to operate on. This seems to have gotten us out of the immediate issues. But I’m eager to find a better solution that might be more permanent. As you have seen, this is new in 3.3.5. I recognize this is a problem. Previously, attempts to accept the message on the second and subsequent lists would throw an uncaught exception - see https://gitlab.com/mailman/mailman/-/issues/914<https://gitlab.com/mailman/mailman/-/issues/914> and this was a fix for that. Yeah I’m seriously amazed we’ve not had complaints in the year we’ve been running mailman3 that people have lost emails to multiple lists. Only now that you fixed the exception have people seen missing emails :) Please file an issue for this at https://gitlab.com/mailman/mailman/-/issues<https://gitlab.com/mailman/mailman/-/issues> and I will try to find a better solution. Your approach of munging Message-IDs will create other issues. Consider a post to a list with direct CC to userx. userx replies-all to the message received directly. the In-Reply-To of this reply is the unmunged Message-ID which will affect threading in the archives and other recipient's MUAs. I realize this is preferable to losing the message, but I hope we can do better. Yeah it’s not a great solution but it’s the quickest I could come up with that works “for us”. 99% of our lists are announcement lists only with minimal replies so while this will break some. I’m hoping it will give us enough time to wait out a proper fix. I’ve created a new issue #955 with as much detail as I think you’ll need. Let me know if you need any more. -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@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<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org> --- [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 ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: attachment.png Content-Type: image/png Name: attachment.png Replaced multipart/alternative part with first alternative.

3 years, 8 months

Re: Easiest way to install a new mailman3 deployment?

by Ruth Ivimey-Cook

On 03/01/2021 15:47, Stephen J. Turnbull wrote: > ieso(a)johnwillson.com writes: > > > Here's an interesting suggestion I received that I'm going to kick > > around a bit.. has anyone tried using Ansible to assist the > > installation process? > > > > https://github.com/rivimey/ansible-mailman3 > > rivimey is very competent. That would undoubtedly be a good place to > start. However, her setup may be more complicated than most folks > need (IIRC, she has a multi-homed setup with Mailman core, Postorius, > and HyperKitty on three separate IPs on a separate subnet in the DMZ, > while Mailman was really designed for three Mailman applications > running on the same host, along with the database server and MTA). Thank you for your compliment. I have only split mailman in two: mailman-core with the email-related parts, and postorius for the UI. As yet, although Hyperkitty "works", I haven't addressed the fact that mails get archived in folders on the email host and so (for me) hyperkitty can't see them. Ideally, they would be on the postorius/hyperkitty host, or possibly network shared The Ansible role linked to above includes a lot of options but doesn't impose splitting the components as I've said: it merely enables it. If anyone wants to further refine the ansible role I am happy to consider updates, especially sorting the archive! In an earlier post on this thread (that I now see was only sent to ieso@ -- sorry!) I linked to the role I used as a starting point for my work, which does indeed do most of the "simple out-of-the-box" implementation of mailman. > the "ansible-mailman3" role by "natefoo": Mailman 3 installation, > configuration, and management for Linux > > There are other ansible roles which will install mysql etc as needed. > If I didn't need to split the host for mailman3-core from > mailman3-web, I think it would have worked out of the box. > > I hadn't heard of Ansible before, but it looks perfect for this > > kind of situation. > > I'm not sure we want to maintain an Ansible configuration, but I > imagine we could stick it in contrib as "an example that works for > somebody YMMV unsupported NO WARRANTY". :-) Ansible is very good at describing deployments and I would definitely suggest investigating it if you are doing that sort of thing. One of the nice parts of Ansible is that you do not have to describe whole hosts - it will happily manage a small part without compromise. Another really nice part is that it requires very little of the host. If Ansible is not to your liking, you may find "Salt" and "Saltstack" an improvement, though for me it was not as good. Ansible has a role archive in the form of the Ansible Galaxy website; I would suggest simply that Mailman docs mention the role's existence. As an Ansible user, that is where I would look first, so the main point of mentioning it in mailman docs is to let people who don't use Ansible know about it. Regards, Ruth -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

4 years, 6 months

Re: only show mail domains from web host on web-host-url

by Jens Günther

Thank you for the clarification! Am 19.03.21 um 18:48 schrieb Abhilash Raj: > > >> On Mar 19, 2021, at 6:38 AM, Jens Günther <jens.guenther(a)posteo.de> wrote: >> >> Thank you for your answer. I should have seen that in the Docs, but somehow missed it: https://docs.mailman3.org/en/new/prodsetup.html > > You seem to have landed on a very old version of the docs that I didn’t unfortunately knew > was even available. I have disabled that page now. > > The settings are documented in https://docs.mailman3.org/en/latest/config-web.html > >> >> I set it in the corresponding file, but unfortunately it doesn't work :-( I tried other setting to prove, that the file is used (ALLOWED_HOSTS works, changed here from '*' to 'localhost' and my example-domains, this works). It seems to be the same as this user describes (a while ago): https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… >> >> How could I check, that the setting is used!? >> >> But maybe some additional information: >> - I use the Debian installation on a stable buster, so mailman is version 3.2.1 >> - I use apache2 as my web-server and use the given alias-conf-file >> - Python is version 3.7.3 >> - Postorius is Version 1.2.4 >> - HyperKitty is version 1.2.2 >> >> -> In Django admin-Panel (/mailman3/admin/) I added 2 Websites test1.xyz.de and test2.xyz.de >> -> In Postorius (/mailman3/postorius/domains/) I added 2 Domains as Mail Hosts test1.xyz.de and test2.xyz.de with the corresponding Web hosts as stated above >> -> I added 1 list (/mailman3/postorius/lists/) for each Mail Domain as follows: test1(a)test1.xyz.de and test2(a)test2.xyz.de >> -> then created a vhost in apache2 with SSL-cert and added the Domains in ALLOWED_HOSTS: test1.xyz.de and test2.xyz.de >> -> When I go to the 2 Testdomains (corresponding web hosts), I see on each both lists for the different Mail domains >> >> What do I miss? Or where to investigate? >> >> Thank you in advance, best regards. >> >> By the way: what'S the difference in the 2 docs? https://docs.mailman3.org/en/latest/index.html and https://mailman.readthedocs.io/en/latest/README.html > > Mailman Suite consists of several individual projects including Mailman Core, Postorius (Web UI) and > Hyperkitty (Archiver). The first URL is the landing page for the entire suite and should direct you to > individual projects. The second one is the individual Mailman Core project. Historically, Core was the > only project and hence claims the name “mailman” in most places. > >> >> Am 18.03.21 um 21:52 schrieb Mark Sapiro: >>> On 3/18/21 9:20 AM, jens.guenther(a)posteo.de wrote: >>>> Is it possible, to only show publicly (if advertised) these lists on a certain url, that are corresponding to the web host the url I accessed mailman through? >>> Set FILTER_VHOST = True in your settings_local.py or where ever you put >>> your site Django settings. >> _______________________________________________ >> 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/ >

4 years, 3 months

Re: Best guide for installing from pypi

by Abhilash Raj

Hi, On Tue, Feb 23, 2021, at 10:00 AM, duane(a)fairsay.com wrote: > Hi. > > I've got a partial mailman3 install done and, based on the > documentation, am not sure how to complete it! (this is my first time) > > I've installed mailman3 (3.3.3) on a Debian 10 server using python3.7, > mysql, postfix, apache, etc. and have run the install using pip3 > install mailman. The "mailman info" command works, version shows > "3.3.3 (Tom Sawyer)" the databases creates, tables, all exist, etc. So > it seems the necessary services are running. I'm running froxlor on the > server to configure the non-mailman services (apache, ssl, postfix, > etc). I had also tried apt install mailman-full but it was an older > version, so using the pypi route ensured I was on the latest version. I don't know anything about Froxlor, so I won't be able to help with any issues caused due to that unfortunately. > > Looking at https://docs.mailman3.org/en/latest/install/virtualenv.html, > what I can't figure out is: > 1) There is no /opt/mailman/ user - the user installed seems to be > "list" The user recommended to create is "mailman" with "/opt/mailman" as the home directory for the user. Debian systems use the "list" user to run Mailman. You can simply substitute the user from mailman to list, the name itself doesn't make a lot of different, just make sure you do change the name in systemd config files and sudo commands that you use. > 2) Is a virtual environment needed for a production environment? It is recommended by Linux distros that you don't install from pip directly into the system's site-packages. This can *potentially* have side effects and break other systems that rely on Python packages installed on your system, some which you might not even be aware of that relies on Python (like, Yum package manager does in RHEL systems). Hence, if you aren't use the system packages to install Mailman, it is recommended that you use an isolated Python virtualenv. > 3) if django is setup properly or the webservice is working > 4) I've tried to connect to some web interface > (posterious/hyperkitty/some mailman3 web frontend) via lynx to > localhost:8001 on the local machine - but it has a 404 error 8001 is Mailman Core's API endpoint. To test Web Frontend, you want to reach out to: https://<mydomain>/ after configuring your Nginx to reverse-proxy the uwsgi. Uwsgi runs a custom protocol, also called uwsgi, which Nginx understands and is able to reverse proxy. You can't use Lynx to test that. However, if you do want to test your service locally, you can add this line the uwsgi.init[1] after the "uwsgi-socket" line: http-socket = 0.0.0.0:8080 This will make uwsgi also accept HTTP connections on Port 8080 that you can use to test. [1]: https://docs.mailman3.org/en/latest/install/virtualenv.html#setting-up-a-ws… > > Anyone got any tips as to next steps? > (I'm also happy to pay someone to coach me through it!) > > Cheers, > > Duane > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

4 years, 4 months

Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by gordon＠dickens.com

David Newman wrote: > One general comment: Debian packages install files with a different > owner than the pip install. You want to be sure all your directories and > files are owned by the Mailman user ('mailman' on Debian). Yes, I have checked the ownerships. The debian package installed everything in mailman3 as user "list" whereas I have now setup everything to run as user "mailman". As I previously mentioned, mailman3 (core) is running fine. In fact mailman3 has properly posted numerous messages to several of my mailing lists since I finished setting it up with pip. However, mailman3-web (or mailman-web) is not working, I think because of a permissions issue. The installation instructions specify that mailman3-web (or mailman-web) run as user=mailman and group=mailman. However, the debian installation specifies the data files as user=www-data and group=www-data which is what apache runs as. For instance, I have my static files stored in the /var/lib/mailman3/web/static directory and the previous Debian mailman3 version set all the ownerships and groups to www-data for /var/lib/mailman3/web, /var/lib/mailman3/web/static along with all of the directories and files in the static subdirectory. So, when I run "mailman-web collectstatic" it bombs on the following permissions error: PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/web/static/hyperkitty/js/hyperkitty-common.js' So, my question is as follows. Should I continue to run mailman3-web as user mailman and change the ownership of the /var/lib/mailman3/web directory to mailman or should I leave the permissions of the /var/lib/mailman3/web directory alone and have mailman3-web run as user and group www-data? > Do you have anything further in any of the logs in /opt/mailman/web/logs ? Yes, everytime that I try to start mailman3-web it posts this to the log and which includes a permission error as the last line: *** Starting uWSGI 2.0.20 (64bit) on [Wed Jan 26 17:00:13 2022] *** compiled with version: 10.2.1 20210110 on 24 January 2022 19:51:51 os: Linux-5.10.0-10-amd64 #1 SMP Debian 5.10.84-1 (2021-12-08) nodename: slc.mailhub4u.com machine: x86_64 clock source: unix pcre jit disabled detected number of CPU cores: 8 current working directory: / detected binary path: /opt/mailman/venv/bin/uwsgi chdir() to /usr/share/mailman3-web your processes number limit is 31530 your memory page size is 4096 bytes detected max file descriptor number: 1024 lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) bind(): Permission denied [core/socket.c line 230] > This one might be due to a bug I hit as well. There's a problem with > mistune, one of the components. If that's the issue here, this should > address it, run as the mailman user: > pip install mistune==2.0.0rc1 > mailman-web migrate > mailman-web compress > mailman-web collectstatic > mailman-web compilemessages Thanks for that tip David! Reverting mistune back to version 2.0.0rc1 allowed "mailman-web migrate" to work. I think that the balance of my problems are permissions related to running mailman3-web (or mailman-web) as user mailman versus www-data. So, please let me know, based on your installation, if I should change the permissions for /var/lib/mailman3/web/ to user/group mailman or should I run mailman3-web as user/group www-data. Also, any other advice from David or anyone else would be very much appreciated. Thanks! Gordon

3 years, 5 months

[SOLVED] Re: Re: multiple sites on a mailman3 server question

by William Oliver

On Wed, 2021-12-29 at 09:21 -0800, Mark Sapiro wrote: > On 12/29/21 8:48 AM, William Oliver wrote: > > > > [snip] > If you are following > https://docs.mailman3.org/en/latest/install/virtualenv.html you have > ``` > location / { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > > } > ``` > in your nginx config and everything goes to uwsgi. What you want is to > put those proxy directives in only the mailman locations as at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > and then configure your document root so other locations are served > from > there. > The problem was more stupid than one might imagine. My browser was caching so no matter what changes I made, it loaded domain/mailman/lists because that was what was cached. When I tinkered with things, I only changed whether or not mailman was loaded after that. I changed machines and used a different browser, and it started working fine. And it worked fine on my regular box once I cleared my browser's cache. It turns out that nginx works like it's supposed to work. Go figure. So, just to make things clear. Here was my goal: www.domain.com <-- go to welcome page lists.domain.com <-- go to mailman later, I'll install roundcube for mail.domain.com This gives me two primary entries in nginx. I'll send www.domain.com to /var/www/html2 and lists.domain.com to /var/www/html (though mailmanweb will kick in before that). Here's the /etc/nginx/sites-enabled file that works. The entry for location/ for the mailman section is different from the one you pointed to, but it is cut and pasted from one of the examples on that site. I can't find it right now, though -- but it works fine, and life is short. Anyway, this works if you clear your browser's cache: **************************************************** ##### paths for www.exampledomain.com ##### #### just goes to /var/www/html2 ##### server { root /var/www/html2; index index.html index.htm index.nginx-debian.html; server_name exampledomain.com, mail.exampledomain.com, www.exampledomain.com; location /{ # try_files $uri $uri/ =404; } ##### added 12/19 listen 443 ssl default_server; listen [::]:443 ssl default_server; ########## ssl_certificate /etc/letsencrypt/live/exampledomain.com/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/exampledomain.com/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot } ##### this for lists.exampledomain, that turns on mailman server { root /var/www/html; index index.html index.htm index.nginx-debian.html; server_name lists.exampledomain.com; location /{ proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; #proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-Proto $scheme; proxy_redirect off; } location /static/ { alias /opt/mailman/web/static/; } ##### added 12/19 listen 443 ssl ; listen [::]:443 ssl ; ########## ssl_certificate /etc/letsencrypt/live/exampledomain.com/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/exampledomain.com/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot } ###### Certbot stuff to force things to 443 server { if ($host = mail.exampledomain.com) { return 301 https://$host$request_uri; } # managed by Certbot if ($host = www.exampledomain.com) { return 301 https://$host$request_uri; } # managed by Certbot if ($host = lists.exampledomain.com) { return 301 https://$host$request_uri; } # managed by Certbot listen 80 ; listen [::]:80 ; server_name www.exampledomain.com lists.exampledomain.com mail.exampledomain.com exampledomain.com; return 404; # managed by Certbot } ********************************************************

3 years, 6 months

Mailman-users search results for query "2021"