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

[MM3-users] Re: Non-ascii characters missing from Pipermail archive txt and gz downloads

by Mark Dale

Hi Ruth, Apologies for the late response. I posted my message to the MM3 list in error and have since reposted it to the MM2 list. However, thank you for taking the trouble to reply. The problem lies outside the choice of editor as both files are being viewed in the same editor -- with one correct and the other not. Mark Sapiro has explained (on the MM2 list) what is causing the problem. Armed with that information I just have to now find a way .... Regards, Mark -------- Original Message -------- From: Ruth Ivimey-Cook [mailto:ruth@ivimey.org] Sent: Friday, April 9, 2021, 15:24 UTC To: mark(a)postmark.io, Mailman users Subject: [MM3-users] Non-ascii characters missing from Pipermail archive txt and gz downloads > Hi Mark > > I'm not sure, but I think the problems are to do with the program you are using to view the txt file. > > A modern mail reader understands the Content-type: header and will adjust its character processing accordingly, but a .txt file has no default character encoding, so any text editor will have to "use its best judgement". Some will default to utf-8, because that is compatible with 7-bit ASCII (NOT Latin1) while others will just put characters out and hope for the best (esentially leaving the result to the encoding of the font). > > In theory, a UTF-encoded text file can begin with the "BOM" marker, a sequence of characters which is supposed to indicate which variety of Unicode is in use, but this is rarely present, especially for UTF-8. > > Try looking at your text file with a UTF-8 capable text editor **and ensure that you tell the editor to use the UTF-8 encoding**. I expect it will look ok then. > > > Hope this helps, > > Ruth > > > On 09/04/2021 13:52, Mark Dale via Mailman-users wrote: >> Mailman 2.1.34 >> Debian 10 >> Postfix >> >> Hi >> >> I'm hoping someone can shine a light on character encoding issue I've encountered. >> >> A plain-text email with non-ascii characters in the body gets posted to the list. >> >> As per Mark Sapiro's guide I've captured the incoming message to file. >> >> - https://www.mail-archive.com/mailman-users@python.org/msg73469.html >> >> The message is received by Mailman with the non-ascii characters displaying correctly. >> >> The header of that message has: >> >> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 >> Thunderbird/78.9.0 >> MIME-Version: 1.0 >> Content-Type: text/plain; charset=utf-8 >> Content-Language: en-AU >> Content-Transfer-Encoding: 8bit >> >> In the list's mbox file and archive webpage, the message displays the non-ascii characters correctly. >> >> In the archive's downloaded .txt (and also .gz) file, the non-ascii characters are missing and displayed as "?". >> >> I've copied the message text in below, from both the correct one from the email and the erroneous .txt file. Hopefully they won't get scrambled up when I send this. >> >> Any advice on getting the non-ascii characters written into the archive .txt file would be gratefully received. >> >> Thanks, >> Mark >> >> >> === Message text as okay in mbox and as shown on the archive webpage === >> >> If one goes by the definition of veḷippaṭai as given in the Tamil Lexicon that the meaning of an ambiguous word should be disambiguated by a qualifying word, then aruvi āmpal does not conform to that definition since in the case of aruvi āmpal in Patiṟṟuppattu 63, aruvi is really made up of aru+vi, a compound. Moreover, the expression aṭai aṭuppu aṟiyā is already there to clarify that āmpal is a number and not a flower. Thus, aruvi simply provides information in addition to aṭai aṭuppu aṟiyā that āmpal is not a flower. The modern commentator Aruḷampalavaṉār also does not call it veḷippaṭai. >> >> === >> >> === Message text with missing characters in te archive's txt and gz downloads == >> >> If one goes by the definition of ve?ippa?ai as given in the Tamil Lexicon that the meaning of an ambiguous word should be disambiguated by a qualifying word, then aruvi ?mpal does not conform to that definition since in the case of aruvi ?mpal in Pati??uppattu 63, aruvi is really made up of aru+vi, a compound. Moreover, the expression a?ai a?uppu a?iy? is already there to clarify that ?mpal is a number and not a flower. Thus, aruvi simply provides information in addition to a?ai a?uppu a?iy? that ?mpal is not a flower. The modern commentator Aru?ampalava??r also does not call it ve?ippa?ai. >> >> === >> _______________________________________________ >> 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/ >

5 years, 3 months

[MM3-users] Re: Problems after upgrading from bullseye to bookworm

by Eggert Ehmke

Hello Mark, thank you. I did change that entries, and now my mailman runs fine on Debian Bookworm. I did a complete reinstall of the venv directory to have a clean start. Maybe this was not needed. What's missing in the documentation: -the directiories web/logs have to be created manually with the ownership mailman. -The debian package pkg-config must be installed. -the package psycopg2-binary can/must be installed without version restriction on Bookworm Maybe this info helps some other people. Cheers, Eggert Am Montag, 26. Juni 2023, 22:22:37 CEST schrieb Mark Sapiro: > 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. ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

3 years

[MM3-users] Re: Hyperkitty "All Threads" results in error

by Mark Dadgar

On Oct 14, 2020, at 4:37 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/14/20 11:12 AM, Mark Dadgar wrote: >>> On Oct 4, 2020, at 10:34 AM, Mark Dadgar <mark(a)pdc-racing.net> wrote: >>> >>> So I have been wrestling with this problem for a while now. Most times, but not every time, when someone clicks on the All Threads link in hyperkitty, a 500 error is generated. > > > Does this happen on all lists, only some lists or only one list? > > >>> I googled it, obviously, and at first I thought it was related to this issue, but that has not proven to be the case: >>> >>> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > What did you google? This query gets a lot of stuff with some hints, but > nothing definitive. > > django render raises VariableDoesNotExist("Failed lookup for key " > > One thing I noted at > <https://askbot.org/en/question/3095/django-error-variabledoesnotexist-faile…> > was > > models out of date - run python manage.py syncdb and python manage.py > migrate > > You could try that. Note that your django admin command might be > something other than `python manage.py`. Also note syncdb has been > removed from Django >=1.9. Currently, the above becomes `makemigrations` > followed by `migrate`. > > I also suggest running the django admin commands > > `collectstatic --clear --noinput` > and > `compress` My re-install seems to have fixed this issue as well. BONUS! - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 5 months

[MM3-users] Re: Dealing with hyperkitty spool files (was Re: Re: Fwd: [Django] ...)

by David Partain

> On Wed, 2021-03-03 at 08:29 -0800, Mark Sapiro wrote: > > 1. Am I correct in assuming that I can just use my favorite editor > > (vi) to remove the offending characters from the file? > No. The file is a Python pickle and you can't edit it. You would need > to get the message and the metadata from the pickle (you could at least > view it with the `mailman qfile` command), edit the message and then > re-pickle the message and metadata. And, in my impatience, I tried it before receiving your response and now I seem to have done silliness in my database :( New error in mailman-web.log: AttributeError: 'NoneType' object has no attribute 'subject' Sigh. Stupid me. If you have suggestions on fixing that... Right now, my plan is simply to remove the first message in the queue (since I assume it'll be the "broken" one) and it'll just not be in the archive. Life's hard. Even if I unpack 'em to edit, I'll find mail in, for example, in base64, and I'm not going to fix the mail by decoding, editing, re-encoding, ... Nope. > > 3. Can I do something to make hyperkitty go through the spool? > > > > I don't know what you mean. Sorry I wasn't clear. I simply meant, "Is there a way to start hyperkitty going through the spool manually?" It sounds like, though, that I don't need to do that if it's going to happen that often anyway. Cheers, David

5 years, 4 months

[MM3-users] Re: nginx configuration on a multitasking server

by David Newman

On 12/22/21 7:29 PM, Mark Sapiro wrote: > On 12/22/21 6:20 PM, David Newman wrote: >> >> Update: The above worked fine until MM3 informed a list owner of >> pending subscription requests, with a URL like this: >> >> https://lists.example.com/mailman/admindb/listname >> >> and that URL returned a 404 error. > > > This looks like a uwsgi issue as discussed at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > although that's with apache and not nginx so it may not be. If I'm reading the thread correctly, it's Apache workarounds to an underlying Debian issue, so I agree it may not apply with nginx. > > >> Adding a stanza for 'location /mailman/' to the nginx config above >> clears the 404 error, but Postorius returns "Page not found" with no >> entry in the web or MM3 logs, and a 200 OK in the Nginx logs. >> >> I think the URL is supposed to go to the list page in Postorius. How >> to configure this so that list owners and moderators get a valid URL >> for list management? > > > I'm not sure what the solution is in this case, but a workaround would > be to add > > url(r'^mailman/', include('postorius.urls')), > > to the urlpatterns list in urls.py. There are 260 files named 'urls.py' under /opt/mailman, mostly for socialaccount stuff. Where does that change go? All files? Or just this one: /opt/mailman/venv/lib/python3.9/site-packages/postorius/urls.py Or somewhere else? Thanks again. dn

4 years, 7 months

[MM3-users] Re: Python 3.13 compatibility

by Washington Odhiambo

On Sun, Mar 29, 2026 at 6:11 PM Thomas Krichel <krichel(a)openlib.org> wrote: > Mark Sapiro writes > > > If you do that and it results in a working system, you can then patch > > mailman/utilities/i18n.py as follows > > Thank you. This works, and I can successfully import a first > list configuration. > > > However there are other incompatibilities between the released Mailman > > versions and Python 3.13. > > Hmm https://docs.mailman3.org/en/latest/install/virtualenv.html > states "3.13 is recommended as it is the latest version of Python > with which Mailman is tested." > > > At the moment, until updated packages are > > released, in a Python 3.13 environment it is best to install all of > mailman, > > django-mailman3, postorius, hyperkitty and mailman-web from the heads of > the > > gitlab branches. > > I would love to see a command line for that. When I go to the gitlab > page, https://gitlab.com/mailman/, I see a bunch of project that > don't immediately correspond to pip package names. > pip install git+https://gitlab.com/mailman/mailman@master pip install git+https://gitlab.com/mailman/mailmanclient@master pip install git+https://gitlab.com/mailman/mailman-hyperkitty@master pip install git+https://gitlab.com/mailman/hyperkitty@master pip install git+https://gitlab.com/mailman/django-mailman3@master pip install git+https://gitlab.com/mailman/postorius@master pip install git+https://gitlab.com/mailman/mailman-web@master -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

3 months, 3 weeks

[MM3-users] Re: Hyperkitty download mbox

by Andrew Hodgson

Mark Sapiro wrote: >On 4/26/21 2:00 AM, Andrew Hodgson wrote: > >> Yep there is a problem with an imported mbox which seems to be present somewhere in the archive on all the lists which I imported using that method. Here is a recent trace from the download option: [...] >Thanks for the traceback. The issue appears to be with folded headers that should either be unfolded before storing in HyperKitty's database or upon retrieval for this process. This is probably because of outlook.com folding Message-ID: headers. See >https://gitlab.com/mailman/mailman/-/issues/844 for one manifestation of this. >I think if you replace the >``` > msg["Message-ID"] = "<%s>" % self.message_id ``` line at 178 in /opt/mailman/venv/lib/python3.7/site-packages/hyperkitty/models/email.py >with >``` > msg["Message-ID"] = "<%s>" % self.message_id.strip(' <>\r\n') ``` it will avoid this issue. I tried this but get the same error, hope I did the modification correctly. [2021-04-30 19:56:31 +0000] [22104] [ERROR] Error handling request Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.7/site-packages/gunicorn/workers/sync.py", line 180, in handle_request for item in respiter: File "/opt/mailman/venv/lib/python3.7/site-packages/hyperkitty/views/mlist.py", line 335, in stream_mbox msg = email.as_message() File "/opt/mailman/venv/lib/python3.7/site-packages/hyperkitty/models/email.py", line 178, in as_message msg["Message-ID"] = "<%s>" % self.message_id.strip(' <>\r\n') File "/usr/lib/python3.7/email/message.py", line 409, in __setitem__ self._headers.append(self.policy.header_store_parse(name, val)) File "/usr/lib/python3.7/email/policy.py", line 145, in header_store_parse raise ValueError("Header values may not contain linefeed " ValueError: Header values may not contain linefeed or carriage return characters Thanks. Andrew.

5 years, 2 months

[MM3-users] Re: Footer variables

by Washington Odhiambo

On Mon, Mar 2, 2026 at 1:56 PM Stephen J. Turnbull <steve(a)turnbull.jp> wrote: > Washington Odhiambo via Mailman-users writes: > > > In my /opt/mailman/mm/var/templates/lists/ > > kictanet.lists.kictanet.or.ke/en/list:member:regular:footer.txt, I > have: > > > > Archived at: ${hyperkitty_url > > First, I assume the unbalanced `{` is a typo. > Yes. That was a typo actually. > Second, I don't think that is correct syntax for this flavor of > template, it's just "$hyperkitty_url". (It might be OK, but this > language is designed for an undelimited reference to the template > variable.) Third, there is no provision for that substitution in footers, as the > substitions are a hard-coded list in the decorate() function in > handlers/decorate.py. It is available in the Archived-At header > field. > I have seen that in the footer for this MM3 users ML for ages. And my MM3 installation is new :) > It wouldn't be hard to add, I suspect, but currently there is no > protocol for an archiver to communicate its archived-at URL to the > decorate function. There are generic callbacks for the Archived-At > and List-Archive header fields, but those are simple lists and don't > allow you to specify the particular archiver as $hyperkitty_url. > How did @Mark Sapiro <mark(a)msapiro.net> add the footer to mailman-users(a)mailman3.org? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

4 months, 3 weeks

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

by Abhilash Raj

Excerpts from Simon Liebold via Mailman-users's message of May 29, 2017 2:16 pm: > Am 28.05.2017 um 22:24 schrieb Mark Sapiro: >> 'Delete this message' is in the 'message' view. "Delete this thread" is >> in the 'thread' view. > > Now found the message view. Thanks. > >> HyperKitty requires Django<1.11. The comment in the requirements in >> setup.py implies this is only a django-haystack requirement >> >> "Django>=1.8", >> # Don't upgrade to 1.11 until django-haystack supports it: >> # https://github.com/django-haystack/django-haystack/pull/1499 >> "Django<1.11", >> >> but since it works for me with Django 1.10, you might want to try that. > > OK, I was still running an RC version. Silly me. > >> In particular, this looks like Django 1.11 bug >> <https://code.djangoproject.com/ticket/27975>. > > Which was closed in the release version that I initially upgraded to > (1.11.1). > > 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") > You may have to do `python manage.py makemigrations` after adding a new INSTALLED_APPLICATIONS and before running `python manage.py migrate` Hope that helps! -- thanks, Abhilash Raj

9 years, 1 month

[MM3-users] Re: FILTER_VHOST fix - was: Postorius & multi domain

by Gelpi Andrea

Il 23/04/20 19:02, Mark Sapiro ha scritto: > On 4/23/20 2:48 AM, Gelpi Andrea wrote: >> >> I saw the change in the file. >> >> As I'm not a programmer How can I test your fix? >> >> My system was installed via Debian 10 stable repository. >> >> I upgrade with testing repository postorius, django and mailmanclinet >> >> Postorius V 1.3.2 >> Django V. 2.2.12 >> Django filters V 2.1.0 >> Djanog mailman V 1.3.2 >> mailmanclient V 3.3.0 > > > I don't know where the Debian package puts things, but you have to find > the location of postorius/views/list.py. Something like > > locate views/list.py > > should find it. Then you need to download > <https://gitlab.com/mailman/postorius/-/merge_requests/500.diff> and > edit it to remove the first 15 lines so the first remaining line is the > > diff --git a/src/postorius/views/list.py b/src/postorius/views/list.py > > line. Then make a backup copy of postorius/views/list.py and run the command > > patch postorius/views/list.py path/to/500.diff > > where postorius/views/list.py is actually the full path to > postorius/views/list.py and 500.diff is the edited file you downloaded. > > Then restart uWSGI. If anything goes wrong, restore your backup copy of > postorius/views/list.py and restart uWSGI. > > I can confirm that the fix works. Thank You so much. -- Gelpi ing. Andrea ************************************************** I documenti vitali dimostreranno la loro vitalita' spostandosi spontaneamente da dove li avevate lasciati a dove non riuscirete a trovarli. **************************************************

6 years, 3 months

Search results for query "sapiro"