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

[MM3-users] Re: [Spam] Installation Help on Ubuntu 18

by Mark Sapiro

On 7/26/20 12:37 AM, Stephen J. Turnbull wrote: > > That's not our guide, we don't support it, and at least I don't > recognize the author offhand, can't speak for the rest of the team. The author has been involved in a few threads on this list. > Now that our NO WARRANTY notice is out of the way, I will say that > guide is written in very good style, with great attention to detail > and appropriate warnings about delicate parts of the procedure. If > you end up succeeding with it, I'll add a link to it to our docs. It is currently linked from the first paragraph at <https://wiki.list.org/DOC/Mailman%203%20installation%20experience>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: Importing config and archives only partially succeeded?

by Mark Sapiro

On 12/12/20 3:56 PM, Eric Broens via Mailman-users wrote: > After everything was imported, and I noticed that the mails were not shown in the archives for half of the mailinglists, I ran "manage.py update_index" to index the mails for all mailinglists.This command is still running for hours.Since it builds the search index, I don't expect that this would make the mails available on the webpage. I agree, that won't make the mails available on the webpage. If you're using the default Whoosh search engine, "hours" is not unexpected. Elasticsearch is much faster and Xapian faster still. What do you see in Postorius - Settings -> Archiving for the lists whose messages don't show? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Header Filter madness

by Mark Sapiro

On January 11, 2021 5:50:04 PM MST, Brian Carpenter <brian_carpenter(a)emwd.com> wrote: >I have a client whose header filters seemed to have stop working. No >matter what I try, it seems none of their header filters are being >applied. Other lists on the same server that use header filters, are >working fine. This particular header is the subject header. I can >duplicate their problem but only with their list. If I create the exact > >same header on a test list using the exact same subject line, the >header >filter does its job (moderate). Just not with this one list. Is the poster's moderation action or the list's moderation action set to accept? Moderation action accept (rather than default processing) will bypass header filters an many other rules. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

5 years, 5 months

[MM3-users] Re: MM3 to MM3 migration

by Mark Sapiro

On 1/31/23 18:35, David Newman wrote: > > > Thanks for this. Would I need to create the lists first on the new > server before restoring databases and running hyperkitty_import? No. If you transfer the database, that will bring the lists and hyperkitty archives with it. > Also, I'm unclear about there not being scripts for settings, users, > etc. –– isn't that stuff in the mailman database? Yes, it's all in the database. What I was referring to is an abstract need to export everything for a single list from the database to some kind of flat file and a way to import that into another installation, but none of that is relevant if you are going to transfer the whole database. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Mailman issues after re-boot

by Mark Sapiro

On 10/3/23 16:42, paulrubin37(a)gmail.com wrote: > > So clearly the issue is caused by the DB url: > url: postgresql://mailman:XXXXX@localhost/mailman > > something between python and PostgreSQL. > > (venv) mailman@mail:~> mailman info > Traceback (most recent call last): ... > File "/opt/mailman/venv/lib64/python3.11/site-packages/sqlalchemy/dialects/postgresql/psycopg2.py", line 690, in import_dbapi > import psycopg2 > File "/opt/mailman/venv/lib64/python3.11/site-packages/psycopg2/__init__.py", line 51, in <module> > from psycopg2._psycopg import ( # noqa > SystemError: initialization of _psycopg raised unreported exception Something is broken in psycopg2-binary. Try in your venv ``` pip install --force-reinstall psycopg2-binary\<2.9 ``` In your venv you need ``` python -c 'import psycopg2' ``` to succeed (i.e. return without reporting an error). -- 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: Congrats & MM3 Development Plans Request - Take 2

by Mark Sapiro

On 5/21/24 10:34 AM, David Wilson wrote: > > As someone who is quite interested in the Mailman3 development plans, I > tried to follow the link you provided but with no success. It timed > out. Is that still a valid or the best link? It should work. > Can you also please point me to the best source or site to get a general > understanding of short and long term *MM3 development plans*, including > various upcoming GSOC projects, including yours. You might try this one - https://wiki.list.org/x/17892316 which should take you to the top of the GSOC page. If that times out, it could be some kind of firewall issue at your end. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: Django administration - User permissions

by Mark Sapiro

On 5/29/24 11:18 AM, advorkin(a)cs.princeton.edu wrote: > > So, just to be clear, in order for someone to have an ability to create/delete a mailing list, they must be a superuser? The reason I'm asking is for security purposes and making sure that specific user has only minimal access. Currently that's true. It should be possible for a domain owner to create a list in that domain, but currently I don't think it is. > What are those Django permissions for...? Is there a use for them? Those permissions correspond to database tables, and I think they allow actions on those tables through the django admin UI. They do not (currently at least) allow any Postorius or HyperKitty UI actions. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: Announce Only List

by Mark Sapiro

On 8/14/20 12:40 PM, Allan Hansen wrote: > I set the Default action to take when a member posts to the list to ‘Discard.’ > and set the Moderation option for the few allowed posters to ‘Accept immediately (bypass other rules). Which works until someone who wants to post to or spam the list realizes that all they need to do is spoof the From: address to be one of the addresses that sent posts that they received. A more secore, but more tedious solution is to set the authorized poster's moderation action to hold and then approve valid posts. Or leave everyone's moderation action at list default and post with an Approved: <password> (pseodo)header. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rules/docs…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: Member Issue Discovered

by Mark Sapiro

On 10/28/20 1:42 PM, Brian Carpenter wrote: > > This is a bug with Affinity which I have scheduled to be fixed. However > I am confused. Data is completely removed from Mailman 3 core when you > delete the account via Postorius but not when you unsubscribe from a list? Why do you keep bringing this up? The current design of Mailman core does not remove the user when the user unsubscribes from a list, even if it is their only subscription. We know you don't like this behavior, but there are reasons for it. On the other hand, when a user removes their account, the circumstance is different and we do remove the user's information in this case because that's what the user asked for. -- 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: New Mailman 3 installation issues

by Mark Sapiro

On 5/18/21 1:21 PM, sarah.hartt(a)ionica.ca wrote: > > I am getting new entries in the django logs. > > /opt/mailman/web/logs/mailmanweb.log > > ERROR 2021-05-18 20:08:38,893 3078109 django.request Internal Server Error: /accounts/login/ > Traceback (most recent call last): ... > File "/opt/mailman/venv/lib64/python3.6/site-packages/compressor/templatetags/compress.py", line 82, in render_offline > 'is the original content:\n\n%s' % (key, original_content)) > compressor.exceptions.OfflineGenerationError: You have offline compression enabled but key "fa788b08b65fd318d68cfc5afebc18acd3e93cebffadb54d863572ad1754f368" is missing from offline manifest. You may need to run "python manage.py compress". have you run the commands: ``` mailman-web migrate mailman-web collectstatic mailman-web compress ``` The last of these is not in the doc - I'll fix that - and may be the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

Search results for query "sapiro"