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

[MM3-users] Re: [Bug] Someone not a member of list is treated as member - strange

by Mark Sapiro

On 8/23/25 05:57, Wikinaut wrote: > > When sending from address2, my mail is accepted. When I, for sake of completeness switch 1. to moderate mails from member[sic], my mail from address2 gets moderated. If any of the From: header, the envelope sender, the Reply-To: header if any or the Sender: header if any of a post contains a member address, the post is considered to be from that member. That is the default list, but it can be modified by setting sender_headers in the [mailman] section of mailman.cfg. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/email/message.… and https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… Does this explain the issue? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 2 weeks

[MM3-users] Re: How to connect mailman into existing postfix server

by Mark Sapiro

On 09/16/2018 02:07 AM, Hagen Bauer wrote: > Hi to all, > > I am trying to setup mailman3 with the Docker Image. Everythings works > relative nicely but I am blocked by the Postfix integration part. > > I have a small postfix server that is delivering mails to known domains > and an alias map. The standard use case assumes that the external > postfix is only routing mails to the mailman lmtp. If I do this all my > old users are recected. If your list domain is a virtual alias domain, see <https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#unusual-…>. This is written assuming 'hash' tables and I think the Docker image generates 'regexp' tables, but it should work with those. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 2 months

[MM3-users] Re: Hyperkitty issue(s)

by Mark Sapiro

On 5/28/20 8:06 AM, brylon(a)oit.rutgers.edu wrote: > Yes, I've stopped/started Mailman (quite a few times). > > Is there a particular order to undo Hyperkitty and re-do? Or perhaps add some debug lines to a particular file to get at the root cause? I'm not certain, but I don't think your issue has anything to do with the installation of HyperKitty itself. From the OP, the issue occurs in REST upon a get of /3.1/lists/bry_test4.lists-test.rutgers.edu/archivers which is probably coming from Postorius -> Settings -> Archiving. The actual error occurs in Core trying to process that request, and while it clearly has to do with archiving configuration, I don't think the installation of Hyperkitty is the issue. What happens if you set [archiver.hyperkitty] enable: no and restart Mailman? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: LTMP to Postfix problem

by Mark Sapiro

On 6/18/20 2:24 PM, Brian Carpenter wrote: > > The log entry posted today was: > > Jun 18 15:07:32 2020 (29862) lmtp runner started. > > That was when I restarted Mailman core. If it happens again, I will see > if the lmtp runner is running. My feeling is it died but I don't know > for sure. If you have it, look through the mailman.log for entries around the last time the connections started to be refused. See if there are entries about the runner exiting. Also, just before you restarted, there will be several runner caught SIGTERM. Stopping. and runner exiting. messages. If lmtp runner is among those, it was still running when you restarted. What you are looking for is some exception/traceback from the time connections start to be refused. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: how to delete a list member using the Linux command line

by Mark Sapiro

On 6/19/20 2:10 PM, Mike Wertheim wrote: > Thanks! > > I'm on Debian 10, and the latest Mailman version that's available in the > Debian package manager is 3.2.1. > > I really have no idea how packages get updated in the package manager. Do > you know why Mailman 3.3.1 is not yet available in Debian's package > manager? (Does someone on the Mailman project need to push it there? Or > does someone on the Debian side need to pull it in?) The Debian packaging folks are aware of all our releases. Packaging them is up to Debian. See this reply <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960072#10> to a different issue for a bit more info. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: Mailman config is not being applied

by Mark Sapiro

On 8/23/24 10:45 AM, roberto.blandino--- via Mailman-users wrote: > Debian: 11.10 > GNU Mailman 3.3.3 (Tom Sawyer) > Server version: Apache/2.4.61 (Debian) > PHP 7.4.33 (cli) (built: Apr 12 2024 00:02:16) ( NTS ) > > I have a list and when i add a no member on the web interface and on the Non-Member options i set "Administration options" to "Accept skip other rules" when i send email from that address it keeps being moderated and when i open again the options it keeps saying "Default by list" The options are not being write on changes Is there some kind of redirect in your Apache config that's losing post data? Do other settings in Postorius "stick"? Is this a Debian package? If so, see https://wiki.list.org/x/12812344 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: mailman-web Cleaning Up a Few Issues

by Mark Sapiro

On 11/4/25 11:22, dap1--- via Mailman-users wrote: > Not fatal but hundreds of emails per day. I copies the crontabs from the documentation; Here is the crontab I have: > > * * * * * /opt/mailman/venv/bin/mailman-web runjobs minutely > 0,15,30,45 * * * * /opt/mailman/venv/bin/mailman-web runjobs quarter_hourly > @hourly /opt/mailman/venv/bin/mailman-web runjobs hourly > @daily /opt/mailman/venv/bin/mailman-web runjobs daily > @weekly /opt/mailman/venv/bin/mailman-web runjobs weekly > @monthly /opt/mailman/venv/bin/mailman-web runjobs monthly > @yearly /opt/mailman/venv/bin/mailman-web runjobs yearly But based on https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… you have some other crontab running mailman stuff. Try sudo grep -r '/usr/share/mailman3-web/manage.py' /etc/cron* /var/spool/cron (on one line if wrapped) to find it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 1 week

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

by Mark Sapiro

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

6 years, 11 months

[MM3-users] Re: Spam sign ups

by Mark Sapiro

On 8/17/20 6:40 PM, Seth Seeger wrote: > > I know this was asked a while back on this list, but I'm hoping there might be an update? Any way to add an am-I-human test to the sign up? You might find <https://github.com/praekelt/django-recaptcha> helpful. However, the Mailman 2.1 listinfo subscribe forms for the MM 2.1 @python.org lists all have reCaptcha as well as the features that require GETting the form before POSTing it and requiring at least 5 seconds betweeh GETting and POSTing the form, and yet we still occasionally see periods of massive robotic web subscription attempts of which many succeed, even on lists that require confirmation. The bottom line is robots are better than humans at solving captchas. See the first few hits at <https://www.google.com/search?q=robotic+captcha+success>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: My Server is unable to connect to Mailman REST API few times

by Mark Sapiro

On 9/24/20 4:34 AM, Shashikanth Komandoor wrote: > Thank you Mark for your response. > > I am not sure. How can I check that if it is from unshunting ? It is from unshunting if you or someone else manually ran `mailman unshunt`. I was trying to understand how Mailman would be trying to add a message for the digest to a non-existent list. One way I think is if a message to be added was shunted from the digest queue and then unshunted after the list was deleted. This however seems unlikely. Another possibility is mailman was stopped with an entry for the list in the digest queue and started again after deleting the list. This seems more likely. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

Search results for query "sapiro"