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

[MM3-users] Re: how to unhold a hold message from a nonmmeber in hold list.

by Guillermo Hernandez (Oldno7)

El 21/4/23 a las 14:29, Mark Sapiro escribió: > On 4/21/23 1:19 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> I'm having troubles with Django and cannot access to web admin. >> >> I need to unhold a message while figures out what is happening. >> >> Searching the mailman cli help commands didn't help me. >> >> Anyone who knows how to unhold a message, please? > > > See this post > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > Thanks, Mark. That could have been a life saver if I hadn't reset the UI. I'm writing it down for a future need. -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 1 month

[MM3-users] Re: Template URI gets written incorrectly

by Mark Dale

On 2023-05-24 10:11, Mark Sapiro wrote: > On 5/23/23 16:51, Mark Dale via Mailman-users wrote: >> >> When I create a template, it writes the URI incorrectly into the template table in the mailman3 database and the list stops working. >> >> For example, it writes: >> >> http://localhost/mailman3/postorius/api/templates/list/markslist.lists.post… >> >> When I correct it like so, all is well: >> >> https://lists.postmark.io/mailman3/postorius/api/templates/list/markslist.l… >> >> Have I missed a config setting somewhere, or is this a bug with the older Debian Mailman 3.3.3 ? > > > You need to set > > POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.postmark.io/' > > in your Django settings. Debian probably has set it to 'http://localhost/'. > Indeed that was it! Thanks very much Mark. /etc/mailman3/mailman-web.py Line 190: POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.postmark.io/'

2 years

[MM3-users] Re: [SOLVED] Re: Re: Help with Newbie error -- I think I deleted my server

by William Oliver

On Sat, 2021-12-25 at 10:19 -0800, Mark Sapiro wrote: > On 12/25/21 7:13 AM, William Oliver wrote: > > > > Just out of curiosity, if I could not have guessed a valid ID > > number > > and did not have the admin interface, how could I have figured out > > what > > site IDs were available? > > > If Postorius is working, recent versions show the SITE_ID in the > domains > view. I.e. after you added your domain you could have noted the > SITE_ID > and made the change in settings before deleting the example.com > domain. > > In any case, the django_site table in Mailman's database has the > information. > Thanks. Yep, I peeked at the database and there it was. That would probably been more efficient than randomly choosing numbers... billo

3 years, 4 months

[MM3-users] Re: how to unhold a hold message from a nonmmeber in hold list.

by Odhiambo Washington

On Fri, Apr 21, 2023 at 11:20 AM Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users(a)mailman3.org> wrote: > I'm having troubles with Django and cannot access to web admin. > > I need to unhold a message while figures out what is happening. > > Searching the mailman cli help commands didn't help me. > > Anyone who knows how to unhold a message, please? > TBH, I find it a lot easier to fix the web UI than mess with the python shell :-) While you wait for @Mark Sapiro <mark(a)msapiro.net> to save you, you can be reading the following: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 1 month

[MM3-users] Re: Permissions issue after upgrade of virtualenv

by Odhiambo Washington

On Thu, Mar 9, 2023 at 10:41 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/9/23 11:25, Odhiambo Washington wrote: > > > > Thu Mar 09 22:17:59.313459 2023] [core:error] [pid 15655] (13)Permission > > denied: [client 197.232.xx.xx:26574] AH00035: access to / denied > > (filesystem path '/opt/mailman/mm') because search permissions are > missing > > on a component of the path, referer: https://mm3-lists.kictanet.or.ke/ > > I did not change Apache config and I made sure that /opt/mailman is all > > owned by mailman:mailman. > > > > What am I missing? > > > X permission on one or more of /opt, /opt/mailman, /opt/mailman/mm > Wow. That would have taken me a decade to spot! The X permissions were missing on /opt/mailman. Thank you very much. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 2 months

[MM3-users] Re: pending subscriptions lost?

by IEM Network Operation Center (IOhannes m zmölnig)

On 3/14/22 17:03, Mark Sapiro wrote: > On 3/14/22 06:00, IEM Network Operation Center (IOhannes m zmölnig) wrote: > > This is https://gitlab.com/mailman/mailman/-/issues/729 fixed in Mailman > 3.3.5. thanks for comfirming. > > >> - i (as administrator) do not see any "pending subscriptions" (the >> list is setup with a simple "Confirm" subscription policy > > The count badge only counts subscriptions waiting moderator approval. If > you pull down the Subscription requests tab and click Pending > Confirmation you should see them and be able to discard them. hmm. i'm not sure i can follow. my "Subscription requests" tab seems to not have any "Pending Confirmation" section (see attached screenshot). this is with "Postorius Version 1.2.4" (as installed by the mailman3 Debian package). fdsm< IOhannes ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: Subscription requests.png

3 years, 2 months

[MM3-users] Re: clicking on a username when viewing a thread results in "Page not found"

by Ken Alker

Mark Sapiro wrote: > On 6/26/23 12:20 AM, Ken Alker wrote: > > If I click on a username when viewing a thread, it returns "Page not found" then "This page either doesn't exist, or it moved somewhere else.". Any idea why this may be happening? > This is a problem. That link goes to, e.g., > https://example.com/archives/users/<user_id>/. What do you get if you > strip the user_id and just go to what > https://example.com/archives/users/ translates to on your system? > You should get a page saying > Not implemented > > This feature has not been implemented yet, sorry. > > If you get a 404, there is an issue with your web server configuration > or maybe your top level urls.py. I get "Not implemented". I do not get a 404 error.

1 year, 10 months

[MM3-users] Re: Migrating mailman3 to latest ubuntu lts

by Helio Loureiro

Hi, I looked to the version I in the old installation: mysql> select * from alembic_version; +--------------+ | version_num | +--------------+ | 4bd95c99b2e7 | +--------------+ 1 row in set (0.00 sec) I set the same version on the new. Actually I loaded a fresh dump from DB to be sure it was the same. And now it is starting without errors. I guess that was it. Thanks a lot! Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Thu, 14 Dec 2023 at 18:47, Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/14/23 01:48, Helio Loureiro wrote: > > > > > But it is failing to start displaying the domain name from the previous > > machine. > > > > (venv) mailman@new-server ~ (v3.3.9)> mailman start > > Starting Mailman's master runner > > Generating MTA alias maps > > Traceback (most recent call last): > > File > > > "/local/mailman/venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", > > line 1969, in _exec_single_context > > self.dialect.do_execute( > > File > > > "/local/mailman/venv/lib/python3.10/site-packages/sqlalchemy/engine/default.py", > > line 922, in do_execute > > cursor.execute(statement, parameters) > > File > > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/cursors.py", > line > > 153, in execute > > result = self._query(query) > > File > > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/cursors.py", > line > > 322, in _query > > conn.query(q) > > File > > > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/connections.py", > > line 558, in query > > self._affected_rows = self._read_query_result(unbuffered=unbuffered) > > File > > > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/connections.py", > > line 822, in _read_query_result > > result.read() > > File > > > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/connections.py", > > line 1200, in read > > first_packet = self.connection._read_packet() > > File > > > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/connections.py", > > line 772, in _read_packet > > packet.raise_for_error() > > File > > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/protocol.py", > > line 221, in raise_for_error > > err.raise_mysql_exception(self._data) > > File > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/err.py", > > line 143, in raise_mysql_exception > > raise errorclass(errno, errval) > > pymysql.err.OperationalError: (1054, "Unknown column > 'domain.alias_domain' > > in 'field list'") > > > The issue is your domains table and possibly others are not up to the > current schema. This should be accomplished by Mailman core running all > the necessary migrations in mailman/database/alembic/versions/. For some > reason, alembic's MigrationContext thinks the migrations have been run, > but they haven't. In the `mailman` database, the alembic_version table > has the version_num of the putative current version. The migration that > added alias_domain is dfe82cf73702_add_alias_domain.py. If there is no > alias_domain column in the domain table, alembic_version.version_num > should be a version older than 'dfe82cf73702'. > > I suggest querying the prior mailman database for the > alembic_version.version_num value and setting that in the current > database, assuming that that migration exists in > mailman/database/alembic/versions/. > > This may be sufficient, but there may be other inconsistencies depending > on exactly what you did. > > -- > 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 helio(a)loureiro.eng.br >

1 year, 5 months

[MM3-users] Re: Hyperkitty on Debian 12

by Markus Grandpré

short addendum: I was able to correct the following warnings when performing database operations on the mailman-web database: 1) /usr/lib/python3/dist-packages/django_q/conf.py:139: UserWarning: Retry and timeout are misconfigured. Set retry larger than timeout, failure to do so will cause the tasks to be retriggered before completion. See https://django-q.readthedocs.io/en/latest/configure.html#retry for details. 2) django_mailman3.MailDomain: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. on our Debian 12 system in file </etc/mailman/mailman-web.cfg>: 1) Q_CLUSTER = { 'orm': 'default', 'retry': 360, 'save_limit': 100, 'timeout': 300, 'worker': 2 } 2) DEFAULT_AUTO_FIELD = 'django.db.models.BigAutoField' Best Markus Am 26.03.24 um 08:06 schrieb Markus Grandpré: > Dear Mr Sapiro, > > thank you very much for your help. The required command is: > > # mailman-web hyperkitty_import \ > -l mailman21-migration-test-04(a)mailman.uni-konstanz.de \ > /var/mailman21/testlist.mbox > > Due to the following warnings, I still have to customize Hyperkitty: > > django_mailman3.MailDomain: (models.W042) Auto-created primary key used > when not defining a primary key type, by default > 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > DjangoMailman3Config.default_auto_field attribute to point to a subclass > of AutoField, e.g. 'django.db.models.BigAutoField'. > ... > > Can you give me another hint? As Linux admin I installed the packages > mailman and mailman-web that were offered to me under Debian 12. > Although during the installation of the packages user "list" was > created, I cannot use it: > > # su - list > This account is currently not available > > As with Mailman 2.1, I will probably have to continue working with > Mailman3 as root. Too bad that there is no documentation for Debian > admins like me, who don't want to dive too deep into the python > framework. Or have I overlooked something? > > Best regards, > Markus > > > > Am 25.03.24 um 18:56 schrieb Mark Sapiro: >> On 3/25/24 07:58, Markus Grandpre wrote: >>> Dear list members, >>> >>> when following the instructions to migrate list archives from >>> Mailman21 to Mailman3 (see [1]), I face the following problem: >>> >>> # python3 manage.py hyperkitty_import -l mailman21-migration-test-04 >>> /var/mailman21/testlist.mbox >>> python3: can't open file '/var/mailman21/manage.py': [Errno 2] No >>> such file or directory >>> >>> and have no clue, where to find the right <manage.py> file. The command >> >> >> This depends on how you installed Mailman 3. You may or may not want >> `python3 manage.py` at all. The required command could be something >> like `django-admin` or `mailman-web`. >> >> Also the `#` prompt indicates you may be running as root. Mailman >> related commands should be run as the Mailman user (could be `mailman` >> or `list` or ... depending again on how you installed Mailman). >> Running as root can create files owned by root that later can't be >> read by the Mailman user. >> > > > _______________________________________________ > 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 markus.grandpre(a)uni-konstanz.de -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

1 year, 1 month

[MM3-users] Re: How to see the admin password reset in docker with mailman3

by Jeremy Stanley

On 2023-04-06 14:38:41 -0700 (-0700), Mark Sapiro wrote: [...] > I can't answer that question, but you can set an admin user and > password with the django admin createsuperuser command. And for reference, here's how it's run at setup for the containers: https://github.com/maxking/docker-mailman/blob/b581310/web/docker-entrypoin… python3 manage.py createsuperuser --noinput --username \ "$MAILMAN_ADMIN_USER" --email "$MAILMAN_ADMIN_EMAIL" For a maybe more automate-able example, here's how we call it from outside the container via docker exec on our deployments: https://opendev.org/opendev/system-config/src/commit/ab0e6e1/playbooks/role… docker exec mailman-web bash -c \ "DJANGO_SUPERUSER_PASSWORD={{ mailman3_admin_password }} \ python3 manage.py createsuperuser --no-input --username \ {{ mailman3_admin_user }} --email \ '{{ mailman3_admin_email }}'" The things in {{}} are Jinja2 templated values we supply through Ansible, you could just replace them with whatever values are appropriate for your deployment. -- Jeremy Stanley

2 years, 1 month

Search results for query "sapiro"