Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: Clearing webserver cache - Nginx

by Mark Sapiro

On 9/29/24 00:59, Odhiambo Washington via Mailman-users wrote: > > Could you allow me to revisit this issue since I haven't solved it? First, > I bypassed CloudFlare DNS proxying just to ensure I have nothing is coming > in between my browser and the web server. > That did not help with the issue of the "missing" CSS files. Then you have som other issue in your configuration. > Ideally, I should not be creating these symlinks, right? On my old server > the symlinks weren't necessary. That is correct. > I have created some symlinks and that appears to help with Apache. I will > test with Nginx and see how it goes. > ``` > root@eu:/opt/mailman/mm/static/CACHE/css# ls -al > total 196 > drwxr-xr-x 2 mailman mailman 4096 Sep 29 10:40 . > drwxr-xr-x 4 mailman mailman 4096 Mar 21 2024 .. > lrwxrwxrwx 1 mailman mailman 23 Sep 29 10:40 output.ac23d5f5127c.css -> > output.d29798365ddb.css > lrwxrwxrwx 1 mailman mailman 23 Sep 29 10:31 output.bacec526ec98.css -> > output.e69dbb26da3b.css > -rw-r--r-- 1 mailman mailman 1209 Mar 21 2024 output.d29798365ddb.css > -rw-r--r-- 1 mailman mailman 569 Mar 21 2024 output.e68c4908b3de.css > -rw-r--r-- 1 mailman mailman 180904 Mar 21 2024 output.e69dbb26da3b.css > root@eu:/opt/mailman/mm/static/CACHE/css# > ``` > My question though: What is the source of truth for the files that should > be in /opt/mailman/mm/static/CACHE/css/ ?? When you run `django-admin collectstatic --clear ...` it removes all the old files from the static/ directory and installs new ones. At this point static/CACHE/ contains no files. Then when you run `django-admin compress` it creates three output.*.css files in static/CACHE/css and one output.*.js file in static/CACHE/js and creates a static/CACHE/manifest.json file that points to those four files and which is what Django uses for the paths to put in the relevant <script ...> and <link rel="stylesheet" ...> tags in the pages it serves. I.e. static/CACHE/manifest.json is the source of truth. > Maybe that is what I need to focus on. If need be, then I should *fix* the > contents of that file so that it doesn't contain the nonexistent files, no? I very much doubt that it does contain the nonexistent files since it is built by the same `django-admin compress` that creates the output* files. > Lastly, why is it that my https://mm3-lists.kictanet.or.ke/archives/ does > not display content similar to what https://lists.mailman3.org/archives/ > does? > What change should I make in which settings.py? This is a clue. I presume you actually have archived lists. There is something very wrong in your configuration if HyperKitty is not finding those lists. Possibly you have more than one WSGI server running and you aren't always proxying to the correct one. That seems far fetched to me, but without seeing all your web server, WSGI server and Django configurations, I have no idea what the issue could be. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: Block members from sending cc's and bcc's

by Mark Sapiro

On 10/19/25 14:28, Cathryn McGuire wrote: > Hi Mark, > > 1. Since this post in July, I've been trying to work with EMWD to get the cc's blocked. I've tried every rule configuration in the Header Filter to no avail. EMWD can't seem to help. The setting options are as follows: > > Acceptable aliases > > This is a list, one per line, of addresses and regexps matching addresses that are acceptable in To: or Cc: in lieu of the list posting address when 'require_explicit_destination' is enabled. Entries are either email addresses or regexps matching email addresses.Regexps are entries beginning with '^ and are matched against every recipient address in the message. The matching is performed with Python's re.match () function, meaning they are anchored to the start of the string. What is the content of this? Probably should be empty. > 2. Require Explicit Destination (this is a checked box. Could it be interfering with the Header filters?) No, it doesn't interfere with header checks. > This checks to ensure that the list posting address or an acceptable alias explicitly appears in a To: or Cc: header in the post. > > 3. Default action to take when a member posts to the list > > Accept immediately (bypass other rules) > Default action to take when a member posts to the list. > Hold: This holds the message for approval by the list moderators. > Reject: this automatically rejects the message by sending a bounce notice to the post's author. The text of the bounce notice can be configured by you. > Discard: this simply discards the message, with no notice sent to the post's author. > Accept: accepts any postings without any further checks. > Default Processing: run additional checks and accept the message. NOTE - when set here, all members are blocked. What does Blocked mean? If you mean held for moderation, what is the reason they are held? > 4. We also have the problem of large image file sizes being let through no matter what setting we have. We have it set to 500KB, but everything is accepted. > > Maximum message size > 500 > The maximum allowed message size in KB. This can be used to prevent emails with large attachments. A size of 0 disables the check. > > Perhaps some settings are over-riding others? If you have Default action to take when a member posts to the list set to Accept, that bypasses this check and many others. > What do you think? What do you have in your header filter rules? More importantly, what are you trying to accomplish? I.e. what do you want to happen in the following cases? 1. Message To: the list, no Cc: 2. Message To: the list, Cc: to other address 3. Message To: somewhere else, Cc: to the list 4. Message To: elsewhere, Bcc: to the list (require explicit destination will hold this one) Maybe others? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 weeks, 1 day

[MM3-users] Re: Issues with a DMARC record leading to message being shunted

by Mark Sapiro

On 12/23/23 1:57 AM, Ralf Hildebrandt via Mailman-users wrote: > Hi! > > Recently a mail was not being distributed via our MM3 instance; I searched the logs and found: > > Dec 22 04:54:27 2023 (24) ACCEPT: <1d431542-b386-467b-8bf2-305f19ee7eb4(a)somenet.org> > Dec 22 04:54:28 2023 (28) Uncaught runner exception: list index out of range > Dec 22 04:54:28 2023 (28) Traceback (most recent call last): > File "/usr/lib/python3.10/site-packages/mailman/core/runner.py", line 179, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/lib/python3.10/site-packages/mailman/core/runner.py", line 272, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/lib/python3.10/site-packages/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) > File "/usr/lib/python3.10/site-packages/mailman/core/pipelines.py", line 53, in process > handler.process(mlist, msg, msgdata) > File "/usr/lib/python3.10/site-packages/mailman/handlers/validate_authenticity.py", line 125, in process > authenticate(msg, msgdata) > File "/usr/lib/python3.10/site-packages/mailman/utilities/retry.py", line 44, in f_retry > return f(*args, **kwargs) > File "/usr/lib/python3.10/site-packages/mailman/handlers/validate_authenticity.py", line 93, in authenticate > auth_result = authenticate_message( > File "/usr/lib/python3.10/site-packages/authheaders/__init__.py", line 395, in authenticate_message > dmarc_result = check_dmarc(msg, spf_result, dkim_result, dnsfunc=dnsfunc, psddmarc=psddmarc) > File "/usr/lib/python3.10/site-packages/authheaders/__init__.py", line 343, in check_dmarc > result, result_comment, from_domain, policy = dmarc_per_from(from_domain, spf_result, dkim_result, dnsfunc, psddmarc) > File "/usr/lib/python3.10/site-packages/authheaders/__init__.py", line 90, in dmarc_per_from > record, orgdomain = receiver_record(from_domain) > File "/usr/lib/python3.10/site-packages/authheaders/dmarc_lookup.py", line 117, in receiver_record > retval = lookup_receiver_record(hostSansDmarc, dnsfunc) > File "/usr/lib/python3.10/site-packages/authheaders/dmarc_lookup.py", line 92, in lookup_receiver_record > tags = answer_to_dict(str(result)) > File "/usr/lib/python3.10/site-packages/authheaders/dmarc_lookup.py", line 42, in answer_to_dict > retval = {t[0].strip().lower(): t[1].strip().lower() for t in rawTags} > File "/usr/lib/python3.10/site-packages/authheaders/dmarc_lookup.py", line 42, in <dictcomp> > retval = {t[0].strip().lower(): t[1].strip().lower() for t in rawTags} > IndexError: list index out of range > > Dec 22 04:54:28 2023 (28) SHUNTING: 1703220868.1418982+b27f5db154375fcd2c418d467172e4aad0d3d57a > > So the message has been shunted, due to this error. Something with > DMARC and tags. So I checked the DMARC record for the sending domain > somenet.org. It is "v=DMARC1;p=none;pct=100;rua=mailto:postmaster@somenet.org;mailto:postmaster@somenet.org;ri=3600;fo=1;" > which is syntactically incorrect. The extra ";mailto:postmaster@somenet.org" is wrong, I guess the tag "ruf=" is missing here! > > It should probably read "v=DMARC1;p=none;pct=100;rua=mailto:postmaster@somenet.org;ruf=mailto:postmaster@somenet.org;ri=3600;fo=1;" > > So, should mm3 somehow "catch" this error somehow? Perhaps we should catch it. We already have other issues involving authheaders.authenticate_message. There's an invalid From: issue at https://gitlab.com/mailman/mailman/-/issues/1100 reported at https://github.com/ValiMail/authentication-headers/issues/25 and a different invalid DMARC issue at https://gitlab.com/mailman/mailman/-/issues/1109 reported at https://github.com/ValiMail/authentication-headers/issues/26. For now, I reported this at https://github.com/ValiMail/authentication-headers/issues/27 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: config incoming email in my domain cpanel

by Rafael Mora

El jue., 3 ago. 2017 a las 15:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/03/2017 12:58 PM, Rafael Mora wrote: > > > > Does the rDNS PTR record should be placed in my Centos7 server? > > You can't do this. Hostgator or whoever manages the network (Telmex > Colombia S.A. ?) has to do this. > > > > I've created the DNS A record for lists.labbrands.com with the IP but I > > don't know the port that it uses so I can make a port redirect to my > local > > ip address wich is 192.168.1.42, do you know the port????? > > > You need to forward port 25 for SMTP mail delivery and if you want the > web UI (Postorius and HyperKitty) accessible from the outside, port 80 > for http and/or port 443 for https > < > https://www.iana.org/assignments/service-names-port-numbers/service-names-p… > >. > I mean for incoming mail redirected from my hostgator hosting, because when I suscribe an email address MM3 sends a confirmation email, so I have to reply to be suscribed to the list. > > -- > 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

8 years, 3 months

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Tim Cutts

Yup. I noticed that when I went through this two days ago. I hadn’t got around to mentioning it yet. :-) > On 8 Jul 2022, at 18:01, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 7/8/22 9:16 AM, kisner(a)live.com wrote: >> Just out of curiosity and to try to improve the doc I can do this a little later. But I can tell you for sure the pip install psycopg2-binary<2.9 command failed for me on Ubuntu 22.04 and Debian 11.3. I'm not saying it's *not* me, and I don't know when the last time that doc was updated but I couldn't get it to work on a few different distros. > > > The issue is when you do > ``` > pip install psycopg2-binary<2.9 > ``` > your shell (sh, bash, zsh or whatever) interprets `<2.9` as an input redirection and probably says something like `2.9: No such file or directory`. You need to do something like > ``` > pip install psycopg2-binary\<2.9 > ``` > or > ``` > pip install 'psycopg2-binary<2.9' > ``` > I'll update the doc. > > -- > 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, 3 months

[MM3-users] Re: How to prevent members to attach executables (exe, bat, ...) to the emails sent to list

by Mohsen Masoudfar

Good morning Mark, You were right, the parameter m.filter_content was set to False, I believe the default. I changed it to True and it worked as expected. Thanks again. Mohsen -----Original Message----- From: Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> Sent: Friday, October 2, 2020 2:54 AM To: Mark Sapiro <mark(a)msapiro.net> Cc: mailman-users(a)mailman3.org Subject: [MM3-users] Re: How to prevent members to attach executables (exe, bat, ...) to the emails sent to list [EXTERNAL EMAIL] Mark Sapiro writes: > Filtering by extension only works on message parts that have an > associated file name. Thus, while you can add things like 'exe', 'bat', > 'cmd', 'com', 'pif', 'scr', 'vbs' and 'cpl' to filter_extensions, it > won't be completely effective. > > A better approach is to use MIME types[1] and only allow those you want. > For a discussion list, a reasonable set is what this list uses: I wouldn't say "better" if you're concerned about the executables being malware. There's long history of concealing malware by giving it a MIME type different from what the extension implies, and there was at least one Windows exploit that used this technique to achieve automatic execution of malware simply by displaying the message. _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

5 years

[MM3-users] Re: can't get mail into mailman3 in docker

by matthew＠alberti.us

Bob, Can you run the command "sudo docker logs mailman-core" and see what the end of that says? Another good command to run is "sudo docker ps" and make sure the mailman-core container is actually running. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, August 11, 2021 1:25 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: can't get mail into mailman3 in docker On 8/10/21 11:29 AM, bob B wrote: > /opt/mailman/core/mailman-extra.cfg. now has > #lmtp_host: localhost > lmtp_host: 127.0.0.1 > lmtp_port: 8024 > > But but mail log shows > 2021-08-10T14:13:28.927266-04:00@####### postfix/qmgr[37253]: > DDF5D3083EC2: from=<user(a)user.com>, size=8181, nrcpt=1 (queue active) > 2021-08-10T14:13:28.973273-04:00@####### postfix/lmtp[39368]: > DDF5D3083EC2: to=<test@.....>, relay=127.0.0.1[127.0.0.1]:8024, > delay=0.07, delays=0.04/0.02/0.01/0, dsn=4.4.2, status=deferred (lost > connection with 127.0.0.1[127.0.0.1] while receiving the initial > server greeting) > > Also to clarify the images no longer have hard coded ips so I should NOT DO this correct? > ----------------------------- > lmtp_host: 172.19.199.2 > lmtp_port: 8024 > smtp_host: 172.19.199.1 > smtp_port: 25 > ----------------------------- I think that's correct, but I'm at a loss for helping further. Hopefully @maxking will be able to help. -- 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/

4 years, 2 months

[MM3-users] Re: Adding Mass Subscribe custom template error

by Arte Chambers

Where can I find the setting ``` POSTORIUS_TEMPLATE_BASE_URL ``` Thank you, Paul 'Arte Chambers' Robey 502-408-6922 On Tue, Jan 28, 2025 at 6:22 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/28/25 12:31, Arte Chambers via Mailman-users wrote: > > > > I'm getting the following error when using mass subscription on a testing > > list with a custom template loaded for [list:user:notice:welcome] > > ``` > > HTTP Error 400: HTTPConnectionPool(host='localhost', port=8000): Read > timed > > out. (read timeout=5) > > ``` > > > It appears you are setting the template in Postorius and there is an > issue with your setting for POSTORIUS_TEMPLATE_BASE_URL. It looks like > this is something like > ``` > POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000/' > ``` > and that connection is timing out. Try setting just the scheme and host > for access to Postorius. I.e., if you access Postorius at a URL like > https://www.example.com/mailman3/, try > ``` > POSTORIUS_TEMPLATE_BASE_URL = 'https://www.example.com/' > ``` > > -- > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to paul.m.robey(a)gmail.com >

9 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I installed whoosh, ran the server and got this: DisallowedHost at / Invalid HTTP_HOST header: '192.168.1.42:8000'. You may need to add u'192.168.1.42' to ALLOWED_HOSTS. Request Method: GET Request URL: http://192.168.1.42:8000/ Django Version: 1.11.3 Exception Type: DisallowedHost Exception Value: Invalid HTTP_HOST header: '192.168.1.42:8000'. You may need to add u'192.168.1.42' to ALLOWED_HOSTS. Exception Location: /var/lib/mailman/env2/lib/python2.7/site-packages/django/http/request.py in get_host, line 113 Python Executable: /var/lib/mailman/env2/bin/python2 Python Version: 2.7.5 Python Path: ['/var/lib/mailman/env2/lib/python2.7/site-packages/django_q', '/var/lib/mailman/mailman-suite/mailman-suite_project', '/var/lib/mailman/env2/lib64/python27.zip', '/var/lib/mailman/env2/lib64/python2.7', '/var/lib/mailman/env2/lib64/python2.7/plat-linux2', '/var/lib/mailman/env2/lib64/python2.7/lib-tk', '/var/lib/mailman/env2/lib64/python2.7/lib-old', '/var/lib/mailman/env2/lib64/python2.7/lib-dynload', '/usr/lib64/python2.7', '/usr/lib/python2.7', '/var/lib/mailman/env2/lib/python2.7/site-packages'] Server time: Fri, 21 Jul 2017 23:35:16 +0000 Where's the ALLOWED_HOSTS file???? El vie., 21 jul. 2017 a las 16:32, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 02:27 PM, Rafael Mora wrote: > > > > it says it needs whoosh > > > > How do I install that? on env2 with python2 or env with python3 ??? > > > In env2 do 'pip install whoosh' > > -- > 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

8 years, 3 months

[MM3-users] Re: Migration of archives from Sympa to MM3

by Tom Fillmore

Great! ...appreciate your time. T The earth is but one country and mankind its citizens... - Baha'u'llah ------- Original Message ------- On Monday, February 28th, 2022 at 11:27 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/28/22 10:53, Tom Fillmore wrote: > > > Moving existing lists to MM3 looks doable the archives are a different story. Has anyone ever migrated archives from Sympa to MM3? > > Mailman can import archives where the messages are in a Unix format mbox > > file. It appears sympa can export archives as a zip file containing > > monthly files of messages > > https://sympa-community.github.io/manual/customize/archives.html. > > If these files are in Unix mbox format, HyperKitty's hyperkitty_import > > function can import them directly, either individually or concatenated. > > If not, they would need to be processed to add Unix `From` lines and > > possibly make other changes. In any case, the mbox to be imported should > > be checked for unescaped `From` lines in message bodies with a script > > such as the one at https://www.msapiro.net/scripts/cleanarch3. > > -- > > 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

Search results for query "sapiro"