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

[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, 8 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, 6 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

3 months, 3 weeks

[MM3-users] Re: [Mailman-Users] VERP on Mailman 3

by Mark Sapiro

On 2/7/26 12:24, John Price via Mailman-users wrote: > > After going back to look at older emails from mailman 2, I guess I was > wrong. I'm just fighting a few auto-responders that don't get any hint > as to what email address is subscribed. Luckily it's only a few and I > guess I'll just block them. If you set the list's personalize attribute to Personalization.individual you can create a list:member:regular:footer template containing a $member or $user_email substitution. If the autoresponder includes the original message, you can get the recipient address that way. If the autoresponse contains only headers, you can set Personalization.full to put the recipient address in the To: header, but that may not be desirable for other reasons. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 weeks

[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

7 years, 2 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, 6 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, 5 months

[MM3-users] Re: Trouble importing a Mailman 3 Postgres database into a new Mailman 3 instance (Docker)

by Mark Sapiro

On 7/21/22 08:09, skenny(a)scss.tcd.ie wrote: > > I was afraid that by removing the default database that comes with the database container, I'd be losing some vital information that may have been added or changed in the database config since I first got my production server working 2 years ago - changed field values, extra table columns ... ? Does that make any sense? I've a hazy understanding at best of the minutiae of databases, being honest. You should run your Django admin command with the `migrate` argument, however you run that in your container after you import the database to apply any necessary migrations. This should fix any issues with added columns or changed definitions. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: Audit Logs

by Mark Sapiro

On 1/30/19 11:53 AM, Enrique Terrazas wrote: > Greetings, > I’m wondering if there is an “audit log” of sorts to see who made changes to a specific list. What we’re after is a way of tracking, in case requested, who made additions or deletions of subscribers etc. I can see the DELETE commands in the ./mailman/logs/mailman.log file but it doesn’t specifically state who made the request. It can be inferred from the timestamps. I’m just wondering if there is somewhere else I should be looking for this information. There is a 'subscribe' log, but currently the only events logged there are moderator approvals of unsubscribe requests held because the list's unsubscription_policy is moderate. Please submit an issue at <https://gitlab.com/mailman/mailman/issues/new> requesting logging of the information you'd like to see in this log. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

[MM3-users] Re: [Django] ERROR (EXTERNAL IP): Internal Server Error:

by Mark Sapiro

On 11/18/19 9:26 AM, Wolfgang Bock via Mailman-users wrote: > > Hello, > > I got an errormessage via mail to root@[domain-01]. > > The complete text is attached in a utf-8-text-file. > > In the lines ...6, 8, 12, 119, 138, 141, 149, 150, 151, 155, 161, 162, > 165, 166, 169, 187, 247, 251, 321 ....you can find links to different > domains anonymised as [domain-01], [domain-02], [domain-03], [domain-04]. You attempted to delete testliste02.[domain-01] via Postorius and Mailman's REST API returned a 500 status. You may find more information in mailman.log. I'm only guessing, but possibly this is because you posted to the URL <https://[domain-02]/mailman3/postorius/lists/testliste02.[domain-01]/delete>. I.e., you were accessing Postorius at https://[domain-02]/mailman3/postorius/ (domain-02) and deleting a domain-01 list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

Search results for query "sapiro"