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

[MM3-users] Re: Language switch

by Mark Sapiro

On 1/30/23 02:01, Massimiliano Paragnani wrote: > Hi, > I can't set other languages in MM3 web. > I did it https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/model/docs… > I tried to add language cose in settings_local.py and in mailman.cfg but nothing happens The locale for Mailman's web UI (Django) is determined by your Browser by the Accept-Language header that it sends with requests. You can also set `LANGUAGE_CODE` in settings_local.py to set a default for the installation <https://docs.djangoproject.com/en/4.1/ref/settings/#language-code>. Not that all of this requires that the appropriate compiled message catalogs exist. This requires running the Django admin `compilemessages` command. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

[MM3-users] Re: Setting configuration variables on all lists from command line

by Mark Sapiro

On 10/26/2017 08:00 AM, Peter Mueller wrote: > Hello, > > could you provide an example how I can set various configuration variables > using "mailman withlist" or "mailman "shell" on _all_ lists? > > E.g. I want to set on all lists: > m.send_welcome_message = 0 > m.send_goodbye_message = 0 $ bin/mailman shell Welcome to the GNU Mailman shell >>> from zope.component import getUtility >>> from mailman.interfaces.listmanager import IListManager >>> listmanager = getUtility(IListManager) >>> for mlist in listmanager.mailing_lists: ... print(mlist.list_name) ... mlist.send_welcome_message = False ... mlist.send_goodbye_message = False ... commit() ... >>> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 10 months

[MM3-users] Re: [SOLVED] Re: Re: Help with Newbie error -- I think I deleted my server

by Mark Sapiro

On 12/25/21 7:13 AM, William Oliver wrote: > > Just out of curiosity, if I could not have guessed a valid ID number > and did not have the admin interface, how could I have figured out what > site IDs were available? If Postorius is working, recent versions show the SITE_ID in the domains view. I.e. after you added your domain you could have noted the SITE_ID and made the change in settings before deleting the example.com domain. In any case, the django_site table in Mailman's database has the information. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: Message-Footer after migrating to Mailman3

by Mark Sapiro

On 9/1/22 03:19, Peter Münster wrote: > > My language setting is "fr", so I've copied templates/site/en > templates/site/fr and now it works. > > So no real problem, but the question remains: why did it not work with > "en"? Because of https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n… which you referenced previously ``` After all those paths are searched, the final fallback is the English template within the Mailman source tree. ``` I.e. the final fallback is to the English template in the source tree, not to a list, domain or site specific English template in Mailman's `config.TEMPLATE_DIR`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users] Re: HyperKitty failure: {"error": "'Thread' instance needs to have a primary key value before this relationship can be used."} (400)

by Mark Sapiro

On 10/19/22 15:52, armin.schoeffmann(a)aegaeon.de wrote: > OK, > quick test - your guess is correct: > Django 4.1.x is the culprit. Downgrading to 4.0.8 brought hyperkitty back to life. > Support for 4.1 was introduced with commit 0f50cae8 (Merge branch 'django4.1' into 'master'). > As I'm not familiar with mailman's dev-conventions - is there a recommended procedure to report the issue? Open an issue at https://gitlab.com/mailman/hyperkitty/-/issues/new -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[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

1 year, 9 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

7 months, 1 week

[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

5 years, 8 months

[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, 2 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, 1 month

Search results for query "sapiro"