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

[MM3-users] Re: Hyperkitty Error

by Mark Sapiro

On 12/9/19 5:25 PM, Brian Carpenter wrote: > I am seeing the following error being repeated every 2 seconds in the uwsgi-error.log: > > 01:22:05 [Q] INFO Process-1:19112 processing [compute_thread_positions] > 01:22:05 [Q] ERROR Failed [compute_thread_positions] - 'DiGraph' object has no attribute 'node' : Traceback (most recent call last): > File "/usr/lib/python3.6/site-packages/django_q/cluster.py", line 381, in worker > res = f(*task['args'], **task['kwargs']) > File "/usr/lib/python3.6/site-packages/hyperkitty/tasks.py", line 127, in _compute_thread_positions > compute_thread_order_and_depth(thread) > File "/usr/lib/python3.6/site-packages/hyperkitty/lib/analysis.py", line 55, in compute_thread_order_and_depth > walk_successors(thread.starting_email.id) > File "/usr/lib/python3.6/site-packages/hyperkitty/lib/analysis.py", line 37, in walk_successors > obj = graph.node[msgid]["obj"] > AttributeError: 'DiGraph' object has no attribute 'node' > > I am running the docker version of Mailman, version 1.3.0. Any suggestions? See <https://gitlab.com/mailman/hyperkitty/issues/268> fixed by <https://gitlab.com/mailman/hyperkitty/merge_requests/201>. You need to change 'graph.node' to 'graph.nodes' at both line 37 and line 44 in /usr/lib/python3.6/site-packages/hyperkitty/lib/analysis.py to accomodate networkx >= 2.0 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Re: Adding user - Error 409 Subscription request already pending

by Mark Sapiro

On 6/17/22 12:19, Dan Caballero wrote: > Thanks very much for the guidance. I ran the code and received the output for the list but after a commit and exit the members still weren't subscribed. That's expected. The process I posted only removes the pending request so a subsequent subscribe can succeed. > I then ran mailman syncmembers using a list I had. That was able to complete this time and make all the necessary additions. > > I'm going to see about making a wrapper script for future use. Thank you again. For Mailman core >=3.3.5 this should not be an issue. The underlying issue is https://gitlab.com/mailman/mailman/-/issues/729 which is fixed in 3.3.5. Now pending subscription confirmations expire after the configured pending_request_life (default 3 days) so they shouldn't hang around virtually for ever. I just added some sample scripts to https://www.msapiro.net/scripts/. The script at https://www.msapiro.net/scripts/delete_orphans_expireds.py will delete subscriptions pending user confirmation that are older than the current pending_request_life. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: Can't Start Mailman3 Core on Fresh Install

by Mark Sapiro

On 7/21/22 10:09, Jonathan Green wrote: > I've triple checked the password in mailman.cfg and used the same > username/password directly in MySQL and was able to get to the mailman3 > database. I did run a test script in python3 using the PyMySQL connector > and got the same error. Is there some permissions issue I need to look for? > I ran the install as user root - perhaps the user running the python script > doesn't have access somehow? First, your primary support resource for the Debian/Ubuntu packages should be Debian. That said, the database access credentials are also configured in the DATABASES setting in your Django settings, although your OP indicates this error is in core. I'm not sure what running the install as `root` will do in the Debian/Ubuntu package, but with that package, the user that needs to access things is `list` and all the Mailman processes should run as `list`. Did your test script do pymysql.connect(user='list', ...)? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: message awaits moderator approval

by Mark Sapiro

On 12/21/22 08:53, Eggert Ehmke via Mailman-users wrote: > > Now it turned out that there were several relicts of the old list in the > database, in particular in the template table. I removed them using direct SQL > commands. > > Now my new mailing lists work as expected. > > Is this a bug in postorius? I think when I delete a mailing list, all relicts > should be deleted from the database. Were there Postorius custom templates for that list?, I.e. did the template table entries have Postorius URLs. If so, this is probably a Postorius issue. I haven't actually looked, but when Postorius deletes a list, it should delete any of it's templates from the postorius_emailtemplate table and revert the template table entries. Beyond that, Postorius is just telling Mailman core to delete the list, and when Mailman core does that it should probably also remove any var/templates/lists/<list_id> directory and any entries from the template table with context = the list_id. If it doesn't, this is a core issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: attachment.html

by Sam Darwin

Thanks for making this change! It's a big improvement! Another random idea, not required, - using javascript, literally disable or enable all the settings which are disabled or enabled by 'Filter content'. So if someone tries to set 'Convert html to plaintext', they can't, until 'Filter content' is enabled On Mon, Jun 26, 2023 at 10:22 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/26/23 6:22 PM, Mark Sapiro wrote: > > > > You are correct that the UI is not clear on what settings depend on > > Filter content. We need to fix that. > > I've created an issue for this at > https://gitlab.com/mailman/postorius/-/issues/584 and committed a fix at > https://gitlab.com/mailman/postorius/-/merge_requests/815 > > -- > 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 samuel.d.darwin(a)gmail.com >

2 years, 11 months

[MM3-users] Re: Speed up importing mailman2 lists

by Mark Sapiro

On 2/19/25 06:08, t.maintz(a)fz-juelich.de wrote: > We are currently planning to migrate from mailman2 to mailman3 as a container, have around 1500 lists and would like to complete the migration ideally in a few hours. We would like to switch off mailman2 to have a defined state of the lists and import them to mailman3. The import of all lists via script takes about 3 days. Parallelizing the imports does not work due to lockings in the database. > However, we cannot accept a downtime of 3 days. Does anyone have tips on how we can speed up the procedure or are there best practices for larger environments? What Mailman 3 version are you importing to? I ask because prior to Mailman core 3.3.1, user's passwords were imported and the encryption of the password was quite time consuming. If in fact you are importing to Mailman <3.3.1, see https://gitlab.com/mailman/mailman/-/merge_requests/565 for a patch that will speed this up considerably and see https://mail.python.org/archives/list/mailman-developers@python.org/thread/… for discussion of this change. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: Table 'mailmansuite.django_q_ormq' doesn't exist ("Delete this thread" -> 'HTTP-500 -> NoneType' object has no attribute 'all')

by Mark Sapiro

On 05/29/2017 02:16 PM, Simon Liebold via Mailman-users wrote: > > Now, I get to see the confirmation view and upon confirming I see these > (luckily different) errors like below (same with Django 1.10): > > Could not delete message P2GJLK4JPDU2K6ZKBSDUWASF2TVHCJTT: (1146, "Table > 'mailmansuite.django_q_ormq' doesn't exist") > Could not delete message 4I2TRZTFXMMH2XRQAS73IAEIYROFE5YM: (1146, "Table > 'mailmansuite.django_q_ormq' doesn't exist") > > True, this table doesn't exist in the database. It isn't created by > python manage.py migrate. > > The error is served with HTTP-200. No stack trace in mailmansuite.log. Do you have django_q in INSTALLED_APPLICATIONS in your Django config and do you have # # Asynchronous tasks # Q_CLUSTER = { 'timeout': 300, 'save_limit': 100, 'orm': 'default', } in your Django config and are you running django-admin qcluster at startup? See <https://mail.python.org/pipermail/mailman-developers/2017-May/026064.html>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years

[MM3-users] Re: uncaught bounce messages

by Mark Sapiro

On 10/26/21 8:18 AM, Seth Seeger wrote: > > I have just upgraded to 3.3.4 from 3.3.2 (via docker). > > Do we need to do anything more than reset the delivery status? I am getting (seemingly) continual emails about bounces. I keep running the recipe in the link which resets everyone's delivery status. I've grep'd one member's address out of bounce.log (see below my signature). > > Is it just catching up on old bounces? There is no significant change in bounce processing from 3.3.2 to 3.3.4 If you really upgraded from 3.3.2, I don't know what would be responsible. On the other hand, it looks like you may in fact have upgraded from Mailman < 3.3.1 in which case, those are old, previously unprocessed bounces, and your log certainly looks like that. If you think some or all users shouldn't have had delivery disabled, you can run the mailman shell seccion in the post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… to re-enable them and let current bounce processing handle the truly undeliverable ones. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: Broken web UI after upgrade

by Mark Sapiro

On 12/16/22 03:36, Odhiambo Washington wrote: > > I am probably getting closer to where the problem is. By looking at nginx > error_log while access the site, I see that there are > just two CSS files that are missing, as shown in the error lo here: > https://pastebin.ubuntu.com/p/7wbwMgqMyS/ > > Question is - why is it specifically looking for these two files > - /opt/mailman/mm/static/CACHE/css/output.93545e20bc30.css > -/opt/mailman/mm/static/CACHE/css/output.e1f0c6022e8f.css > > Where are these files supposed to come from and why are they missing? > I have looked at my current CACHE directory and compared with the backup of > the same site before upgrade and these files aren't the same either: They come from django admin `compress` which used files created by django admin collectstatic. I suggest you run ``` django-admin collectstatic --clear --noinput --verbosity 2 django-admin compress --verbosity 2 ``` where `django-admin` is your django admin command. If this doesn't fix the issue, perhaps the more verbose output will help find the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Speed up importing mailman2 lists

by Mark Sapiro

On 2/24/25 05:36, t.maintz(a)fz-juelich.de wrote: > > Can you tell me how to implement this in Postfix? Here's what we do on mail.python.org which supports both Mailman 2.1 and Mailman 3 lists. We also use an alias domain as described at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… because python.org is a virtual_alias_domain. The relevant settings in main.cf are alias_maps = ... hash:/srv/mailman/data/aliases lmtp_destination_recipient_limit = 1 recipient_delimiter = + relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains transport_maps = ... hash:/opt/mailman/mm/var/data/postfix_lmtp virtual_alias_domains = python.org ... virtual_alias_maps = ... hash:/srv/mailman/data/virtual-mailman hash:/opt/mailman/mm/var/data/postfix_vmap The alias_maps and the hash:/srv/mailman/data/virtual-mailman setting in virtual_alias_maps are MM 2.1 settings. The hash:/opt/mailman/mm/var/data/* settings are MM 3. Since transport_maps takes priority over aliases, if there is a MM 3 list in hash:/opt/mailman/mm/var/data/postfix_lmtp, mail for that list will be delivered to MM 3 via LMTP. If not, and the destination is a MM 2.1 list, delivery will be via the virtual_alias_mapping hash:/srv/mailman/data/virtual-mailman -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

Search results for query "sapiro"