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

[MM3-users] Re: Mailman3 stopped sending out mail

by Mark Sapiro

On 11/22/23 6:39 AM, webmaster(a)orcas.de wrote: > as of now I think the same as here: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > Just got it in the logs: "Uncaught runner exception: module 'time' has no attribute 'clock'". That specific issue is from using Mailman Core < 3.3.0 with Python >= 3.8. Note the current release of Mailman Core is 3.3.9. Releases less than 3.3.0 are over 4 years old. > Should we add another try catch because of circumstances like this? This is Python, not Perl or PHP. And we do catch exception and log them as we did in this case. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

[MM3-users] Re: Heads up: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated

by Mark Sapiro

On 2/10/25 01:07, Andreas Vetter wrote: > > That is unfortunately not enough to get rid of the Warning, because venv/lib/ > python3.11/site-packages/mailman_web/settings/mailman.py contains the old > ACCOUNT_AUTHENTICATION_METHOD and allauth is complains about it. In the recommended virtualenv installation, the settings that Django sees are /etc/mailman3/settings.py. That in turn contains ``` from mailman_web.settings.base import * from mailman_web.settings.mailman import * ``` but if following those imports you have ``` del ACCOUNT_AUTHENTICATION_METHOD ``` Django won't see it and won't complain. Did you actually try this? If so, did you put the `del ACCOUNT_AUTHENTICATION_METHOD` after `from mailman_web.settings.mailman import *` in /etc/mailman3/settings.py? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Handling of SPAM mails in mailman3 - Do not append original mail to moderation mail

by Mark Sapiro

On 1/18/20 7:11 AM, Torge Riedel wrote: > > I agree. So how to proceed on that? Get developers involved, post > somewhere a feature request? To be honest I don't know how this is > handled in development community of mailman3. You can post to mailman-developers(a)python.org, but such things tend to get put aside and forgotten. The best way to report a bug, feature request, issue, etc is to use the trackers at gitlab.com. In the case of Mailman core, this is <https://gitlab.com/mailman/mailman/issues> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

[MM3-users] Re: Hacking attempts?

by Mark Sapiro

On 7/14/22 12:29 AM, Lists via Mailman-users wrote: > > Is this a problem with our setup? i.e. the “Internal Server Error” bit, or are the hackers just sending bad data that is causing the error? also how do we stop/block this? You have Fedora enabled as one of your social account oAuth providers, but it is may be misconfigured or just broken?. Is it possible to log in via fedora at all? If you don't want/need it, just remove it. I am curently traveling and on my way home and don't have time to provide details of removal, but if you need help, ask and I or someone will respond. -- 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: Removing Moderators

by Mark Sapiro

On 7/21/24 13:39, steve.bachinsky(a)tena-sda.org wrote: > In the case of adding a moderator based on an email address, it is unclear whether there is already a user associated with that email address or not. So I tried to use the "moderator = user_manager.make_user(email)" interface. However, when trying to use "mlist.subscribe(moderator, MemberRole.moderator)", I get an error that User must have preferred address. And while I can set "moderator.preferred_address = email", I then get error that there is no attribute "verified_on", and I can't set that on the User. moderator.preferred_address needs to be set to an Address object, not an email. I.e. moderator.preferred_address = user_manager.get_address(email) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: Caching problem with templates

by Mark Sapiro

On 6/26/25 04:25, Mark wrote: > > A footer template is created and initially it works as expected. > > Editing the footer template sees the new content written to the database, > > In addition to viewing the edited content in the database, the new > template can also be viewed in Lynx on localhost at: > > http://localhost:8000/mailman3/api/templates/list/<IDENTIFIER>/list:member:regular:footer > > The problem is that the original template is being cached somewhere and > the old footer persists in new emails. What does the database query ``` SELECT uri FROM template WHERE name = 'list:member:regular:footer' AND context = '<IDENTIFIER>'; ``` return? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months

[MM3-users] Re: Missing Base64 encoding from control message reply

by Mark Sapiro

On 9/24/23 07:20, Stephen J. Turnbull wrote: > > The only thing I can think of at the moment that might move the > discussion forward is if Mark knows how to run his test in your Docker > environment to see if it also produces > Content-Type: text/plain; charset="US-ASCII" > Content-Transfer-Encoding: 7bit Assuming there is not something like ``` [language.en] charset: utf-8 ``` in your mailman.cfg overriding the default us-ascii charset for English, if you send a message From: yourself to list-confirm-xxxxxxx(a)example.com with Subject: Re: Your confirmation is needed to join the list(a)example.com mailing list (replacing list and example.com with the actual list and domain), you should receive a response like (some headers removed) ``` Subject: The results of your email commands From: list-bounces(a)example.com To: mark(a)example.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-ID: <169556563227.2592.7908020161516725770(a)example.com> Date: Sun, 24 Sep 2023 07:27:12 -0700 Precedence: bulk X-Mailman-Version: 3.3.9b1 List-Id: A test list <list.example.com> List-Help: <mailto:list-request@example.com?subject=help> List-Owner: <mailto:list-owner@example.com> List-Subscribe: <mailto:list-join@example.com> List-Unsubscribe: <mailto:list-leave@example.com> The results of your email command are provided below. - Original message details: From: Mark Sapiro <mark(a)example.com> Subject: Re: Your confirmation is needed to join the list.example.com mailing list. Date: Sun, 24 Sep 2023 07:27:10 -0700 Message-ID: <20230924142710.GA23819(a)example.com> - Results: Confirmation token did not match - Done. ``` What do you get? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: mail loops back to myself

by Mark Sapiro

On 6/13/25 01:59, Florian Sukup wrote: > > > On 6/13/25 01:58, Mark Sapiro wrote: > >> but I'm at a loss to understand the issue, unless your >> /etc/postfix/master.cf is missing an uncommented entry for lmtp like >> ``` >> lmtp unix - - y - - lmtp >> ``` >> > > I found it there, here is my master.cf: I realized after the fact that that probably wasn't the issue because it probably would have logged an error. > mailman unix - n n - - pipe > flags=FRX user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py > ${nexthop} ${user} > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > Is the last line a problem? It seems to be from mailman2. It's a Debian thing for an unsupported MM 2.1 process to deliver mail to Mailman. It doesn't do any harm if it's not referenced in main.cf. > Is there a possibility to debug in more detail? To find out when and > where it takes the wrong turn? I'm unable to see where this is going wrong. I think it is a Postfix issue, not a Mailman issue per se, and while we make a best effort to help with Postfix-Mailman integration issues we are not the primary support resource for Postfix which is the postfix-users(a)postfix.org mailing list. See https://www.postfix.org/lists.html for info on subscribing and posting. Also, since you are dealing with Debian packages, the primary support resource is Debian. 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

8 months, 2 weeks

[MM3-users] Re: howto reallow a banned email ?

by Mark Sapiro

On 6/18/19 9:12 PM, Nicolas Pettiaux wrote: > > By mistake a user has been banned to post to mailman list. How can I > allow him not only to post but also to become a member of a list ? > > I have not found any info on the web, or I have been unable to search > correctly. Do you have the Postorius web UI in your installation? If so go to the list's Ban List and remove the unwanted entry. Or is this perhaps a Mailman 2 question? If so you'll find the ban_list in the web admin UI at Privacy options... -> Subscription rules. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

[MM3-users] Re: Mailman REST API not available. Please start Mailman core.

by Mark Sapiro

On 7/26/20 12:00 AM, joseverde(a)gmail.com wrote: > Okay, so I got the webservice of Mailman3 up and running, but when I go to mailman3/postorius/lists/, I get the following error: > > Something went wrong > Mailman REST API not available. Please start Mailman core. Do your settings in the webservice section of mailman.cfg for things like: admin_pass: restpass admin_user: restadmin hostname: localhost port: 8001 (Defaults shoun) match your Django settings MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' MAILMAN_REST_API_URL = 'http://localhost:8001' Also, is Mailman's `rest` runner running ps -fwwA|grep runner=rest should show 3 processes. The runner and 2 workers. -- 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

Search results for query "sapiro"