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

[MM3-users] Re: API access to Hyperkitty

by Abhilash Raj

On Tue, Feb 9, 2021, at 10:44 AM, Mark Sapiro wrote: > On 2/9/21 10:23 AM, Brian Carpenter wrote: > > Is it possible to download Hyperkitty's archives to a remote server via > > an API? Is there documentation that explains how to accomplish this task? > > > > > I don't think there is documentation, but if you look at the target of > any `download` button, it should be obvious. I.e. the link to download > the entire archive for this list is > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/export/… > > The `mailman-users(a)mailman3.org-2021-02.mbox.gz` part is the name of the > file to download to and the `-2021-02` part can be anything or nothing, > but the name must begin with the list posting address and end with > `.mbox.gz`. > > If the archive is large, this can time out in which case adjust `start` > and `end` to download it in pieces. Hyperkitty also has a traditional REST API, which can be used to ingest archives on a different server that doesn’t necessarily want to deal with mboxes. The documentation comes with Hyperkitty and is typically available at “/api” in Hyperkitty. So something like this on our server: https://lists.mailman3.org/archives/api/ There is also a “HTML” version where you can actually browse through the API like a webpage. It returns Json/XML/txt when you ask for it. The above page should have the details. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

4 years, 4 months

[MM3-users] Re: Set member.moderation_action via REST API as part of message approval?

by Mark Sapiro

On 3/3/25 14:27, Andy Matthews wrote: > We're using Mailman 3.3.9. > > Entity<Form> data = Entity.entity(form, MediaType.APPLICATION_FORM_URLENCODED_TYPE); > response = getTarget().path("lists/" + listId + "/config").request().method("PATCH", data); You are patching the list's config and with that patch you are replacing the old value of `accept_these_nonmembers` with the new, not appending the new value. You would need to retrieve the existing value, update it and PATCH that. However, as you know, that setting is deprecated and exists only to support the regexp and @list type of entries. For explicit email addresses, the intent is to create a nonmember and set the nonmember's moderation_action to `defer` - you normally don't want `accept` because that bypasses all the subsequent checks such as administrivia, implicit-dest, max_recipients, max_size, , no_subject, etc. > The result of these two API calls is that both the subscribers and nonmembers properties of the mailing list are updated to include the new email (let's call it abc(a)123.com) The user can immediately send another email which is not held for moderation. The issue comes when a different nonmember sends an email and is approved (let's call it xyz(a)789.com) For some reason this blows out the "always accept" status of user abc(a)123.com and requires their email to be approved again. > > After some research I believe this is because the `accept_these_nonmembers` property has been deprecated (which seems valid because that property remains an empty array). Additional reading seems to indicate that we can now set `moderation_action` on each individual user which supercedes the mailing list's `default_nonmember_action` property (in our case it is `Action.hold`). That is correct, and that is the intended way to deal with nonmember moderation. > The docs indicate that I should be able to submit a patch request to update the moderation action for any user: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > > But it requires the user ID. And when trying to get the user_id for a nonmember it appears that it is not returned by the API. The following call: > `/3.0/addresses/abc(a)123.com` > > returns > ``` > { > "email": "abc(a)123.com", > "original_email": "abc(a)123.com", > "registered_on": "2025-03-03T19:18:35.169703", > "self_link": "https://0.0.0.0:8001/3.0/addresses/abc@123.com", > "http_etag": "\"92c44d0b3b323450f3576e6352acb59b4cc5d6f0a\"" > } > ``` > So I'm not sure how I would be able to update this particular record without a member or user id. > > So, all that said, I'm looking for information on how to do one of the following. > > 1. When submitting a user's email to the `accept_these_nonmembers`, is there a way to indicate that the `member.moderation_action` should be a specific value? No. You can put the email in the appropriate *_these_nonmembers, but that does only that. It doesn't affect the nonmember's moderation_action, nor does it create a nonmember if there isn't one already, but if there is a nonmember with non-None moderation_action, that action takes precedence over *_these_nonmembers. > 2. Retrieve a nonmember record and have it include a member or user id that I can use to explicitly update the `member.moderation_action` value? You must be able to set a nonmember's moderation_action via REST. (The docs may need updating.) Postorius does it, so it can be done, but I don't offhand know the endpoint and I'm leaving the country for vacation tomorrow and don't have time to research it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 1 week

[MM3-users] Re: User settings triggers error

by Mark Sapiro

On 6/16/20 12:18 PM, Mark Dadgar wrote: > On Jun 16, 2020, at 11:47 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >>> File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py" in call >>> 99. raise HTTPError(url, response.status, content, response, None) >> >> And gets a 500 from core. >> >> >>> During handling of the above exception (HTTP Error 500: b'A server error occurred. Please contact the administrator.'), another exception occurred: >> >> >> Which we aren't interested in. >> >> The next step is to look in core's mailman.log to see what the rest call >> was and the exception and hopefully traceback the caused the 500 response. > > > Here’s what’s logged during that error: > > Jun 16 12:16:54 2020 (1326) 127.0.0.1 - - "GET /3.1/users/mark(a)pdc-racing.net HTTP/1.1" 200 432 > Jun 16 12:16:54 2020 (1326) REST request handler error: > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1245, in _execute_context > self.dialect.do_execute( > File "/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py", line 581, in do_execute > cursor.execute(statement, parameters) > psycopg2.errors.UndefinedFunction: operator does not exist: text = uuid > LINE 4: WHERE "user"._user_id = '05dcbeb4-b784-45eb-96f8-6f9e4b7ab6c... > ^ > HINT: No operator matches the given name and argument types. You might need to add explicit type casts. > > > The above exception was the direct cause of the following exception: > > Traceback (most recent call last): > File "/usr/lib/python3.8/wsgiref/handlers.py", line 137, in run > self.result = application(self.environ, self.start_response) > File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 50, in wrapper > rtn = function(*args, **kws) > File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 218, in __call__ > return super().__call__(environ, start_response) > File "falcon/api.py", line 232, in falcon.api.API.__call__ > File "falcon/api.py", line 229, in falcon.api.API.__call__ > File "falcon/api.py", line 582, in falcon.api.API._get_responder > File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 131, in find > attribute = getattr(resource, name, MISSING) > File "/usr/lib/python3/dist-packages/mailman/rest/users.py", line 203, in _user > return user_manager.get_user_by_id(user_id) > File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File "/usr/lib/python3/dist-packages/mailman/model/usermanager.py", line 94, in get_user_by_id > if users.count() == 0: > File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 3630, in count > return self.from_self(col).scalar() > File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 3355, in scalar > ret = self.one() > File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 3325, in one > ret = self.one_or_none() > File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 3294, in one_or_none > ret = list(self) > File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 3367, in __iter__ > return self._execute_and_instances(context) > File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 3392, in _execute_and_instances > result = conn.execute(querycontext.statement, self._params) > File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 982, in execute > return meth(self, multiparams, params) > File "/usr/lib/python3/dist-packages/sqlalchemy/sql/elements.py", line 287, in _execute_on_connection > return connection._execute_clauseelement(self, multiparams, params) > File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1095, in _execute_clauseelement > ret = self._execute_context( > File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1249, in _execute_context > self._handle_dbapi_exception( > File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1476, in _handle_dbapi_exception > util.raise_from_cause(sqlalchemy_exception, exc_info) > File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 398, in raise_from_cause > reraise(type(exception), exception, tb=exc_tb, cause=cause) > File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 152, in reraise > raise value.with_traceback(tb) > File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1245, in _execute_context > self.dialect.do_execute( > File "/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py", line 581, in do_execute > cursor.execute(statement, parameters) > sqlalchemy.exc.ProgrammingError: (psycopg2.errors.UndefinedFunction) operator does not exist: text = uuid > LINE 4: WHERE "user"._user_id = '05dcbeb4-b784-45eb-96f8-6f9e4b7ab6c... > ^ > HINT: No operator matches the given name and argument types. You might need to add explicit type casts. > > [SQL: SELECT count(*) AS count_1 > FROM (SELECT "user".password AS user_password, "user".id AS user_id, "user".display_name AS user_display_name, "user"._user_id AS user__user_id, "user"._created_on AS user__created_on, "user".is_server_owner AS user_is_server_owner, "user"._preferred_address_id AS user__preferred_address_id, "user".preferences_id AS user_preferences_id > FROM "user" > WHERE "user"._user_id = %(user_id_1)s) AS anon_1] > [parameters: {'user_id_1': UUID('05dcbeb4-b784-45eb-96f8-6f9e4b7ab6cb')}] > (Background on this error at: http://sqlalche.me/e/f405) > Jun 16 12:16:54 2020 (1326) 127.0.0.1 - - "GET /3.1/users/05dcbeb4b78445eb96f86f9e4b7ab6cb/addresses HTTP/1.1" 500 59 > Jun 16 12:16:54 2020 (1326) REST request handler error: > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1245, in _execute_context > self.dialect.do_execute( > File "/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py", line 581, in do_execute > cursor.execute(statement, parameters) > psycopg2.errors.UndefinedFunction: operator does not exist: text = uuid > LINE 4: WHERE "user"._user_id = '05dcbeb4-b784-45eb-96f8-6f9e4b7ab6c... > ^ > HINT: No operator matches the given name and argument types. You might need to add explicit type casts. This looks like another manifestation of the issue reported at https://gitlab.com/mailman/django-mailman3/-/issues/35 and https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… If you are running django-mailman3 1.3.3 and haven't upgraded to django-mailman3 1.3.4, see the above list post for a workaround. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: How to identify the exact reason behind the shunting of the mails ?

by Shashikanth Komandoor

Thank you Mark, Then I will try to upgrade the version Thank you once again. On Fri, Jun 18, 2021 at 8:01 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/18/21 6:48 AM, Shashikanth Komandoor wrote: > > Dear Mark, > > > > FYI, I observed this issue with the postfix that receives the > > mails from the previous MTA and hands it over to the mailman. But I fixed > > at postfix by upgrading it to the version postfix 3. > > > > But still Mailman is not able to understand Hindi (Indian > local > > language) in which language the display names of the email ids are there. > > > > So, now what to do at Mailman so that it can also understand > > local languages or any work around or other alternate solutions for these > > sort of cases. > > > As noted in my reply at > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > the issue is a Mailman bug which is fixed in the next release. It has to > do with the fact that the display names are RFC 2047 encoded and not the > particular encoding. > > Actually, the fix at > https://gitlab.com/mailman/mailman/-/merge_requests/841 depends on > https://gitlab.com/mailman/mailman/-/merge_requests/652 which was > released in Mailman 3.3.2. A complete patch for versions < 3.3.2 is > attached. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

3 years, 11 months

[MM3-users] Re: Avoiding non-members to be saved.

by Mark Sapiro

On 8/7/21 4:55 AM, Stephen J. Turnbull wrote: > Guillermo Hernandez (Oldno7) via Mailman-users writes: > > > Yesterday I had a problem with a private list. A spammer sent a mail > > forging one address that was a non-member (in fact was an "accept this > > no subscriber mails" from mailman 2.1 import) with very bad intentions > > and it was distributed. > > If you upgrade from Mailman 2 to Mailman 3, the accept_these_nonmembers > list for each list is grandfathered into the Mailman 3 list (from > rules/moderation.py): > > # Check the '*_these_nonmembers' properties first. XXX These are > # legacy attributes from MM2.1; their database type is 'pickle' and > # they should eventually get replaced. > for action_name in ('accept', 'hold', 'reject', 'discard'): > legacy_attribute_name = '{}_these_nonmembers'.format( > action_name) > > > There were no list of "accept this non members" in the Postorius > > config > > If there is no such list in Postorius, I would guess that some > developer thought "OK, this is a legacy feature and I'll get back to > it when we move it to the proper database" (unfortunate, but most of > us have open-subscription member-posts-only lists, and the current > workflow seems to work well, so this feature may not be so salient). Moderation in MM 3 works as follows: Is poster address a member. If so apply the member's moderation action, else Does poster address appear or match a pattern in the legacy (accept|hold|reject|discard)_these_nonmembers (first match in that order). If so, apply the appropriate action, else If the poster address is not a non-member, add it as a nonmember and apply the default nonmember moderation. > > I think it is solved now (deleting all and putting to hold just the > > non-members addresses that I would want to pass messages on) > > This should not be necessary, unless there were pre-approved addresses > that are no longer appropriate. But Mailman can't know that! The import21 process imports *_these_nonmembers by adding any regexps to the corresponding MM 3 *_these_nonmembers and adding any addresses as nonmembers with the appropriate moderation action. > > The fact is that any sender address of mails sent to the list is saved > > as a "non member", and it make me nervous as it will grow despite it is > > a legitimate message or not. This is the way MM 3 works. The only reason *_these_nonmembers exists in MM 3 is to support the legacy regexps from MM 2.1. For non-regexp addresses the address is a nonmember with the appropriate moderation action. I actually find this convenient. When a nonmember posts spam to a list and that spam is held, I discard the spam in Postorius and at the same time set the nonmember's moderation action to discard so I never see any more from that address. Also, when someone who I recognize as a list member posts from an alternate nonmember address, I can accept that post and set the nonmember address moderation action to default processing. > As far as I can see there is no other rule except that legacy rule > (and the rule that accepts all posts, which is rarely used) that will > accept a post from nonmembers. As I note above, nonmembers and members alike have a moderation action which can be any of Hold, Reject (with notice), Discard (no notice), Accept (without any further checks), Default Processing (continue with additioal checks) or the list's default action for (non)members. -- 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: Problems after upgrading from bullseye to bookworm

by Thomas Ward

FYI I updated my workaround on the linked issues on Gitlab to reflect this. Technical Note that this may not apply after the PDM backend updates which are in the works to not normalize metadata (which causes this problem). I have not tested a fresh setup yet since the issue was first identified but it is possible the issue is easily resolved once updated versions of these flufl libraries land in PyPI with the pdm backend fixes in place for the build envs of those libraries. Sent from my Galaxy -------- Original message -------- From: Mark Sapiro <mark(a)msapiro.net> Date: 6/26/23 16:23 (GMT-05:00) To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Problems after upgrading from bullseye to bookworm On 6/26/23 12:35 PM, Ken Alker wrote: > I'm brand new to this, so take this with a grain of sale, but, I had a similar problem a few days ago, however, mine was "flufl.i18n>=3.2". Perhaps the same thing is happening with flufl.lock (but that didn't bite me). > > I solved my problem by following this: <https://gitlab.com/mailman/mailman/-/issues/1085> and, ultimately modifying "$VENV_ROOT/lib/$PYVERSION/site-packages/mailman-3.3.8.egg-info/requires.txt" per that thread (see <https://gitlab.com/mailman/mailman/-/issues/1085#note_1442207929> by Thomas Ward section called "The WORKAROUND"). Maybe you need to do the same thing, but for flufl.lock. Yes, the same issue now affects flufl.lock as well as flufl.i18n. You will need to change both flufl.lock->flufl_lock and flufl.i18n->flufl_i18n. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to teward(a)thomas-ward.net

1 year, 11 months

[MM3-users] Re: New year releases!

by Mark Sapiro

On 1/4/23 13:54, Dan Caballero wrote: > I'm attempting this upgrade in my test environment which is a Docker container with Python 3.9.10 virtual environment. I was able to upgrade all the Python requirements but when I run mailman-web migrate I get an error. It seems related to the mailman-web package. See output below. > > > "(mailmanve) mailman@1d0e3a230c94:/var/www/mailman-www$ mailman-web migrate > Traceback (most recent call last): > File "/opt/mailmanve/bin/mailman-web", line 33, in <module> > sys.exit(load_entry_point('mailman-web==0.0.6', 'console_scripts', 'mailman-web')()) > File "/opt/mailmanve/lib/python3.9/site-packages/mailman_web/manage.py", line 37, in main > execute_from_command_line(sys.argv) > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line > utility.execute() > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/management/__init__.py", line 440, in execute > self.fetch_command(subcommand).run_from_argv(self.argv) > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/management/base.py", line 402, in run_from_argv > self.execute(*args, **cmd_options) > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/management/base.py", line 448, in execute > output = self.handle(*args, **options) > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/management/base.py", line 96, in wrapped > res = handle_func(*args, **kwargs) > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/management/commands/migrate.py", line 97, in handle > self.check(databases=[database]) > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/management/base.py", line 475, in check > all_issues = checks.run_checks( > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/checks/registry.py", line 88, in run_checks > new_errors = check(app_configs=app_configs, databases=databases) > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/checks/urls.py", line 14, in check_url_config > return check_resolver(resolver) > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/checks/urls.py", line 24, in check_resolver > return check_method() > File "/opt/mailmanve/lib/python3.9/site-packages/django/urls/resolvers.py", line 494, in check > for pattern in self.url_patterns: > File "/opt/mailmanve/lib/python3.9/site-packages/django/utils/functional.py", line 57, in __get__ > res = instance.__dict__[self.name] = self.func(instance) > File "/opt/mailmanve/lib/python3.9/site-packages/django/urls/resolvers.py", line 715, in url_patterns > patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module) > File "/opt/mailmanve/lib/python3.9/site-packages/django/utils/functional.py", line 57, in __get__ > res = instance.__dict__[self.name] = self.func(instance) > File "/opt/mailmanve/lib/python3.9/site-packages/django/urls/resolvers.py", line 708, in urlconf_module > return import_module(self.urlconf_name) > File "/usr/local/lib/python3.9/importlib/__init__.py", line 127, in import_module > return _bootstrap._gcd_import(name[level:], package, level) > File "<frozen importlib._bootstrap>", line 1030, in _gcd_import > File "<frozen importlib._bootstrap>", line 1007, in _find_and_load > File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked > File "<frozen importlib._bootstrap>", line 680, in _load_unlocked > File "<frozen importlib._bootstrap_external>", line 850, in exec_module > File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed > File "/var/www/mailman-www/urls.py", line 20, in <module> > from django.conf.urls import include, url > ImportError: cannot import name 'url' from 'django.conf.urls' (/opt/mailmanve/lib/python3.9/site-packages/django/conf/urls/__init__.py)" In Django 3.1 django.conf.urls.url was a deprecated alias to django.urls.re_path and in Django 4.0 it was removed. See, e.g. <https://docs.djangoproject.com/en/3.2/ref/urls/> and <https://docs.djangoproject.com/en/4.0/ref/urls/>. However, the above Traceback doesn't identify which module contains the from django.conf.urls import include, url import. If I look through our sources, I only find this import in mailman-suite/mailman-suite_project/urls.py as an example. You need to look at your urls.py files. Try something like grep -r 'from django.conf.urls import include, url' /opt/mailmanve/lib/python3.9/site-packages/ to find which module contains that import. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I have installed rubygem-sass and added the config to settings.py previously and even executed this command: # Copy all the static files to one single location. $ python2 manage.py collectstatic I tested the commands you suggested and this is what I got: (env2) [mailman@localhost mailman-suite_project]$ pwd /var/lib/mailman/mailman-suite/mailman-suite_project (env2) [mailman@localhost mailman-suite_project]$ django-admin collectstatic --clear No Django settings specified. Unknown command: 'collectstatic' Type 'django-admin help' for usage. El mié., 2 ago. 2017 a las 10:56, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/02/2017 07:55 AM, Rafael Mora wrote: > > HyperKitty is looking for some files in /static/CACHE/... but it doesn't > > find them: > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > 404 > > 105 > > [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > 404 > > 105 > > > > > > Should I run any command to activate the CACHE dir? > > > You need to ensure you have a working sass compiler. As I said at > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > >, > See the third bullet under > <http://docs.list.org/en/latest/prodsetup.html#dependencies>. > > Then you need to run commands like > > django-admin collectstatic --clear > django-admin compress > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 10 months

[MM3-users] Re: 'Failed adding message' error when migrating a list from mailman2 to mailman3

by Prasanth Nair

Thank you, Mark. Kind regards, Prasanth On Thu, 14 Oct 2021 at 19:17, Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/14/21 9:04 AM, Stephen J. Turnbull wrote: > > Prasanth Nair writes: > > > > > *2%Failed adding message <mailman.2.1593699619.32248>: 'ascii' codec > can't > > > encode character '\ufffd' in position 252: ordinal not in > range(128).* > ... > > > I ran the check_hk_import script before migrating and it was not > > > giving any error. > > > > In order to catch this kind of error, the check script would have to > > pretty much do the import but throw it away. > > > The check_hk_import script > <https://www.msapiro.net/scripts/check_hk_import> is designed to detect > and report conditions which would cause the django hyperkitty_import > process to abort and stop processing the mbox. It doesn't catch errors > like the above, but these are non-fatal and just cause the offending > message to be skipped. > > As Steve says, the Message-ID was reported so find it in the mbox and if > you want it in the archive, extract it from the mbox, fix it and then > just rerun the import with just that message as input[1] and a > --since=1970-01-01 option. > > Note the issue could be in a header, but also could be in a body part > implicitly or explicitly declared as charset="us-ascii". > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 7 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/search

by Odhiambo Washington

I'll create the merge request. On Sat, Jan 28, 2023, 21:49 Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/28/23 09:39, Odhiambo Washington wrote: > > Now that you have mentioned > > > https://gitlab.com/mailman/mailman-suite-doc/-/blob/master/source/install/v…, > , > > please show me how to import it, edit. Then I can submit a diff. > > Alternatively, I'd love to be given access to edit that document (and the > > edit can be reviewed before getting published) to make it easy to follow > by > > someone with zero python background. > > I am willing to invest some time in improving it for laymen. > > > There are multiple ways to proceed. The simplest is to just download > > https://gitlab.com/mailman/mailman-suite-doc/-/blob/master/source/install/v… > (there's a download button on that page), edit that and post the edited > file somewhere where we can get it to look at. > > The better way is more complex. That way is for you to create a personal > project space at https://gitlab.com/users/sign_up and clone the > mailman/mailman-suite-doc project into your personal space and edit it > there and then create a merge request to merge your edits into the > mailman/mailman-suite-doc project. GitLab documentation is at > https://gitlab.com/help > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to odhiambo(a)gmail.com >

2 years, 4 months

Search results for query "sapiro"