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

[MM3-users] Re: Compression error

by Mark Sapiro

On 8/16/19 7:18 PM, Andrew Bernard wrote: > I did a git pull today. Now I get the following error and the archives wont display: > > compressor.exceptions.OfflineGenerationError: You have offline compression enabled but key "b5ae52a1ebb585c556edceb45a148cb948b2a2673d133a340a90cd02fdd34828" is missing > from offline manifest. You may need to run "python manage.py compress". Here is the original content: > > Any clues? Did you do what it says, i.e. run "python manage.py compress" or however you spell your django admin command? It isn't always necessary, but I recommend that every time you do an update, you run all four of $DJANGO_CONTROL_SCRIPT collectstatic --clear --noinput --verbosity 0 $DJANGO_CONTROL_SCRIPT compress $DJANGO_CONTROL_SCRIPT compilemessages $DJANGO_CONTROL_SCRIPT migrate where $DJANGO_CONTROL_SCRIPT is the command to run django-admin or manage.py or however you spell it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: installation

by Mark Sapiro

On 11/22/20 5:38 PM, Henry S wrote: > Thanks Mark and Brian. I'll try the suggestions. > > My IP might have got blocked by CBL when testing mailman3 against a > Gmail address. I have since removed it from CBL. I don't know how my IP > got into the Outlook's block list. Maybe a used one. Will try DKIM > signing and Microsoft programs. Outlook and friends (Hotmail, Live, MSN. ...) can be a real pain. If you're not aware, start at <https://sender.office.com/>. Also, this requires patience. It may take several back and forth emails, some of which ask questions which have already been answered earlier in the quoted thread, but in every case where I've persisted, the block has ultimately been removed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: How to create a list with → advertised=false ← by command line "mailman create [OPTIONS] LISTNAME" ?

by Mark Sapiro

On 8/4/25 11:01, Wikinaut wrote: > I use the following REST-API sequence (excerpt:) to create a list but want to use the much quicker command line. However, only a few [OPTIONS] can be set via command line. Create the list via the command line `mailman create` and specify the desired style, e.g. `private-default` for a list with `advertised = False`, `archive_policy = ArchivePolicy.private` and `subscription_policy = SubscriptionPolicy.confirm_then_moderate`. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/styles/doc… for some info on styles and see https://gitlab.com/mailman/example-mailman-plugin for information on creating a plugin to configure additional list styles. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 1 week

[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

5 years, 5 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

3 years, 8 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

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

8 years, 8 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

5 years, 5 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

5 years, 4 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

Search results for query "sapiro"