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

[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, 10 months

[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/

5 years

[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 >

1 year, 6 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

9 years

[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/

4 years, 5 months

[MM3-users] Re: Mailman3 via Docker and NGINX

by Abhilash Raj

On Wed, Dec 19, 2018, at 8:18 AM, Mark Sapiro wrote: > On 12/19/18 7:03 AM, brian(a)emwd.com wrote: > > I have Mailman3 installed on CentOS 7 using maxking's docker image. I believe the installation went fine and running "curl http://172.19.199.3:8000/postorius/lists/" produces the correct output. I also will be using exim and nginx with this installation. > ... > > location / { > > include uwsgi_params; > > uwsgi_pass 172.19.199.3:8000; Change this to use port 8080 instead of 8000. 8000 is for HTTP protocol and 8080 is for uwsgi protocol. See the docs[1]. [1]: https://github.com/maxking/docker-mailman#setting-up-your-web-server > > uwsgi_read_timeout 300; > > proxy_set_header Host $host; > > proxy_set_header X-Forwarded-For $remote_addr; > > } > > } > > > Since you can curl http://172.19.199.3:8000/postorius/lists/ and get the > correct output, uwsgi or whatever your wsgi process is is working at > that level, and I don't think you should be invoking uwsgi in nginx. I > think you should be using proxy_pass. > > See > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> > for the nginx config used on lists.mailman3.org. > > -- > 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/ > -- thanks, Abhilash Raj (maxking)

7 years, 8 months

[MM3-users] Re: Hyperkitty Recommended mySQL Database Setup & Archive Importing

by matthew＠alberti.us

Thanks Mark. Also, just to confirm, should the database connection string also be updated? In both the core and web configuration, I have something like: DATABASE_URL=mysql+pymysql://mailman:password@database/mailmandb Note the trailing UTF-8 encoding stuff isn't there. Should we be specifying utf8mb4 there as well? I'm planning to test this in a dev environment. If I can somewhat confirm the fix procedure won't break an existing install (like I have), I'll submit a PR(s) to the docker-mailman github. - Matt Alberti -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, December 9, 2020 1:29 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Hyperkitty Recommended mySQL Database Setup & Archive Importing On 12/8/20 1:02 PM, matthew(a)alberti.us wrote: > Mark/Ruth/The List, > Thanks for the prompt responses. Before I try to figure out a way to > correct this... is the "character_set_database" the only thing I > should be looking at? You need to set 'OPTIONS': {'charset': 'utf8mb4'} in the DATABASES['default'] definition in your django settings. I'm not sure if this overrides the various collation, etc. settings in the DB or not, but it wouldn't hurt to update the DB. -- 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/

5 years, 8 months

[MM3-users] Re: Advice on migrating to Mailman 3

by Mark Sapiro

On 2/13/20 2:02 PM, Christoph Groth wrote: > > The only problem is that our list runs on Mailman 2. We would like to > move to Mailman 3, but this does not seem to be that simple. Perhaps > someone here would be so kind to give us advice? I think it's pretty simple, but I've been a Mailman developer for 15 years ;) > The number of (shared) hosters who offer Mailman 3 seems to be very > limited [3]. Would it be a good idea to book a virtual private server > (VPS) somewhere, that runs, say, Debian, and simply install Mailman > 3 through the distribution’s package system? I’m already running > a small personal box with nginx on it, and this is very little work, but > running Mailman would require sending out up to a few thousand email > messages per day (our list has a few hundred subscribers). Is this > something that one is commonly allowed to do on a VPS system? Most VPS > offers that I see are silent about mail. This list is on a VPS hosted by RackSpace. mail.python.org which hosts hundreds of lists is a VPS hosted by DigitalOcean, and my bicycling club's web site, email and mailing lists are on a VPS also hosted by DigitalOcean. These servers all run some version of Ubuntu, but because we are developers, they do not use the Debian/Ubuntu packages. They are all installed from the heads of the GitLab branches and kept pretty much up to date with those. All three servers use Postfix as an MTA. We have no issues with mail volume per se. What you will see with a new VPS is your IP being blocked by various ISPs. It takes a bit of communication and patience to work through these blocks, but once you develop a good reputation, they tend to go away. > If we setup such a system, can we assume that it will silently operate > without causing much administration work most of the time (like my nginx > server)? Or is maintaining a Mailman 3 server a significant burden ([2] [2], or [3]? > seems to imply that)? If yes, are you aware of organizations that > propose Mailman 3 hosting for open source projects? Python.org seems to > host some lists for third party projects, but otherwise I haven’t seen > much. I don't think a Mailman 3 installation needs an undue amount of baby sitting. I do run daily reports that list the contents of mailman's queues (normally empty, but messages in the shunt queue need investigation) and grep a couple of logs for errors. mail.python.org hosts lists for Python related open source projects. Kwant seems to be eligible. Ask postmaster(a)python.org specifying the desired list name and name and email address of the initial list owner(s). However, we don't normally import lists or archives from elsewhere. > [1] https://kwant-project.org/ > [2] https://mailman-mail5.webfaction.com/listinfo/kwant-discuss > [3] > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Re: mailman3-web and the django middleware problem

by Thomas Stein

Am 26. April 2024 18:23:56 MESZ schrieb Mark Sapiro <mark(a)msapiro.net>: >On 4/25/24 22:30, Thomas Stein wrote: >> Am 2024-04-26 00:52, schrieb Mark Sapiro: >>> One thing you could try is in settings_local.py, put >>> ``` >>> from settings import MIDDLEWARE >>> x = list(MIDDLEWARE) >>> x.insert(0, 'allauth.account.middleware.AccountMiddleware') >>> MIDDLEWARE = x >>> ``` >>> to work around the NameError. >> >> After that I get: >> >> File "/usr/share/mailman3-web/urls.py", line 20, in <module> >> from django.conf.urls import include, url >> ImportError: cannot import name 'url' from 'django.conf.urls' (/usr/lib/python3/dist-packages/django/conf/urls/__init__.py) >> dpkg: error processing package mailman3-web (--configure): >> installed mailman3-web package post-installation script subprocess returned error exit status 1 >> Errors were encountered while processing: > > >This is another Debian/Ubuntu packaging issue. The packaged >/usr/share/mailman3-web/urls.py is incompatible with Django>=4.1. Replace it with the one at https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/urls.py?re… > >> I guess I'll wait for the new package for now. > >Hopefully that will fix it, or, as Odhiambo suggests, you can uninstall the Debian/Ubuntu packages and install per https://docs.mailman3.org/en/latest/install/virtualenv.html > I did that. It went actually quite well. Had to change the owner of the mailman databases with alter table though. cheers! t.

2 years, 3 months

[MM3-users] Fwd: [GNC-dev] Passwords are Confidential

by flywire

Looking forward to Mailman 3. How can I get an indication of when Mailman 3 code is likely to run on Fedora 29? On Sun, Apr 26, 2020 at 1:42 AM Mark Sapiro wrote: > On 4/25/20 2:08 AM, flywire wrote: > > MailMan version 2.1.29 > > > > On Sat, Apr 25, 2020 at 6:08 PM Adrien Monteleone wrote: > > > > You can turn off the reminder in your mailman settings. > > > > As this is part of the mailman code, perhaps a bug report to them > > would be in order concerning the storage issue. > > > > Regards, > > Adrien > > > > > On Apr 24, 2020 w17d115, at 11:29 PM, flywire > > > > > > My password is confidential so please don't email it to me in > > plain text. > > > Don't even store it, instead encrypt what I entered and store that > > so you > > > can verify an encrypted version of the password I enter in the > future. > > > This is a well known, long standing issue which will not be fixed in > Mailman 2.1. See <https://bugs.launchpad.net/mailman/+bug/265179> > > It is fixed in Mailman 3. > > -- > Mark Sapiro > Derek Atkins 2020-04-25 18:32:15 EDT Code runs Fedora 29. Mailman 3 isn't available on F29. When code gets upgraded, mailman will be upgraded. As for turning off the reminder; you can turn it off yourself. Thank you.

6 years, 3 months

Search results for query "sapiro"