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

[MM3-users] Re: Upgrade Mailmam Core from

by Mark Sapiro

On 9/27/22 05:42, sascha.rissel(a)gmail.com wrote: > For the moment, I ignored this error > error: invalid command 'bdist_wheel' > ---------------------------------------- > ERROR: Failed building wheel for mailman > > and carried on, with creating a configuration file at /etc/mailman3/mailman.cfg for Mailman Core. > I notice that directory /etc/mailman3 has not been creating during mailman setup from with venv. > > Is this correct? > Shall I manually create this directory or persist mailman.cfg at some other location where system user mailman has permissions to? I suggest you remove the venv and start over ensuring you do `sudo su mailman` before creating the venv. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: Archiving Display Email Signature in Plain-Text

by Mark Sapiro

On 3/5/26 13:58, msok--- via Mailman-users wrote: > The Archiving is still display Email Signature in Plain-Text after I configured filter content: No and convert html to plaintext: No in Alter Messages. And Markdown text in Archiving settings. In addition to that, I also configured HYPERKITTY_RENDER_INLINE_IMAGE = True in settings.py file Have you set the list's Archive Rendering mode to Markdown? HYPERKITTY_RENDER_INLINE_IMAGE is only effective for markdown rendering. Also, I'm not certain this is the case, but normally, HyperKitty only displays text/plain parts of a message and other parts are shown only as links to attachments to be downloaded. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 2 weeks

[MM3-users] Re: venv and upgrade from python 3.11 to 3.13 because of OS-upgrade

by Mark Sapiro

On 3/12/26 07:05, Stephen J. Turnbull wrote: > Andreas Vetter writes: > > > How should I upgrade? > > I haven't done this, so take it with a grain of salt. > <instructions snipped> Steve's suggestion is good, however there are a couple of incompatibility issues between the currently released version of Mailman core and Python 3.13 and also between mailman-web and django-allauth. For this reason you should upgrade these in your venv from GitLab. pip install git+https://gitlab.com/mailman/mailman@master pip install git+https://gitlab.com/mailman/mailman-web@master -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 1 week

[MM3-users] Re: Updated script for checking and fixing mbox files.

by Mark Sapiro

On 1/19/23 23:47, Odhiambo Washington wrote: > > At what point does an MM3 List Admin require this script? > I am unable to figure that out :-) The script is useful for finding and cleaning up issues in mbox files to be used as input to hyperkitty_import. The normal flow would be to process the mbox with cleanarch3 to fix any unescaped From lines and bad Date: headers and then check the mbox with the ck_hk_import script to identify any messages in the mbox that might throw uncaught exceptions in hyperkitty_import and manually fix or remove those, and finally run hyperkitty_import. -- 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: Problems getting MM3 to work

by Mark Sapiro

On 4/24/23 8:18 AM, Alain D D Williams wrote: > > It thinks that my domain is example.com ... when I 'grep -r example.com /opt/mailman' > I see 11338 lines - far too many to look through. > > Could someone please tell me what/where I configure to enter my test domain. The Postorius Domains view will show you the SITE_ID for your domain. In /etc/mailman3/settings.py you probably have SITE_ID = 1 Change that to the value from the Postorius Domains view. If you have more than one domain, you can set SITE_ID = 0 and that should show the domain from the http request. -- 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: When QQ email sends emails to the Mailman service set up by oneself, members of the list who use QQ email cannot receive the emails, and it shows that the emails are rejected.

by Mark Sapiro

On 5/10/24 18:36, rqchen(a)cnic.cn wrote: > When QQ email sends emails to the Mailman service set up by oneself, members of the list who use QQ email cannot receive the emails, and it shows that the emails are rejected. Is this a DMARC issue? Does the list apply DMARC mitigations? -- 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: Mailman REST API not available. Please start Mailman core.

by Mark Sapiro

On 2/12/25 12:17, Odhiambo Washington via Mailman-users wrote: > > rm -rf /opt/mailman > mkdir /opt/mailman > chown mailman:mailman /opt/mailman > chmod 755 /opt/mailman > sudo su mailman > cd > pwd [should show that you are in /opt/mailman] > > Start over again from there. But if you currently have a working Mailman installation, maybe even a Debian package, and you don't want to start over from scratch, especially because you have Python 3.7.3 and current Mailman requires Python >=3.9,<=3.12, just see <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> -- 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: Heads up: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated

by Mark Sapiro

On 8/1/25 11:58, Wikinaut wrote: > > WARNINGS: > ?: settings.ACCOUNT_EMAIL_REQUIRED is deprecated, use: settings.ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] > > > > My # Mailman Web configuration file: > # /etc/mailman3/settings.py > > # Get the default settings. > from mailman_web.settings.base import * > from mailman_web.settings.mailman import * > > # Settings below supplement or override the defaults. > # see https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > del ACCOUNT_AUTHENTICATION_METHOD > ACCOUNT_LOGIN_METHODS = {'email', 'username'} In addition to the above add ``` del ACCOUNT_EMAIL_REQUIRED ACCOUNT_SIGNUP_FIELDS = ['username*', 'email*', 'password1*', 'password2*'] ``` -- 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: Can disabled users enable themself?

by Mark Sapiro

On 7/9/26 07:33, Flo via Mailman-users wrote: > > I created a weblate account and changed it. Now I checked the > repository: There is the correct translation, however, it comes after "" > and takes 3 lines. Maybe this is correct, however, it looks different > than the others. It's just the way long lines are handled. In this case the content of the three lines ``` msgstr "" "Ihre Mitgliedschaft in der Mailingliste ${mlist.display_name} wurde " "deaktiviert" ``` will be concatenated into a single string. There won't be any actual line breaks unless there are '\n' in the string. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 1 week

[MM3-users] Re: Mass change Digest delivery mode

by Mark Sapiro

On 8/4/26 9:34 PM, iMark wrote: > > Le 2026-08-05 04:02, Mark Sapiro a écrit : > >> In Python, block structure is defined by indentation which is >> critical. In interactive mode, a `>>> ` prompt indicates you are at >> the outer level and a `... ` prompt indicates you are in a block. >> > > >> The complete interaction should look like >> ``` >>>>> for member in m.members.members: >> ... if member.delivery_mode != DeliveryMode.regular: ... >> member.delivery_mode = DeliveryMode.plaintext_digests >> ... >>>>> commit() >> ``` Note the above has a formatting error. See my followup post correcting that. > I got to the last line ( member.delivery_mode = > DeliveryMode.plaintext_digests ) and entered it to then get the ellipsis > (as you've shown). > > What happens after that so I can get back to the outer level (>>>>) and > commit ? > > If I hit Enter, I get this error Enter is the appropriate thing. It then runs the block. > ... > Traceback (most recent call last): > File "<console>", line 3, in <module> > AttributeError: property 'delivery_mode' of 'Member' object has no setter And upon running the block it encounters the above error. Unfortunately when I tested this, I tested on a list with only regular members and didn't encounter the error. The last line ``` member.delivery_mode = DeliveryMode.plaintext_digests ``` needs to be ``` member.preferences.delivery_mode = DeliveryMode.plaintext_digests ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 weeks, 2 days

Search results for query "sapiro"