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

[MM3-users] Re: Shunt Error Mail?

by Pete Ashdown

On 3/2/21 4:09 PM, Mark Sapiro wrote: > On 3/2/21 2:52 PM, Pete Ashdown wrote: >> I have a number of list managers with subscribers who are confused as to >> why their messages are silently disappearing. I've read the archives on >> how to decipher why a message was shunted, but this is not workable at >> scale. Is sending an error email back to the sender a consideration? > Why are messages being shunted? Each shunted message has thrown some > kind of uncaught exception which is logged with a traceback in Mailman's > mailman.log. > > These should be due to bugs that should get fixed or possibly malformed > messages which are almost always spam. > > In short, under normal circumstances messages should not be shunted at > all and when they are it is something the site admins need to address. > It is normally not something the sender of the message can do anything > about. This is good to know. I was concerned that shunting could happen due to HTML or message content (ie: not size).

5 years, 1 month

[MM3-users] Re: MAILMAN_ARCHIVER_KEY - 401 error

by Torsten R.

Mark Sapiro wrote: > The issue is not related to message content. > One possibility is that there is an incompatibility between > mailman-hyperkitty >= 1.2.0 and HyperKitty <= 1.3.4. that could cause > this. What are your versions? Understood, just wanted to mention that as I read it in another thread about the 401. Hyperkitty is 1.3.4 and mailman-hyperkitty is 1.2.0 > What is your setting in mailman-hyperkitty.cfg for base_url: base_url is set to https://www.fqdn.tld/mailman/hyperkitty > if you append api/ to that and do something like > curl base_url/api/ > it should return a page of documentation of the API. If that is the > case, the issue is almost certainly communicating the api key between > mailman-hyperkitty and HyperKitty I get some information back when appending /api/ to that URL mentioned above about REST API and some formats and endpoints. So, from your words it looks like there is some issue in the communication between mailman-hyperkitty and HyperKitty. Is there some place I could/should start looking or some log I should be examining (maybe some loglevel to be increased as well)?

3 years, 11 months

[MM3-users] Re: A few more MM3 questions

by Marc SCHAEFER

Re, On Wed, May 29, 2024 at 09:23:07AM -0400, Mark Sapiro wrote: > > 2) I imported a list and all messages get a footer of: > > %(web_page_url)slistinfo/%(_internal_name)s > > which I guess changed between MM2 and MM3; however when I > > look at that list configuration in the web interface of MM3, > > I see no templates defined, nor any clue where this is > > configured: where may I change this? > > import21 creates these templates in (I think in your case) > /var/lib/mailman3/templates. Yes, I used import21, and there are files there, and they contain the "web_page_url" that is the cause of the problem. May I just modify those files, and is there any way to see, in the web GUI, where those files are referenced? In the database itself, the template table is empty (as seen in the GUI) and I did not see the text "web_page_url" in a dump of the database, so I have some issues to understand how this is used by Mailman (except direct file access to /var/lib/mailman3/templates?)

1 year, 10 months

[MM3-users] Re: FYI: Django security releases issued: 4.0.6 and 3.2.14

by David Newman

On 7/7/22 1:20 PM, Mark Sapiro wrote: > On 7/7/22 12:44 PM, David Newman wrote: >> >> However, pip now throws a warning when looking at package info: >> >> (venv) mailman@somehost:/home/dnewman$ pip show mailman-web >> WARNING: Ignoring invalid distribution -jango >> (/opt/mailman/venv/lib/python3.9/site-packages) >> ... > > What does > ``` > ls -la /opt/mailman/venv/lib/python3.9/site-packages/-jango* > ``` > show? I suspect you have some spurious stuff there. The timestamps might > give a clue as to how it got there. > > If it shows anything, > ``` > rm -rf /opt/mailman/venv/lib/python3.9/site-packages/-jango* > ``` > will probably fix it. That was my first thought too. But there's nothing in that directory beginning with a hyphen, not even with the -a switch. The Django directories are as follows: django Django-3.2.14.dist-info django_allauth-0.47.0.dist-info django_appconf-1.0.5.dist-info django_compressor-3.0.dist-info django_extensions django_extensions-3.1.5.dist-info django_gravatar django_gravatar2-1.4.4.dist-info django_haystack-3.1.1.dist-info django_mailman3 django_mailman3-1.3.7.dist-info django_picklefield-3.0.1.dist-info django_q django_q-1.3.9.dist-info djangorestframework-3.13.1.dist-info dn

3 years, 8 months

[MM3-users] Re: hyperkitty.views.mailman Could not archive the email with message-id '<snip>': A string literal cannot contain NUL (0x00) characters

by Gilles Filippini

Gilles Filippini a écrit le 12/03/2021 à 01:41 : > Mark Sapiro a écrit le 12/03/2021 à 00:59 : >> On 3/11/21 3:10 PM, Gilles Filippini wrote: >>> >>> Looking at the offending message with 'mailman qfile', it appears it is >>> a legitimate one actually, sent from an Android phone. >>> >>> Couldn't hyperkitty be a bit less strict? >> >> >> Possibly. It looks like this may be >> <https://gitlab.com/mailman/hyperkitty/-/issues/271>, fixed? by >> <https://gitlab.com/mailman/hyperkitty/-/merge_requests/215>. What >> HyperKitty version is this? >> <https://gitlab.com/mailman/hyperkitty/-/merge_requests/215> is in 1.3.2. >> >> If your HyperKitty is >= 1.3.2, please file a new issue at >> <https://gitlab.com/mailman/hyperkitty/-/issues> > > This is Hyperkitty 1.3.4. > I'll file an issue tomorrow. Here it is: https://gitlab.com/mailman/hyperkitty/-/issues/346 Thanks, _g.

5 years

[MM3-users] Re: Problem with debian uipgrade

by Lars Schimmer

Am 08.03.2022 um 21:08 schrieb Mark Sapiro: > Possibly one way to fix this is to run > ``` > django-abmin migrate socialaccount > ``` > where django-admin is the name of your django management command. > > Then running `django-abmin migrate` should succeed. The issue appears to > be due to the face that `django-admin migrate` runs the migrations in > alphabetical order by app. This is fine if migrations were run during > the period after socialaccount.0003_extra_data_default_dict was created > and before hyperkitty.0007_allauth_20160808_1604 was created, but it's > an issue in an installation that wants to migrate > hyperkitty.0007_allauth_20160808_1604 without having previously migrated > socialaccount.0003_extra_data_default_dict. Thx for your always competent answers. In this case I just needed to uncomment the not needed socialaccount lines in mailman3.cfg. As we do not use them. And now I hope for a debian package upgradem or I need to replace them with virtuelenv install as soon as I need to upgrade. MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

4 years

[MM3-users] Re: Caching problem with templates

by Mark

> On 6/26/25 04:25, Mark wrote: >> >> A footer template is created and initially it works as expected. >> >> Editing the footer template sees the new content written to the >> database, >> >> In addition to viewing the edited content in the database, the new >> template can also be viewed in Lynx on localhost at: >> >> http://localhost:8000/mailman3/api/templates/list/<IDENTIFIER>/list:member:regular:footer >> >> The problem is that the original template is being cached somewhere >> and the old footer persists in new emails. ================================= On 2025-06-26 16:10, Mark Sapiro wrote: > What does the database query > ``` > SELECT uri FROM template WHERE name = 'list:member:regular:footer' AND > context = '<IDENTIFIER>'; > ``` > return? ================================= The result of the query is: +--- uri +---- http://localhost:8000/mailman3/api/templates/list/<IDENTIFIER>/list:member:regular:footer +---- I should have also said, if I delete the template, emails still use the old footer -- not the Mailman default as I would have expected. And I had a look in /opt/mailman/mm/var/templates/lists/ -- nothing there.

9 months, 1 week

[MM3-users] Re: Missing Base64 encoding from control message reply

by Stephen J. Turnbull

Mark Sapiro writes: > The issue is the message declares > > Content-Transfer-Encoding: base64 > > but the body is not base64 encoded so the MUA tries to base64 decode it > and even though that's invalid, produces the garbled output. :-( > I tried to duplicate this in a test installation with the charset > for English set to utf-8, but I get a similar response but with > > Subject: =?utf-8?q?The_results_of_your_email_commands?= I think that's unfortunate. Not really a bug, but the RFCs recommend using the defaults (ie, US-ASCII) where that's possible. I wonder if it's possible to use email.policy to change that.[1] With respect to the actual problem, I don't have anything to say until we have more information about the relevant settings. Oh, I guess I also wonder if maybe the language doesn't have a translation for that message yet? Steve Footnotes: [1] Speaking of bugs, my MUA decoded that MIME word when it quoted the message even though it's not in the header! Aaargh.

2 years, 6 months

[MM3-users] Re: Migrating Mailman 3 lists

by Stephen J. Turnbull

Andrew Hodgson writes: > Mark Sapiro wrote: > >On 5/19/20 7:25 PM, Mark Dadgar wrote: > >> For reference my pgloader script looks like: > >> > >> load database > >> from sqlite:///var/lib/dbconfig-common/sqlite3/mailman3-web/mailman3web.db > >> into postgresql://mailman3:XXREDACTEDXX@localhost/mailman > >> > >> with include drop, create tables, create indexes, reset sequences, no truncate > Have you tried this without indexes and then run the migrate > script? It may re-create them as part of the schema upgrade > check. That was my immediate guess. I'm not an SQL expert, but I believe that sequences and indexes are different entities, they're both optimizations that you don't need (ie, ignoring performance), and implementations differ on how they're implemented. Eg, if sqlite implements them as tables, while PostgreSQL has a special data structure, you could run into this kind of behavior. I'm pretty sure that these will be recreated appropriate to the new database when the schema validator is done. But don't trust me, and *do* keep a backup. ;-) Steve

5 years, 10 months

[MM3-users] Re: List archives Recent Posts problem

by Mark Dadgar

On Jun 23, 2020, at 3:19 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/18/20 9:01 AM, Mark Dadgar wrote: >> In the last day or so, hitting the Recent page in my list archives results in a spinner and an error message: >> >> Internal Server Error: /mailman3/hyperkitty/list/trackjunkies(a)pdc-racing.net <mailto:mailman3/hyperkitty/list/trackjunkies@pdc-racing.net>/recent-threads >> >> AttributeError at /hyperkitty/list/trackjunkies(a)pdc-racing.net <mailto:hyperkitty/list/trackjunkies@pdc-racing.net>/recent-threads >> 'NoneType' object has no attribute 'subject' > > > Is this still an issue? > > If so, see the entire thread at > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> > for a possible solution. It’s still a problem. I restarted the whole machine and that did not fix it. I also tried to delete any row in the hyperkitty_thread table where starting_email_id was null and that did not return any deleted rows. mailman=> delete from hyperkitty_thread mailman-> where starting_email_id = null; DELETE 0 All of my member functions are still broken as well. :( - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 9 months

Search results for query "sapiro"