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

[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

7 months, 1 week

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

[MM3-users] Re: Delete a single email or thread from hyperkitty archive

by Mark Sapiro

On 7/15/19 4:08 AM, Andrew Bernard wrote: > What is the message view? How to display that? [Pardon my ignorance - I can't see it.] I am logged in as superuser. An example of thread view is <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>, and a message view is <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> You won't see the Reattach this thread, Delete this thread or Delete this message links on those pages because you must be a superuser to see them, but they are in the right sidebar just above TAGS. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: hyperkitty installation: Unclear instructions

by Mark Sapiro

On 1/5/23 16:08, Johannes Rohr wrote: > Thanks. But can you tell me where the manage.py is that is needed for > the import command mentioned here? > > https://docs.mailman3.org/en/latest/migration.html > > python manage.py hyperkitty_import -lfoo-list(a)example.com > $var_prefix/archives/private/foo-list.mbox/foo-list.mbox When you follow the virtualenv install the Django management command is named `mailman-web`. This is shown for example at https://docs.mailman3.org/en/latest/install/virtualenv.html#run-database-mi… and the next few sections. For importing archives, it would be, with the venv active, e.g. ``` (venv)$ mailman-web hyperkitty_import -lfoo-list(a)example.com $var_prefix/archives/private/foo-list.mbox/foo-list.mbox ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: Best practice when deleting a mailing-list (archiving an old list)

by Mark Sapiro

On 9/10/24 01:06, Marc SCHAEFER wrote: > > So, is there a simple way to export a list's archives in a way it can > be reimported, now that everything seems to be in the database? Assuming you are concerned about a HyperKitty archive, there is a 'Download' button on the list's overview page. If the archive is large, this may time out in which case you can download it in pieces, e.g. via URLs like https://example.com/archives/list/<FQDN_LISTNAME>/export/filename.mbox.gz?start=2020-01-01&end=2020-12-31 to get the year 2020. -- 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: Hyperkitty archive: date format in thread overview of list does not honor DATETIME_FORMAT of settings.py

by Mark Sapiro

On 5/28/25 01:45, Christian Schneider wrote: > > Although the problem should be fixed according to this url: > https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/templates/hy… > it persists in my relatively fresh install...Hyperkitty-1.3.12, mailman-hyperkitty-1.2.1 > (According to this url https://docs.mailman3.org/en/latest/ these are the latest versions) The fix will be released in HyperKitty 1.3.13. > Is there a way to access a newer version (maybe develop-version) via pip install of Hyperkitty? pip install git+https://gitlab.com/mailman/hyperkitty.git -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 3 weeks

[MM3-users] Re: task runjobs minutely uses 100% cpu

by Mark Sapiro

On 2/12/20 4:51 AM, Bjoern Franke wrote: > Hi, > >> I installed the corresponding Debian packages: python3-xapian-haystack, >> python3-xapian, libxapian30. > > some digging: > The commit keyword was removed in > d3f1e011da3d9bebd88c78fe7a87cd6171ae650c[1] which was included in 2.1.0 > - the last release of xapian-haystack. > Later this commit was reverted in > 253c4c2898f16a5dee2c99324621a14e3e2a789b - so it's fixed only in master > of xapian-haystack. Which is why you should install via the recommended pip install git+https://github.com/notanumber/xapian-haystack.git rather than the Debian package. It would be good to report this issue to Debian so they fix their broken package. -- 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: mailman3 OWNERS_CAN_ENABLE_PERSONALIZATION option

by Mark Sapiro

On 12/2/20 5:42 PM, Henry S via Mailman-users wrote: > I am trying to change email "To" field to user's email instead of > mailing list's email. e.g. "To: <user(a)gmail.com>" instead of "To: > <mailman-users(a)mailman3.org>" In Postorius set Settings -> Alter Messages -> Personalize to Full. > I looked around old mailman configs they mentioned about adding > > OWNERS_CAN_ENABLE_PERSONALIZATION option in mm_cfg.py > > is this feature still available in mailman3 ? Can I do it via Postorius > or REST API? There is no setting in Mailman 3 to control the ability to set personalization. It is always available. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Welcome message template errors

by Mark Sapiro

On 4/22/24 17:06, Mark wrote: > > There was no line POSTORIUS_TEMPLATE_BASE_URL in /etc/mailman3/settings.py So presumably you were getting the default POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' from mailman-web/settings/mailman.py because of from mailman_web.settings.mailman import * in your settings.py. > Then, as site-owner, creating a new custom Welcome template (again via > the WebUI) I can see it correctly added to the database in > mailman.template.uri > > - > https://lists.mydomain.com/mailman3/api/templates/list/lists.mydomain.com/l… And what happens if you go to that URL in a web browser? Also what do you get when going to https://lists.mydomain.com/mailman3? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: Problems with SPOOFED_UNAUTH

by Mark Sapiro

On 9/11/25 02:42, M.Ede via Mailman-users wrote: > > Thanks for the hint, I removed authentication-results header as well as arc-authentication-results with your patch, but rspamd still results in SPOOFED_UNAUTH. > > I'm now investigating further why rspamd behaves this way. > > DKIM signing happens when sending from a non anonymous list, but with anonymous something differs ... I'm certain that the SPOOFED_UNAUT issue has nothing to do with any arc-* or authentication-results headers. I strongly suspect that the issue is because there is no DKIM signature from the From: domain. You need to investigate your DKIM signing rules to see why and fix this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 week, 2 days

Search results for query "sapiro"