Search results for "2021" - Mailman-users

Re: Bug in 2.1.36?

by Joel Lord

Well, I found a workaround that may have completely obviated this. I found instructions for individually handling outstanding moderator requests from the command line using withlist, and went through and flushed the 7 spammy requests that were in there. (I'd forgotten to include that this traceback was triggered from a single list's admindb URL.) With request.pck down to 20 bytes, we're back to normal. I'm going to presume that there were requests in there that were somehow corrupted by the upgrade process? On 11/12/2021 4:06 PM, Joel Lord wrote: > I'm not sure if this is a bug or something about the new CSRF fix > doesn't get along with something I have (mis)configured, but this > definitely seems to be related. Sadly the script I use to backup > mailman before upgrading I recently stopped backing up the lists > themselves, so going back to 2.1.35 doesn't seem to be an option due to > the .pck file version bump. Here's the trace I get: > > Traceback (most recent call last): > File "/mailman/mailman-${domainslug}/scripts/driver", line 117, in > run_main > main() > File "/mailman/mailman-${domainslug}/Mailman/Cgi/admindb.py", line > 342, in main > print doc.Format() > File "/mailman/mailman-${domainslug}/Mailman/htmlformat.py", line > 352, in Format > output.append(Container.Format(self, indent)) > File "/mailman/mailman-${domainslug}/Mailman/htmlformat.py", line > 267, in Format > output.append(HTMLFormatObject(item, indent)) > File "/mailman/mailman-${domainslug}/Mailman/htmlformat.py", line 53, > in HTMLFormatObject > return item.Format(indent) > File "/mailman/mailman-${domainslug}/Mailman/htmlformat.py", line > 445, in Format > % csrf_token(self.mlist, self.contexts, self.user) > File "/mailman/mailman-${domainslug}/Mailman/CSRFcheck.py", line 53, > in csrf_token > mac = sha_new(secret + `issued`).hexdigest() > TypeError: unsupported operand type(s) for +: 'NoneType' and 'str' > > Running Python 2.7.5 > . -- Joel Lord

3 years, 7 months

Re: Unable to get mailman3 working on Ubuntu 20.04 LTS

by Shawn Heisey

On 10/28/2021 5:28 PM, Abhilash Raj wrote: > The instructions are basically in the issue description, pending move to a documentation page: > > https://github.com/maxking/docker-mailman/issues/293 > > If you are upgrading the latest 0.4.x release from 0.3.x, you also want to look at > > https://asynchronous.in/docker-mailman/news/#upgrading-to-040-release Awesome! Thank you for that info! I just upgraded from 0.4.1 (which was the tag I used for the initial install) to 0.4.2 and it all looks good. The lists are still there in the output of this command on the host: docker exec -u mailman mailman-core mailman lists After the upgrade, I sent a test message to one of the mailing lists that looks like it worked perfectly. I assumed that it would be necessary to update the tags in the docker-compose.yaml file, and I did so. Should that be added to the instructions? One thing that was very non-obvious is how to get the containers to start at boot time. A command like this, issued three times with the actual ID values for the containers, took care of it for me: docker update --restart=unless-stopped 0576df221c0b If it is possible to have the docker-compose.yaml file set that flag when it creates the containers, I think that would be a good idea. I did notice that the postorius and mysql docker-compose configs do set the database container (but not the mailman containers) to restart always ... but my limited experience with docker tells me that unless-stopped is a better option. > If you can send a PR for the config you set up for Apache in Github, or just an issue, I can include it in the docs :-) I created an issue and included a sanitized copy of my virtualhost config. Thanks, Shawn

3 years, 8 months

Re: Hyperkitty messages stuck in spool

by Mark Dadgar

On Nov 19, 2021, at 5:47 AM, Andrew Hodgson <andrew(a)hodgson.io> wrote: > Stephen J. Turnbull wrote: > >> Mark Sapiro writes: >>> On 11/18/21 6:38 AM, Andrew Hodgson wrote: >>>> >>>> Ok thanks for this. Its happening because the Gunicorn process > > running the Django server is being killed due to OOM > > conditions. Is there any settings I can change to > > troubleshoot/throttle this in Gunicorn or Django? >>> >>> I don't think there's anything that can be done in gunicorn or django > about this. This is an OS issue. You need to give the server more memory > or allocate a (bigger) swap file. >> >> If those things are difficult, depending on OS and the hardware, it may also be possible to tell the OS that gunicorn is an import process that should not be killed. But in the long run, the server needs more memory. > > Thanks for this it was due to changing cloud providers. My old provider I installed Debian from an ISO file which created the swap partition but on the new provider I used their cloud image with no swap. Swap now created and everything is back to normal. Its running on an instance with 2GB of RAM and based on how I am seeing the usage running I would see this as an absolute minimum for a standard Mailman 3 stack. I had this same experience on Digital Ocean. The short-term fix was enabling swap and the long-term fix was upping my service level to something with more memory. Without swap, I don’t think 2GB is realistically sufficient to run a full mm3 instance. The cloud providers really don’t like you to run swap because it hammers their SSDs. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

3 years, 7 months

Re: Not able to start mailman server

by Mark Sapiro

On 8/5/21 12:53 AM, Kartheek Reddy Bondugula wrote: > Hi, > > I am trying to setup postorius using this website - > > https://docs.mailman3.org/projects/mailman/en/release-3.0/src/mailman/docs/W... That documentation is out of date. Start at https://docs.mailman3.org/en/latest/ > I am trying to create a mailling list and it web interface for the users in my group > > The command 'pip install -e ./'(python3) runs successfully but still i am not able to start the server Is the result the same as in your post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…, i.e., /usr/local/Cellar/python(a)3.9/3.9.5/bin/python3.9: can't open file '/usr/local/opt/python(a)3.9/bin/master': [Errno 2] No such file or directory > my mailman info shows - > > GNU Mailman 3.3.5b1 (Tom Sawyer) > Python 3.9.5 (default, May 4 2021, 03:36:27) > [Clang 12.0.0 (clang-1200.0.32.29)] > config file: /Users/.../Documents/mailman/var/etc/mailman.cfg > db url: sqlite:////Users/.../Documents/mailman/var/data/mailman.db > devmode: DISABLED > REST root url: http://localhost:8001/3.1/ > REST credentials: restadmin:restpass We recommend following this guide https://docs.mailman3.org/en/latest/install/virtualenv.html What is the content of the /Users/.../Documents/mailman/var/etc/mailman.cfg file? The 'pip install -e ./' command should have created a bin/ directory containing both `mailman` and `master` executable files and this `mailman` command is the one you should be running. It appears the `mailman` command you are running is '/usr/local/opt/python(a)3.9/bin/mailman'. If that is in fact a symlink to a different bin/mailman file, there should also be a symlink from '/usr/local/opt/python(a)3.9/bin/master' to the existing bin/master or you should adjust your path. What do `which -a mailman` and `which -a master` show? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

Re: So near, and yet so far (Configuring Mailman)

by Joel Lord

On 1/29/2021 12:01 PM, Jack Lenox via Mailman-users wrote: > Hello all, > > I've spent more time than I care to admit trying to configure Mailman. And I almost have it all working now, but I just can't seem to get my Mailman/Postfix combo to receive emails. > > When I try to send emails to lists I'm rebuffed with undelivered notices with: > > <testlist(a)lists.fiftyshadesof.green>: Host or domain name not found. Name service error for name=lists type=AAAA: Host not found > and: > <testlist(a)lists.fiftyshadesof.green>: Host or domain name not found. Name service error for name=lists.fiftyshadesof.green type=MX: Host not found, try again > > This to me appears to be an issue with my DNS settings, but I can't work this out either. I have an A record for lists.fiftyshadesof.green pointing at my server, and an MX record pointing at that: > > lists.fiftyshadesof.green. 0 IN MX 0 lists.fiftyshadesof.green. > lists.fiftyshadesof.green. 0 IN A 193.37.35.191 > > I have driven myself mad with this and would very much appreciate any advice anyone can offer. The key here isn't in your mailman config, or even your postfix config (you might be able to fix it there, I'm not sure). The key is in the error: <testlist(a)lists.fiftyshadesof.green>: Host or domain name not found. Name service error for name=lists type=AAAA: Host not found Specifically, type=AAAA. It's looking for an IPv6 host record and you don't have one. I'm going to guess you got that bounce not from your lists host, rather from your mail relay? Somewhere along the way something is trying to use IPv6 and needs to get kicked to either not do that or at least fall back to IPv4. -- Joel Lord

4 years, 5 months

Re: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Lars Schimmer

On 27/02/2021 04:02, Stephen J. Turnbull wrote: > Lars Schimmer writes: > > > Hm, it completely ignores the standard way for Debian: > > apt-get install mailman3-full > > also exim4 as standard mailer. > > And apache2. > > Right. The idea is that Debian is a *component* of *Brian's* system, > not that Brian is installing a Debian system. One problem is that a > lot of people like to run Debian Stable, which lags our releases by > many months, sometimes a couple of years. A lot of people run a > Debian Stable system plus a couple of mission-critical apps from > source or from upstream repositories. Maybe the debian packages are old because people do not care about and use always upstream because debian packages are old? I do know lots of software projects with recent debian packages for stable, testing and unstable. Esp. in the wide use of debian based systems all over the internet. One reason to run those system is the easyness in install and the stable function of its component. Not to need to install all software from upstream because no one cares about a recent package. > It's not necessary to "keep up" to be very helpful to our users, of > course. But I think Brian's document is likely to be the "gold > standard" for a while. I understand why Abhilash wants it in the > official docs. :-) If it should be a gold standard, it should mention the default setup of a standard debian system (which is exim4, btw) and not assuming a special setup debian system. > Steve > MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

4 years, 4 months

Re: [Django] ERROR (EXTERNAL IP): Service Unavailable

by Mark Sapiro

On 2/25/21 9:38 AM, dancab(a)caltech.edu wrote: > Mark, > > Is it only this list that has an issue? > > Yes, this is the only list that is having the issue. > > Can you visit other pages for this list? > > Yes, I'm able to view the members list, list settings, templates, etc. > > I've restarted the service and tried to access the held messages for the list once again. Here's what is in the mailman log. > > > ERROR 2021-02-25 17:28:14,197 393 postorius Mailman REST API not available > Traceback (most recent call last): > File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 706, in urlopen > chunked=chunked, > File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 445, in _make_request > six.raise_from(e, None) > File "<string>", line 3, in raise_from > File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 440, in _make_request > httplib_response = conn.getresponse() > File "/usr/lib64/python3.6/http/client.py", line 1346, in getresponse > response.begin() > File "/usr/lib64/python3.6/http/client.py", line 307, in begin > version, status, reason = self._read_status() > File "/usr/lib64/python3.6/http/client.py", line 276, in _read_status > raise RemoteDisconnected("Remote end closed connection without" > http.client.RemoteDisconnected: Remote end closed connection without response This is from Django's log. What's in Mailman core's mailman.log? Since everything else is accessing the REST API with no problem, I think core must be stuck on something and timing out. Is there a time delay between trying to get the held messages view and the "Mailman REST API not available. Please start Mailman core." response? Also is there a non-zero count in the badge on the Held messages tab? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

Re: spanish localization

by Victoriano Giralt

On Fri, 2021-02-12 at 19:53 +0900, Stephen J. Turnbull wrote: > Victoriano Giralt writes: > > > 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: > > I don't understand what you think this proves. We can't do the > translations ourselves; we don't have the lingistic skills. So the > dates on the .po files are going to reflect translator activity as > well as core dev activity. Am I missing something that we can do > something about? Thanks Stephen for reminding me that sometimes I write what looks like proper English on the surface, but the meaning of it comes from the deep corners of my mind in some long forgotten dialect :-) I just wanted to make visible that the .mo files were a "bit old". For example, Guillermo, in this thread, pointed that the Spanish translation was quite compelte. Actualy, I spent some hours bringing them to 100% around Christmas. But, the .mo file for es from the pip install --update i did recently is dated November 7th. I have definitely added a lot of translated material from then until the end of the year. I know the translation happens outside the development community. I tried to point that there might be some synchronisation problem, so to say, between the translation site and the packaging of the latest mailman release. I hope this time I've managed to express myself better ;-) I swear my brain was thinking in English as a wrote :-) :-) -- 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: Unknown templates being used

by Tom Stoddard

On 2/14/2021 1:31 PM, Mark Sapiro wrote: > That message is not built from a template. It comas from the `mailman > notify` command which currently says > ```> def _send_notice(mlist, count, detail): >> """Creates and sends the notice to the list administrators.""" >> subject = _('The {} list has {} moderation requests waiting.').format( >> mlist.fqdn_listname, count) >> # XXX This should be a template. >> text = _("""The {} list has {} moderation requests waiting. > ``` > I.e., we know it should be a template, but it currently isn't. That's fine but it doesn't explain why I have received messages that were built by a template for some subscription requests. In other words, why is there a template being used in some instances and on others a "mailman notify command" is being used? Are there different methods for people to use to request a subscription? Please understand that I'm new to mailman 3 and don't have knowledge of its source code. From reading some of the messages that have been sent by this list, I assume it's written in python, which is a language I have not year learned. I'm asking this because I help to administer several different lists and there are some other moderators who have very limited technical skills. I try to help them the best I can, which is why I'm trying to understand why these messages seem to differ so that I can explain it to others. By the way, Brian at EMWD has been extremely helpful to me already and, as he stated, he informed me that this is an issue with Mailman 3 so I thought I'd try getting the answer directly from this group. Thank you for your time. I do recognize and appreciate the time and effort that goes into creating and maintaining open source software.

4 years, 4 months

Re: Mailman notify generating emails for request that aren't visible.

by Simon Coggins

Looking at the code in gitlab it looks like it wasn’t merged until 1.3.6: https://gitlab.com/mailman/postorius/-/blob/1.3.6/src/postorius/urls.py#L53 But it’s not in 1.3.5: https://gitlab.com/mailman/postorius/-/blob/1.3.5/src/postorius/urls.py#L49 Thats ok, I’m going to 1.3.6 in a few days so that should solve my issue. -Simon --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 On 1 Nov 2021, at 12:39 pm, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: On 10/31/21 7:27 PM, Simon Coggins wrote: > Oops sorry I hit send to soon. If I try to go > to /lists/listname.example.com/unsubscription_requests<http://listname.example.com/unsubscription_requests> > <http://listname.example.com/unsubscription_requests<http://listname.example.com/unsubscription_requests>> I get a 404, it > looks like unsubscription_requests > <http://listname.example.com/unsubscription_requests<http://listname.example.com/unsubscription_requests>> isn’t in my > urls.py list for Postorius? It should be. It was added by https://gitlab.com/mailman/postorius/-/commit/0aba874cae15b1baae2839dca57d3…<https://gitlab.com/mailman/postorius/-/commit/0aba874cae15b1baae2839dca57d3…> -- 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>

3 years, 8 months

Mailman-users search results for query "2021"