Search results for "2021" - Mailman-users

Re: mailman3 postorius cannot retrieve template

by Wolfgang Bock

Hello Mark, I reconstruct the configuration problems regarding the creation of templates in mm3: I installaed mailman3 via the debian bullseye package(s). BTW: My experience is to install it step by step, not as mailman3-full, but as mailman-3, mailman3-doc, mailman3-web and python3-django-mailman3. In my case the full installation did not run clean, the step-by-step variant run clean. The debian bullseye variant comes with a nginx conf-file in /etc/mailman3/nginx.conf ... # This nginx config file is part of the mailman3-web package. # # This nginx configuration file is a vhost configuration. ... # Nginx SSL snippet. To enable it, please uncomment and update the server_name and the ... server { listen 443; listen [::]:443; server_name mailman.example.com; server_tokens off; # # ## Strong SSL Security # ## https://raymii.org/s/tutorials/Strong_SSL_Security_On_nginx.html & https://cipherli.st/ ssl on; ssl_certificate /etc/letsencrypt/live/mailman.example.com/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/mailman.example.com/privkey.pem; # ... The configuration "ssl on" is outdated as nginx -t comments. The actual configuration should be: /etc/nginx/ /etc/nginx/sites-available/nginx.lists.mydomain.ssl (and /sites-enabled) .... server { listen 443 ssl http2; listen [::]:443 ssl http2; server_name lists.mydomain.com; # for example server_tokens off; ssl_certificate /etc/letsencrypt/live/mydomain.com/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/mydomain.com/privkey.pem; ... If you - as proposed in the mailman3 nginx.conf - include in nginx.lists.mydomain.ssl the following: .... upstream mailman3 { server unix:/run/mailman3-web/uwsgi.sock fail_timeout=0; } .... you cannot in include this in another vhost-nginx configuration (for example): /etc/nginx/sites-available/nginx.lists.mydomain_2.ssl as nginx -t says something like "no double entries please". So I put this in another file like /etc/nginx/sites-available/nginx.00.mailman3.upstream (and via symlink in .../enabled/...) and both nginx-domain-files work. The debian bullseye also serves a file mailman-web.py with an entry ... POSTORIUS_TEMPLATE_BASE_URL = 'https://localhost/mailman3/' ... As mentioned in a mail before that could not work: 1. letsencrypt doesnt serve an entry match for localhost. That floods your syslog. 2. "localhost" doesnt match with the nginx.conf-proposal. It must be something like /etc/mailman3/mailman-web.py .... POSTORIUS_TEMPLATE_BASE_URL = 'lists.mydomain.com/' .... In this combination the creating of templates on the postorius website works. My conclusion: I ask you to consider these experiences in an update for the mailman3 packages in debian bullseye. It would save time, questions and nerves. Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Dienstag, 2. November 2021 23:44 An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: mailman3 postorius cannot retrieve template On 11/2/21 3:28 PM, Wolfgang Bock via Mailman-users wrote: > > I get an db-entry in the mailman3 table template which doesnt lead to > a suitable link: > https://localhost/postorius/api/templates/list/testliste01.mydomain.de/list: > member:regular:footer > > In the next stept it leads to a flood of entries in my syslog because > django is asking for a certificate match for "localhost": > Nov 2 11:47:49 myserver mailman3[175334]: Nov 02 11:47:49 2021 > (175334) Certificate did not match expected hostname: localhost. Certificate: ... > > Letsencrypt cannot deliver this match for "localhost", it is > impossible to configurate letsencrypt to do so. > > The running script must create a postgres INSERT database command > which includes the correct domain-name including the correct path > .../mailman3/api/templates .... and not ... postorius/api/.... > > I dont know, where is the place to correct this. > - in mailman-web.py ?? > ... > ALLOWED_HOSTS ... '*' > or > MAILMAN_REST_API_URL = 'http://localhost:8001' > or > POSTORIUS_TEMPLATE_BASE_URL = 'https://localhost/mailman3/' If you normally access Postorius on your site at something like https://www.example.com/postorius, than set that as POSTORIUS_TEMPLATE_BASE_URL -- 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/

3 years, 8 months

uncaught bounce messages

by David Bremner

I'm getting (many) uncaught bounce messages for one user. Other than forcibly unsubscribing them, is there anything I can do? I hesitate to post this message publically, but here is what I can see, somewhat anonymized The MIME structure looks like └┬╴multipart/mixed 7030 bytes ├─╴text/plain 442 bytes ├─╴message/delivery-status 176 bytes └─╴text/rfc822-headers 5301 bytes In /var/log/mailman3/bounce.log I see lines like Oct 23 08:20:00 2021 (5320) Bounce message w/no discernable addresses: <hex-digits(a)foo.bar> In the delivery-status part I see Final-Recipient: rfc822; fub(a)foo.bar Action: delayed Status: 4.0.0 The initial text/plain part looks like Hi! This is the MAILER-DAEMON, please DO NOT REPLY to this email. A message is delayed for more than 4 hours for the following list of recipients: fub(a)foo.bar: Network error on destination MXs Please note that this is only a temporary failure report. The message is kept in the queue for up to 7 days. You DO NOT NEED to re-send the message to these recipients. Below is a copy of the original message:

3 years, 8 months

Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Sat, May 15, 2021 at 12:01 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/14/21 1:54 PM, Odhiambo Washington wrote: > > > > /usr/local/include/sass > > > > That is the only thing found that is in the base system. > > And that's the one you want. What is it's mode? > root@gw:/usr/home/wash # ls -al /usr/local/include/sass total 104 drwxr-xr-x 2 root wheel 512 Apr 16 16:49 . drwxr-xr-x 176 root wheel 10240 Apr 19 18:05 .. -rw-r--r-- 1 root wheel 2369 Apr 8 11:08 base.h -rw-r--r-- 1 root wheel 10742 Apr 8 11:08 context.h -rw-r--r-- 1 root wheel 6632 Apr 8 11:08 functions.h -rw-r--r-- 1 root wheel 6489 Apr 8 11:08 values.h -rw-r--r-- 1 root wheel 198 Apr 8 11:08 version.h I imagined I needed an executable. drwxr-xr-x 2 root wheel 512 Apr 16 16:49 sass -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 1 month

Re: Mysterious Bounces Being Logged

by Mark Sapiro

On March 26, 2021 2:08:01 PM PDT, Brian Carpenter <brian_carpenter(a)emwd.com> wrote: > >I would think any mail administrator for a mailman server would want to > >know why bounces are happening. I never saw this issue with Mailman 2. >Did it exist? No. Mailman 2.1 always included the DSN in notices to the admin. >Is the patch going to make it to the next version of Mailman 3 core? No. I don't think it's generally useful. It's use is too obscure. >Are >there any plans to make bounce processing more transparent to server >admins so we can troubleshoot delivery issues? Absolutely. At first MM3 wasn't processing bounces at all. A GSOC student did the bulk of the current implementation and we were happy to get that even though this piece was missing. We know we need it. If you don't think we're working fast enough, you can submit a merge request or dock our pay. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

4 years, 3 months

Re: "Unsubscribe all" failed with large lists

by Abhilash Raj

thanks, Abhilash Raj On Wed, Jan 20, 2021 at 10:34, Alan So <ktso(a)cuhk.edu.hk> wrote: > We are currently testing latest mailman suite (w/Postorius 1.3.3) and > notice that that the the API call > /3.1/lists/listname.domain/roster/member failed when using > "Unsubscribe all" on Postorius for a large list (~15000 members). > Not sure whether the issue has been already reported or not. It has been reported before for sure, but I couldn't find an issue tracking it in Postorius' tracker so I created one[1]. The Core and Mailmanclient already have a mass-unsubscribe API that doesn't require looping over all address and unsubscribing them one by one, it just needs to be plumbed through in P, in case someone wants to take a stab at it. [1]:https://gitlab.com/mailman/postorius/-/issues/464 > _______________________________________________ > 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/>

4 years, 5 months

Re: Setting for archiving multi email domains?

by Duane Raymond

On Wed, 10 Mar 2021 at 15:52, Brian Carpenter <brian_carpenter(a)emwd.com> wrote: > > Update: the other person on the test list has indicated they are > receiving the emails now - and that gmail may be the cause of the issue by > filtering out copies of the message I had sent. (my fairsay.com address > is gmail hosted, but another is not and is simply forwarded there). > > > > ...so perhaps the problem is solved (will do a little more testing to > verify!) > > It's Gmail. Just check the mail.log and look for status=sent > Thanks Brian - then I think it is fixed :-) Thank you Mark and Brian for your patience and persistence. I'll keep monitoring the situation as new subscribers (not sure if all) seem to also be missing the user id in the members table and I then need to run an update query to fix it - but at least I know what to look for and how to resolve it! (this last week was painful!) Cheers, Duane

4 years, 3 months

Re: Core, Hyperkitty and Postorius releases

by Mark Sapiro

On 5/14/21 3:00 PM, Odhiambo Washington wrote: > On Sat, May 15, 2021 at 12:47 AM Mark Sapiro <mark(a)msapiro.net> wrote: > >> Those are headers for compiling some sass. Possibly you actually have a >> `sassc` installed in which case you may need >> >> COMPRESS_PRECOMPILERS = ( >> ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), >> ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), >> ) >> >> > This change makes the error I was getting to go away. However, I cannot > login to manage lists, even after restarting mailman. > > The error details are here: https://pastebin.ubuntu.com/p/vM2c5WYyJ4/ The relevant part of which is OfflineGenerationError at /accounts/login/ You have offline compression enabled but key "fa788b08b65fd318d68cfc5afebc18acd3e93cebffadb54d863572ad1754f368" is missing from offline manifest. You may need to run "python manage.py compress". Here is the original content: I.e., something went wrong with your compress command. Try it again. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

List enumeration problem

by kawhite＠ancestry.com

On our mailman instance we see the following enumeration of ALL lists and ALL users consistently every 7.5 minutes. Does anyone know why this would be the case? We have a lot of mailing lists so it slows our machine down a lot. Apr 30 15:31:36 2018 (39026) 127.0.0.1 - - "GET /3.0/lists/a(a)example.com HTTP/1.1" 200 310 Apr 30 15:31:36 2018 (39026) 127.0.0.1 - - "GET /3.0/lists/a(a)example.com/config HTTP/1.1" 200 2021 Apr 30 15:31:36 2018 (39026) 127.0.0.1 - - "GET /3.0/lists/b(a)example.com HTTP/1.1" 200 325 Apr 30 15:31:37 2018 (39026) 127.0.0.1 - - "GET /3.0/lists/b(a)example.com/config HTTP/1.1" 200 2108 Apr 30 15:31:37 2018 (39026) 127.0.0.1 - - "GET /3.0/lists/c(a)example.com HTTP/1.1" 200 326 Apr 30 15:31:37 2018 (39026) 127.0.0.1 - - "GET /3.0/lists/c(a)example.com/config HTTP/1.1" 200 2049 Apr 30 15:31:37 2018 (39026) 127.0.0.1 - - "GET /3.0/lists/d(a)example.com HTTP/1.1" 200 324 ... Apr 30 16:26:28 2018 (9581) 127.0.0.1 - - "GET /3.0/users/a@a HTTP/1.1" 404 13 Apr 30 16:26:28 2018 (9581) 127.0.0.1 - - "GET /3.0/users/b@b HTTP/1.1" 404 13 Apr 30 16:26:28 2018 (9581) 127.0.0.1 - - "GET /3.0/users/c@c HTTP/1.1" 404 13 Apr 30 16:26:28 2018 (9581) 127.0.0.1 - - "GET /3.0/users/d@d HTTP/1.1" 404 13

7 years, 1 month

Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Sat, May 15, 2021 at 1:08 AM Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users(a)mailman3.org> wrote: > > On 14/5/21 23:52, Odhiambo Washington wrote: > >> Which OS are you using? > > FreeBSD. > > > > > As Mark pointed, you probably have installed the textproc/sassc port (or > package). I'ts an equivalent for sass. Do the config as advised. > > I have mailman3 installed and running smoothly in a pair of 12.2 RELEASE > FBSD servers. > > There is a thread about this installations that can help: > https://forums.freebsd.org/threads/mailman-3.61050/post-488128 > <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> I will look into this. I know FreeBSD has a mailam3 port, but I have mailman2 in production and the port installs to /usr/local/mailman so I have to be careful - install mailman3 in /opt, then plan on hosing mailan2 and moving mailman3 to it's place after migration. It's not simple. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 1 month

Re: Header Filter madness

by Mark Sapiro

On 1/11/21 6:14 PM, Brian Carpenter wrote: > > On 1/11/21 8:48 PM, Mark Sapiro wrote: >> On January 11, 2021 5:50:04 PM MST, Brian Carpenter >> <brian_carpenter(a)emwd.com> wrote: >>> I have a client whose header filters seemed to have stop working. No >>> matter what I try, it seems none of their header filters are being >>> applied. Other lists on the same server that use header filters, are >>> working fine. This particular header is the subject header. I can >>> duplicate their problem but only with their list. If I create the exact >>> same header on a test list using the exact same subject line, the >>> header >>> filter does its job (moderate). Just not with this one list. What's in the X-Mailman-Rule-* headers of the post that should be but isn't held? Are there other header filter rules besides the one that doesn't work? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

Mailman-users search results for query "2021"