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

[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

6 months

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

[MM3-users] Re: How to upgrade to 3.10

by Mark Sapiro

On 3/3/26 12:24, Paul Tomblin via Mailman-users wrote: > ERROR: Could not find a version that satisfies the requirement nntplib; python_version >= "3.13" (from mailman) (from versions: none) > ERROR: No matching distribution found for nntplib; python_version >= "3.13" > > I guess I need to upgrade my python version? At <https://gitlab.com/mailman/mailman/-/blob/master/pyproject.toml?ref_type=he…> we require `standard-nntplib` if the python version is >= 3.13. However in Mailman 3.3.10 this line erroneously required `nntplib` rather than `standard-nntplib`. Thus the failure. I have noted before there are incompatibilities between Mailman <= 3.3.10 and Python 3.13. This is one of them. You could downgrade your Python to 3.12, but I recommend installing Mailman core from gitlab with ``` pip install git+https://gitlab.com/mailman/mailman@master ``` That version is compatible with Python 3.13. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months

[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, 4 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, 8 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, 7 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, 9 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, 3 months

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

[MM3-users] Re: Negative number for digest size

by Mark Sapiro

On 2/4/20 3:12 AM, Gila Halpern wrote: > If I set the digest size threshold to -1, will that make the digest size unlimited, and it will send once per period specified in the digest frequency setting? No. Setting digest_size_threshold to anything <=0 will send a digest on every post. You have to just set it to a very large number (or a reasonable value for the largest you want the digest to grow before it is sent). However, when periodic digests are sent has nothing to do with Digest Frequency. That setting which is misnamed and improperly described (see <https://gitlab.com/mailman/postorius/issues/395>) controls only how often the digest volume number is incremented and issue number reset. The frequency of periodic digests is controlled by when cron runs the `mailman digests --periodic` command. -- 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"