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

[MM3-users] Re: anomalous behavior

by Donato Molino

On Saturday 05 October 2024, alle 11:07, Mark Sapiro wrote: > On 10/5/24 11:01, Mark Sapiro wrote: > > > > Is there anything relevant in mailman.log? Are there messages in > > Mailman's shunt queue?. The fact that the message is archived means the > > issue is either in mailman/handlers/to_outgoing.py or > > mailman/runners/outgoing.py Great Mark! They were the permissions of /var/lib/mailman3/templates/lists I changed them from root:root to list:list and now work perfectly A thousand thanks Donato

1 year, 8 months

[MM3-users] Re: possible backscatter attack using Mailman3 servers

by Mark Sapiro

David Newman wrote: > > I have made this change. As for not having web accounts, this just means > new users cannot sign up to manage their Mailman settings, correct? I > presume existing web accounts will continue to work. That's correct.

1 year, 5 months

[MM3-users] Re: The paradox of VERP probe messages

by Jeremy Stanley

On 2025-01-29 19:26:30 -0000 (-0000), Mark Sapiro wrote: > Mark Sapiro wrote: > > > > You could submit an issue at > > https://gitlab.com/mailman/mailman/-/issues/new to make this configurable. > > I did this. See https://gitlab.com/mailman/mailman/-/issues/1195 Thanks! I would have been happy to file it, just hadn't gotten a free moment yet. -- Jeremy Stanley

1 year, 4 months

[MM3-users] Re: Confirmation emails aren't sent to users.

by Ibiam Chihurumnaya

Mark Sapiro wrote: > On 2/14/26 01:04, Stephen J. Turnbull wrote: > > mailman-web diffsettings also works. (As far as I know > > mailman-web is effectively an alias for django-admin.) > > Actually, in our recommended virtualenv install mailman-web is preferred > because django-admin doesn't load /etc/mailman3/settings.py by default. > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan I mostly use mailman-web for this reason.

4 months, 1 week

[MM3-users] Re: Opinions wanted.

by Stephen J. Turnbull

Mark Sapiro writes: > On 3/8/26 10:18, Stephen J. Turnbull wrote: > > Mark Sapiro writes: > > > > > How significant an issue do you think that is? > > > > Very, if you have 20K lists. > > That's not the issue I was asking about. That issue is if the > selection The point is a user story where it was important to be able to narrow the window conveniently. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

3 months, 2 weeks

[MM3-users] Re: Attack on Mailman Server?

by Mark Sapiro

On 3/9/23 12:34, Eggert Ehmke via Mailman-users wrote: > In the log file there are several entries like this: > > > ERROR 2023-03-09 13:09:34,066 53357 django.request Internal Server Error: /accounts/ > signup/ > Traceback (most recent call last): > File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/handlers/exception.py", > line 47, in inner > response = get_response(request) > File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/handlers/base.py", line > 181, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/opt/mailman/venv/lib/python3.9/site-packages/django/views/generic/base.py", line > 70, in view > return self.dispatch(request, *args, **kwargs) > File "/opt/mailman/venv/lib/python3.9/site-packages/django/utils/decorators.py", line 43, in > _wrapper > return bound_method(*args, **kwargs) > File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/decorators.py", line 18, in > wrap > resp = ratelimit.consume_or_429(request, action=action, **rl_kwargs) > File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/ratelimit.py", line 77, in > consume_or_429 > return render(request, "429." + app_settings.TEMPLATE_EXTENSION, status=429) > File "/opt/mailman/venv/lib/python3.9/site-packages/django/shortcuts.py", line 19, in > render > content = loader.render_to_string(template_name, context, request, using=using) > File "/opt/mailman/venv/lib/python3.9/site-packages/django/template/loader.py", line 61, in > render_to_string > template = get_template(template_name, using=using) > File "/opt/mailman/venv/lib/python3.9/site-packages/django/template/loader.py", line 19, in > get_template > raise TemplateDoesNotExist(template_name, chain=chain) > django.template.exceptions.TemplateDoesNotExist: 429.html > > So what is special about this 429.html? Django allauth is returning a 429 status because it is rate limiting due to too many requests in a short time (a bot accessing the signup page multiple times per second.) Allauth is telling Django to render a status=429 response using a 429.html template and Django can't find one. This would appear to be a django-allauth issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Phantom Email Address in Nonmember List

by Mark Sapiro

On 9/18/24 09:35, Steve Brown via Mailman-users wrote: > > Yes, that is what is happening, but only for messages from the steve@stevebrown address. I can send a screenshot and a .txt of the headers (of the message after sent back to me from MM3 and long!) but didn't see a way to do that on the archive page. Do I need to post from my gmail address? The usual behavior of most MUAs (mail clients) is to set the envelope sender to the same address as From:. In that case, you won't see an issue like this. In your case, when you send via tmdhosting servers, they set that odd bounce+... address as the envelope sender, presumably so they can do something in processing DSNs returned to that address. If you post the full headers of such a message from the list, either inline or as a .txt attachment, I'll look and say what I can. As far as getting headers from HyperKitty is concerned, if you click on a thread containing the message, there is a Download button which will produce a gzipped mbox containing the message(s) in that thread, but the headers are very minimal - only From:, To:, Subject:, Date:, Message-ID:, MIME-Version: and Content-Type:. There is also a From_ separator, but it contains the From: address, not the true envelope sender. > One clue I hadn't spotted before was a bodyhash_mismatch warning in the headers. No idea where that came from. Doesn't appear in emails from me to other addresses. Is that in Authentication-Results:? It is probably saying an original DKIM signature fails to verify because of a body mismatch which is expected if Mailman has filtered any MIME parts or added a message header or footer. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Ok, I'll install whoosh on env2 Thanks 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, 11 months

[MM3-users] Re: statistics monitoring for Mailman3

by Seth Seeger

> On Mar 12, 2021, at 12:10 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 3/11/21 8:05 PM, Mark Sapiro wrote: >> >> The data are in Mailman's smtp.log, but I'm not aware of anyone who's >> written anything to analyze it. It would be fairly easy to do depending >> on exactly what you want. > > > You inspired me. See <https://www.msapiro.net/scripts/smtp_report>. I get the following error: File "./smtp_report", line 44 print(f' {lname}: {tot}') ^ SyntaxError: invalid syntax I'm running python3 (3.5.3), and I'm afraid I don't know enough python to know what's wrong. Thanks, Seth

5 years, 3 months

[MM3-users] Re: Problem upgrading from 2.1 to 3, dockerized

by Mark Sapiro

On 8/8/25 11:43, jesper.holck--- via Mailman-users wrote: > I recently followed the instructions here https://github.com/g4rf/dockerized-mailcow-mailman, and was able to create a new Mailman 3, Debian-based installation. I then followed the instructions here https://docs.mailman3.org/en/latest/migration.html in order to migrate from my old, Centos-based installation, to the new, Debian-based installation. It seemed to work well, but unfortunately a problem showed up. > > Whenever someone posted to one of the lists on the new installation, the messages were rejected by Postfix: > > postfix-mailcow-1 | Aug 5 20:55:48 ef2b760c2e61 postfix/cleanup[8681]: B7B856099EC: message-id=<A8946B8E-2A47-4701-9548-4544981FAC5E(a)gmail.com> > postfix-mailcow-1 | Aug 5 20:55:49 ef2b760c2e61 postfix/cleanup[8681]: B7B856099EC: milter-reject: END-OF-MESSAGE from unknown[172.22.1.1]: 5.7.1 This message does not meet our delivery requirements; from=<mylist-bounces(a)myserver.dk> to=<mylistuser1(a)gmail.com> proto=ESMTP helo=<[172.19.199.4]> > postfix-mailcow-1 | Aug 5 20:55:50 ef2b760c2e61 postfix/cleanup[8681]: 216D36099EC: message-id=<A8946B8E-2A47-4701-9548-4544981FAC5E(a)gmail.com> > postfix-mailcow-1 | Aug 5 20:55:50 ef2b760c2e61 postfix/cleanup[8681]: 216D36099EC: milter-reject: END-OF-MESSAGE from unknown[172.22.1.1]: 5.7.1 This message does not meet our delivery requirements; from=<mylist-bounces(a)myserver.dk> to=<mylistuser2(a)mail.dk> proto=ESMTP helo=<[172.19.199.4]> The above messages are not messages normally seen from Postfix. They apparently come from some mailcow milter. > So, for each of the existing lists, I had to delete the old list and create a new one - with the same name and the same users. After this, everything seems to work as expected. I can think of nothing that `mailman import21` would do that would be different from creating a list, configuring it and adding members. Since you are following a third party how-to, please see https://wiki.list.org/x/12812344 - perhaps reporting this at https://github.com/g4rf/dockerized-mailcow-mailman/issues would be appropriate. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 2 weeks

Search results for query "sapiro"