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

[MM3-users] Re: Hyperkitty CSS issue

by Mark Sapiro

On 6/14/20 1:48 PM, Ryan Morash wrote: > I migrated my existing mailman3 install from using the Debian packages to a virtualenv setup. For the most part everything seems to be running fine, but I'm running into an issue where Hyperkitty 1.3.3 is referencing an incorrect CSS file. It is trying to load "/static/CACHE/css/hyperkitty.39ef00cc7454.css" which does not exist. If I replace that reference (using my browser's dev tools) with "/static/CACHE/css/output.12a071da81b1.css" everything looks fine. I've ran the collectstatic, compress, and migrate commands successfully with no change. Any ideas on how to fix this? Have you tried running collectstatic with the --clear option or removing everything in STATIC_ROOT before running collectstatic?, See, e.g., <https://docs.djangoproject.com/en/2.2/ref/contrib/staticfiles/> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: changing default preferred language of list

by Mark Sapiro

On 3/29/22 13:01, Paul Paulchen wrote: > > As far as I understood, it should be pretty easy. My wish: every new list we create has a default value for the preferred language: de (instead of us) ... > We put the values in: > > [mailman] > default_language: de > > "/etc/mailman.cfg" and "/opt/mailman/mailman-extra.cfg" > Nothing changes. When I create a new list via Postorius, is see the preferred language is US. This is a bug in Mailman's REST API. I just created https://gitlab.com/mailman/mailman/-/issues/997 for this. Creating the list via `mailman create` sets the list's preferred language as expected, but creating it via the REST API whoch Postorius uses does not. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: mailman-web Cleaning Up a Few Issues

by Mark Sapiro

On 11/6/25 10:23, dap1--- via Mailman-users wrote: > Odd, this is the output but none of those packages (if that is what they are) exist to be removed. > > mailman3-doc/noble-updates 3.3.8-3.1ubuntu0.1 all > mailman3-full/noble-updates 3.3.8-3.1ubuntu0.1 all > mailman3-web/noble,now 0+20200530-2.1 all [residual-config] > mailman3/noble-updates 3.3.8-3.1ubuntu0.1 all > > I've removed that cron file. And that cron is part of or maybe all of the residual-config left from mailman3-web. What happens if you do sudo apt purge mailman3-web Backup /etc/mailman3/ first in case it removes something wanted from there. Note that all this says that at some point the mailman3-web package was installed and subsequently removed but not purged. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 1 week

[MM3-users] Re: Auth question

by Mark Sapiro

On 03/26/2017 02:06 AM, David Krantz wrote: > > I have of course activated password login as it was not possible to get the > provider based logins to work (might be but not worth the time for me right > now). Is there any way for an user to request a new password when it is > forgotten? > > I presume that the Persona login is removed now. I cannot hide it in my > version or at least I do not know how. All of this is fixed in the current GitLab branches. See the login page at <https://lists.mailman3.org/accounts/login/?next=/mailman3/lists/> for example. You really need to upgrade. Please see <https://wiki.list.org/x/17891998> for a discussion of how you can do that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 6 months

[MM3-users] Re: Exception in the HyperKitty archiver: 'utf-8' codec can't encode characters

by Mark Sapiro

On 6/15/20 9:43 AM, Gilles Filippini wrote: > Hi, > > I'm seeing the above error in mailman-core logs each time an email is > processed. Is there something I missed in the configuration? I'm using > dockerized mailman 0.3 from maxking. I'm guessing you have one message in var/archives/hyperkitty/spool/ that is causing this issue. The message itself will probably have invalid utf-8 encodings in a message part declared as charset=utf-8. Every time a new message is archived, HyperKitty reprocesses this message and hits the error again. You can examine the message with `bin/mailman qfile`. It is a Python pickle of a message object. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[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

6 years, 2 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, 10 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, 9 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, 8 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

3 years

Search results for query "sapiro"